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.
# ps ax |grep ossec |grep -v grep 24077 ? S 0:00 /var/ossec/bin/ossec-execd 24081 ? S 0:00 /var/ossec/bin/ossec-agentd 24085 ? S 0:00 /var/ossec/bin/client-logcollector 24089 ? S 0:00 /var/ossec/bin/client-syscheckd # /var/ossec/bin/ossec-control stop client-logcollector not running .. client-syscheckd not running .. Killing ossec-agentd .. Killing ossec-execd .. OSSEC HIDS v2.4 Stopped # ps ax |grep ossec |grep -v grep 24085 ? S 0:00 /var/ossec/bin/client-logcollector 24089 ? S 0:00 /var/ossec/bin/client-syscheckd Found a couple related threads, but none with a resolution. Anyone else seeing this? Thanks, d. NOTICE: The information contained in this e-mail and any attachments is intended solely for the recipient(s) named above, and may be confidential and legally privileged. If you received this e-mail in error, please notify the sender immediately by return e-mail and delete the original message and any copy of it from your computer system. If you are not the intended recipient, you are hereby notified that any review, disclosure, retransmission, dissemination, distribution, copying, or other use of this e-mail, or any of its contents, is strictly prohibited. Although this e-mail and any attachments are believed to be free of any virus or other defects, it is the responsibility of the recipient to ensure that it is virus-free and no responsibility is accepted by the sender for any loss or damage arising if such a virus or defect exists.
