[Bug 272502] databases/postgresql13-server: startup script not redirecting stdout, breaking Ansible
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 14 Jul 2023 13:52:32 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272502 Bug ID: 272502 Summary: databases/postgresql13-server: startup script not redirecting stdout, breaking Ansible Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: pgsql@FreeBSD.org Reporter: topical@gmx.net Flags: maintainer-feedback?(pgsql@FreeBSD.org) Assignee: pgsql@FreeBSD.org The startup script uses pg_ctl which forwards stdout from postgresql daemon to parent process. Since py39-ansible-core-2.15, the "service" module waits until stdout of startup script is completely read. In our case, this will happen when the postgresql daemon terminates, i.e. never and so the Ansible playbook is stuck. According to pg_ctl, this is a feature. But in real life, the only messages you get are ``` LOG: ending log output to stderr HINT: Future log output will go to log destination "syslog". ``` So this feature is useless and makes trouble. Either, pg_ctl must be fixed (which imho is unlikely as under Linux, usually systemd is used which has no problem with that behaviour) or we must modify the rc.d script to redirect stdout to /dev/null on startup. -- You are receiving this mail because: You are the assignee for the bug.