Good morning er....fellow winders...(?)
I had an issue with a node that I needed to remove and then add into solarwinds. It was part of a action monitor template and I have been trying to add it back into the template. For the love of me I cannot seem to get any credential to get authority from the server.
I have tried my own account (A domain admin account) the svc accounts (that lave local admin permissions) that can logon to the server, every account that was memorised within solarwinds. Removed it, added it, I have tried to see what credentials the other nodes have (there are 4 in total for this template) Nothing. Not even shouting at my screen and then crying into my water has resolved the issue.
Could anyone with some insight provide me with some advice.
I suspect the node is the issue. If you have already re-added it then doing that again will not help. If other nodes are working then the underlying processes must be. Is it possible the server has dropped out of Active Domain?
That's what I thought yesterday. As the failover was perfectly fine to add monitoring and was working fine with credentials. But then I went to the server in question and it's was kinda fine yesterday after removing it and then adding it, but today it flat out refuses to monitor anything. When it does it's in an unknown state.
The node is connected to the domain as it's part of a cluster.
Yes. If I run a test ping from solarwinds it is successful. It can see the CDM (CPU, Drives and memory)
the values and thresholds were already amended as it's an SQL server. Again, that's perfectly fine.
Thank you for your help btw.
I would try adding the node again (without removing it) by IP address. Solarwinds will come up with this
Press the Re-Add ---
Just in-case there is a rogue entry somewhere ... It should pick up the applications so no need to re-add/apply those, just next>next it all.
let me know if that helps ... otherwise I am exhausted for ideas as not seen before .. could be time for a Solarwinds Tech Case
I did re-add it and then click next as instructed. I still have the same issue. I will raise a call to solarwinds and see if they have any ideas.
Thank you for your time and effort.
How weird. I have found (while casually exploring our environment) that ALL of the appinsight nodes are in a state of unknown.
Once I have moved some monitoring on some nodes I will have a look later today or tomorrow to see if the same thing is happening with all of them. I think it might as they are all exhibiting the same symptoms.
With regards to other nodes/other applications.
I did a test on another server and the server in question. I was able to add other SAM's and they produced an up/down state (depending on what I added. I added one up and one down on two servers.)
When you say logging, are you referring to the logging within solarwinds, or the event logs within windows.
That's interesting. I ran the same app jobs this morning (Windows even log monitor) on the server in question, with the same credentials as yesterday afternoon and it appears to be hanging.
might there be an issue with the node? I did sort of suspect that this morning, but thought to try other routes before making an assumption.
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. Learn more today by joining now.