Also, I'm still curious if you changed anything. Has this ever worked? etc.

On Tue, Aug 2, 2011 at 1:44 AM, George Ochola <[email protected]> wrote:
> This is a server install
>
> ________________________________
> From: dan (ddp) <[email protected]>
> To: [email protected]
> Sent: Tuesday, August 2, 2011 12:25 AM
> Subject: Re: [ossec-list] OSSEC 2.6 ERROR: Queue
> '/var/ossec/queue/ossec/queue' not accessible: 'Queue not found
>
> Log messages like this typically have another error message before them. If
> not:
> Is this a local install, agent install, or server install?
> What did you recently change?
>
> On Mon, Aug 1, 2011 at 7:15 AM, George Ochola <[email protected]>
> wrote:
>> Hi All
>> I have just installed OSSEC 2.6 on my AIX 5.3 machine which was previouly
>> running 2.5.1 , but on installing 2.6. I get the following error what
>> could
>> be the problem, how do i fix this problem,
>>
>>
>> 2011/08/01 14:02:57 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Queue not found'.
>> 2011/08/01 14:03:03 ossec-logcollector(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Queue not found'.
>> 2011/08/01 14:03:12 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'No such file or
>> directory'.
>> 2011/08/01 14:03:18 ossec-logcollector(1211): ERROR: Unable to access
>> queue:
>> '/var/ossec/queue/ossec/queue'. Giving up..
>> 2011/08/01 14:03:23 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Queue not found'.
>> 2011/08/01 14:03:38 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'No such file or
>> directory'.
>> 2011/08/01 14:03:54 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Queue not found'.
>> 2011/08/01 14:04:09 ossec-rootcheck(1211): ERROR: Unable to access queue:
>> '/var/ossec/queue/ossec/queue'. Giving up..
>> Kind Regards
>>
>> George Ochola
>>
>> ________________________________
>>
>>
>>
>>
>>
>
>
>

Reply via email to