wlouisharris

Ok, thank you Thwack admin for correcting my issue. Good day.

Thank you. If they can create a KB article it could save support calls. It's a very easy fix.

We just did the 12.4 upgrade. We ran into an issue and later found fix from some members on the the Thwack forum. It would be helpful if all your support reps are familiar with this error. We had to run the installation manually as a workaround: NPM 12.4 - Error during contacting servers: Another Installation Session is…

Hey Serena,we would also like information on how we can perform upgrades without downtime. I have opened a case and also referred this to our product manager.

We upgraded our QA silo and we have have had issues with the license store getting corrupted. I've been working with support on this. Re: NPM 12.5 upgrade - installation issues and corrupt license store I'm not sure if we had something environmental prior to the upgrade but we are not going to upgrade our production silo…

Thanks. The database maintenance issue a documented case. The issue where the node management page does not load may be environmental so I'm waiting to hear back from support. 

Sure, I assume you are with support. This case is directly related to the DB maintenance issue - case # 01760181. The 2nd case I opened I have not correlated with 2024.2.1 but we did not start seeing this until we upgraded which is case # 01759940. I have escalated case # 01759940. My contact information is in the case #…

At first everything seemed ok with the upgrade to 2024.2.1. We have noticed the node management page won't load when trying to add nodes. We have to reboot the main poller. I started looking if there was a new release, and there is a Release candidate - 2024.4. I started looking through the release notes and they indicate…

To add, we aren't going to upgrade to any version until Q1 of 2024 unless there is some major bug found or security patch we need. 

FWIW we haven't seen any problems with job engine failures. I think the big thing is moving to the new platform that consolidates the installer to one package; which in turn will make future upgrades much faster. We are going to 2023.3 and will probably wait for the stable release in 2024. 

We have a large environment. About 120K elements and our SQL DB is around 1 Terabyte. The element # is not x-large but the data we collect and DB size probably constitutes x-large. Support is telling me the DB maintenance has been slower starting before the upgrade. I just started noticing the log was not indicating…

We're in a similar boat. We are on 2020.2.5. We skipped all the 2022.x versions. We were set to upgrade to 2022.x in February but we found out those version had a bug with Netpath which is heavily used by my Ops team. The 2023.x versions were still in RC so we held off. We hit change freezes in the meantime. We're at the…

We just upgraded our QA environment from 2022.3 to 2023.1. We did not have any issues. We ran the offline installer from the main poller. The configuration wizard did take a very long time to run, but completed without any errors. After that we completed the upgrade from the console using the central deployment tool. It…

I'm glad to see 2023.1 is released as a GA now. We upgraded our QA instance to 2022.3.1. We had some issues with the install and had to do a great deal of it manually and had to reinstall the software on several hosts. After talking with support they confirmed that they had a lot of support calls on 2022.x versions. There…

That's the way we worked around access for accounts without admin access in Solarwinds. This is the cmdlet: PS C:\Users\user> $swis = Connect-Swis -Trusted -Hostname solarwinds-app-server

Keep us posted. I also have a Windows 2012 R2 environment. We had a lot of problems with version 11.5 and 12.01. We really stabilized our environment with version 12.1 so we are holding off on upgrading to 12.2. We will probably do version 12.2 in QA soon.

We had a similar issue after upgrading to version 12.1 where we had a memory leak. It turns out our problem was related to a bad dashboard. The dashboard was doing a long running query that never finished and spike memory. It has been my experience with the product most CPU and memory issues are tied back to something that…

Serena, this KB article, correcting the site bindings, did resolve our issue.

Here's the case # - Case # 00415997

Hey alterego - here is the support case # - CASE # 00276075 - HA POOLS SWITCHING TO UNKOWN STATE

It's frustrating for sure. I was wondering if this was a fixed issue in NPM 12.4 but apparently not. The problem seemed to surface around the time we added additional pollers. The new pollers we added do not utilize HA. I have also noticed if you do not space out the HA restart on the main poller pool it will trigger a…

We use Bluecat DNS. We had to end up using a 128 bit MD5 key to get it to work. Of course the newer security standard is SHA2(256 bit)keys. Basically we had our DNS team create a new zone for Solarwinds called solarwinds-ha; then they had to delegate us to have root privileges within that zone. From a process standpoint it…

Ultimately support told us this is a known issue with 12.4 and we should upgrade to 2019.4. We have an upgrade coming anyways so we will try it. It sounds like building a new VM and just setting up a new web server is the easiest solution. It's just not easy for us to trade in our VM's.

Thanks. Just to clarify my question. We know the solutions to resolve the polling engine down. We just want to be able to effectively monitor the condition. The out of box monitors I mention are not catching this condition.

I get an error and I simplified the query but still get the same error. 1)Here is the simplified SQL query: SELECT TOP 10000 Nodes.NodeID AS NodeID, Nodes.DNS AS DNS, Interfaces.InterfaceID AS InterfaceID, Case InBandwidth When 0 Then 0 Else (In_Averagebps/InBandwidth) * 100 End AS Recv_Percent_Utilization, Case…

Hey Bartley, what server O/S verions are you running? I am running Windows 2012 server and NPM 12.1. We had extreme difficulties with installers when we were on Windows 2008 R2 server, but as we refreshed to 2012 server we are having less problems. What are the specs on your servers? We have 70 gig C and 40 Gig H on our…

We did finally close our case. I have seen the our HA environment stay in healthy state for over 10 days now. So yes, if you have your HA pool go to critical state, look for any SQL errors in the Solarwinds event log and make sure SQL connectivity is not the root cause.

I changed the query a bit. It looks like status=1 is healthy in the HA.poolmembers table. We basically wrote an alert looking for this condition. SELECT HostName, Status, LastHeartbeatTimestamp FROM Orion.HA.PoolMembers WHERE Status != '1'

Thanks - yes we do have the checkbox ticked off for this setting:

Thanks. Did you repair core services on all your Orion servers? I assume I would need to do app server, APE's, and web servers.