This morning I tried to turn a plugin back on (moderator plugin) and got the following error when rebuilding the app. I then disabled the plugin and rebuilt again to only get the same error. I also tried disabling all the plugins. Any other ideas? This is on my sandbox so it’s not critical. It was working fine prior to this and I didn’t make any other changes besides a git pull. FAILED -------------------- Pups::ExecError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return # Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params "socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1" 740f79002f403805b363a73f114aef7a2075556ac205778eb27e2d63f2c0fe74 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Looks like it’s trying to spawn a new process when there is already one running? Try a reboot?: sudo shutdown -r now

Curiosity: does sudo reboot command do the same thing as sudo shutdown -r now? ( i always used reboot on linux, only used shutdown -r -t 0 in windows :D)

Failed to Bootstrap with "postgres already running"

Product Support Self-hosting

merefield (Robert) May 21, 2019, 5:49am 5

Suspect they do the same thing under the hood (switching run levels) but don’t quote me on it!

Topic		Replies	Views
"postgres already running " on Self-hosting	1	1185	June 18, 2018
[Solved]Bootstrap fails, Postgres already running Self-hosting	20	11339	March 30, 2015
Error while Plugin Install Product Support reactions , postgres	0	89	March 29, 2025
Bootstrap Error when trying to rebuild Self-hosting	6	639	April 11, 2019
Update fails with error postgres already running stop container Self-hosting	2	278	August 30, 2024

Failed to Bootstrap with "postgres already running"

Related topics