This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Event monitor - no heartbeat

Hi,
using nsm 3.1.1 for AD (servers are 2008R2) and suddenly new users are not being managed. I have restarted the server and restarted services but I am now getting no heartbeat in the NSM dashboard and if I try and manually restart the nsm event monitor service, it gets stuck in the "stopping" state, I can kill the process from task manager and then restart the service but it still doesn't work. When I checked the server because there were issues reported with new account creation there was no indication in dashboard that there was a problem with the event service but since I restarted it it doesn't see the heartbeat. It looks like the problem has been there for a few days going by the last modified date on the e-cache database. I carried out the standard prune routine for the ecache database (i.e checking for cached events, stopping the services and renaming the database) when the service was restarted, the new database was created but the modification stamp hasn't changed (I'm assuming because to all intents and purposes the event service is not running)

any help would be appreciated. It has been running happily for over two years.

Thanks,

Dave
  • 0
    Davey1 wrote:

    > using nsm 3.1.1 for AD (servers are 2008R2) and suddenly new users are
    > not being managed. I have restarted the server and restarted services
    > but I am now getting no heartbeat in the NSM dashboard and if I try
    > and manually restart the nsm event monitor service, it gets stuck in
    > the "stopping" state, I can kill the process from task manager and
    > then restart the service but it still doesn't work. When I checked
    > the server because there were issues reported with new account
    > creation there was no indication in dashboard that there was a
    > problem with the event service but since I restarted it it doesn't
    > see the heartbeat. It looks like the problem has been there for a few
    > days going by the last modified date on the e-cache database. I
    > carried out the standard prune routine for the ecache database (i.e
    > checking for cached events, stopping the services and renaming the
    > database) when the service was restarted, the new database was
    > created but the modification stamp hasn't changed (I'm assuming
    > because to all intents and purposes the event service is not running)


    Any errors in the event monitor log?

    --
    Your world is on the move. http://www.novell.com/mobility/
    Supercharge your IT knowledge. http://www.novell.com/techtalks/
  • 0 in reply to 
    In the event monitor log I have just found that it is reporting ES event sender subsytem failures. I have also found in the engine log is an error #314 reading event record request from (nsm server ip) and this starts at the same time as the last update timestamp on the ecache database so it looks like it cannot talk to the database. The database, event monitor and engine all run on the same server so it isn't a network connectivity issue.

    Dave
  • 0 in reply to 
    Also, just to add,NSM dashboard now thinks the heartbeat is ok but it is still generating errors in the log (so I feel better about not noticing it for a while!!)