2017/04/28 15:54:58 ossec-analysisd(1103): ERROR: Unable to open file 'queue/fts/fts-queue'. 2017/04/28 15:54:58 ossec-testrule(1260): ERROR: Error initiating FTS list
On Friday, April 28, 2017 at 3:55:35 PM UTC-4, Nikki S wrote: > > No changes have been to the configuration file! > > > # ./ossec-control restart > cat: /var/ossec/var/start-script-lock/pid: No such file or directory > cat: /var/ossec/var/start-script-lock/pid: No such file or directory > cat: /var/ossec/var/start-script-lock/pid: No such file or directory > cat: /var/ossec/var/start-script-lock/pid: No such file or directory > cat: /var/ossec/var/start-script-lock/pid: No such file or directory > ./ossec-control: line 89: /var/ossec/var/start-script-lock/pid: No such > file or directory > ossec-monitord not running .. > ossec-logcollector not running .. > ossec-remoted not running .. > ossec-syscheckd not running .. > ossec-analysisd not running .. > ossec-maild not running .. > ossec-execd not running .. > ossec-csyslogd not running .. > OSSEC HIDS v2.8.3 Stopped > Starting OSSEC HIDS v2.8.3 (by Trend Micro Inc.)... > OSSEC analysisd: Testing rules failed. Configuration error. Exiting. > > # ./ossec-control start > Starting OSSEC HIDS v2.8.3 (by Trend Micro Inc.)... > OSSEC analysisd: Testing rules failed. Configuration error. Exiting. > > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to ossec-list+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
