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
The agent does not check in to the SysOrb server. Upon inspection, the agent process no longer runs on the server it was installed on.
On windows you can look for "soagent.exe" in the task manager - if this process cannot be found, the agent is not running.
On UNIX and Linux based systems you can look for the "soagent" process using pgrep, top, prstat or similar process overview tools.
Agent crashes are either caused directly by software problems in the SysOrb agent, or they can be caused by driver or library problems in the host system software that the agent is interacting with.
Please enabled extended logging, to better diagnose precisely which subsystem of the agent is causing the crash.
On Windows, enter the SysOrb configuration tool on the system on which the agent is installed. Go to "SysOrb Agent", "General" and "Amount of logging". The log level will be set to "1" - you should change this to "-1".
On UNIX, Linux based or NetWare systems you can edit the agent configuration file (agent.conf or agent.cfg). Change the line that says "loglevel = 1" to instead say "loglevel = -1".
After this change, start up the agent again. Let it run until it crashes. Please be aware that the agent is now logging excessively - if it takes days for the agent to crash, know that the log file can grow to hundreds of megabytes or more.
Once the agent has crashed, the log file should hold very valuable information that will be essential to further troubleshooting. Please open a support request with Evalesco and be sure to send the log file too.
If the log file is too large, please upload it to: