On Thu, Mar 12, 2015 at 5:30 AM, CraigL <[email protected]> wrote: > Apologies for the delay coming back to you on this, I have just updated our > test install with the latest ossecalert branch, and removed my cron job to > restart the agent at midnight. I will report back tomorrow with results >
Thanks, but I think it'll have the same roll-over problem. Still debugging this issue. Hopefully I can figure it out before 2.9. > Thanks, > > Craig > > > On Wednesday, 25 February 2015 20:24:31 UTC, dan (ddpbsd) wrote: >> >> On Thu, Feb 19, 2015 at 8:58 AM, CraigL <[email protected]> wrote: >> > >> > >> > On Thursday, 19 February 2015 12:15:31 UTC, dan (ddpbsd) wrote: >> >> >> >> On Thu, Feb 19, 2015 at 3:14 AM, CraigL <[email protected]> wrote: >> >> > Further update, while I haven't seen the usual "File not available >> >> > error" no >> >> > logs have been sent to the central server since after midnight which >> >> > leads >> >> > me to believe that some part of the logrotate process or this patch >> >> > for >> >> > alerts.log may not be quite there. >> >> > >> >> >> >> Alerts were being sent successfully before midnight though? >> > >> > >> > Yep, last log generated and received was 23:56, then nothing until I >> > restarted the agent this morning. >> >> If you still have the test environment setup, please try my ossecalert >> branch: >> https://github.com/ddpbsd/ossec-hids/tree/ossecalert >> >> I just started a test run here, and more testing is good. > > -- > > --- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
