6 Controlling Logging

Other Resources

Postgres as a Service

Deploy a Managed Postgres Cluster in Minutes! Enterprise-ready and Oracle compatible.

6 Controlling Logging

6 Controlling Logging

Failover Manager writes and stores one log file per agent and one startup log per agent in /var/log/efm-2.1. You can control the level of detail written to the agent log by modifying the jgroups.loglevel and efm.loglevel parameters in the cluster properties file:

# Logging levels for JGroups and EFM.
# Valid values are: FINEST, FINER, FINE, CONFIG, INFO,
# WARNING,SEVERE
# Default value: INFO
# It is not necessary to increase these values unless
# debugging a specific issue. If nodes are not discovering
# each other at startup, increasing the jgroups level to
# FINER will show information about the TCP connection
# attempts that may help diagnose the connection failures.

jgroups.loglevel=INFO
efm.loglevel=INFO

The logging facilities use the Java logging library and logging levels. The log levels (in order from most logging output to least) are:

FINEST
FINER
FINE
CONFIG
INFO
WARNING
SEVERE

For example, if you set the efm.loglevel parameter to WARNING, Failover Manager will only log messages at the WARNING level and above (WARNING and SEVERE).

By default, Failover Manager log files are rotated daily, compressed, and stored for a week. You can modify the file rotation schedule by changing settings in the log rotation file (/etc/logrotate.d/efm-2.1). For more information about modifying the log rotation schedule, consult the logrotate man page:

$ man logrotate

6 Controlling Logging