Re: [ossec-list] Re: Same old song ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue

2017-04-13 Thread dan (ddp) 
On Mon, Apr 10, 2017 at 2:46 PM, Anoop Perayil  wrote:
> I am running OSSEC on a Security Onion build Ubuntu 14.04.5 LTS.
> The issue started after I added in more disk since I ran out of space in /
>

I really wish SO would partition their system properly. Big /, nothing
else is very annoying.
Check permissions. Maybe things didn't copy over properly?

> On Monday, 10 April 2017 23:52:07 UTC+5:30, Joshua Gimer wrote:
>>
>> Do you have SELinux running in an enforcing mode? What is the output of
>> sestatus?
>>
>> Josh
>>
>> On Wed, Oct 12, 2016 at 8:58 AM, Kernel Panic  wrote:
>>>
>>> Really do not know, just installed  it from repo and tried to start the
>>> service.
>>>
>>> Thanks
>>> Regards
>>>
>>> El martes, 11 de octubre de 2016, 15:22:03 (UTC-3), Kernel Panic
>>> escribió:

 Hi guys,
 Yes, I've been reading the error on the list, lots of cases and I got it
 too but I run out of idea.

 The log:

 2016/10/11 13:04:40 ossec-syscheckd(1210): ERROR: Queue
 '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
 2016/10/11 13:04:40 ossec-rootcheck(1210): ERROR: Queue
 '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
 2016/10/11 13:04:46 ossec-logcollector(1210): ERROR: Queue
 '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
 2016/10/11 13:04:46 ossec-logcollector(1211): ERROR: Unable to access
 queue: '/var/ossec/queue/ossec/queue'. Giving up..
 2016/10/11 13:04:48 ossec-syscheckd(1210): ERROR: Queue
 '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
 2016/10/11 13:04:48 ossec-rootcheck(1210): ERROR: Queue
 '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
 2016/10/11 13:05:01 ossec-syscheckd(1210): ERROR: Queue
 '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
 2016/10/11 13:05:01 ossec-rootcheck(1211): ERROR: Unable to access
 queue: '/var/ossec/queue/ossec/queue'. Giving up..

 The queue
 srw-rw. 1 ossec ossec 0 Oct 11 13:04 /var/ossec/queue/ossec/queue

 Also read the local_rules may have issues, tested with -t and no errors
 displayed also with xmllint

 xmllint local_rules.xml
 
 --SNIP-
 
 
 

 There is a file also under /var/ossec/etc/decoder.xml that seems not
 good , is that correct?
 xmllint decoder.xml
 decoder.xml:52: parser error : Extra content at the end of the document
 
 ^

 And found this:

 xmllint  ossec.conf
 ossec.conf:74: parser error : Comment not terminated
 

 Line 74, what's missing here?

  
 
 72000





 ossec-hids-2.8.3-53.el6.art.x86_64
 ossec-hids-server-2.8.3-53.el6.art.x86_64
 ossec-wui-0.8-4.el6.art.noarch

 Thanks for your time and support
 Regards








>>> --
>>>
>>> ---
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> Thanks,
>> Joshua Gimer
>>
>> ---
>>
>> http://www.linkedin.com/in/jgimer
>> http://twitter.com/jgimer
>
> --
>
> ---
> 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.

-- 

--- 
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.

Re: [ossec-list] Re: Same old song ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue

2017-04-13 Thread dan (ddp) 
On Mon, Apr 10, 2017 at 2:34 PM, Felix Martel  wrote:
> Perhaps this is way off base, but have you added an agent for localhost ? In
> my context of a new install, a ton of issues went away after I added an
> agent for the localhost (name=localhost, IP=127.0.0.1). Didn't export the
> key or anything. Once I did that, my queue errors went away and my agents
> started reporting.
>

You shouldn't have to add an agent for the localhost, it's
automatically considered agent 000.

> If I have one rant regarding OSSEC HIDS, it's the structure and quality of
> documentation: Sketchy at best... Doing a lot of poking in the dark to solve
> issues.
>

Please help: https://github.com/ossec/ossec-docs


