hi, I just upgraded to 2.0... same here, seg fault with local and agent id ./syscheck_control -i 006
Integrity changes for agent 'wsus (006) - x.x.x.x': Segmentation fault immediately after issuing ./syscheck_update -u 006 the seg fault is gone for the agent 006. But ./syscheck_update -u 000 ** Invalid agent id '000' How could I update for the local server 000 ? Anyway, from ./syscheck_control -h "-u <id> Updates (clear) the database for the agent." Does this mean, clear the database and build a new one or just update it by running syscheck. And what for is syscheck_update then? And what would be the proper way to run syscheck on an agent (from the server) ? BTW, I might have found a bug: On a Windows 2000 Server, agent-2.0, setting syscheck.sleep_after=150 in internal_options.conf prevents the agent from startup. tia+regards, matthias On Mar 24, 1:43 pm, Michael Caplan <[email protected]> wrote: > Hi, > > I'm running Ossec 2.0 and am getting a segfault when trying to list > modified files for my local machine: > > /var/ossec/bin/syscheck_control-i 000 > > Integrity checking changes for local system 'AFCINTMONAPPVM1 - > 127.0.0.1': > Segmentation fault > > Ossec also reported on the error in my messages log: > > kernel: syscheck_contro[7321]: segfault at 0000000000000008 rip > 0000003dae88fe3b rsp 00007fff89a8ec50 error 4 > > Anyone else come across this? > > Thanks, > > Mike > > Please consider the environment before printing this email. > > E-mail messages may contain viruses, worms, or other malicious code. By > reading the message and opening any attachments, the recipient accepts full > responsibility for taking protective action against such code. Henry Schein > is not liable for any loss or damage arising from this message. > > The information in this email is confidential and may be legally privileged. > It is intended solely for the addressee(s). Access to this e-mail by anyone > else is unauthorized.
