cURL Script Stopped working

[JoeP]

About two days ago, a script I run with a cron job stopped working. From the limited testing I was able to do it appears the cURL has stopped working. I have a ticket open with BH support, but they are either not paying attention to it, are baffled by it, are overwhelmed by too many open support tickets, or are getting ready for the holiday weekend.
I'm wondering if the fact that There's been a RED status item on the server for the same period might have something to do with it. The "Disk/dev/sdc1 (/home) is at 91%. Could this be the cause for the problem?
Before you slam me... I know this is a user to user forum. I was just hoping that one of you users might have some idea what would cause cURL to fail, and/or might know what symptoms the overloaded resource might cause.
I have tested the url's that my cURL functions use several times and they are valid and responsive. This script ran without incident for months, then just suddenly stopped working sometime during the night of the 27th of August.
Thanks,
joe

[Early Out]

First, the "Disk/dev/sdc1 (/home)" flag simply indicates that the disk drive on that server is 91% full, which is up in the range that usually triggers the BH admins to start moving some accounts to a new server to free up some space. It can't produce any processing errors.

Second, use Live Chat to find out what's going on. Support tickets generally take a few days to get any response - for a more immediate problem like this, Live Chat is the way to go.

[JoeP]

First, the "Disk/dev/sdc1 (/home)" flag simply indicates that the disk drive on that server is 91% full, which is up in the range that usually triggers the BH admins to start moving some accounts to a new server to free up some space. It can't produce any processing errors.

Second, use Live Chat to find out what's going on. Support tickets generally take a few days to get any response - for a more immediate problem like this, Live Chat is the way to go.

I was on live chat for over two hours. They gave up and suggested filing a support ticket.
So far, on this issue, getting a bit frustrated.
joe

[Early Out]

I was on live chat for over two hours. They gave up and suggested filing a support ticket.That's not a good sign. I don't recall seeing that happen any time recently.

They might be running a short staff for the holiday weekend, so if you don't get a satisfactory response by Tuesday, it might be time to steel yourself, and get on Live Chat again. Wish I had some better advice. :(

Maybe the problem will ring a bell with someone else, but this certainly feels like a server problem that won't be fixable from your end.

[siguie]

Are you on Box 314?

My cron jobs all stopped on Aug 12 and I made a post here about it ...
http://forum.bluehost.com/showthread.php?t=14210

Basically it looks like a computer glitch overwrote my cron text and neither Live Help nor some level 2 guy had any clue. :rolleyes:

It might be something similar that happened to you even if it wasn't directly the cron that was effected in your case.

There's a good chance that BH wont be able to figure out what happened but I'd like to keep track of these scripts that stop for no apparent reason :)

[JoeP]

Are you on Box 314?

My cron jobs all stopped on Aug 12 and I made a post here about it ...
http://forum.bluehost.com/showthread.php?t=14210
Basically it looks like a computer glitch overwrote my cron text and neither Live Help nor some level 2 guy had any clue. :rolleyes:
It might be something similar that happened to you even if it wasn't directly the cron that was effected in your case.
There's a good chance that BH wont be able to figure out what happened but I'd like to keep track of these scripts that stop for no apparent reason :)

The problem (my problem) is not that the cron job stopped working, it's that the script that the cron job runs stopped working. I have done some debug and it appears that curl_exec($ch) never executes successfully. I have tried the same script from a different server and it worked fine. So, here's the facts:

The script worked 100% up until the night of 8/27.
The script has failed 100% of the time since the morning of 8/28.
The script fails because curl_exec($ch) never executes successfully.
The script works 100% from a different server.

My conclusion... Something got broken on the bluehost server.

I have filed a new support ticket more specific to the curl problem rather than confusing the issue with cron.
joe

[JoeP]

The problem (my problem) is not that the cron job stopped working, it's that the script that the cron job runs stopped working. I have done some debug and it appears that curl_exec($ch) never executes successfully. I have tried the same script from a different server and it worked fine. So, here's the facts:

The script worked 100% up until the night of 8/27.
The script has failed 100% of the time since the morning of 8/28.
The script fails because curl_exec($ch) never executes successfully.
The script works 100% from a different server.

My conclusion... Something got broken on the bluehost server.

I have filed a new support ticket more specific to the curl problem rather than confusing the issue with cron.
joe

Update:
Support seems to have determined that curl is working in general but not for the port I use for a video server. I have determined that access to the port is not blocked at my end, or by my ISP since I can access the server either directly from a browser, or indirectly via curl running from a different server. My suspicion is that they changed something on the server or a router that is blocking that port.
joe