Hi,I've upgraded my OSTICKET to v1.8.0.1.After doing so CRON.PHP is unable to pull emails from my POp3 mail server.OSTicket pulls emails just fine if I run itself, but when using CRON.PHP all I get is a message returned  kwaheri rafiki!This all worked perfectly until I upgraded to v1.8.0.1Anyone have any ideas where I should look? I've taken a good browse at this forum but to no avail.Kindest Regards in advancePhil B

FYI,PHP version 5.4.12

f1lby I am seeing this exact same issue. Seems we are not alone. Here is the thread I have been involved with;http://forum.osticket.com/d/discussion//system-not-fetching-tickets-since-upgrade#latestIt appears the only thing that is triggering the email function is the 300 screen refresh on the browser sessions.

f1lby 

I am seeing this exact same issue. Seems we are not alone. Here is the thread I have been involved with;http://forum.osticket.com/d/discussion//system-not-fetching-tickets-since-upgrade#latest

It appears the only thing that is triggering the email function is the 300 screen refresh on the browser sessions.

Hi gkinney,Yep, that's exactly what I'm encountering too. The browser triggers the pickup of mail fine, but CRON.PHP fails miserably. :-(I tried to use a 1.7 version of CRON.PHP in place of the 1.8 version, but that didn't help.If I find any solution I'll post my findings here.Best Regards

f1lby  I am seeing this exact same issue. Seems we are not alone. Here is the thread I have been involved with;http://forum.osticket.com/d/discussion//system-not-fetching-tickets-since-upgrade#latest It appears the only thing that is triggering the email function is the 300 screen refresh on the browser sessions.

Hi gkinney,

Yep, that's exactly what I'm encountering too. The browser triggers the pickup of mail fine, but CRON.PHP fails miserably. :-(

I tried to use a 1.7 version of CRON.PHP in place of the 1.8 version, but that didn't help.

If I find any solution I'll post my findings here.

Best Regards

Thanks! I will do the same!

12 days later

Hey guys,maybe i can help youwe did find that when our host put shell permissions down to chrooted the cron would run their end, but would not run on the site. so to them it looks like it ran and to me it didnt, setting more laxed permission on shell worked. (Bash shell)In cron star everything, but in the minute put */1 so it runs every minute. just putting in 1 will run it once every hour.you can also test it by putting in this line in the cron.php to see if you get an email when the cron job runs. put it at the top of the php file.mail('yourmail@your email.com.au','Cron Test A1','Test');if you get an email, cron.php is actually running.another test is turn on debugging in> settings >default log level.then everytime cron.php is run, in > Dashboard > system logs it shows cron has run every minute.Finally the last thing i can tell you is the line which cron had to run, this is what i personally had to use:/usr/bin/php /var/www/vhosts/***********.com.au/httpdocs/support/api/cron.php

7 days later

**RESOLVED**Well upgraded my broken 1.8.0.1 to 1.8.0.2 and the

cron.php that didn't work now works fine. Looks like something has been

fixed!So upgrade to 1.8.0.2 and all should be OK.:-D

Great!  I'm glad that you're fixed.  I'll close this thread since your resolved but please feel free to post again should you encounter any other issues.

Write a Reply...