Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How turn off the output of the reaper handler log #46

Open
93910676wangd opened this issue Mar 26, 2024 · 1 comment
Open

How turn off the output of the reaper handler log #46

93910676wangd opened this issue Mar 26, 2024 · 1 comment
Assignees

Comments

@93910676wangd
Copy link

Hello, I am currently facing a problem.
pgpool runs in Docker and upon reviewing its logs, it is discovered that there are a lot of logs related to reaper handler.
How can I turn off the output of the reaper handler? Please confirm and answer, thanks.

  • Pgpool version: 4.4.3

  • sample output log
    pgpool-reaper handler-log

  • Pgpool.config (log section)

#------------------------------------------------------------------------------
#LOGS
#------------------------------------------------------------------------------
#- Where to log-
Log_destination='stderr '
#Where to log
#Valid values are combinations of stderr,
#And syslog Default to stderr
#- What to log-
#Log_line_prefix='% m:% a pid% p:' # print style string to output at beginning of each log line
#Log_connections=off
#Log connections
#Log_disconnections=off
#Log disconnections
Log_host name=on # off
#Hostname will be shown in ps status
#And in logs if connections are logged
Log_statement=off # off
#Log all statements
#Log_per_dode_statement=off
#Log all statements
#With node and backend information
#Notice_per_dode_statement=off
#Logs note message for per node detailed SQL statements
#Log_cliend_messages=off
#Log any client messages
#Log_standby_delay='if_over_threshold '
#Log standby delay
#Valid values are combinations of always,
#If over_threshold, none
#- Syslog specific-
#Syslog'facility='LOCAL0 '
#Syslog local facility Default to Local0
#Syslog_ident='pgpool '
#Syslog program identification string
#Default to 'pgpool'
#- Debug-
#Logerrors verbosity=default # term, default, or verbose messages
#Client_min_messages=warning # values in order of decreasing detail:
#Debug5
#Debug4
#Debug3
#Debug2
#Debug1
#Log
#Notice
#Warning
#Error
Log_min_messages=warning # values in order of decreasing detail:
#Debug5
#Debug4
#Debug3
#Debug2
#Debug1
#Info
#Notice
#Warning
#Error
#Log
#Fatal
#Panic
#This is used when logging to stderr:
#Logging_collector=off
#Enable capturing of stderr
#Into log files
#(change requirements restart)
#-- Only used if logging_collector is on---
#Log_directory='/tmp/pgpool_logs'
#Directory where log files are written,
#Can be absolute
#Log_filename='pgpool -% Y -% m -% d_% H% M% S. log '
#Log file name pattern,
#Can include strftime() escapes
#Log_file_mode=0600
#Creation mode for log files,
#Begin with 0 to use optical notation
#Log_truncate on rotation=off
#If on, an existing log file with the
#Same name as the new log file will be
#Truncated rate than attached to
#But such truncation only occurs on
#Time driven rotation, not on restarts
#Or size driven rotation Default is
#Off, meaning append to existing files
#In all cases
#Log_rotation_age=1d
#Automatic rotation of logs will
#Happen after that (minutes) time
#0 disable time based rotation
#Log_rotation_size=10MB
#Automatic rotation of logs will
#Happen after that much (KB) log output
#0 disable size based rotation
@pengbo0328
Copy link
Collaborator

@93910676wangd Sorry for the late reply.

The following log messages appear when a child process exits due to settings (e.g., child_life_time or child_max_connections) .
This is the normal behavior.

reaper handler
reaper handler: exiting normally

If you want to turn off the output of the reaper handler, you need to set log_min_messages to fatal or panic.

@pengbo0328 pengbo0328 self-assigned this Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants