簡體   English   中英

docker 上的 repmgrd 和 supervisord - 失去父母?

[英]repmgrd and supervisord on docker - losing parent?

我已經用PostgreSQLrepmgrd創建了一個 Docker 鏡像,所有repmgrd都用supervisor啟動。

我現在的問題是,當它啟動時, repmgrd通過催生supervisor似乎樣的模具,另外一個是在它的位置。 這導致我無法使用supervisorctl來控制它,而不得不解決pkill或類似的方法來管理它。

文件

FROM postgres:10

RUN apt-get -qq update && \
    apt-get -qq install -y \
        apt-transport-https \
        lsb-release \
        openssh-server \
        postgresql-10-repmgr \
        rsync \
        supervisor > /dev/null && \
    apt-get -qq autoremove -y && \
    apt-get -qq clean && \
    rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

# public keys configuration for passwordless login
COPY ssh/ /var/lib/postgresql/.ssh/
# postgres, sshd, supervisor and repmgr configuration
COPY etc/ /etc/
# helper scripts and entrypoint
COPY helpers/ /usr/local/bin/

ENTRYPOINT ["/usr/local/bin/pg-docker-entrypoint.sh"]

pg-docker-entrypoint.sh是啟動supervisord -c /etc/supervisor/supervisord.conf

配置文件

[unix_http_server]
file = /var/run/supervisor.sock
chmod = 0770
chown = root:postgres

