(ddpbsd) wrote:
>
> On Thu, Apr 18, 2013 at 4:17 PM, w3ndtr >
> wrote:
> > Dan,
> > I stand corrected. I thought it was all better, but then I checked the
> web
> > interface and all clients were inactive. I then found the below in the
> log
> >
.
On Thursday, April 18, 2013 2:47:22 PM UTC-5, w3ndtr wrote:
>
> Dan,
> Thank you for the suggestions. I gave it another try with the below
> process I no longer get the database connection error.
>
> process:
> stop ossec
> stop mysql
> remove the database section fr
the database disabled (did not work -> had
to remove all database entries from .processlist)
started ossec
watched the ossec.log
On Wednesday, April 17, 2013 11:53:59 AM UTC-5, dan (ddpbsd) wrote:
>
> On Wed, Apr 17, 2013 at 12:36 PM, w3ndtr >
> wrote:
> > Hello,
&g
Hello,
I am currently running ossec 2.5.1 and will be upgrading to 2.7 in the next
few months. The ossec server was first installed with the database enabled
from the steps on the wiki walk-through. It has been running fine, but the
database has never been used and I would like to remove that
t; On Wed, Nov 7, 2012 at 10:58 AM, w3ndtr >
> wrote:
> > I have OSSEC 2.5 server up and running currently without any issues with
> > agent monitoring and will be upgrading to the newer version next year.
> Is
> > there a way to scan a NAS device with the agent or agent
I have OSSEC 2.5 server up and running currently without any issues with
agent monitoring and will be upgrading to the newer version next year. Is
there a way to scan a NAS device with the agent or agentless monitoring?
The specific NAS that I am looking to scan is a EMC Celerra.
