#21653 [Com]: Warning: fsockopen() [function.fsockopen]: php_hostconnect: connect failed

[laudanp at yahoo dot com]

ID: 21653
Comment by: laudanp at yahoo dot com
Reported By: support at hostcolor dot com
Status: Closed
Bug Type: Sockets related
Operating System: RedHat 7.2
PHP Version: 4.3.3RC2-dev
New Comment:

HI folks, welcome back. So, what is the status? Those errors are
still there.


Previous Comments:
------------------------------------------------------------------------

[2003-07-05 12:32:46] laudanp at yahoo dot com

Well its Independence weekend in the USA today, so its party time.
Hopefully next week we can all get back to business. Happy Fourth all.

------------------------------------------------------------------------

[2003-07-04 10:40:09] developer at yecc dot net

HI ALL
I download php 5 and install it on my computer that have RH7.3 But
socket connection warning exists on php 5.
What I must do?
Developers of php what you do?
Are you ok?

------------------------------------------------------------------------

[2003-07-01 09:16:47] larry at bowenaero dot com

I'm also seeing this problem with SquirellMail 1.4.0 since my host
upgraded to 4.3.2. SM worked flawlessly before the upgrade. The
problem surfaces frequently, but with no obvious pattern.

[url]http://BowenAero.com/p.php[/url]

Any help is appreciated.

-LB

------------------------------------------------------------------------

[2003-07-01 06:38:08] laudanp at yahoo dot com

Ok, I disabled any port blocking on my end this morning, and as it
turns out I get the same messages as when port blocking was on:

Warning: fsockopen(): unable to connect to xxx.xxx.xxx.xxx:21 in
/var/www/html/testpaul.php on line 134
Connection Refused: Port 21 used by Nerte 7.8.1.

This is odd indeed.

------------------------------------------------------------------------

[2003-06-30 08:27:35] laudanp at yahoo dot com

CORRECTION TO THIS:

So something is different between the TCP and UDP connections. Now,
I'm
running these scans from a box that is dropping the probes. Hence,
since UDP is connectionless and TCP is connection oriented, the bug
may
have something to do with this? I haven't tested it on a system that
is
not running a firewall recently. What do your tests show now with the
current snapshot?

------------

CORRECTED VERSION:

*... Now, I'm running these scans from the server against a system that
is dropping the probes via a firewall. ... I haven't tested it on a
system that is not protected by a firewall (or disabled it). What do
your tests show now with the current snapshot? ...*

-----

Thanks

------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]

[laudanp at yahoo dot com]

ID: 21653
Comment by: laudanp at yahoo dot com
Reported By: support at hostcolor dot com
Status: Feedback
Bug Type: Sockets related
Operating System: RedHat 7.2
PHP Version: 4.3.3RC2-dev
New Comment:

Each "ports are filtered or open" line is with respect to the client PC
(target PC), and not the server that PHP is installed.

Scenario A:

- ports are filtered (closed or stealth)
- PHP 4.2.3 is installed

Scenario B:

- ports are open
- PHP 4.2.3 is installed

Scenario C:

- ports are filtered (closed or stealth)
- PHP 4.3.x is installed

Scenario D:

- ports are open
- PHP 4.3.x is installed

Ok, under both Scenario A and B, no "fsockopen()..." error is
generated.

Under both Scenario C and D, the "fsockopen()..." error is displayed.

Clearly what worked 100% of the time in 4.2.3, no longer functions in
4.3.x. This has been an ongoing issue for several months now.


Previous Comments:
------------------------------------------------------------------------

[2003-07-10 11:41:03] [email]sniper@php.net[/email]

This is propably stupid question..but why shouldn't fsockopen() give an
error when it fails to connect???
Obviously that's what is happening here?


------------------------------------------------------------------------

[2003-07-10 02:51:25] support at hostcolor dot com

I am not the original submitter of the bug but I was contacted by mr.
Paul Laudanski and also by seeing the number of comments it seems that
the problem is still there. We certainly found no solution as nothing
else but reverting to 4.2.3 helped.
best regards and good luck

------------------------------------------------------------------------

[2003-07-09 09:21:01] laudanp at yahoo dot com

HI folks, welcome back. So, what is the status? Those errors are
still there.

------------------------------------------------------------------------

[2003-07-01 06:38:08] laudanp at yahoo dot com

Ok, I disabled any port blocking on my end this morning, and as it
turns out I get the same messages as when port blocking was on:

Warning: fsockopen(): unable to connect to xxx.xxx.xxx.xxx:21 in
/var/www/html/testpaul.php on line 134
Connection Refused: Port 21 used by Nerte 7.8.1.

