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
No empty blocks in meta database.
SysOrb server shuts down, unable to start again, with a message in the server.log stating the following:
Tue Apr 29 14:13:18 2014: [dbms]: Exception during TQL_CREATE : No empty blocks in meta database
Tue Apr 29 14:13:18 2014: Process [dbms]: Caught:
Tue Apr 29 14:13:18 2014: Process [dbms]: No empty blocks in meta database
Tue Apr 29 14:13:18 2014: Process [dbms] terminated unexpectedly with exit code 1. Will shut down.
Tue Apr 29 14:13:18 2014: Closing log.
This can be caused by two things:
1. There is no more space left on the disk where the database files are located.
2. Due to an old database size limitation in SysOrb, installations that are old, might experience this when their database files have grown very big.
Depending of the cause, there is two sollutions:
1. Add more diskspace to the disk that have your databasefiles.
2. This issues needs to be fixed by running a fix on the database files. Either upload your databasefiles to us, and we will fix them, or let us log in to your server, and we will run the fix locally.
