Is it just me, or have cron jobs stopped? One I added last week worked fine till this morning. I don’t get email reports and the job isn’t kicking off the twitter post it’s supposed to. The last successful run was 7:57 am and it’s now 3:09…it missed 7 runs since then.
Here’s the command it’s running:
/usr/bin/wget -o/dev/null -O- http://example.com/myscript.php
Thanks,
Tim
would be good to list which server, seems odd if it ran this morning that it would be upgrade related.
Okay, I don’t recall now why I set it up this way. The cron job is on web3 (Linux) but the script is on wincf. The script could actually live on the site on web3. I’ll change that. But, I ran the script directly and find that it can’t access libcurl. The php.ini must have changed on wincf. I’ll submit a ticket because this means my own site and a couple of my customers are throwing a library-load error. X(
Tim
Ah yes, now I recall. The script uses libcurl to send out the announcement to twitter. I couldn’t figure out how to enable that php extension on web3 (htaccess syntax always throws me for a loop) but I could on wincf (php.ini syntax is easier). So, I put the script on the windows server.
Maybe some Apache expert could post the htaccess syntax for enabling an extension so that I could put this script where it belongs? (libcurl and openssl is what i need)
Thanks,
Tim
can you check and confirm if working on the wincf side now?
Yes, it is back to working. So this wasn’t a problem with a different php.ini or something like that?
Tim
bah, the problem was more along the lines of parallels insistence to remove the old path for php, which we were manually adding back (it wasn’t causing the problems)
I added it back after they had removed it again.
they moved it to c:\hpshere.net\3rdparty\php\phpsubversion\path last time
now they moved it to c:\program files\hpshere\3rd party\php\phpversion
Cool. I’m glad it’s working again. The cron-managed twitter app is a bit of a frivolity. (My weather station sends out hourly tweets with current conditions.) But the failure of loading curl was also affecting a client’s ecommerce app. They hadn’t called yet, which is nice for once. So, thank you for fixing this!
Tim