[root@mx2 bin]# tail -f /var/ossec/logs/ossec.log 2016/02/10 14:27:25 ossec-rootcheck: DEBUG: Starting ... 2016/02/10 14:27:25 ossec-rootcheck: Starting queue ... 2016/02/10 14:27:28 ossec-syscheckd(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2016/02/10 14:27:28 ossec-rootcheck(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2016/02/10 14:27:34 ossec-logcollector(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2016/02/10 14:27:34 ossec-logcollector(1211): ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue'. Giving up.. 2016/02/10 14:27:36 ossec-syscheckd(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2016/02/10 14:27:36 ossec-rootcheck(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2016/02/10 14:27:49 ossec-syscheckd(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2016/02/10 14:27:49 ossec-rootcheck(1211): ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue'. Giving up..
the same miercuri, 10 februarie 2016, 14:36:42 UTC+2, dan (ddpbsd) a scris: > > > On Feb 10, 2016 7:32 AM, "Maxim Surdu" <maxs...@gmail.com <javascript:>> > wrote: > > > > Hi dear community, > > > > i install and configure about 10 agents > > > > but one of then after install client key did not start > > > > > > [root@mx2 bin]# ./ossec-control start > > Starting OSSEC HIDS v2.8.3 (by Trend Micro Inc.)... > > Started ossec-execd... > > 2016/02/10 14:27:25 ossec-agentd: INFO: Using notify time: 600 and max > time to reconnect: 1800 > > Started ossec-agentd... > > 2016/02/10 14:27:25 ossec-logcollector: DEBUG: Starting ... > > Started ossec-logcollector... > > 2016/02/10 14:27:25 ossec-syscheckd: DEBUG: Starting ... > > 2016/02/10 14:27:25 syscheckd: Reading Configuration > [/var/ossec/etc/ossec.conf] > > 2016/02/10 14:27:25 syscheckd: Reading Client Configuration > [/var/ossec/etc/ossec.conf] > > 2016/02/10 14:27:25 ossec-rootcheck: DEBUG: Starting ... > > 2016/02/10 14:27:25 ossec-rootcheck: Starting queue ... > > 2016/02/10 14:27:28 ossec-syscheckd(1210): ERROR: Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > > 2016/02/10 14:27:28 ossec-rootcheck(1210): ERROR: Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > > 2016/02/10 14:27:36 ossec-syscheckd(1210): ERROR: Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > > 2016/02/10 14:27:36 ossec-rootcheck(1210): ERROR: Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > > 2016/02/10 14:27:49 ossec-syscheckd(1210): ERROR: Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > > 2016/02/10 14:27:49 ossec-rootcheck(1211): ERROR: Unable to access > queue: '/var/ossec/queue/ossec/queue'. Giving up.. > > ossec-syscheckd did not start > > > > > > please any suggestions because this servers are very important for > monitoring logs. > > > > Check the ossec.log for more detailed log messages. > > > Many thanks, > > Maxim Surdu > > > > -- > > > > --- > > 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+...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- --- 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.
