HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=27)
-   -   Cron job has stopped working (http://www.howtoforge.com/forums/showthread.php?t=58313)

erkan 19th August 2012 17:24

Cron job has stopped working
 
Hi

This is strange. One och my cron jobs have stopped working. I have severall and in my logs on my site I can see them running when they should but one of them isnīt running at all now.

It stopped runnig yesterday after updated my server to the latest PHP and MySql version. PHP 5.3.16 and MySql 5.5.27.

I have ISPConfig 3.0.4.6.

The cron job in question is a URL cron job, the URL is:

http://www.fotoforalla.se/index.php?...nity&task=cron

I have other similar cron jobs but they run fine.

till 19th August 2012 17:55

Please take a look into the file /var/log/syslog and search for cron errors.

erkan 19th August 2012 18:03

Yes there are severall pages with this:

Aug 19 17:55:01 d64 /USR/SBIN/CRON[17714]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Aug 19 17:55:01 d64 /USR/SBIN/CRON[17715]: (getmail) CMD (/usr/local/bin/run-getmail.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Aug 19 17:55:01 d64 pure-ftpd: (?@::1) [INFO] New connection from ::1
Aug 19 17:55:01 d64 pure-ftpd: (?@::1) [INFO] Logout.
Aug 19 17:55:01 d64 imapd: Connection, ip=[::1]
Aug 19 17:55:01 d64 imapd: Disconnected, ip=[::1], time=0
Aug 19 17:55:01 d64 pop3d: Connection, ip=[::1]
Aug 19 17:55:01 d64 pop3d: Disconnected, ip=[::1]
Aug 19 17:55:01 d64 postfix/smtpd[17780]: connect from localhost.localdomain[127.0.0.1]
Aug 19 17:55:01 d64 postfix/smtpd[17780]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Aug 19 17:55:01 d64 postfix/smtpd[17780]: disconnect from localhost.localdomain[127.0.0.1]
Aug 19 17:55:15 d64 suhosin[9423]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '66.249.72.115', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:55:36 d64 suhosin[20407]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '66.249.72.115', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:55:40 d64 suhosin[20407]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '66.249.73.18', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:55:48 d64 suhosin[15387]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '66.249.66.134', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:55:53 d64 suhosin[15387]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '66.249.66.134', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:56:01 d64 /USR/SBIN/CRON[19560]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Aug 19 17:56:38 d64 suhosin[9423]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '74.125.78.83', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:56:59 d64 suhosin[20407]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '66.249.66.134', file '/var/www/fotoforalla.se/web/index.php')
Aug 19 17:57:01 d64 /USR/SBIN/CRON[20247]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Aug 19 17:57:11 d64 suhosin[15387]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '87.227.67.23', file '/var/www/fotoforalla.se/web/index.php')

Could this have something to do with that I edited my Joomla htaccess file after reading this:

http://magazine.joomla.org/issues/Is...medium=twitter

I added the new lines of htaccess code from that article.

till 19th August 2012 20:33

Quote:

Could this have something to do with that I edited my Joomla htaccess file after reading this:
Yes, this can be the case. You should undo the changes and then test the cronjob again.

erkan 19th August 2012 21:09

No it didnīt work, the cron job still doesnīt work and I still get the same error messages in my log.

Could it be some problem with ISPConfig och PHP 5.3.16?

erkan 19th August 2012 21:12

Or wait, the cron job seems to work now, but I still get the same error messages in my log, it is still the same messages but there are new ones every minute.

falko 20th August 2012 10:39

You mean these messages?
Quote:

Aug 19 17:57:11 d64 suhosin[15387]: ALERT - script tried to increase memory_limit to 2147483648 bytes which is above the allowed value (attacker '87.227.67.23', file '/var/www/fotoforalla.se/web/index.php')
That seems to be an attacker and has nothing to do with your cron jobs or PHP version.

erkan 20th August 2012 10:55

Ok I see, is there something I can do about that or should I just leave it?

erkan 20th August 2012 12:41

Ater I removed my changes to the htaccess file the cronjob worked once but now it has stopped working again.

falko 21st August 2012 13:57

Can you post your cron job here?

Are there any cron errors in your logs?


All times are GMT +2. The time now is 20:00.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.