shaun_9999

As an update and under the advice of my manager... I have been instructed to build an entirely new platform in hopes that there was a slight hiccup in many part of the upgrade. So I will see how that goes. I will let people know of my findings.

That is myself. How can I help?

This patch is a literal piece of s**t. Now, after discovering that this morning ALL of front-facing server is broke. I can't connect to anything to the box. A reboot causes it to flat out fail and not connect to any part of the server. It's actually a joke now and although you might say you've not had problems in testing,…

Looking at the event logs I have noticed that you get an insufficient memory every time it fails. Application: SolarWinds.BusinessLayerHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Net.Sockets.SocketException at…

This morning it failed again. After restarting the server (twice) restarting services (a lot of times) solarwinds config (4 times) Rebuilding the site (2 times) It is now finally working after messing about with it for three hours. Also, 1. stop IIS 2. Stop all Solarwinds Services on that device 3. delete the following…

Although not an official fix...much like he RDP issue that occurred in May. This very well could be a work around until something is more permanent.

I have raised a ticket with solarwinds (00117521) And I have done a diagnostics for them to view too.

I still have the same problem I had yesterday: the application is in a state of unknown. any ideas?

After adding the node as per the other nodes credentials, it has added, but it's in an unknown state. I will wait for the pollers to poll and see what happens.

Bump

Be ready for think 'omfg...what is wrong with their environment' .2.2.2 .2.2.2 Node status is Up. - BASCSI-CSWL-1 Node status is Up. ..2. ..2. Node status is Unmanaged. ntp1.csdsse.com Node status is Up. .3.. - SL4CSS-EVBL-2 .3.. Node status is Up. 7.33.1.65 7.33.1.65 Node status is Up. AgentVMware (AgentForVMware-vSphere)…

See I thought it was how I was doing my logic. But I really hate 137 alerts sitting there being a f*****g annoyance. I don't even know where this hate has come from with alerting, but it's all I can think about. I know I can make it better, but I am unsure how at the moment. I might think about it the weekend. If you are…

I am not allowed coffee for the simple reason that I had never drunk it until a couple of weeks ago. The caffeine stimulation made me go a little weird and I kind of didn't concentrate for the rest of the day and it rolled onto a good portion of the evening. 

Add the cluster and then add the two server, but poll them as WMI (you are going to be monitoring the services, drives and any other resources.) All of your resources will be added to the cluster IP address. The services will be added to the nodes themselves.

Hmm is that something you configured yourself? Or is it something that just appeared?

Bump.

Nope. This particular node is on a different subnet. Though I can poll the node via SNMP and via WMI. If I could poll, then I should be able to monitor performance counter shouldn't I? 

as an update - it has murdered the resources of the front-end facing server. I have performed the following to resolve the incident: - rebooted/repaired the Orion services. - Cleared the temp file. - Run a config. - Reboot the server. - Remove some dynamic queries.

Solarwinds have claimed that the link went down on the database side, I'm not sure that's true as we were still get every alert, save the node down/reset alerts. And they were being triggered in the logs.

It takes about a minute to do now. So I'm not sure. I suppose I just need to chuck it on a domain and see what happens.

I have already thought about it a little more and seen a few forum posts regarding this. The answer is to give it enough threshold so that if you get a spike for more than x amount of time, you would need to investigate. Rather than leave the issue to slowly grow until it's broke and requires a reboot.

Just a quick update. From moving the services over to my less broken server I am able to install solarwinds again (currently running the config and install) if this works then This should be a sticky for anyone else who's stupid and doesn't take a snapshot.

I actually forgot all about this. I should see if this is still a problem. Or maybe write things down a little more.

Just to add clarity.

As an added note - the alerts are being triggered on the front end, but not on the back end, as in the solarwinds database are not seeing it on the SQL side. 

I think I have figured it out. When you failover, it takes seconds to move from the active to the passive. So I will never see an alert about it. Is it still worth having an alert to see if the cluster fails.

As an update - I removed and added some nodes to some groups and they have not updated. I have removed/added the group. Rebooted services and still nothing. it still shows the oldest information. Am I missing a trick here?

bumpy mc bump

Bump

Just as an update - everything seems to be working fine now. It was all due to an issue on some firewalls that will be scrapped eventually. But it's still a pain in the bottom. I was getting frustrated and angry because I have devised an almost military like plan and expected it to work as intended. After about six weeks…