Hi,
Looking at the wiki
http://www.ossec.net/wiki/Know_How:DatabaseOutput#Create_a_user_for_OSSEC
and configuring mysql,
I think there is a line missing, or at least comment that it might be needed
eg.,
CREATE USER 'ossecuser'@'localhost' IDENTIFIED BY 'ossecpass';
before creating the data
Hi,
I just installed the agent and server via rpm to a RHEL6 setup,
however when I run the scripts in ~bin to configure the agent on the
remote RHEL box it does not ask me for the server IP.
There seems to be no man page etchow do I setup the agent to point
at my remote control server? or wh
Hi,
I just installed the agent and server via rpm to a RHEL6 setup, however when I
run the scripts in ~bin to configure the agent on the remote RHEL box it does
not ask me for the server IP.
There seems to be no man page etchow do I setup the agent to point at my
remote control server? or
In my environment, I use a combination of OSSEC RPM (I built it) and
puppet to download, deploy and auto-register my agents.
I obviously use OSSEC 2.6.
-Stephane
On 11/15/11 10:53 AM, "ninefofo" wrote:
>
>Hey, its noob again.
>
>Any direction I can take on unattended/silent installs?
>
>Thank Yo
I don't know if there are guidelines per se, but what I did is wrapped the
installer on Windows with an autoit script and provided a pre-filled ossec.conf
for the server IP. On Linux I have a script that wraps the ossecbatch perl
program that comes with it, and parses for the key to send over to
Hey, its noob again.
Any direction I can take on unattended/silent installs?
Thank You
Brad
On Nov 9, 2:58 pm, ninefofo wrote:
> Hello,
>
> noob here.
>
> Are there any guidelines on installing the agent unattended, supplying
> the server IP, Key and Starting auto-magically?
>
> Thanks
>
>
The temporary files are located at /var/ossec/logs/ directory with
file names looking like ".report-%d.log", where %d is a number
(pid).The ERROR message means such a temporary file cannot be
opened for WRITE.
Check if any such old files exist. You may want to clean them up.
On Nov 15, 1:56 a
I have configured the install to allow for database support, but when
I run the install script it fails during the make os_dbd portion. I
got no error messages when configuring the install with 'make setdb',
so I believe I have all libraries I need.
*** Making os_dbd ***
make[1]: Entering direct
Hello ,
Is there a comprehensive document, quick reference or so , with
Occec's xml syntax (tags, otpions etc) ?
Thank you
On 11/14/2011 10:19 AM, Holger Gläß wrote:
hi
i got this weekend this error message below ...
ossec-monitord: ERROR: Unable to open temporary reports file.
nobody knows ?
it is the 2.6 version , and i disable all configured reports
in ossec.conf to fix the problem.
holger
whats wrong ? ,
10 matches
Mail list logo