charlesjsmith

Were you able to change out the certificate for rabbitmq? I'm having similar problem.

I'm on 2020.2.6 and I can confirm the behavior if an APE goes unreachable via ping (monitored via ping from our main polling engine) and does not update the database (showing red in polling engines page) everything pretty much freezes that was monitored by the APE It makes sense to me to have items monitored by the APE…

Same here. I have a case 01582121 - completely ignored Mar 12-13. Today I just received a message that they are reviewing my logs.Thursday, March 14, 2024 10:02 AM. Not sure what is going on but its not very good customer service. I had the same issue with my last case. It's really frustrating.

Hi Adrian. Thanks for sharing this information. I'm planning to do similar in the near future and i am running at the same version you were and planning to go to the same release you did. If you don't mind sharing, i'm wondering what the hiccups were that you mentioned " just a couple of hiccups that had already been…

In Dev I upgraded from 2022.4.1 to 2023.1. I have 1 MPE and 1 APE. I ran the installer as admin. I performed the pre-stage just to test and that went fine. I then moved on to the install portion. The install on the MPE hung at 3% but i was busy doing other work and then went to lunch. By the time I got back the screen was…

Great write up. I too noticed the .4 is lingering just around the corner so I'll probably wait to upgrade, if possible since it has the additional vul fixes, until .4 comes out of being a RC and becomes more GA.

I do see a StatusValue column in table [SolarWindsOrion].[dbo].[NetPath_Tests] with values like 100. Not sure if i am on the right track.

Did you ever find an answer to this? We tried many different things but none really do it well. 

*

Ok. New information. I WAS able to use the Pre-stage feature with the offline installer to upgrade from 2020.2.5 to 2020.2.6 HF4 (Orion) and HF3 for my modules - npm, wpm and udt. High level. Use the offline installer to pre-stage the main polling engine. Then you go to the My Orion Deployment on the web to perform the…

I was hopeful for a smooth change as I've spent a lot of time reading thwack, release notes and so on . I upgraded 2 different lab environments that are nothing like our production but i was looking to learn the best i could and it did help some but still not enough. So.. here is my experience. When my installer kicked off…

This is what i have learned from the resources i am talking to: ONLINE installer - will pre-stage the main and additional polling engines. OFFLINE installer - will only pre-stage the main polling engine. At upgrade time the files will be copied over from main to APE's as part of the Centralized Upgrade. I was hoping that…

Did you ever receive a response for this issue?

Did you ever receive a response for this issue?

Thanks for the response. I click search in an inactive session from earlier and perform the search. Search results come back quick, then click on a node and that's when i experience the unexpected error. 

I found the mibs which are tables and then created custom pollers 1.3.6.1.4.1.9.9.109.1.1.1.1.12 - mem used 1.3.6.1.4.1.9.9.109.1.1.1.1.13 - mem free Manipulate as you see fit. Did the trick for us. B/r, Chuck

I'm running into similar issues you all describe. Seems the mibs being polled by default are not accurate and i have also tried making my own custom poller using 1.3.6.1.4.1.9.9.48.1.1.1.5 (used) 354916752 1.3.6.1.4.1.9.9.48.1.1.1.6 (free) 497362912 no luck though as the numbers do not come close to show platform…

Thanks for asking, i had completely forgotten about this post, ha... So yeah I ended up finding out it was SCOM monitoring causing the issue (well actually APMagent which is a sub module of the scom monitoring). I removed scom (Monitoring Agent) from the npm primary server and wow, things cleared up for everyone and mcafee…

Thanks Chris. I found the answer (at least for the issue we were experiencing) it had to do with ipv6 being enabled on the primary servers interface. I stopped orion services disabled ipv6 on the nic, restarted the orion services and the error has been non-existent. Thanks for taking the time to respond!