-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of dan (ddp)
Sent: Friday, July 06, 2012 9:39 AM
To: [email protected]
Subject: Re: [ossec-list] OSSEC Clients stopping

On Fri, Jul 6, 2012 at 9:25 AM, william allen <[email protected]>
wrote:
> I know this is a normal occurrence with OSSEC.  But  when it does the 
> shutdown it does not come back up.
>
>
>
> 2017/07/05 10:42:01 ossec-logcollector(1225): INFO: SIGNAL Received.  
> Exit
>
> Cleaning..
>
> 2017/07/05 10:42:01 ossec-logcollector(1225): INFO: SIGNAL Received. 
> Exit Cleaning.
>
> 2017/07/05 10:42:01 ossec-agentd(1225): INFO: SIGNAL Received.  Exit 
> Cleaning.
>
> 2017/07/05 10:42:01 ossec-execd(1314: INFO: Shutdown received.  
> Deleting responses.
>
> 2017/07/05 10:42:01 ossec-execd(1225): INFO: SIGNAL Received.   Exit
> Cleaning.
>
>
>
> I do not get the following startup PID command?
>
>
>
> 2012/06/29 11:42:51 ossec-execd: INFO: Started (pid: 13571).
>
>
>
> Thanks,
>
> Scott Allen
>
>
>
>

You want all of the daemons to output the "Started (pid: xxxxx)" message?

>
>
>
Not really important. Maybe I didn't explain very well.  I am just wondering
why on a few of my boxes the client stops with the above cleaning items and
doesn't restart after completion.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to