NSM engine does not listen after upgrade to 3.0.1
A colleague of mine upgraded Storage Manager from version 220.127.116.11 to 3.0.1 on Friday, but after the upgrade the engine doesn’t listen on any port any more. Due to a big backlog (140’ events), the engine was set to no longer accept new events a day before – could this be the cause of this problem?
Things we have tried:
- Downgrading to 18.104.22.168
- Changing the port number
- Enabling the http port
The event monitor reports that the engine is not accepting new events, and the admin console reports that it is unable to communicate with the engine.
Tags for this Thread