Thank you, this worked perfect for me. -Josh
On Sep 1, 5:46 am, "dan (ddp)" <[email protected]> wrote: > If everything is running properly after a restart, you've probably hit > a known bug. The path for ossec-logtest is wrong in ossec-control. You > can fix it easily by adding the bin directory to the logtest line. > It'll then look like: > echo | ${DIR}/bin/ossec-logtest > /dev/null 2>&1; > > > > > > > > On Thu, Sep 1, 2011 at 8:10 AM, netkey <[email protected]> wrote: > > hi,all > > > I have upgraded my ossec from version 2.5 to 2.6,it's seems > > fine,but when I start ossec-control,it says "OSSEC analysisd: Testing > > rules failed. Configuration error. Exiting".How can I do? sorry for my > > poor english. > > > [root@localhost: ~]# /app/ossec/bin/ossec-control restart > > Killing ossec-monitord .. > > Killing ossec-logcollector .. > > Killing ossec-remoted .. > > Killing ossec-syscheckd .. > > Killing ossec-analysisd .. > > Killing ossec-maild .. > > Killing ossec-execd .. > > Killing ossec-dbd .. > > OSSEC HIDS v2.6 Stopped > > Starting OSSEC HIDS v2.6 (by Trend Micro Inc.)... > > OSSEC analysisd: Testing rules failed. Configuration error. Exiting. > > Started ossec-dbd... > > Started ossec-maild... > > Started ossec-execd... > > Started ossec-analysisd... > > Started ossec-logcollector... > > Started ossec-remoted... > > Started ossec-syscheckd... > > Started ossec-monitord... > > Completed. > > > and the ossec.log seems fine.
