Hi all. I've looked at different threads regarding emails failing out of NPM in general, but the traditional fixes aren't working for me. I've verified the SMTP server, I've sent test emails, and I get emails fine from NCM (which I installed the same day I upgraded NPM) - and the alerts appear to be firing fine on the alerts page/events page, but we've traditionally gotten emails for these events. I'm just not sure where to look to specifically troubleshoot emails with one portion of NPM and not Orion in general. All of the alerts that were there before are still turned on, but anything that shows up specifically on the "events" page is not generating an email like it was before. I've looked multiple times and cannot figure out where this is breaking. Any suggestions? Thanks!
The SolarWinds guys keep asking me for debugs with varying levels of logging and come back a week later wanting more. I find this process extremely unhelpful, to be completely honest. If I could go back and do it over again, I would absolutely not upgrade. YMMV, but the specific version I installed appears to seriously break alerting.
Our install has been severely affected by the upgrade. Many basic features broke. And we are in the middle of figuring out the best path to get back to normalcy. Rebuilding is a challenge due to varied complexities. Perhaps our installation consultant should not have deployed more than a single all in one PE with all products piled on one host. Single point of failure was a bad move.
There are other threads about 12.0.1 upgrade woes. So I'm not alone or whining.
That sucks. I had the problem where reboot alerts quit along with a few other annoying little things that I got resolved after a few hours. Mostly no one noticed aside from me so I was happy for that at least.
I plan to follow this at some point as my environment has been limping along and my network engineers are without a fully functioning NCM.
1. Backup your DB and SolarWinds machine/VM first. This is in case you have to go back.
2. Upgrade your current SolarWinds installation(s) in the correct order (in accordance with the product upgrade advisor ) so that it upgrades the database.
3. Build your new SolarWinds server using the same IP address and machine name. Obviously, disconnect the NIC until ready to put into production.
4. Install all the latest versions of the SolarWinds products that you just upgraded to (in accordance with the product upgrade advisor ) to a new (dummy) DB. This is just to get them installed. Create any name. This will be deleted.
5. Create backup of the new SolarWinds server so you have something to go back to if you need to later on. You don't want to repeat this build if you done have to. This is just in case something goes wrong.
6. Shut down or disconnect the NIC to the old SolarWinds server.
7. Bring up the new SolarWinds server and/or enable its NIC.
8. Run the Configuration wizard on the new server and map it to the upgraded DB from step 2.
9. Delete the dummy DB.
10. Decommission the old server after you have verified the new one is fine.
SolarWinds support took a look at it last week and has collected some diags and sent them off for their dev team to review. We tried a bunch of things, including this:
...but in the end, we still don't have any alerts firing. Not even basic ones. Not only do my events not create emails anymore, not even the built in stuff seems to be generating emails. If you run a test fire from a given alert, though, that does go through.
I have noticed that I have to restart my SW server about every 3 weeks to keep the emails alerts flowing. I did not perform a fresh install but rather an upgrade.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.