Hi Daniel,
Yes, I did upgrade the server first and did restart it.
I ran wireshark on the server and could see that packets from the client
were coming in to it, but that there were no responses from the server.
So, I next stopped the client and server. I then started the server and
noticed that ossec-remoted successfully started up (without having to
"truss -f" it). I then started the client and all is now well.
Cheers,
Richard
--On 28 September 2006 21:35 -0300 Daniel Cid <[EMAIL PROTECTED]> wrote:
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
Richard Hopkins,
Information Services,
Computer Centre,
University of Bristol,
Bristol, BS8 1UD, UK
Tel +44 117 928 7859
Fax +44 117 929 1576
