Postgres as a Service
Deploy a Managed Postgres Cluster in Minutes! Enterprise-ready and Oracle compatible.
Failover Manager writes and stores one log file per agent and one startup log per agent in /var/log/cluster_name-3.5 (where cluster_name specifies the name of the cluster).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: TRACE, DEBUG, INFO, WARN, ERROR
# 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 DEBUG will show
# information about the TCP connection attempts that may help
# diagnose the connection failures.The logging facilities use the Java logging library and logging levels. The log levels (in order from most logging output to least) are:TRACE
ERRORFor example, if you set the efm.loglevel parameter to WARN, Failover Manager will only log messages at the WARN level and above (WARN and ERROR).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-3.5). For more information about modifying the log rotation schedule, consult the logrotate man page: