Changing EGO log levels

If you must troubleshoot or debug your system, change log levels from the default LOG_WARNING to a log level that provides more details (for example, LOG_DEBUG). You can also enable or disable logging completely.

Before you begin

Log on as root or egoadmin.

About this task

Separate log levels are set for each daemon. To change the log level for an entire cluster, you must set each daemon individually.

Logging level settings are not permanent and do not change ego.conf. When the cluster shuts down or restarts, logging level settings do not persist. Instead, log levels reset to LOG_WARNING. Refer to the egosh command for details on all the command options.

Note: If you are setting the log level for VEMKD and this daemon fails over, the permanent setting in ego.conf (Warning level) becomes the current setting. To change it, follow these steps once more.

Procedure

To enable the more detailed log level LOG_DEBUG, run egosh debug daemon on.

For example, egosh debug vemkdon.

You can also specify a log class using the -c option if you want to receive entries concerning one log class (such as authentication or memory).

You have enabled log level LOG_DEBUG for vemkd. All entries are logged in vemkd.log.hostname.
To return the log level to the default LOG_WARNING, run egosh debug daemon off.

For example, egosh debug vemkdoff.

You have returned your log level to LOG_WARNING (the default) for vemkd. All entries are logged in vemkd.log.hostname.

What to do next

You should debug your system as quickly as possible and set your log level to warning for daily activity.

CAUTION:

The LOG_DEBUG logging level is very verbose and fills up your log files quickly, which can adversely affect performance.