For the past month or two I've been dealing with an issue where pound will 
randomly hang for several minutes, and then eventually correct itself. Manually 
restarting the process will also correct this. I think it has to do with the 
load on the server. We increased the load in the time frame mentioned, though 
not by anything unreasonable. I spun up a new VM and tried both the custom PCI 
version from github as well as the latest stable 2.7 release, but both have the 
same issue. We were running several sites plus Exchange OWA/ActiveSync/Outlook 
Anywhere on the system, but as of Thursday are only running Exchange services, 
and the problem persists. Exchange services are where the increased load came 
from as we are now running 20 or so laptops through Outlook Anywhere 
constantly, as opposed to maybe half that before. I tried increasing the number 
of files open allowed, per a mailing list thread from some time back, but it's 
still having the issue. I am monitoring it with a script I wrote to check for 
availability, which will email me and restart the service if it's down. 
Everything was fine from last evening until around 8 this morning, when people 
started working again, so it seems it's connected to the Outlook Anywhere 
connections, since that's what would have started around that time this 
morning. ActiveSync runs 24/7, so if that was the problem it shouldn't have 
stopped hanging during the off-hours. I don't see anything in the logs that 
appears to be helpful, so I'm hoping someone here can suggest a debug log 
setting or a fix, or anything. Log level is currently set to 2. Is there a way 
to get more information than that?

Thanks,

Drew Green


Drew Green, MCSE, CEH
Director of Information Technology & Security Services<https://www.tjtsec.com>
[cid:TJT_Footer_Logo2_4d5b7ceb-69ac-4bcf-bd5f-3f7b2ba92bc6.png]<http://www.tjtpa.com>
4700 Falls of Neuse Road
Suite 400
Raleigh, NC 27609

Direct: 919-532-7925
Main:   919-571-7055
Fax:    919-516-0277
Email Disclaimer<http://www.tjtpa.com/email-disclaimer>

Reply via email to