On 1/20/2014 2:42 AM, Daniel M. Zimmerman wrote:

On 19 Jan 2014, at 23:23, Shaun Gamble<listrdr@redco.com.au>  wrote:

Is anyone else experiencing problems with CGPSA as a helper on Windows servers?

I am running CGP 6.0.8 x64 on a Windows 2012 server. I have been running CGPSA for years. Originally on a Windows 2003 server and then I moved it to a newer 2012 server about a year ago. The only thing that has changed is the upgrade from CGP5 to CGP6.

CGPSA actually works fine for a while and then just seems to stop. What I think is happening is the automatic restart helper is kicking in (config in CGPSA) and once this happens CGP seems to throw a tantrum. You cannot disable the helper in CGP as it just reports it is unable to kill the helper. If you stop waiting and change to another webadmin page (say monitor instead of settings) and go back to the helpers page, the helper is then showing as disabled. Mail will then flow freely again. Obviously mail is flowing but the helper is disabled still.

Any ideas?

You could try disabling the automatic restart part of CGPSA (max_requests = 0) and see how it behaves. It is possible that newer versions of SpamAssassin have fixed the memory leaks that the max_requests feature was introduced to prevent. It is also possible, though perhaps not likely, that parallel_requests would work with Win32 now given that progress must have been made with respect to Perl's emulation of fork().

-Dan

Your recommendations here are exactly how I run CGPSA. No auto-restart, and with parallel requests on. I haven't had any issues with it on Windows Server 2008R2.

Bret

-----
This message is from the CGPSA Mailing List.
To unsubscribe, E-mail to: <cgpsa-discuss-off@mail.tffenterprises.com>.