This is odd indeed.

------------------------------------------------------------------------

[2003-06-30 08:27:35] laudanp at yahoo dot com

CORRECTION TO THIS:

So something is different between the TCP and UDP connections. Now,
I'm
running these scans from a box that is dropping the probes. Hence,
since UDP is connectionless and TCP is connection oriented, the bug
may
have something to do with this? I haven't tested it on a system that
is
not running a firewall recently. What do your tests show now with the
current snapshot?

------------

CORRECTED VERSION:

*... Now, I'm running these scans from the server against a system that
is dropping the probes via a firewall. ... I haven't tested it on a
system that is not protected by a firewall (or disabled it). What do
your tests show now with the current snapshot? ...*

-----

Thanks

------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]

[laudanp at yahoo dot com]

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.3RC2-dev
New Comment:

Hi I provided the feedback above, I'm still having those problems.
Help


Previous Comments:
------------------------------------------------------------------------

[2003-07-18 18:53:18] [email]sniper@php.net[/email]

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.

No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result.



------------------------------------------------------------------------

[2003-07-10 14:53:49] laudanp at yahoo dot com

In addition, I'm not sure why the error would continue even after
wez...

"[22 Jun 5:11am CDT] [email]wez@php.net[/email]
When I visited your test page, it seemed to be working; the port-scans
triggered my port-sentry and that dropped the route to your machine.
So the only "problem" is that you see two separate error messages?
I've removed a redundant message from the stable branch.

"

------------------------------------------------------------------------

[2003-07-10 14:53:00] laudanp at yahoo dot com

In addition, the [url]http://64.246.34.44/[/url] address I listed just above is no
longer in use. You can refer back to the original
[url]http://computercops.biz[/url] links way above.

Thanks

------------------------------------------------------------------------

[2003-07-10 14:51:31] laudanp at yahoo dot com

Each "ports are filtered or open" line is with respect to the client PC
(target PC), and not the server that PHP is installed.

Scenario A:

- ports are filtered (closed or stealth)
- PHP 4.2.3 is installed

Scenario B:

- ports are open
- PHP 4.2.3 is installed

Scenario C:

- ports are filtered (closed or stealth)
- PHP 4.3.x is installed

Scenario D:

- ports are open
- PHP 4.3.x is installed

Ok, under both Scenario A and B, no "fsockopen()..." error is
generated.

Under both Scenario C and D, the "fsockopen()..." error is displayed.

Clearly what worked 100% of the time in 4.2.3, no longer functions in
4.3.x. This has been an ongoing issue for several months now.

------------------------------------------------------------------------

[2003-07-10 11:41:03] [email]sniper@php.net[/email]

This is propably stupid question..but why shouldn't fsockopen() give an
error when it fails to connect???
Obviously that's what is happening here?


------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]

[laudanp at yahoo dot com]

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.3RC2-dev
New Comment:

re: "No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result."

Thanks for replying to me. I'll go ahead and open a new ticket while
referencing this one for posterity. Look for it tonight.


Previous Comments:
------------------------------------------------------------------------

[2003-07-23 14:31:25] laudanp at yahoo dot com

Hi I provided the feedback above, I'm still having those problems.
Help

------------------------------------------------------------------------

[2003-07-18 18:53:18] [email]sniper@php.net[/email]

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.

No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result.



------------------------------------------------------------------------

[2003-07-10 14:53:49] laudanp at yahoo dot com

In addition, I'm not sure why the error would continue even after
wez...

"[22 Jun 5:11am CDT] [email]wez@php.net[/email]
When I visited your test page, it seemed to be working; the port-scans
triggered my port-sentry and that dropped the route to your machine.
So the only "problem" is that you see two separate error messages?
I've removed a redundant message from the stable branch.

"

------------------------------------------------------------------------

[2003-07-10 14:53:00] laudanp at yahoo dot com

In addition, the [url]http://64.246.34.44/[/url] address I listed just above is no
longer in use. You can refer back to the original
[url]http://computercops.biz[/url] links way above.

Thanks

------------------------------------------------------------------------

[2003-07-10 14:51:31] laudanp at yahoo dot com

Each "ports are filtered or open" line is with respect to the client PC
(target PC), and not the server that PHP is installed.

Scenario A:

- ports are filtered (closed or stealth)
- PHP 4.2.3 is installed

Scenario B:

- ports are open
- PHP 4.2.3 is installed

Scenario C:

- ports are filtered (closed or stealth)
- PHP 4.3.x is installed

Scenario D:

- ports are open
- PHP 4.3.x is installed

