Results 1 to 2 of 2

Thread: Logged Scheudler inbound email errors

  1. #1
    vstokesjr is offline Senior Member
    Join Date
    Dec 2009
    Posts
    33

    Default SCHEDULER not getting email - log show error

    OS: Linux
    Apache: 1.3.41
    PHP: 5.2.5
    Sugar: 5.5.0

    We created an inbound group email from the Admin panel. The configuration works fine - that is - when we test the connection it works. However, we are getting repeated error entries in the sugar log:

    Tue Dec 22 07:30:13 2009 [3689][1][FATAL] SCHEDULERS: could not get an IMAP connection resource for ID [ cc9e497c-1a48-e5fb-1dbc-4b2ab84ea976 ]. Skipping mailbox [ Registrations ].
    It appears the problem is in the scheduler. If I create a personal inbound mailbox with the same credentials it works fine.

    Any hints?
    Last edited by vstokesjr; 2009-12-22 at 04:19 PM. Reason: spelling and title

  2. #2
    vstokesjr is offline Senior Member
    Join Date
    Dec 2009
    Posts
    33

    Default Re: Logged Scheudler inbound email errors

    I found this thread:
    http://www.sugarcrm.com/forums/showt...t=31923&page=2

    Most important:

    Quote Originally Posted by commshop
    Below are more details regarding the Wget approach.

    In the SugarOpenSource_AdminGuide_4.5.pdf I found the following:

    2. No PHP binary found or it is broken.
    􀁼 Change the mechanism by which your cronjob calls Sugar's cron.php.
    􀁺 Determine if this is an option at this time by finding either “curl” or “wget” on your system. This is done with the commands “which curl” and “which wget”.

    If you use cURL, your crontab entry should look as follows:
    * * * * * curl --silent http://yourdomain/yoursugarcrminstance/cron.php

    If you use wget, your crontab entry should look like:
    * * * * * wget -q http://yourdomain/yoursugarcrminstance/cron.php

    Note: Both curl and wget have numerous switches that do not always map to
    different versions on different platforms. Experiment in the terminal until
    you find the “perfect” line, and add it as the line for your crontab entry.
    We used the curl method and that appears to have fixed our problem.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 1
    Last Post: 2009-04-22, 09:00 PM
  2. Errors Logged - campaign mail
    By along in forum Help
    Replies: 2
    Last Post: 2009-03-30, 02:51 PM
  3. Replies: 8
    Last Post: 2008-12-04, 08:07 PM
  4. Replies: 3
    Last Post: 2008-04-09, 11:59 AM
  5. Inbound Email/Group Email - Assign option after viewing
    By malcolmh in forum Feature Requests
    Replies: 2
    Last Post: 2006-10-09, 08:21 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •