I've been running LiteSpeed for a few months now, but just tracked two problems down to something in the LiteSpeed/LSPHP configuration & I'm hoping to get advice.
We're running LS 4.1.4, and all our web sites configurations are generated from our old apache files.
fsockopen
The first problem is that fsockopen seems to no longer be working.
Here's my simple test:
And here's my result:
So, name resolution is fine, but for some reason the fsockopen fails.
(The 2nd problem is with Curl, but I just realized it might well be result of fsockopen failing, so I'm saving that for the moment.)
Any ideas?
We're running LS 4.1.4, and all our web sites configurations are generated from our old apache files.
fsockopen
The first problem is that fsockopen seems to no longer be working.
Here's my simple test:
<?
echo gethostbyname('www.paypal.com');
$fp = fsockopen ('www.paypal.com', 80, $errno, $errstr, 30);
echo "!! $errno";
echo "!! $errstr";
?>
echo gethostbyname('www.paypal.com');
$fp = fsockopen ('www.paypal.com', 80, $errno, $errstr, 30);
echo "!! $errno";
echo "!! $errstr";
?>
66.211.169.14
Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /var/www/rpgnet/members/test.phtml on line 4
Warning: fsockopen() [function.fsockopen]: unable to connect to www.paypal.com:80 (php_network_getaddresses: getaddrinfo failed: Name or service not known) in /var/www/rpgnet/members/test.phtml on line 4
!! 0!! php_network_getaddresses: getaddrinfo failed: Name or service not known
Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /var/www/rpgnet/members/test.phtml on line 4
Warning: fsockopen() [function.fsockopen]: unable to connect to www.paypal.com:80 (php_network_getaddresses: getaddrinfo failed: Name or service not known) in /var/www/rpgnet/members/test.phtml on line 4
!! 0!! php_network_getaddresses: getaddrinfo failed: Name or service not known
(The 2nd problem is with Curl, but I just realized it might well be result of fsockopen failing, so I'm saving that for the moment.)
Any ideas?