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
Windows agent late for check-in every hour
On a Windows-based system, the SysOrb agent is reported late for check-in almost exactly every 60 minutes.
There are no other symptoms of problems on the system or any network connectivity problems to be found.
This may be caused by a deficiency in Windows "Internet Time" clock adjustments in combination with a virtualization environment that automatically adjusts the guest system clocks.
On a virtualized guest, the clock will usually be synchronized to the hypervisor clock by the virtualization software. The hypervisor should then use clock synchronization (such as NTP) to always have an accurate clock.
If, however, the virtualized guest system also has Windows Internet Time enabled (right click on the clock in the tray, select "Adjust date and time" and select the "Internet Time" tab), then this clock synchronization can conflict with the virtualization system clock adjustments.
Becuase Windows Internet Time adjustments are very primitive - they make a "hard" adjustment of the clock and may even cause the guest time to go backwards(!), this can have any number of ill effects on all software that relies on the time of day - including the SysOrb agent.
If Windows Internet Time sets the system clock back five minutes, then the agent will wait for an additional five minutes until it checks in, because it compares the current time of day with its next expected check-in time.
Do not use Windows Internet Time. Especially on virtualized systems, where the virtualization software will automatically synchronize the guest clock to the hypervisor clock.
Even on non-virtualized systems, Windows Internet Time should be avoided if at all possible.
If a system is a member of a domain, its time will be automatically synchronized to the domain controller. If a system is not virtualized and not in a domain, you can use the SNTP feature of Windows (please consult Windows documentation for details) to enable network time synchronization against a local time server.