Cron Jobs stopped after a change.

Jorge Soares

• January 20, 2016 15:49

Hi, I have a site hosted in company. I use 11.52.1.3 My Current Cron Jobs is Minute Hour Day Month Weekday Command Actions 1 0 * * * php /home/xxx/public_html/a_php/cnt/myonline_his.php >/dev/null 45 0 * * * php /home/xxx/public_html/a_php/mail/gest_agenda_cron.php >/dev/null In 13/Jan I only change the script of second Job. After this change, the Cron stopped. I contacted ultrasurge.com, and they replied so: " As soon as you seutp a cron job is cpanel it is ready to use and nothing else needs to be done. There is no such thing activating it. " Can you help me in that issue ? Thanks Jorge

• 

  amdbuilder

  • January 21, 2016 02:38

  What happens if you attempt to run the command using shell? Do you get any error messages that might indicate a server problem? You might also try enabling the cron emails to see if they have any additional information.

  0
• 

  Jorge Soares

  • January 21, 2016 10:02

  Because the Cron is stuck, I run everyday the two job commands using shell, and successfully. I made a small program that only changes a field from a table, and I put it in Cron to run 5 minutes later, with no option ">/dev/null". Nothing happened. Cron skips any Jobs Command. Ignore also one Job Command that has not changed for years. I read in other threads, topics such as "crond restart" and " crond service status up/down" ... I wonder if ...

  0
• 

  cPanelMichael

  • January 21, 2016 18:31

  You may need to reach out to your hosting provider again and ask them to verify if the "crond" service is running as it should. Thank you.

  0
• 

  Jorge Soares

  • January 25, 2016 12:47

  Unfortunately the host are not friendly and their response was: "we're all right, that's your problem!" After reading many threads, someone wrote to submit a program xxx.php, with instruction phpinfo(), and see which path was used. I figured out the Host has changed the path from "/home/" to "/home2/". I changed paths and now everything is working. Also I read in those threads to check the file "php.ini" and ".htaccess", and add a simple program (echo 'hello';) to cron, without ">/dev/null 2>&1". This helped. Cheers js

  0
• 

  cPanelMichael

  • January 25, 2016 18:45

  I am happy to see the issue is now resolved. Thank you for updating us with the outcome.

  0

Please sign in to leave a comment.