Hi list, I'm pretty new here (just subscribed). I've installed ossec yesterday and trying to use it to monitor one linux box and one HP-UX box. I installed the agent on HP-UX and got the "socket busy" error. I've seen some post here about a bug for the agent on HP-UX, with no solution.
Here it is: 2010/10/20 14:04:28 ossec-logcollector: socket busy .. 2010/10/20 14:04:28 ossec-logcollector(1224): ERROR: Error sending message to queue. 2010/10/20 14:04:29 ossec-syscheckd: socket busy .. 2010/10/20 14:04:39 ossec-syscheckd: socket busy .. 2010/10/20 14:04:39 ossec-syscheckd: socketerr (not available). 2010/10/20 14:04:39 ossec-syscheckd(1224): ERROR: Error sending message to queue. 2010/10/20 14:04:49 ossec-syscheckd: socket busy .. 2010/10/20 14:04:59 ossec-syscheckd: socket busy .. [...] What I've just discovered is: if you do a stop & start of the agent (NOT a restart), the agent seems to work fine (tested twice). Actually I don't know why and I'm going to investigate a bit (but I'm not a hp- ux expert). This hp-ux box is "almost" for testing purposes, so if some of you feel like doing some test... just let me know. I'd like to see this problem solved to move Ossec to our production environment :) Thanks a lot for your attention. Marco
