Re: Failed to Lock PID File

[Jason Haar <Jason.Haar () trimble co nz>]

Todd Wease wrote:
> Hi Mike,
>
> Can you apply the attached patch which should print the cause of the
> error?  
This is just a "me too". Last weekend my home server ground to a halt.
There were 100's of copies of snort running and syslog was full of

 snort[17832]: FATAL ERROR: Failed to Lock PID File
"/var/run//snort_eth0.pid" for PID "17832"
 snort[17834]: FATAL ERROR: Failed to Lock PID File
"/var/run//snort_eth0.pid" for PID "17834"
 etc


After I managed to kill the snort processes, I found there was a
/var/run//snort_eth0.pid.lck (.lck? I think that's what it was - too
late now), deleted that and /var/run//snort_eth0.pid and restarted
snort, and it's been fine since.

This is snort-inline-2.8.0-1.i386 on a CentOS5 server.



-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1


------------------------------------------------------------------------------
_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users