Ok, under both Scenario A and B, no "fsockopen()..." error is
generated.

Under both Scenario C and D, the "fsockopen()..." error is displayed.

Clearly what worked 100% of the time in 4.2.3, no longer functions in
4.3.x. This has been an ongoing issue for several months now.

------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]

[laudanp at yahoo dot com]

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.3RC2-dev
New Comment:

I opened a new bug report here:

[url]http://bugs.php.net/bug.php?id=24785[/url]


Previous Comments:
------------------------------------------------------------------------

[2003-07-23 14:44:48] laudanp at yahoo dot com

re: "No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result."

Thanks for replying to me. I'll go ahead and open a new ticket while
referencing this one for posterity. Look for it tonight.

------------------------------------------------------------------------

[2003-07-23 14:31:25] laudanp at yahoo dot com

Hi I provided the feedback above, I'm still having those problems.
Help

------------------------------------------------------------------------

[2003-07-18 18:53:18] [email]sniper@php.net[/email]

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.

No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result.



------------------------------------------------------------------------

[2003-07-10 14:53:49] laudanp at yahoo dot com

In addition, I'm not sure why the error would continue even after
wez...

"[22 Jun 5:11am CDT] [email]wez@php.net[/email]
When I visited your test page, it seemed to be working; the port-scans
triggered my port-sentry and that dropped the route to your machine.
So the only "problem" is that you see two separate error messages?
I've removed a redundant message from the stable branch.

"

------------------------------------------------------------------------

[2003-07-10 14:53:00] laudanp at yahoo dot com

In addition, the [url]http://64.246.34.44/[/url] address I listed just above is no
longer in use. You can refer back to the original
[url]http://computercops.biz[/url] links way above.

Thanks

------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]

[phpbugs at whitesands dot net]

ID: 21653
Comment by: phpbugs at whitesands dot net
Reported By: support at hostcolor dot com
Status: No Feedback
Bug Type: Sockets related
Operating System: RedHat 7.2
PHP Version: 4.3.3RC2-dev
New Comment:

I'm getting the same "Operation now in progress (115)" w/ PHP 4.4.2
configured with:

'./configure' '--with-mysql=/usr' '--with-apxs2=/usr/local/bin/apxs'
'--enable-mbstring'

and using Apache 2.0.59 on RHEL 4 and using this script:

<?php
$fp = fsockopen ("localhost", 80, $errno, $errstr, 30);
if (!$fp) {
echo "$errstr ($errno)<br>\n";
}
fclose ($fp);
?>

What I have been able to figure out is that if I have less that ~500
virtual domains in the httpd.conf file, the problem goes away. If I
have more, the problem comes back. Am I hitting some kind of resource
limit?


Previous Comments:
------------------------------------------------------------------------

[2006-06-28 09:08:42] sosingus at yahoo dot com

I have a similar problem using php 4.4.1 with pfsockopen
Part of code:
------------------
<?php
$fp = pfsockopen("ssl://example.com", 443, $errno, $errstr);
if (!$fp){
echo "$errstr ($errno)<br>\n";
exit;
}
?>
Output:
------------------
Operation now in progress (115)

Modules:
------------------
'./configure' '--with-gd' '--with-msql=/usr/local/msql2.0'
'--with-mysql=/usr/local/mysql' '--with-apache=../apache_1.3.34'
'--with-jpeg-dir=/usr/lib' '--with-png-dir=/usr/lib' '--with-mhash'
'--with-openssl=/usr/local/ssl' '--enable-ftp' '--enable-imap'
'--with-zlib-dir=/usr/local/lib' '--with-pear'
'--with-curl=/usr/local/lib' '--with-pear=../PEAR-1.1'
'--enable-mbstring=all' '--with-dom=/usr/local'
'--with-domxml=/usr/local' '--enable-memory-limit=yes'
'--enable-sockets' '--with-gd-native-ttf' '--enable-gd-imgstrttf'
'--with-freetype-dir=/usr/local' '--enable-shared'
'--with-expat-dir=/usr/local' '--with-dom-xslt=/usr/local'
'--with-xslt-sablot'

Additional info
--------------------
I have it working on another domain and server with php 4.3.4

------------------------------------------------------------------------

[2005-01-05 12:50:42] suhailc at gmail dot com

Hi,

I get the following error:

Warning: fsockopen(): unable to connect to whois.crsnic.net:43 in
/home/ecompco/public_html/test.php on line 2
Could not open connection

However, the connection is made perfectly and fast when I switch off
APF. I get:

Connected OK.

