Can't ping pear.php.net

List overview All Threads
Download

newer

older

For those hosting WordPress blogs

Lack of support for xz-compressed...

David Paul

3 Dec 2012 3 Dec '12

11:25 a.m.

Anyone been having difficulties using pear, curl, etc. to other domains lately? I've started getting the following when trying to use PEAR: # pear list-all Connection to `pear.php.net:80' failed: Connection timed out if I try to send a cURL request to the majority of domains I get the same issue (though curl www.google.co.uk is fine)

Attachments:

attachment.html (text/html — 506 bytes)

Show replies by date

jan＠henkins.za.net

3 Dec 3 Dec

11:34 a.m.

Hello David, On 2012-12-03 11:25, David Paul wrote:

...

Anyone been having difficulties using pear, curl, etc. to other domains lately? I've started getting the following when trying to use PEAR: # pear list-all Connection to `pear.php.net:80 [1]' failed: Connection timed out if I try to send a cURL request to the majority of domains I get the same issue (though curl www.google.co.uk [2] is fine)

Nope, checks out fine on all my Bitfolk VPS domains: ~# pear list-all All packages [Channel pear.php.net]: ==================================== Package Latest Local pear/Auth_HTTP 2.1.8 HTTP authentication pear/Auth 1.6.4 Creating an authentication system. pear/Auth_SASL 1.0.6 1.0.2 Abstraction of various SASL mechanism responses pear/LiveUser 0.16.14 User authentication and permission management framework pear/Auth_PrefManager 1.2.2 Preferences management class pear/Auth_RADIUS 1.0.7 Wrapper Classes for the RADIUS PECL. pear/Auth_PrefManager2 2.0.0dev1 Preferences management class pear/LiveUser_Admin 0.4.0 User authentication and permission management framework pear/Auth_SASL2 0.1.0 Abstraction of various SASL mechanism responses. [...] I use my own BIND instances as resolvers. Regards, Jan Henkins

David Paul

11:54 a.m.

I wonder what I've done wrong then :( On 3 December 2012 11:34, <jan(a)henkins.za.net> wrote:

...

Hello David, On 2012-12-03 11:25, David Paul wrote:

Anyone been having difficulties using pear, curl, etc. to other domains lately? I've started getting the following when trying to use PEAR: # pear list-all Connection to `pear.php.net:80 [1]' failed: Connection timed out if I try to send a cURL request to the majority of domains I get the same issue (though curl www.google.co.uk [2] is fine)

Nope, checks out fine on all my Bitfolk VPS domains: ~# pear list-all All packages [Channel pear.php.net]: ==============================**====== Package Latest Local pear/Auth_HTTP 2.1.8 HTTP authentication pear/Auth 1.6.4 Creating an authentication system. pear/Auth_SASL 1.0.6 1.0.2 Abstraction of various SASL mechanism responses pear/LiveUser 0.16.14 User authentication and permission management framework pear/Auth_PrefManager 1.2.2 Preferences management class pear/Auth_RADIUS 1.0.7 Wrapper Classes for the RADIUS PECL. pear/Auth_PrefManager2 2.0.0dev1 Preferences management class pear/LiveUser_Admin 0.4.0 User authentication and permission management framework pear/Auth_SASL2 0.1.0 Abstraction of various SASL mechanism responses. [...] I use my own BIND instances as resolvers. Regards, Jan Henkins ______________________________**_________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…

David Paul

noon

