Hello Iñaki. Thank you. I have a doubt: what is Procees Monitor? Is an OSSEC´s tool to monitor the general performance?
I don´t understand when you speak about mutex resource to know if another process is running..... Thank you very much! On Mar 31, 11:12 am, "Iñaki R." <[email protected]> wrote: > Also you could spent some more time (I you have it ;)) and use Procces > Monitor from sysinternals to see what is doing the process and why > really crash. A mutex is a typical resource to know if another process > is running. Restarting the server solves the problem? > > Greetings > > dan (ddp) wrote: > > I think most of the troubleshooting steps would require access to the > > server. > > You could try recreating the agents on the server (manage_agents, > > delete agent, recreate), then reinstall on the agent boxes with the > > new client keys. Make sure the hard drives aren't full or out of > > inodes on the server. > > > On Wed, Mar 31, 2010 at 7:59 AM, Lucio Emanuel Soldo <[email protected]> > > wrote: > >> Hello, > >> Thank you for your answer. These are the logs, from the agent > >> and > >> the server: > > >> Agent: > >> ossec-agent: INFO: Trying to connect to server <my ip server> > >> ossec-agent: Error waiting mutex (timeout). > > >> OSSEC Server: > >> I don t have a log into the server. > > >> Thank you very much. -- To unsubscribe, reply using "remove me" as the subject.
