check the permissions on /var/ossec/queue or as it appears from your log /var/ossec/queue/ossec/queue and make sure that ossec has r-rw access. not sure why, but i've had /var/ossec/queue's file permissions change during a reboot a couple of times in the past, and that will cause the kind of problem your describing. if that's it just change the permissions on the folder so ossec can access it again.
[EMAIL PROTECTED] wrote: > Hello, > I rebooted the server and found ossec failed. I tried to start it > > service ossec start > Starting OSSEC: 2007/08/21 00:56:01 ossec-syscheckd(1210): Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection r > efused'. > 2007/08/21 00:56:01 ossec-rootcheck(1210): Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > 2007/08/21 00:56:09 ossec-syscheckd(1210): Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > 2007/08/21 00:56:09 ossec-rootcheck(1210): Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > 2007/08/21 00:56:22 ossec-syscheckd(1210): Queue > '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. > 2007/08/21 00:56:22 ossec-rootcheck(1211): Unable to access queue: > '/var/ossec/queue/ossec/queue'. Giving up.. > [FAILED] > > > Any idea why it failed? > > Regards, > DM > > . > >
