Comments
-
First comment
-
Didn't realize this could be done. Cannot wait to give it a try.
-
What is the point? This is a HUGE pain for some of us and has been a suggestion for 6 YEARS! And look at all the votes! Obviously voting for these "feature requests" does nothing.
-
This is expected behavior I believe.
-
I would modify the /etc/ssh/sshd_config file: LogLevel DEBUG Then on the ssh server run: tail -f /var/log/messages Then try the connection from SolarWinds and it should give you an indication on why it is failing. Let me know if that helps.
-
I feel the same regarding mission shortcuts. It gives points but does not specify which mission shortcut as I know I am missing points for quite a few, but I do not know which ones to specify.
-
We have a custom property Environment which we have populated with Linux Non-Prod or Linux Prod. I have two of these set up, one for non production and one for production.
-
These are Linux Servers RHEL 7.5, some SLES11
-
I had this issue with AIX as well. The issue was the file /opt/SolarWinds/Agent/bin/cert/SWI-Agent-SecureString-[RANDOMCHARS] I seen in the log it was looking for a cert with one name but the actual cert had another. The only way I found that fixed it (copying the file did not work) was to create a symbolic link with the…
-
how much is it?
-
Same
-
see
-
Hello?
-
Nice
-
Amazing! Good Job WLUTHER!
-
I am not receiving any points for this.
-
My application monitor template has the following component monitors: Inode check - grabs the value of .1.3.6.1.4.1.8072.1.3.2.3.1.1.5.105.110.111.100.101 NFS check - grabs the value of .1.3.6.1.4.1.8072.1.3.2.3.1.1.3.110.102.115
-
I would love an answer to this! I have tried everything, and I can see no way to currently implement discovery of nodes with the agent. It doesn't make sense.
-
I am having the same issue. I believe they have reset them for me as I now am getting credit for things, but I should already have credit as I have completed all of this prior. I also do not get credit for monthly mission shortcuts.
-
How many processes are you wanting to monitor? You could create one application template and then add multiple component monitors, one for each process:
-
I just spent an hour on a webex going over SCM with someone. Talk to Matthew H.
-
Your question is extremely vague. What is it you are trying to do? Some things can be done with the API, while others cannot.
-
auditpol /set /subcategory:"Handle Manipulation" /failure:disable
-
Check the permissions of the folder /opt/SolarWinds/Agent/bin/appdata/Logs - we found many of our application templates had unknown status until a restart (temporarily), but changing the folder permissions for world r/w seemed to fix it permanently.
-
Sounds like it should be basically the same. Here is the documentation: https://docs.fortinet.com/uploaded/files/4324/fortigate-logging-60.pdf
-
We used to deploy the Agent and did not have serious issues with it. We deployed using ansible, by copying the tarball over and running the install.sh
-
Every time I turn around I run into one of these weird issues with SolarWinds.
