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
Disabling specific checks
Certain checks performed on the agent causes the agent or even the entire system to crash
Certain drivers or shared libraries that the SysOrb agent calls can contain buggy code, which is beyond the control of the SysOrb agent.
If upgrading the driver or shared library that causes the agent to fail is not feasible, the specific check that causes the problems can be disabled in the agent configuration. This is done by adding the string "disable_checks" to the SysOrb agent configuration, following a comma separated list of the checks to disable. On Posix systems the configuration file is by default located at /etc/sysorb/agent.conf. On Windows one needs to open the registry editor (regedit) and locate the key HKEY_LOCAL_MACHINE\Software\SysOrb\SOAgent and adding a new string value name "disable_checks", with the value being a comma separated list of specific checks to disable.
The following individual checks can currently be disabled this way:
- fs - Filesystem checks
- mem - Memory checks
- system - Generic system checks
- proc - Processes checks
- smart - Smart checks
- ifthrough - Interface throghput checks
- ifevents - Interface events checks
- custom - Custom checks
- log - Log checks
- fanspeed - Fanspeed checks
- temperature - Temperature checks
- voltage - Voltage checks
- raid - RAID checks
- esx_vms - VmWare ESX checks
- scm - Services checks (Windows only)
- perf - Performance counter checks (Windows only)
- ioqueue - Ioqueue checks (Solaris only)
- processors - Processors checks (Posix systems and Netware only)
- safte - SAFTE checks
- ipmisens - IPMI sensors checks
- cciss - CCISS checks
- csmiplus - CSMI checks
- block - Block devices checks