Changing the log level

Increase the verbosity of log output on the IBM Storage Ceph Provisioner server or node agent to diagnose complex issues.

About this task

Increasing the log level adds verbose output to service log files and can help diagnose complex issues. A service restart is required after changing the log level. This does not impact functionality or cause data loss.

Important: Change the log level only when directed by IBM support.

Procedure

  1. Add the debug environment variable to the relevant service unit file.
    • To increase log verbosity on the Provisioner server, edit /etc/systemd/system/metaltank-server.service and add the following line under the [Service] section:

      Environment="MTANK_DEBUG=1"
    • To increase log verbosity on a cluster node agent, edit /etc/systemd/system/metaltank-agent.service and add MTANK_DEBUG=1 to the ExecStart environment string.

  2. Reload the systemd daemon and restart the relevant service.
    • On the Provisioner server:

      sudo systemctl daemon-reload
      sudo systemctl restart metaltank-server.service
    • On a cluster node:

      sudo systemctl daemon-reload
      sudo systemctl restart metaltank-agent.service

Results

The service restarts with increased log verbosity. Use journalctl to view the detailed log output:

journalctl -u metaltank-server.service
journalctl -u metaltank-agent.service

What to do next

After collecting the required diagnostic information, remove the MTANK_DEBUG=1 environment variable and restart the service to return to normal log verbosity.