This error message indicates a general network connectivity error between the monitoring station and the monitored agent servers. It has only been seen on Windows monitoring stations and is generally resolved using one of the following methods:
Disable TCP Offload Engine (TOE)
If your monitoring station server has a TOE-enabled network card, you may need to disable it. TOE is intended to accelerate long-running TCP connections. Since up.time uses many short-lived connections to contact agents, its process can be mismanaged by the TOE. Please perform the following commands on the monitoring station to disable TOE:
If the TCP/IP Offload setting is not found by using the previous steps, you may need to disable the TCP Offload setting within another program or Windows service with an advanced network card configuration. For example:
Windows TCP Stack is overloaded
If up.time is monitoring more than 500 services, you may find that the default Windows TCP stack options are not sufficient to maintain the outbound up.time connections. In this case, we recommend adjusting registry settings on the monitoring station to relieve some common TCP bottlenecks:
Under the :HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters registry key, create the following new keys:
|
Windows Event Log Monitor returns Output: Monitor failed: For inp... | Rating | Views | |
---|---|---|---|
![]() |
This error indicates that the target agent server's up.time agent is incompatible with your monitoring station version. Please upgrade the agent on the impacted server and verify that this error is... By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 497 |
![]() ![]() ![]() ![]() ![]() |
3203 |
/var/adm/messages kernel: cdrom: open failed | Rating | Views | |
---|---|---|---|
![]() |
On some agent server configurations these types of log messages may appear whenever the up.time monitoring station attempts to contact the agent Jun 25 19:19:20 server1 kernel: cdrom: open... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 307 |
![]() ![]() ![]() ![]() ![]() |
4947 |
Error while pinging: Failed to create raw socket | Rating | Views | |
---|---|---|---|
![]() |
This error is commonly caused by permission problems on the icmp executable that up.time uses to verify the PING status for a monitored element. To resolve this issue review the information below... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 279 |
![]() ![]() ![]() ![]() ![]() |
7147 |
Still receiving alerts when topological dependency has failed | Rating | Views | |
---|---|---|---|
![]() |
When the host check for a topological host enters a failure state (i.e. WARN or CRIT), the service monitors for hosts that depend on that element will have their alerts / actions suppressed and... By: uptime Support | Date Created: 7-7-2011 | Last Modified: 8-11-2011 | Index: 533 |
![]() ![]() ![]() ![]() ![]() |
2062 |
Failed to Get Configuration message from Linux Agent | Rating | Views | |
---|---|---|---|
![]() |
This knowledge base article provides a workaround for the most common cause of the Failed to get configuration from agent error with Linux agents, which occurs when there is unexpected or... By: uptime Support | Date Created: 3-7-2013 | Last Modified: 3-7-2013 | Index: 591 |
![]() ![]() ![]() ![]() ![]() |
1934 |