Hello! I'm trying to institute some automatic failover for OSSEC and we're using amazon's elastic files share as the persistence layer for ossec. Right now we have the whole /var/ossec directory symlinked to a directory that exists on the NFS mount.
When we restart the ossec service on the same host, remoted fails to come up... with this in the logs: 2016/12/05 09:33:37 ossec-remoted(1210): ERROR: Queue '/queue/ossec/queue' not accessible: 'Connection refused'. 2016/12/05 09:33:37 ossec-remoted(1211): ERROR: Unable to access queue: '/queue/ossec/queue'. Giving up.. If we delete /var/ossec/queue/ossec/queue and queue/alerts/ar then ossec remoted comes up fine and can access the sockets. Is this a problem with sockets being on an NFS mount? Any suggestions on how to institute automatic failover for the ossec manager? -- --- 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.
