Thx Dan...A quick symlink fixed the issue for me... # ln -s /var/ossec/bin/ossec-logtest /var/ossec/ossec-logtest
However I have OSSEC running as a local install on my development environment, and OSSEC running as manager in our production environment, both upgraded to 2.6 couple of days ago. I find it odd that the local install doesn't spit out the error, whereas the manager install does. Weird... On Jul 21, 5:22 am, "dan (ddp)" <[email protected]> wrote: > There's a small bug in ossec-control. The path for ossec-logtest is > missing the bin directory. > > > > > > > > On Thu, Jul 21, 2011 at 6:10 AM, Andre Pawlowski <[email protected]> wrote: > > Hi list, > > > I have a strange error. When I restart ossec I got the following output: > > > Killing ossec-monitord .. > > Killing ossec-logcollector .. > > Killing ossec-remoted .. > > Killing ossec-syscheckd .. > > Killing ossec-analysisd .. > > Killing ossec-maild .. > > Killing ossec-execd .. > > OSSEC HIDS v2.6 Stopped > > Starting OSSEC HIDS v2.6 (by Trend Micro Inc.)... > > OSSEC analysisd: Testing rules failed. Configuration error. Exiting. > > Started ossec-maild... > > Started ossec-execd... > > Started ossec-analysisd... > > Started ossec-logcollector... > > Started ossec-remoted... > > Started ossec-syscheckd... > > Started ossec-monitord... > > Completed. > > > In the ossec.log I didn't find any error for today. I commented out the > > local_rules.xml in ossec.conf but I got still the same message. > > ossec_logtest doesn't report any error with the rules. > > > Has anyone an idea? > > > Thanks > > > sqall > > > -- > > > Andre Pawlowski > > > ------------------------------------------------------------------- > > > Es ist nicht genug, zu wissen, man muss auch anwenden; > > es ist nicht genug, zu wollen, man muss auch tun. > > -Johann Wolfgang von Goethe