For the life of me I cannot figure out why - I've added ports 43, 443,
4343, 80 to conf.php but still error shows when APF is on. But it does
have something to do with APF.

Regards,
Suhail.

------------------------------------------------------------------------

[2003-07-23 21:16:30] laudanp at yahoo dot com

I opened a new bug report here:

[url]http://bugs.php.net/bug.php?id=24785[/url]

------------------------------------------------------------------------

[2003-07-23 14:44:48] laudanp at yahoo dot com

re: "No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result."

Thanks for replying to me. I'll go ahead and open a new ticket while
referencing this one for posterity. Look for it tonight.

------------------------------------------------------------------------

[2003-07-23 14:31:25] laudanp at yahoo dot com

Hi I provided the feedback above, I'm still having those problems.
Help

------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]

[blah at mailinator dot com]

ID: 21653
Comment by: blah at mailinator 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.3RC2-dev
New Comment:

I have the same problem with Mac OS X 10.4.8 and PHP 5.2.
Unix sockets on the same machine work OK. Same code with TCP/IP socket
fails with "Operation now in progress".


Previous Comments:
------------------------------------------------------------------------

[2006-09-27 20:24:52] phpbugs at whitesands dot net

I'm getting the same "Operation now in progress (115)" w/ PHP 4.4.2
configured with:

'./configure' '--with-mysql=/usr' '--with-apxs2=/usr/local/bin/apxs'
'--enable-mbstring'

and using Apache 2.0.59 on RHEL 4 and using this script:

<?php
$fp = fsockopen ("localhost", 80, $errno, $errstr, 30);
if (!$fp) {
echo "$errstr ($errno)<br>\n";
}
fclose ($fp);
?>

What I have been able to figure out is that if I have less that ~500
virtual domains in the httpd.conf file, the problem goes away. If I
have more, the problem comes back. Am I hitting some kind of resource
limit?

------------------------------------------------------------------------

[2006-06-28 09:08:42] sosingus at yahoo dot com

I have a similar problem using php 4.4.1 with pfsockopen
Part of code:
------------------
<?php
$fp = pfsockopen("ssl://example.com", 443, $errno, $errstr);
if (!$fp){
echo "$errstr ($errno)<br>\n";
exit;
}
?>
Output:
------------------
Operation now in progress (115)

Modules:
------------------
'./configure' '--with-gd' '--with-msql=/usr/local/msql2.0'
'--with-mysql=/usr/local/mysql' '--with-apache=../apache_1.3.34'
'--with-jpeg-dir=/usr/lib' '--with-png-dir=/usr/lib' '--with-mhash'
'--with-openssl=/usr/local/ssl' '--enable-ftp' '--enable-imap'
'--with-zlib-dir=/usr/local/lib' '--with-pear'
'--with-curl=/usr/local/lib' '--with-pear=../PEAR-1.1'
'--enable-mbstring=all' '--with-dom=/usr/local'
'--with-domxml=/usr/local' '--enable-memory-limit=yes'
'--enable-sockets' '--with-gd-native-ttf' '--enable-gd-imgstrttf'
'--with-freetype-dir=/usr/local' '--enable-shared'
'--with-expat-dir=/usr/local' '--with-dom-xslt=/usr/local'
'--with-xslt-sablot'

Additional info
--------------------
I have it working on another domain and server with php 4.3.4

------------------------------------------------------------------------

[2005-01-05 12:50:42] suhailc at gmail dot com

Hi,

I get the following error:

Warning: fsockopen(): unable to connect to whois.crsnic.net:43 in
/home/ecompco/public_html/test.php on line 2
Could not open connection

However, the connection is made perfectly and fast when I switch off
APF. I get:

Connected OK.

For the life of me I cannot figure out why - I've added ports 43, 443,
4343, 80 to conf.php but still error shows when APF is on. But it does
have something to do with APF.

Regards,
Suhail.

------------------------------------------------------------------------

[2003-07-23 21:16:30] laudanp at yahoo dot com

I opened a new bug report here:

[url]http://bugs.php.net/bug.php?id=24785[/url]

------------------------------------------------------------------------

[2003-07-23 14:44:48] laudanp at yahoo dot com

re: "No feedback from original bug submitter.
laudanp at yahoo dot com:
If you still feel this is a bug, open new report with
short example script, expected result and got result."

Thanks for replying to me. I'll go ahead and open a new ticket while
referencing this one for posterity. Look for it tonight.

------------------------------------------------------------------------

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
[url]http://bugs.php.net/21653[/url]

--
Edit this bug report at [url]http://bugs.php.net/?id=21653&edit=1[/url]