[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl = unix:///var/run/supervisor.sock

[supervisord]
logfile = /var/log/supervisor/supervisor.log
childlogdir = /var/log/supervisor
pidfile = /var/run/supervisord.pid
nodaemon = true

[program:sshd]
command = /usr/sbin/sshd -D -e
stdout_logfile = /var/log/supervisor/sshd-stdout.log
stderr_logfile = /var/log/supervisor/sshd-stderr.log

[program:postgres]
command = /docker-entrypoint.sh postgres -c config_file=/etc/postgresql/10/main/postgresql.conf
stdout_logfile = /var/log/supervisor/postgres-stdout.log
stderr_logfile = /var/log/supervisor/postgres-stderr.log

[program:repmgrd]
command = bash -c "sleep 10 && /usr/local/bin/repmgr_helper.sh"
user = postgres
stdout_logfile = /var/log/supervisor/repmgr-stdout.log
stderr_logfile = /var/log/supervisor/repmgr-stderr.log

[group:jm]
programs = sshd, postgres, repmgrd

repmgr_helper.sh/usr/lib/postgresql/10/bin/repmgrd --verbose

配置文件

node_id=1
node_name='pg-dock-1'
conninfo='host=pg-dock-1 port=5432 user=repmgr dbname=repmgr connect_timeout=60'
data_directory='/var/lib/postgresql/data/'

use_replication_slots=1
pg_bindir='/usr/lib/postgresql/10/bin/'
failover='automatic'
promote_command='/usr/bin/repmgr standby promote --log-to-file'
follow_command='/usr/bin/repmgr standby follow --log-to-file -W --upstream-node-id=%n'

ps輸出

root@9f39cb085506:/# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 11:54 ?        00:00:00 bash /usr/local/bin/pg-docker-entrypoint.sh
root        10     1  0 11:54 ?        00:00:01 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor/supervisord.conf
root        13    10  0 11:54 ?        00:00:00 /usr/sbin/sshd -D -e
postgres    15    10  0 11:54 ?        00:00:07 postgres -c config_file=/etc/postgresql/10/main/postgresql.conf
postgres    36    15  0 11:54 ?        00:00:00 postgres: checkpointer process
postgres    37    15  0 11:54 ?        00:00:00 postgres: writer process
postgres    38    15  0 11:54 ?        00:00:00 postgres: wal writer process
postgres    39    15  0 11:54 ?        00:00:00 postgres: autovacuum launcher process
postgres    40    15  0 11:54 ?        00:00:00 postgres: archiver process
postgres    41    15  0 11:54 ?        00:00:01 postgres: stats collector process
postgres    42    15  0 11:54 ?        00:00:00 postgres: bgworker: logical replication launcher
postgres    51    15  0 11:54 ?        00:00:00 postgres: wal sender process repmgr 10.0.14.4(33812) streaming 0/4002110
postgres    55    15  0 11:54 ?        00:00:00 postgres: repmgr repmgr 10.0.14.4(33824) idle
postgres    88    15  0 11:54 ?        00:00:01 postgres: repmgr repmgr 10.0.14.5(33496) idle
postgres    90     1  0 11:54 ?        00:00:03 /usr/lib/postgresql/10/bin/repmgrd --verbose
root       107     0  0 11:54 pts/0    00:00:00 bash
root      9323   107  0 12:50 pts/0    00:00:00 ps -ef

如您所見, repmgrd進程現在是入口點的子進程,而不是supervisor (如sshdpostgres )。 我嘗試直接啟動命令(沒有“幫助程序”),我嘗試使用bash -c ,我嘗試將/usr/bin/repmgrd指定為可執行文件,但無論我最終嘗試什么,我總是得出這個結果。

我的問題是雙重的:為什么會發生這種情況以及我可以做些什么來使repmgrd進程處於supervisor的控制之下。


編輯:正如我所建議的那樣,我在啟動 repmgrd 時嘗試了--daemonize=false

這種幫助,但不完全。 查看輸出:

root@6ab09e13f425:/# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 17:06 ?        00:00:00 bash /usr/local/bin/pg-docker-entrypoint.sh
root        11     1  2 17:06 ?        00:00:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor/supervisord.conf
root        14    11  0 17:06 ?        00:00:00 /usr/sbin/sshd -D -e
postgres    15    11  0 17:06 ?        00:00:00 bash /usr/local/bin/repmgr_helper.sh
postgres    16    11  1 17:06 ?        00:00:00 postgres -c config_file=/etc/postgresql/10/main/postgresql.conf
postgres    37    16  0 17:06 ?        00:00:00 postgres: checkpointer process
postgres    38    16  0 17:06 ?        00:00:00 postgres: writer process
postgres    39    16  0 17:06 ?        00:00:00 postgres: wal writer process
postgres    40    16  0 17:06 ?        00:00:00 postgres: autovacuum launcher process
postgres    41    16  0 17:06 ?        00:00:00 postgres: archiver process
postgres    42    16  0 17:06 ?        00:00:00 postgres: stats collector process
postgres    43    16  0 17:06 ?        00:00:00 postgres: bgworker: logical replication launcher
postgres    44    16  0 17:06 ?        00:00:00 postgres: wal sender process repmgr 10.0.23.136(47132) streaming 0/4008E28
root        45     0  0 17:06 pts/0    00:00:00 bash
postgres    77    15  1 17:06 ?        00:00:00 /usr/lib/postgresql/10/bin/repmgrd --daemonize=false --verbose
postgres    78    16  0 17:06 ?        00:00:00 postgres: repmgr repmgr 10.0.23.136(47150) idle
postgres    79    16  0 17:06 ?        00:00:00 postgres: repmgr repmgr 10.0.23.134(43476) idle
root        86    45  0 17:06 pts/0    00:00:00 ps -ef
root@6ab09e13f425:/# supervisorctl stop jm:repmgrd
jm:repmgrd: stopped
root@6ab09e13f425:/# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 17:06 ?        00:00:00 bash /usr/local/bin/pg-docker-entrypoint.sh
root        11     1  1 17:06 ?        00:00:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor/supervisord.conf
root        14    11  0 17:06 ?        00:00:00 /usr/sbin/sshd -D -e
postgres    16    11  0 17:06 ?        00:00:00 postgres -c config_file=/etc/postgresql/10/main/postgresql.conf
postgres    37    16  0 17:06 ?        00:00:00 postgres: checkpointer process
postgres    38    16  0 17:06 ?        00:00:00 postgres: writer process
postgres    39    16  0 17:06 ?        00:00:00 postgres: wal writer process
postgres    40    16  0 17:06 ?        00:00:00 postgres: autovacuum launcher process
postgres    41    16  0 17:06 ?        00:00:00 postgres: archiver process
postgres    42    16  0 17:06 ?        00:00:00 postgres: stats collector process
postgres    43    16  0 17:06 ?        00:00:00 postgres: bgworker: logical replication launcher
postgres    44    16  0 17:06 ?        00:00:00 postgres: wal sender process repmgr 10.0.23.136(47132) streaming 0/4008E60
root        45     0  0 17:06 pts/0    00:00:00 bash
postgres    77     1  0 17:06 ?        00:00:00 /usr/lib/postgresql/10/bin/repmgrd --daemonize=false --verbose
postgres    78    16  0 17:06 ?        00:00:00 postgres: repmgr repmgr 10.0.23.136(47150) idle
postgres    79    16  0 17:06 ?        00:00:00 postgres: repmgr repmgr 10.0.23.134(43476) idle
root       106    45  0 17:07 pts/0    00:00:00 ps -ef

在啟動時,該進程仍然使用supervisor ,但停止它只會殺死repmgr_helper.sh導致“真實”進程保持活動狀態並重新分配給1作為其父進程。

這並不理想,因為現在我有一個奇怪的情況,進程是活着的,但supervisor認為它不是。 因此發出一個supervisorctl start jm:repmgrd失敗說

[ERROR] PID file "/tmp/repmgrd.pid" exists and seems to contain a valid PID
[HINT] if repmgrd is no longer alive, remove the file and restart repmgrd

根據評論中的討論更新了答案:

這些是當前解決方案的問題:

  1. 啟動 repmgrd 的原始命令:

    command = bash -c "sleep 10 && /usr/local/bin/repmgr_helper.sh"

    運行 bash,它執行另一個 bash 腳本(即 bash 的另一個實例),然后運行 ​​repmgrd,這些進程太多,大多數不需要

  2. supervisord 希望調用的命令保留在前台,但默認情況下 repmgrd 守護進程

  3. 在排除故障時, repmgrd 生成的 pid 文件存在一些問題

這些可以通過以下更改修復:

  1. 要改用的命令:

    command = /usr/local/bin/repmgr_helper.sh

  2. /usr/local/bin/repmgr_helper.sh需要更新以運行sleep 10作為第一步

  3. /usr/local/bin/repmgr_helper.sh作為最后一步應該通過以下方式調用 repmgrd:

    exec /path/to/repmgrd --daemonize=false --no-pid-file

    所以, 由於exec它替換了它啟動它的腳本 b. 它不會守護自己 c. 它不會生成 pid 文件。

原始答案(更新前)

在啟動命令中,嘗試將--daemonize=false傳遞給 repmgrd。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM