Proxy not functioning after power failure I'm having a problem that has me climbing the walls! Running Release 5.0.2_GA (FOSS) and has been operating well for some time, but we had a power failure in our data center and this time the system did not come back up well.
It is running multi-server, one main (core) box and two mail stores. Everything actually appears to be running except that users running POP or IMAP clients can not access mail. It appears that the nginx proxy is having issues, but I've run out of ideas on places to look.
A DB integrity check returns no errors, but this is what I am seeing in the nginx.log file:
2009/01/10 08:39:21 [info] 12559#0: *7114 client 76.194.20.216 connected to 0.0.0.0:110
2009/01/10 08:39:21 [alert] 12559#0: socket() failed (97: Address family not supported by protocol)
2009/01/10 08:39:21 [notice] 3212#0: signal 17 (SIGCHLD) received
2009/01/10 08:39:21 [alert] 3212#0: worker process 12559 exited on signal 11
2009/01/10 08:39:21 [notice] 3212#0: start worker process 12581
2009/01/10 08:39:21 [notice] 3212#0: signal 29 (SIGIO) received
2009/01/10 08:39:21 [info] 12567#0: *7115 client 76.194.20.216 connected to 0.0.0.0:110
2009/01/10 08:39:21 [alert] 12567#0: socket() failed (97: Address family not supported by protocol)
2009/01/10 08:39:21 [notice] 3212#0: signal 17 (SIGCHLD) received
2009/01/10 08:39:21 [alert] 3212#0: worker process 12567 exited on signal 11
2009/01/10 08:39:21 [notice] 3212#0: start worker process 12582
2009/01/10 08:39:21 [notice] 3212#0: signal 29 (SIGIO) received
Repeated for every connection attempt.
Can anyone offer any insights on where to look and how to correct this? It would be greatly appreciated! |