best I can think of at the minute is that the iptables config has been changed (though this is not something I've ever made changes to!) # iptables -n -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination On 3 December 2012 11:34, <jan(a)henkins.za.net> wrote:

...

Hello David, On 2012-12-03 11:25, David Paul wrote:

Anyone been having difficulties using pear, curl, etc. to other domains lately? I've started getting the following when trying to use PEAR: # pear list-all Connection to `pear.php.net:80 [1]' failed: Connection timed out if I try to send a cURL request to the majority of domains I get the same issue (though curl www.google.co.uk [2] is fine)

jan＠henkins.za.net

12:11 p.m.

On 2012-12-03 12:00, David Paul wrote:

...

This means you do not have *any* active iptables rules at all. I think it's your resolver setup, so please have a look in your /etc/resolv.conf file to see where your queries goes. Here is the content of one of mine: ---start--- # cat /etc/resolv.conf search your.domain.name nameserver 127.0.0.1 nameserver 85.119.80.232 nameserver 85.119.80.233 ---end--- Regards, Jan Henkins

Andy Smith

8:10 p.m.

Hi, On Mon, Dec 03, 2012 at 12:00:40PM +0000, David Paul wrote:

...

best I can think of at the minute is that the iptables config has been changed (though this is not something I've ever made changes to!)

Just to clarify, is this thread about something which you are able to resolve when you set 8.8.8.8 as your resolver, but not when you use the BitFolk default resolvers? If so I would really like to know. Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting

jan＠henkins.za.net

8:19 p.m.

Hello Andy, On 2012-12-03 20:10, Andy Smith wrote:

...

Hi, On Mon, Dec 03, 2012 at 12:00:40PM +0000, David Paul wrote:

best I can think of at the minute is that the iptables config has been changed (though this is not something I've ever made changes to!)

Just to clarify, is this thread about something which you are able to resolve when you set 8.8.8.8 as your resolver, but not when you use the BitFolk default resolvers?

I think that it was mostly finger-trouble, to be honest. Defo from my part! ;-)

...

If so I would really like to know.

Cool, will let you know if there is a genuine problem, at least backed with some useful debug info. Regards, Jan Henkins

David Paul

30 May 30 May

9:03 p.m.

I've finally got round to testing this: # dig @127.0.0.1 pear.php.net ; <<>> DiG 9.7.3 <<>> @127.0.0.1 pear.php.net ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached This is with 8.8.8.8 in the resolv.conf (server's been restarted since I added it too) Interestingly, if I try to ping 8.8.8.8 I can't reach it either. Definitely a peculiarity On 3 December 2012 20:19, <jan(a)henkins.za.net> wrote:

...

Hello Andy, On 2012-12-03 20:10, Andy Smith wrote:

Hi, On Mon, Dec 03, 2012 at 12:00:40PM +0000, David Paul wrote:

best I can think of at the minute is that the iptables config has been changed (though this is not something I've ever made changes to!)

Just to clarify, is this thread about something which you are able to resolve when you set 8.8.8.8 as your resolver, but not when you use the BitFolk default resolvers?

I think that it was mostly finger-trouble, to be honest. Defo from my part! ;-) If so I would really like to know.

Cool, will let you know if there is a genuine problem, at least backed with some useful debug info. Regards, Jan Henkins ______________________________**_________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…

Andy Smith

9:23 p.m.

Hello, Can you remind us what the actual problem is? On Thu, May 30, 2013 at 10:03:40PM +0100, David Paul wrote:

...

Note that if you are using dig to query a nameserver on localhost, /etc/resolv.conf will not be used, so 8.8.8.8 was not used in your above example.

...

Interestingly, if I try to ping 8.8.8.8 I can't reach it either. Definitely a peculiarity

From where? I can: $ ping -c 5 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_req=1 ttl=51 time=9.63 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=51 time=14.2 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=51 time=41.2 ms 64 bytes from 8.8.8.8: icmp_req=4 ttl=51 time=30.1 ms 64 bytes from 8.8.8.8: icmp_req=5 ttl=51 time=35.4 ms --- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4219ms rtt min/avg/max/mdev = 9.639/26.136/41.282/12.214 ms $ mtr -nrc 5 8.8.8.8 HOST: bitfolk.com Loss% Snt Last Avg Best Wrst StDev 1. 85.119.80.16 0.0% 5 0.1 0.2 0.1 0.2 0.0 2. 85.119.80.4 0.0% 5 0.8 0.5 0.4 0.8 0.1 3. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 4. 4.69.139.88 0.0% 5 0.5 0.5 0.4 0.7 0.1 5. 4.69.166.142 0.0% 5 0.4 0.4 0.4 0.5 0.0 6. 212.113.15.186 0.0% 5 0.6 4.8 0.5 19.7 8.4 7. 209.85.255.76 0.0% 5 0.6 0.6 0.5 0.7 0.1 8. 209.85.253.196 0.0% 5 7.2 4.3 0.8 11.9 5.0 9. 209.85.240.28 0.0% 5 6.9 6.9 6.6 7.7 0.5 10. 216.239.49.38 0.0% 5 11.7 10.1 9.7 11.7 0.9 11. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 12. 8.8.8.8 0.0% 5 9.7 9.8 9.7 9.9 0.1 I don't have a problem resolving pear.php.net either, using the BitFolk resolvers: $ dig -t any pear.php.net ; <<>> DiG 9.7.3 <<>> -t any pear.php.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26829 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;pear.php.net. IN ANY ;; ANSWER SECTION: pear.php.net. 300 IN CNAME euk1.php.net. euk1.php.net. 300 IN A 5.77.39.20 ;; Query time: 71 msec ;; SERVER: 85.119.80.232#53(85.119.80.232) ;; WHEN: Thu May 30 21:21:01 2013 ;; MSG SIZE rcvd: 65 So, what is the problem again? Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting

4007

days inactive

4185

days old

users@mailman.bitfolk.com

Manage subscription

8 comments

3 participants

tags (0)

participants (3)

Andy Smith
David Paul
jan＠henkins.za.net