Re: [ossec-list] OSSEC 3.3 - OSSEC not compiled with support for 'mysql'

2020-02-05 Thread dan (ddp)
On Wed, Feb 5, 2020 at 7:49 AM dan (ddp)  wrote:
>
> On Fri, Jan 31, 2020 at 2:28 PM Natassia M Stelmaszek  wrote:
> >
> > I performed my original installation without database support because I 
> > didn’t want to complicate things.  When I went to re-compile/reinstall with 
> > the database support included I kept getting the above error.  I finally 
> > fixed it by deleting the object files (*.o) in the scc/os_dbd directory 
> > before recompiling.
> >
> >
> >
> > The developers might consider putting “make clean” as a standard part of 
> > the install process or at least including a note on the page
> >
> > https://ossec-documentation.readthedocs.io/en/latest/legacy/docs/manual/output/database-output.html
> >
> >
> > About the necessity of cleaning the files before recompiling.
> >
>
> Thanks for pointing this out. I think this was one of those "it's
> obvious to me" things that I just skipped over.
> I added instructions to the dev branch in ossec-documentation, and
> submitted a pull request for ossec-docs
> (https://github.com/ossec/ossec-docs/pull/295).
>
> >
> > Also – In the printed book on page 75 it says that you can check to see if 
> > the installation was configured with database support by running
> >
> >
> > /var/ossec/bin/ossec-dbd –V
> >
> >
> > Which would return the information “Compiled with MySQL support” or with 
> > PostgreSQL or without database support.  But the book was written for v1.4 
> > and it doesn’t give that information when you run that command in v3.3.  
> > You might consider restoring that to the –V message.
> >
>
> I'll look into this.
>

Pull request submitted: https://github.com/ossec/ossec-hids/pull/1833
I'm not sure what the previous output looked like, so this may be a
bit different.

> >
> > Natassia
> >
> > --
> >
> > ---
> > You received this message because you are subscribed to the Google Groups 
> > "ossec-list" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to ossec-list+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/ossec-list/0dcd26c1-1881-4091-9b75-f3cfd029725d%40googlegroups.com.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ossec-list/CAMyQvMrDf5j5%3DZdisYt600qMG58FA9cHqjW05X%2BEy76KfUwkmw%40mail.gmail.com.


Re: [ossec-list] OSSEC 3.3 - OSSEC not compiled with support for 'mysql'

2020-02-05 Thread dan (ddp)
On Fri, Jan 31, 2020 at 2:28 PM Natassia M Stelmaszek  wrote:
>
> I performed my original installation without database support because I 
> didn’t want to complicate things.  When I went to re-compile/reinstall with 
> the database support included I kept getting the above error.  I finally 
> fixed it by deleting the object files (*.o) in the scc/os_dbd directory 
> before recompiling.
>
>
>
> The developers might consider putting “make clean” as a standard part of the 
> install process or at least including a note on the page
>
> https://ossec-documentation.readthedocs.io/en/latest/legacy/docs/manual/output/database-output.html
>
>
> About the necessity of cleaning the files before recompiling.
>

Thanks for pointing this out. I think this was one of those "it's
obvious to me" things that I just skipped over.
I added instructions to the dev branch in ossec-documentation, and
submitted a pull request for ossec-docs
(https://github.com/ossec/ossec-docs/pull/295).

>
> Also – In the printed book on page 75 it says that you can check to see if 
> the installation was configured with database support by running
>
>
> /var/ossec/bin/ossec-dbd –V
>
>
> Which would return the information “Compiled with MySQL support” or with 
> PostgreSQL or without database support.  But the book was written for v1.4 
> and it doesn’t give that information when you run that command in v3.3.  You 
> might consider restoring that to the –V message.
>

I'll look into this.

>
> Natassia
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "ossec-list" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ossec-list+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ossec-list/0dcd26c1-1881-4091-9b75-f3cfd029725d%40googlegroups.com.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ossec-list/CAMyQvMovrupW0D36-8qLi0iwV4ZrujoqBFepVuv9Eu_G1QqWLg%40mail.gmail.com.