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?option=com_community&task=cron I have other similar cron jobs but they run fine.
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/I...-part-2?utm_source=dlvr.it&utm_medium=twitter I added the new lines of htaccess code from that article.
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?
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.
You mean these messages? That seems to be an attacker and has nothing to do with your cron jobs or PHP version.
Ater I removed my changes to the htaccess file the cronjob worked once but now it has stopped working again.