user cron failing after upgrade to PHP 5.5
Hi, I have a cron job that I have run for years. Since upgrading to PHP 5.5 it is failing with the error message Fatal Error Unable to create lock file: Bad file descriptor (9)
In the cron logs I see this entry when the job runs.
The actual cronjob is a php script run by the command
I don't know when the command changed, I'm sure it was originally entered as /usr/bin/php _BUscripts/scriptname.php - but I've tried both and still the same errors. I'm using the PHP 5 Handler suphp and Apache suEXEC is ON.
Nov 19 11:54:01 vps crond[24397]: (xyz) RELOAD (/var/spool/cron/xyz)
Nov 19 11:54:01 vps crond[24397]: (tmp.XXXXrf9rnA) ORPHAN (no passwd entry)The actual cronjob is a php script run by the command
/usr/local/cpanel/bin/cpuwatch 8 php _BUscripts/scriptname.phpI don't know when the command changed, I'm sure it was originally entered as /usr/bin/php _BUscripts/scriptname.php - but I've tried both and still the same errors. I'm using the PHP 5 Handler suphp and Apache suEXEC is ON.
-
I found that the crontab for this user had the SHELL="/usr/local/cpanel/bin/jailshell", when I changed it to SHELL="/bin/bash" the job proceeded without error. I don't see any difference in the packages between this account and others that have the SHELL="/bin/bash" I administer all these accounts, is there any security implication here? 0 -
Hello :) Yes, there is a difference in regards to security. You can review information about jailed shell here: Jailed Shell Access Thank you. 0
Please sign in to leave a comment.
Comments
2 comments