Hi all,


Last night one of our BackEnd nodes failed:

Oct  6 19:22:07 proxy2 pound: (7f37405f0710) e500 for 81.83.236.39 response 
error read from 213.207.111.3:8080/GET 
/views/library/jquery/plugins/jqzoom/css/jqzoom.css HTTP/
1.1: Connection timed out (90.090 secs)
Oct  6 19:22:08 proxy2 pound: (7f37400dc710) connect_nb: poll timed out
Oct  6 19:22:08 proxy2 pound: (7f37400dc710) backend 213.207.111.3:8080 
connect: Connection timed out
Oct  6 19:22:08 proxy2 pound: (7f37400dc710) BackEnd 213.207.111.3:8080 dead 
(killed)

The BackEnd is an nginx server which is a reverse proxy to an apache+php+mysql 
server.

During the downtime of this BackEnd, the site was down. I'm not sure if it was 
down for all visitors, or just for all visitors with sessions on this backend 
server.

Could it be that pound keeps directing visitors to a dead BackEnd when they've 
got an active session on that server?

-- 
Met vriendelijke groet,


Erik Hensema
--
HostingXS B.V.
eXcellent Service

Support: support(at)hostingxs.nl
Algemeen: info(at)hostingxs.nl
Administratie: administratie(at)hostingxs.nl

Telefoon: 024 - 324 91 77
Fax: 024 - 324 91 76

Post adres:
Postbus 5
6500 AA te Nijmegen

Website: http://www.hostingxs.nl
Twitter: http://twitter.com/HostingXS