I am trying to track down an issue with a cURL call in PHP. It works fine in our test environment, but not in our production environment. When I try to execute the cURL function, it just hangs and never ever responds. I have tried making a cURL connection from the command line and the same thing happens.
I'm wondering if cURL logs what is happening somewhere, because I can't figure out what is happening during the time the command is churning and churning. Does anyone know if there is a log that tracks what is happening there?
I think it is connectivity issues, but our IT guy insists I should be able to access it without a problem. Any ideas? I'm running CentOS and PHP 5.1.
Updates: Using verbose mode, I've gotten an error 28 "Connect() Timed Out". I tried extending the timeout to 100 seconds, and limiting the max-redirs to 5, no change. I tried pinging the box, and also got a timeout. So I'm going to present this back to IT and see if they will look at it again. Thanks for all the help, hopefully I'll be back in a half-hour with news that it was their problem.
Update 2: Turns out my box was resolving the server name with the external IP address. When IT gave me the internal IP address and I replaced it in the cURL call, everything worked great. Thanks for all the help everybody.
UDP sockets in ad hoc network (Ubuntu 9.10)
1:How do I manage a Python based daemon on Linux?
This then logs to STDERR, or to the file specified using
curl_setopt($curl, CURLOPT_VERBOSE, TRUE);
CURLOPT_STDERR(which takes a file pointer):. How to properly set URL rewrite rules for a php script to only accept POST
From the command line, you must use the following switches:. Parsing line with delimiter in Python
curl_setopt($curl, CURLOPT_STDERR, $fp);
--verboseto report more info to the command line
--trace-ascii <file>to trace to a file
--trace-timeto prepend time stamps to verbose/file outputs. How to restart C daemon program in Linux after receiving SIGHUP signal
sudoing as the user PHP runs under (possibly the one Apache runs under). . The
curlproblem could have various reasons this require a user input, for case an untrusted certificate this is stored in the trusted certificates cache of the root user, although not the PHP one. In this case, the command would be waiting for an input this never happens.. Update: This applies only if you run curl externally using
exec- maybe it doesn't apply..