>
> On Tuesday, October 11, 2016 at 2:22:03 PM UTC-4, Kernel Panic wrote:
>>
>> Hi guys,
>> Yes, I've been reading the error on the list, lots of cases and I got it
>> too but I run out of idea.
>>
>> The log:
>>
>> 2016/10/11 13:04:40 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:40 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:46 ossec-logcollector(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:46 ossec-logcollector(1211): ERROR: Unable to access
>> queue: '/var/ossec/queue/ossec/queue'. Giving up..
>> 2016/10/11 13:04:48 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:48 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:05:01 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:05:01 ossec-rootcheck(1211): ERROR: Unable to access queue:
>> '/var/ossec/queue/ossec/queue'. Giving up..
>>
>> The queue
>> srw-rw. 1 ossec ossec 0 Oct 11 13:04 /var/ossec/queue/ossec/queue
>>
>> Also read the local_rules may have issues, tested with -t and no errors
>> displayed also with xmllint
>>
>> xmllint local_rules.xml
>> 
>> --SNIP-
>> 
>> 
>> 
>>
>> There is a file also under /var/ossec/etc/decoder.xml that seems not good
>> , is that correct?
>> xmllint decoder.xml
>> decoder.xml:52: parser error : Extra content at the end of the document
>> 
>> ^
>>
>> And found this:
>>
>> xmllint  ossec.conf
>> ossec.conf:74: parser error : Comment not terminated
>> 
>>
>> Line 74, what's missing here?
>>
>>  
>> 
>> 72000
>>
>>
>>
>>
>>
>> ossec-hids-2.8.3-53.el6.art.x86_64
>> ossec-hids-server-2.8.3-53.el6.art.x86_64
>> ossec-wui-0.8-4.el6.art.noarch
>>
>> Thanks for your time and support
>> Regards
>>
>>
>>
>>
>>
>>
>>
>>
> --
>
> ---
> 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.

-- 

--- 
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.

Re: [ossec-list] Re: Same old song ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue

2017-04-10 Thread Anoop Perayil 
I am running OSSEC on a Security Onion build Ubuntu 14.04.5 LTS.
The issue started after I added in more disk since I ran out of space in /

On Monday, 10 April 2017 23:52:07 UTC+5:30, Joshua Gimer wrote:
>
> Do you have SELinux running in an enforcing mode? What is the output of 
> sestatus?
>
> Josh
>
> On Wed, Oct 12, 2016 at 8:58 AM, Kernel Panic  > wrote:
>
>> Really do not know, just installed  it from repo and tried to start the 
>> service.
>>
>> Thanks
>> Regards
>>
>> El martes, 11 de octubre de 2016, 15:22:03 (UTC-3), Kernel Panic escribió:
>>
>>> Hi guys,
>>> Yes, I've been reading the error on the list, lots of cases and I got it 
>>> too but I run out of idea.
>>>
>>> The log:
>>>
>>> 2016/10/11 13:04:40 ossec-syscheckd(1210): ERROR: Queue 
>>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>>> 2016/10/11 13:04:40 ossec-rootcheck(1210): ERROR: Queue 
>>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>>> 2016/10/11 13:04:46 ossec-logcollector(1210): ERROR: Queue 
>>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>>> 2016/10/11 13:04:46 ossec-logcollector(1211): ERROR: Unable to access 
>>> queue: '/var/ossec/queue/ossec/queue'. Giving up..
>>> 2016/10/11 13:04:48 ossec-syscheckd(1210): ERROR: Queue 
>>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>>> 2016/10/11 13:04:48 ossec-rootcheck(1210): ERROR: Queue 
>>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>>> 2016/10/11 13:05:01 ossec-syscheckd(1210): ERROR: Queue 
>>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>>> 2016/10/11 13:05:01 ossec-rootcheck(1211): ERROR: Unable to access 
>>> queue: '/var/ossec/queue/ossec/queue'. Giving up..
>>>
>>> The queue
>>> srw-rw. 1 ossec ossec 0 Oct 11 13:04 /var/ossec/queue/ossec/queue
>>>
>>> Also read the local_rules may have issues, tested with -t and no errors 
>>> displayed also with xmllint
>>>
>>> xmllint local_rules.xml
>>> 
>>> --SNIP-
>>> 
>>> 
>>> 
>>>
>>> There is a file also under /var/ossec/etc/decoder.xml that seems not 
>>> good , is that correct?
>>> xmllint decoder.xml
>>> decoder.xml:52: parser error : Extra content at the end of the document
>>> 
>>> ^
>>>
>>> And found this:
>>>
>>> xmllint  ossec.conf
>>> ossec.conf:74: parser error : Comment not terminated
>>> 
>>>
>>> Line 74, what's missing here?
>>>
>>>  
>>> 
>>> 72000
>>>
>>>
>>>
>>>
>>>
>>> ossec-hids-2.8.3-53.el6.art.x86_64
>>> ossec-hids-server-2.8.3-53.el6.art.x86_64
>>> ossec-wui-0.8-4.el6.art.noarch
>>>
>>> Thanks for your time and support
>>> Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>
>> --- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Thanks,
> Joshua Gimer
>
> ---
>
> http://www.linkedin.com/in/jgimer
> http://twitter.com/jgimer
>

-- 

--- 
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.

Re: [ossec-list] Re: Same old song ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue

2017-04-10 Thread Joshua Gimer 
Do you have SELinux running in an enforcing mode? What is the output of
sestatus?

Josh

On Wed, Oct 12, 2016 at 8:58 AM, Kernel Panic 
wrote:

> Really do not know, just installed  it from repo and tried to start the
> service.
>
> Thanks
> Regards
>
> El martes, 11 de octubre de 2016, 15:22:03 (UTC-3), Kernel Panic escribió:
>
>> Hi guys,
>> Yes, I've been reading the error on the list, lots of cases and I got it
>> too but I run out of idea.
>>
>> The log:
>>
>> 2016/10/11 13:04:40 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:40 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:46 ossec-logcollector(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:46 ossec-logcollector(1211): ERROR: Unable to access
>> queue: '/var/ossec/queue/ossec/queue'. Giving up..
>> 2016/10/11 13:04:48 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:48 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:05:01 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:05:01 ossec-rootcheck(1211): ERROR: Unable to access queue:
>> '/var/ossec/queue/ossec/queue'. Giving up..
>>
>> The queue
>> srw-rw. 1 ossec ossec 0 Oct 11 13:04 /var/ossec/queue/ossec/queue
>>
>> Also read the local_rules may have issues, tested with -t and no errors
>> displayed also with xmllint
>>
>> xmllint local_rules.xml
>> 
>> --SNIP-
>> 
>> 
>> 
>>
>> There is a file also under /var/ossec/etc/decoder.xml that seems not good
>> , is that correct?
>> xmllint decoder.xml
>> decoder.xml:52: parser error : Extra content at the end of the document
>> 
>> ^
>>
>> And found this:
>>
>> xmllint  ossec.conf
>> ossec.conf:74: parser error : Comment not terminated
>> 
>>
>> Line 74, what's missing here?
>>
>>  
>> 
>> 72000
>>
>>
>>
>>
>>
>> ossec-hids-2.8.3-53.el6.art.x86_64
>> ossec-hids-server-2.8.3-53.el6.art.x86_64
>> ossec-wui-0.8-4.el6.art.noarch
>>
>> Thanks for your time and support
>> Regards
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>
> ---
> 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.
>



-- 
Thanks,
Joshua Gimer

---

http://www.linkedin.com/in/jgimer
http://twitter.com/jgimer

-- 

--- 
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.

Re: [ossec-list] Re: Same old song ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue

2016-10-12 Thread dan (ddp) 
On Wed, Oct 12, 2016 at 10:30 AM, Kernel Panic  wrote:
> Hi guys
> The remote service was not starting, now it up and running, and have to say
> that this was pure pain!!
>

It would be interesting to find out what happened to your setup to
give you such troubles.

> /var/ossec/bin/ossec-remoted -df
> 2016/10/12 09:08:05 ossec-remoted: DEBUG: Starting ...
> 2016/10/12 09:08:05 ossec-remoted: INFO: Started (pid: 21609).
> 2016/10/12 09:08:05 ossec-remoted: DEBUG: Forking remoted: '0'.
> z77s-tpuppetm01:/var/ossec/etc# 2016/10/12 09:08:05 ossec-remoted: INFO:
> Started (pid: 21610).
> 2016/10/12 09:08:05 ossec-remoted: DEBUG: Running manager_init
> 2016/10/12 09:08:05 ossec-remoted: INFO: (unix_domain) Maximum send buffer
> set to: '4194304'.
> 2016/10/12 09:08:05 ossec-remoted(4111): INFO: Maximum number of agents
> allowed: '16384'.
> 2016/10/12 09:08:05 ossec-remoted(1410): INFO: Reading authentication keys
> file.
> 2016/10/12 09:08:05 ossec-remoted: DEBUG: OS_StartCounter.
> 2016/10/12 09:08:05 ossec-remoted: OS_StartCounter: keysize: 1
> 2016/10/12 09:08:05 ossec-remoted: Unable to open agent file. errno: 13
> 2016/10/12 09:08:05 ossec-remoted(1103): ERROR: Unable to open file
> '/queue/rids/001'.
>
>
> netstat -antuwp | grep ossec
> udp0  0 0.0.0.0:15140.0.0.0:*
> 21908/ossec-remoted
>
> Thank you very much!
> Regards
>
>
> El martes, 11 de octubre de 2016, 15:22:03 (UTC-3), Kernel Panic escribió:
>>
>> Hi guys,
>> Yes, I've been reading the error on the list, lots of cases and I got it
>> too but I run out of idea.
>>
>> The log:
>>
>> 2016/10/11 13:04:40 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:40 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:46 ossec-logcollector(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:46 ossec-logcollector(1211): ERROR: Unable to access
>> queue: '/var/ossec/queue/ossec/queue'. Giving up..
>> 2016/10/11 13:04:48 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:04:48 ossec-rootcheck(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:05:01 ossec-syscheckd(1210): ERROR: Queue
>> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>> 2016/10/11 13:05:01 ossec-rootcheck(1211): ERROR: Unable to access queue:
>> '/var/ossec/queue/ossec/queue'. Giving up..
>>
>> The queue
>> srw-rw. 1 ossec ossec 0 Oct 11 13:04 /var/ossec/queue/ossec/queue
>>
>> Also read the local_rules may have issues, tested with -t and no errors
>> displayed also with xmllint
>>
>> xmllint local_rules.xml
>> 
>> --SNIP-
>> 
>> 
>> 
>>
>> There is a file also under /var/ossec/etc/decoder.xml that seems not good
>> , is that correct?
>> xmllint decoder.xml
>> decoder.xml:52: parser error : Extra content at the end of the document
>> 
>> ^
>>
>> And found this:
>>
>> xmllint  ossec.conf
>> ossec.conf:74: parser error : Comment not terminated
>> 
>>
>> Line 74, what's missing here?
>>
>>  
>> 
>> 72000
>>
>>
>>
>>
>>
>> ossec-hids-2.8.3-53.el6.art.x86_64
>> ossec-hids-server-2.8.3-53.el6.art.x86_64
>> ossec-wui-0.8-4.el6.art.noarch
>>
>> Thanks for your time and support
>> Regards
>>
>>
>>
>>
>>
>>
>>
>>
> --
>
> ---
> 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.

-- 

--- 
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.

Re: [ossec-list] Re: Same old song ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue

2016-10-12 Thread dan (ddp) 
On Wed, Oct 12, 2016 at 9:09 AM, Kernel Panic  wrote:
>
> chmod 777 /var/ossec/queue/ossec/queue
> z77s-tpuppetm01:/var/ossec/logs# /var/ossec/bin/ossec-syscheckd -df
> 2016/10/12 08:09:05 ossec-syscheckd: DEBUG: Starting ...
> 2016/10/12 08:09:05 ossec-rootcheck: DEBUG: Starting ...
> 2016/10/12 08:09:05 ossec-rootcheck: Starting queue ...
> 2016/10/12 08:09:08 ossec-syscheckd(1210): ERROR: Queue
> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
> 2016/10/12 08:09:08 ossec-rootcheck(1210): ERROR: Queue
> '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'.
>

Make sure you're starting these in the correct order. Based on an
`ossec-control start` I get the following order:
ossec-maild
ossec-execd
ossec-analysisd
ossec-logcollector
ossec-remoted
ossec-syscheckd
ossec-monitord

-- 

--- 
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.