-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 12, 2010, at 11:53 AM, David Porcello wrote: > Hi all, > > I'm running OSSEC client 2.4.1 on a handful of RedHat EL 5.5 servers and I'm > seeing the following behavior across the board: It appears that > client-logcollector and client-syscheckd aren't detected as running, and > therefore aren't stopped by ossec-control. If these daemons aren't killed, > multiple instances begin building up with each start or restart request, and > new agent.conf configs are prevented from loading.
Are you, perchance, running the atomicturtle RPM version of ossec? Specifically version 2.4.1-4 ? If so, I think this is a bug in that RPM causing the problem.. I have a SPEC that fixes the problem if you want it, though it removes all of the atomicturtle specific stuff (rules, decoders, etc). > Found a couple related threads, but none with a resolution. Anyone else > seeing this? > > Thanks, > d. - --------------------------- Jason 'XenoPhage' Frisvold [email protected] - --------------------------- "Any sufficiently advanced magic is indistinguishable from technology." - - Niven's Inverse of Clarke's Third Law -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkxsQZ0ACgkQ8CjzPZyTUTSQWQCgmLRn3ZAjHP8eZqYvinCFZ4+d nqUAn0CoHOSjIEBoJAyuhxy4wYBXynSb =g6SA -----END PGP SIGNATURE-----
