ID: 21653
Comment by: laudanp at yahoo dot com
Reported By: support at hostcolor dot com
Status: No Feedback
Bug Type: Sockets related
Operating System: RedHat 7.2
PHP Version: 4.3.0
New Comment:
My current host has not done this whatsoever, we have obtained another
server with another host. We'll be working on it this week. On the
new server we see the same exact error as on the current server at
computercops.biz. So the new server will have the CVS build
installed.
Cross your fingers. (crossing ours)
Previous Comments:
------------------------------------------------------------------------
[2003-06-03 14:37:29] scmvs at cs dot cf dot ac dot uk
I experience the same problem with fsockopen. Is this ever going to be
fixed? (I am using PHP 4.3.2)
------------------------------------------------------------------------
[2003-05-15 01:02:18] davideturner at hotmail dot com
Warning: fsockopen() [function.fsockopen]: php_hostconnect: connect
failed in /home/xxxxxxxxx/include/EnomInterface_inc.php on line 140
Warning: fsockopen() [function.fsockopen]: unable to connect to
resellertest.enom.com:80 in
/home/xxxxxxxxx/include/EnomInterface_inc.php on line 140
Fatal error: Call to undefined function: strerror() in
/home/xxxxxxxxx/include/EnomInterface_inc.php on line 142
Line 140+
$address = gethostbyname( $host );
// Create a TCP/IP socket.
$socket = fsockopen($host,80);
if ( !$socket ) {
$this->AddError( "socket() failed: " . strerror( $socket ) );
------------------------------------------------------------------------
[2003-05-15 00:56:40] davideturner at hotmail dot com
I am receiving the same issue with eNoms app. Worked in 4.2.3 now
receive that error with 4.3.1.
------------------------------------------------------------------------
[2003-05-09 07:25:56] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2003-05-05 13:39:43] laudanp at yahoo dot com
My issue still hasn't been resolved because we still haven't traveled
down your recommended path. Someone at my provider is looking into
this for me.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21653
--
Edit this bug report at http://bugs.php.net/?id=21653&edit=1
