Ok, I went ahead and `/etc/init.d/nginx restart`ed, so if that is the issue, it has been taken care of.

A `traceroute common-lisp.net` would help here as well if there is still a problem.

-- drewc

On Sun, Dec 8, 2013 at 9:35 AM, Erik Huelsmann ehuels@gmail.com wrote:

Nope. It doesn't. Looks like the http server needs a reset your indeed.

sent from my phone On Dec 8, 2013 6:26 PM, "Anton Vodonosov" avodonosov@yandex.ru wrote:

...

ssh also works fine.

08.12.2013, 21:15, "Anton Vodonosov" avodonosov@yandex.ru:

No specific hours. Right now, and when I posted the previous message, I just enter http://common-lisp.net/, or some static file URL, like http://common-lisp.net/project/cl-test-grid/quicklisp-diff2.html into browser.

The connection times out.

I have tried from two machines in different countries.

Does it work for you?

ping common-lisp.net works OK, so the host is available. It seems like an HTTP server problem.

Best regards,

• Anton

08.12.2013, 17:04, "Erik Huelsmann" ehuels@gmail.com:

Hi,

Thanks for the report. It's a bit generic though. Is it on specific hours or services our can you give any other details? Maybe mtr output to see where the route breaks down?

Erik

sent from my phone On Dec 8, 2013 8:51 AM, "Anton Vodonosov" avodonosov@yandex.ru wrote:

Hello.

http://common-lisp.net/ often does not respond, as well as other URLs on the site.

Ah, I think I see what was going on and fixed it. There seems to be Apache2 running as well, and I had to kill it and make it live again.

So, does it work now?

-- drewc

On Sun, Dec 8, 2013 at 4:52 PM, Anton Vodonosov avodonosov@yandex.ruwrote:

Unfortunately, it happens again

That is quite odd. Can you give me some more details?

-- drewc

On Sun, Dec 8, 2013 at 5:52 PM, Anton Vodonosov avodonosov@yandex.ruwrote:

Unfortunately not, even if I ssh to common-lisp.net and do "wget http://common-lisp.net/" It hangs.

09.12.2013, 05:41, "Drew C" me@drewc.ca:

...

Ah, I think I see what was going on and fixed it. There seems to be

Apache2 running as well, and I had to kill it and make it live again.

...

So, does it work now?

-- drewc

On Sun, Dec 8, 2013 at 4:52 PM, Anton Vodonosov avodonosov@yandex.ru

wrote:

...

...

Unfortunately, it happens again

Can it be that HTTP is server neither by the nginx nor Apache you have tried to restart, but by some other server?

Sorry, I forgot to reply to this!

As it turns out, something was wrong with the switch for the network on the rack that the cl-net server is on. They replaced the switch after it failed completely (?!), and it should work now.

I hope it does, and regardless thank you for the insight that helped them find the issue.

-- drewc

On Mon, Dec 9, 2013 at 1:06 AM, Anton Vodonosov avodonosov@yandex.ruwrote:

Lets try to reboot the machine?