Try "upgrading" the agent (you can probably even use the same version and upgrade over itself). I recently had a similar issue, but a reboot seemed to fix everything.
On Mon, Aug 1, 2011 at 12:27 PM, jplee3 <[email protected]> wrote: > Hi all, > > I'm running into a problem where I cannot get the OSSEC agent (2.5.1) > to start due to the "Unable to start OSSEC (check config)" message on > a 64-bit Win2k8 box. I tried modifying the registry as suggested here: > http://groups.google.com/group/ossec-list/browse_thread/thread/8b14612d9f2af055 > > But still am unable to get it to run. > > I can launch from the command prompt using "ossec-agent.exe start" but > I don't want to have to resort to this if there's a 'cleaner' > solution. > > Has anybody run into this issue? Any suggestions? > > The weird thing is that after the initial install of the agent, I was > able to start from the GUI without a problem. The agent stopped itself > over the weekend after the "ERROR: attempted to use null string" error > came up. I tried starting up the agent again this morning and that's > when I encountered the "check config" error. > > Any ideas what to do? Also, what would have caused the null string > issue? I was suspecting it might be the fact that rootcheck was still > enabled so I disabled it. I'm running the agent from the command > prompt currently so I guess we'll find out if it stays up or gives the > null string error again. > > > Thanks
