PostMasterPOP3 can crash because of memory limit or other limitations. The PID may still be active, but the process not. I think the PID is stored in the DB or filesystem, so rebooting won't be of much use prolly. I made a simple kill script which removes the PID so you can start over. Make sure the process is really gone, otherwise you may get some very wierd results when 2 POP3 processes run at the same time!

The attached script should be in de bin dir.

Note that the PostMasterPOP3 script will auto remove a PID after an hour, this script just does that on demand.

Regards,
Richard

Nathan Campbell wrote:
I know of TCPView from SysInternals.
I had rebooted the server several times and manually stopped and started the 
OTRS process. No avail.

Attachment: kill.pl
Description: Perl program

_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/

Reply via email to