Hi all,
Like well explained in the OSSEC documentation, I "upgraded" my OSSEC
server to log into mysql database. I compiled OSSEC with setdb and
updated the previous installation.
I got mysql and OSSEC server working on the same machine.
I made the ossec database with the mysql.schema file and cr
information (may be I should change mysql logging level).
Texte editor is ready to get creative :)
Thanks
On Wednesday, May 9, 2012 1:16:47 PM UTC+2, secatoor wrote:
>
> Hi all,
>
> Like well explained in the OSSEC documentation, I "upgraded" my OSSEC
> server to l
dy to get creative :)
Thanks for your help.
On Wednesday, May 9, 2012 2:47:55 PM UTC+2, dan (ddpbsd) wrote:
>
> On Wed, May 9, 2012 at 7:16 AM, secatoor wrote:
> > Hi all,
> >
> > Like well explained in the OSSEC documentation, I "upgraded" my OSSEC
&
7;s realy queer ! Seems that there something wrong with mysql...
On Wednesday, May 9, 2012 1:16:47 PM UTC+2, secatoor wrote:
>
> Hi all,
>
> Like well explained in the OSSEC documentation, I "upgraded" my OSSEC
> server to log into mysql database. I compiled OSSEC with
ing (timeout or
maxConnection) that I should change ?
Le mercredi 9 mai 2012 18:35:32 UTC+2, Scott VR a écrit :
>
>
>
>
>
> On May 9, 2012, at 6:16 AM, secatoor wrote:
>
> > Is there something specific I have to tell OSSEC to make it stop
> > logging into log files
.. Is there a kind of time out or
other parameter I should modify ?
On Thursday, May 10, 2012 1:54:04 AM UTC+2, Scott VR wrote:
>
>
>
>
>
> On May 9, 2012, at 11:35 AM, Scott VR wrote:
>
> >
> >
> >
> >
> > On May 9, 2012, at 6:16 AM, secato
is currently no way to not log to text files, and to change that
> you'd have to modify the source code. This isn't something I'd
> consider a feature though.
>
>
> >
> > On May 10, 2012, at 4:36 AM, secatoor wrote:
> >
UTC+2, dan (ddpbsd) wrote:
>
> On Thu, May 10, 2012 at 11:32 AM, secatoor wrote:
> > Well, stoping OSSEC loggingg to log files is not really the problem, I
> can
> > handle that with a script...
> >
> > What I really would like to have is all the logs into mysql b
u can see OSSEC succesfully connects to mysql. I think there must be
something with mysql, but because I don't get it's log verbose higher it's
not going to be easy.
Any idea ?
On Friday, May 11, 2012 2:09:18 PM UTC+2, dan (ddpbsd) wrote:
>
> On Fri, May 11, 2012 at 3:
r not.
I also noticed something that seems important !
I just droped complete database and when database is just freshly recreated
it starts to log without any problem, (if I use "select * from data" it
shows every action that happend since ossec started).
I see exactly the same th
't got the mysql server
response).
Strange...!
On Monday, May 14, 2012 5:33:15 PM UTC+2, dan (ddpbsd) wrote:
>
> On Mon, May 14, 2012 at 11:22 AM, secatoor wrote:
> > The last logs from ossec-dbd are those:
> >
> >
> > 2012/05/14 09:24:57 ossec-dbd: DEBUG:
11 matches
Mail list logo
