On adding a resource to be monitored, I get a message "Service is not running" (or) some of my monitored resources generate false alarms.
Reason: During Monitoring, The message 'Service is not running' or 'Resource is not available' is displayed if the service/resource is actually not running in that host or the service is more loaded that it takes more time to respond.
False alarms are also generated when services such as Tomcat, WebLogic, JBoss, Ports, Oracle, MySQL, MS SQL are more loaded and take time to respond.
Check for the following:
1.Can ping the host - "ping <host>". Also, check if there is any spelling mistake in the hostname.
2. Execute the Telnet command- "telnet <host> <port>" from AppManager machine.
3. Check if the Subnet mask provided is correct. Inspite of the checks, if you still get the error, send the support information file to appmanager-support@manageengine.com.
Solution: By default, if the service does not respond within 15 seconds consistently in all regular polls, alarms are being generated. You can change this default value of 15 seconds. To do so, follow the steps given below.
1. Edit the file AMServer.properties located in the <Applications Manager Home>/conf directory.
2. Change the time (in seconds) set for am.sockettest.timeout attribute as 60
3. Restart the Applications Manager Server
New to ADSelfService Plus?
Related Articles
Service is not running error troubleshooting
Follow the below steps to troubleshoot the error Check if the service instance is running in the host name specified. Check if the port number is given correctly. Retry with the "SSL is enabled" option both enabled and disabled in the add/edit ...I am not able to view monitored data in SNMP mode, I get the "No data Available" message.
If you are not able to view the monitored data in SNMP mode, the following are the possible reasons : SNMP service is not enabled on the server. Make sure SNMP service is installed and is running. The SNMP request might have timed out. Refer here. ...I'm not able to monitor the JBoss Application Server and I get an error message.
The below troubleshooting steps are for JBoss version 6 and below. Step 1: JBoss host and Applications Manager host are not accessible from each other. Applications Manager collects JBoss MBean details by directly connecting to the JBoss JNDI Naming ...In Service Monitoring, while trying to discover SNMP Agent running at 161, a message "Service is not running" is displayed.
The Service is running over UDP (User Datagram Protocol). Service Monitoring can discover services running in only connection protocol such as TCP (Transmission Control Protocol). Solution: Discover SNMP Agent through Services->SNMP Agent. Refer ...Best Practices in adding Microsoft 365 monitor
From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated from PowerShell to Graph API as Microsoft 365 PowerShell commands were taking more time to ...