Knowledge Base
Knowlegebase articles
Welcome to SysOrb knowledge base. Her you will find detailed explanation on questions regarding SysOrb. The list is under continues development and new articles will be added. You can follow the links below or enter a "key word" to search all of the articles.
- Agent crashes
- Automatic rescan of all nodes in a domain
- Bandwidth consumption estimate
- Basic database tuning
- Can I customize the reports in SysOrb?
- Disabling specific checks
- Does SysOrb support SNMP traps?
- Explanation of the score keeper strategy.
- How does HTTP Netcheck work in SysOrb?
- How to automatically update alert group on all nodes to “As domain”
- How to backup SysOrb database
- How to change time interval value of agent_checkin_delay
- How to move the SysOrb server to a new server
- How to quickly set downtime on an agent
- I cannot get all of the "performance counters/cache" entries to appear in SysOrb what should I do?
- Migrating MIB information from one SysOrb installation to another
- Migrating the configuration of a Windows SysOrb server from 32 to 64 bits
- No empty blocks in meta database.
- Script to get a list of nodes which have no AlertGroup
- SysOrb agent is not checking in to the Sysorb server
- SysOrb agent stops checking in from a windows server with very long system uptime
- SysOrb server shuts down unexpectedly
- System uptime no longer updates on windows
- Unable to monitor hardware (fans, disks, temperatures etc.) on Windows
- Upgrading SysOrb on Windows
- Uploading a SysOrb database to Evalesco
- What does KiB and MiB mean?
- What is IPMI ?
- Windows agent late for check-in every hour
SysOrb agent stops checking in from a windows server with very long system uptime
On a Windows server with a very high system uptime(around 500+ days) the SysOrb agent suddenly stops checking in to the SysOrb server.
In the SysOrb agent log you see the following:
Reason given: "Error connecting: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. (10055)"
If you run a netstat on the server you get a very long list of TCP connections with the status "TIME_WAIT"
The root cause for this lies in the windows OS please relate to this Microsoft knowledge base article
The recommended solution is to install all latest patches as is likely that hotfix is already present in one of them.
A simple reboot of the server will also clear all the time wait connections and the agent will start checking in again.
