Hi Richard,
Did you upgrade your server first and restarted it? The server must always be upgraded before any agent. Also, I just replied to Brian on another thread about the same problem. Can you try the troubleshooting steps that I mentioned in there? The link to the reply is: http://www.ossec.net/ossec-list/2006-September/msg00333.html Let us know if it helps or not... Thanks, -- Daniel B. Cid dcid ( at ) ossec.net On 9/28/06, Richard Hopkins <[EMAIL PROTECTED]> wrote:
I've upgraded my (Solaris) server to 0.9-2. I then upgraded a (Solaris) client also to 0.9-2. Since then, the client is unable to communicate with the server. The client is logging... 2006/09/28 14:01:41 ossec-agentd: Connecting to server (137.222.xxx.yyy:1514). 2006/09/28 14:01:56 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:02:12 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:02:43 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:03:30 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:04:31 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:05:47 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:07:18 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:09:04 ossec-agentd(4101): Waiting for server reply (not started). 2006/09/28 14:11:05 ossec-agentd(4101): Waiting for server reply (not started). etc. A Windows client (which I have not upgraded) is happily talking to the server. I have made no configuration changes to the clients nor server. On the server, "./list_agents -all" lists the Windows client as does "./list_agents -c". A "./list_agents -n" says "**No agent active". I tried reauthorising the client by recreating its keys but this has made no difference. Any suggestions? Cheers, Richard
