Messaging Gateway

 View Only

  • 1.  Cron

    Posted Nov 06, 2008 02:36 PM

    Every ten minutes I am getting an email from the server that says:

     

     

    Subject: Cron <root@spam> /opt/Symantec/Brightmail/cli/sbin/watchdog

     

    Other watchdog instance is running, running time = 300 sec, exiting

     

     

     

    It started after I enabled SNMP on the server. I am wondering if this is a result of SNMP being enabled. If not what is it and how can it be fixed? If it is because of SNMP, how can the alert be disabled?



  • 2.  RE: Cron

    Posted Nov 06, 2008 02:57 PM

    Same problem here ,I did nothing to configuration but i receive every hour a message frm Cron Daemon

    /etc/cron.hourly/logrotate:

     

    error: log /data/logs/mysql/error.log last rotated in the future -- rotation forced

    error: log /data/logs/mysql/slow-queries.log last rotated in the future -- rotation forced

     



  • 3.  RE: Cron

    Posted Nov 06, 2008 02:59 PM

    Hello,

     

    What version of the product are you using? We saw this in earlier versions and I believe it has been addressed since then.

     

    Let me know.

     

    Thanks!



  • 4.  RE: Cron

    Posted Nov 06, 2008 03:05 PM
    I am using brightmail gateway version 7.7.0-17.


  • 5.  RE: Cron

    Posted Nov 06, 2008 03:33 PM

    If you are still seeing this in 7.7 it could be load related. Generally when the Appliance gets under a heavy load it can throw watchdog errors. The document below talks a little about this.

     

    Title: 'Error "Other watchdog instance (pid xxxx) is running for more than 540 sec, killing it!"'



  • 6.  RE: Cron

    Posted Jan 16, 2009 05:30 AM

    Hello,

     

    I got exactly the same issue after enabling SNMP on brightmail (not yet in production, so it can't be a load issue). Scanners and CC are not on the same appliance.

     

    I'm running version 7.7 too.

     

    Any suggestion ?

     

    Thanks,

     

    Vincent



  • 7.  RE: Cron

    Posted Jan 19, 2009 01:40 PM

    Hello Vincent,

     

    The document that I linked earlier should still apply. The issue that you are seeing is non impacting, but understandably a nuisance. If you go through the steps outlined and the issue is not resolved, the error can be safely ignored.

     

    Thanks!

    Tom