Database summary

The Database >Admin > Summary page draws together information from other pages. It shows what and when activities happen in the database.

Server Info

This area of the page displays information pertinent to database server performance. The same information also appears on the Stats page.

•

Status

This shows whether or not MySQL is currently running.

•

Version

This shows the version of MySQL which is running.

•

Uptime

This shows (in seconds) how long the current session of MySQL has been running. The number goes to 0 each time the database stops.

•

Threads

This indicates how many MySQL threads are in use at the moment. You establish the limit using the Maximum Concurrent Threads field under the Settings tab.

•

Queries

Logs the number of queries made to the database since the last time it was restarted.

•	Slow Queries

Any query which takes a long time to complete gets logged here. By default, that will be any query taking longer than 10 seconds. The number in this field indicates slow queries in the time since the database was last restarted.

Schedules

The Schedules table provides information about the day of the week and the time at which various mechanisms which watch over the integrity of the database run. These times are of interest because these checks make each database table read-only as it is verified. The Schedules include:

•	Quick Syncs

Quick syncs compare information in the database with information in the file system, and only update database entries that have different modification times than those stored in the file system.

Quick synchronization provides more information. Clicking the Edit-Quick-Sync pencil icon will take you to the Quick Sync page where you can establish when you want to run the process.

•	Full Backups

Pay careful attention to the times at which Full Backups are scheduled. Full Backups include coping file previews, so can leave larger tables as “read-only” for some time, and for this reason, are best scheduled for times when system activity will be low.

Scheduling backups provides details about setting times. Clicking the associated Edit Backup pencil will take you to the Backup page where you may change settings.

•	Quick Backups

A Quick Backup does not contain file previews and so, finishes more quickly. You can see the schedule here. Clicking the associated Edit Backup pencil will take you to the Backup page where you may change settings. Scheduling backups provides details.

•	Table Checks

The Xinet database provides a mechanism to check the integrity of its tables.

Scheduling Table Checks provides more information. The associated Table Check pencil will open the Table Check page, where you can change settings.

Database Daemon Info

This section summarizes information about the database daemon (dblogd(8))and the amount of disk space that is free. Changing the stored data and temporary files directories provides more information. Details about the webdblog file(s) provides information that will help you interpret what you see in the right-hand column. About the database daemons provides some background about dblogd(8) and the other programs with which it communicates.

About Last Event Processed

The Last Event Processed field displays the time when the last file system event was added to the database (and thus, made available to Xinet users) and whether dblogd(8) has fallen behind since then. For instance, if a file were added five minutes ago, and nothing else had changed in those five minutes, the time displayed would be from five minutes ago. If, however, events had occurred since that time—but, either the dblogd(8) daemon was busy processing events or had stopped—that delay would be noticed and shown here.

Refreshing the display

By default, when you open the Summary page, it will refresh itself every 50 seconds. You may, however, override the default with either the Refresh Now or Stop Refresh buttons. If you click Stop Refresh, contents will remain frozen as long as you view the current page or until you click the Resume Refresh button. If you leave the page and come back to it later, it will have the same effect as clicking the Resume Refresh button.