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

Stopping/restarting doesn't actually stop/restart postgresql #14

Open
glinton opened this issue Mar 16, 2017 · 5 comments
Open

Stopping/restarting doesn't actually stop/restart postgresql #14

glinton opened this issue Mar 16, 2017 · 5 comments
Labels

Comments

@glinton
Copy link
Contributor

glinton commented Mar 16, 2017

root@data.db.3.1:/ # sv stop db
ok: down: db: 0s, normally up, want up
root@data.db.3.1:/ # ps aux | grep postgre
gonano      61  0.0  0.6 2725420 25416 ?       Ss   17:09   0:00 postgres: database 192.168.0.20(41770) idle
@notxarb
Copy link

notxarb commented May 10, 2017

I think postgresql doesn't like signals, it would rather have pgctl start/stop/restart it.

@glinton
Copy link
Contributor Author

glinton commented May 18, 2017

Could this be what we need - https://serverfault.com/a/410339

@tylerflint
Copy link
Contributor

@glinton wow, great find!

@notxarb
Copy link

notxarb commented May 22, 2017

Another thing that I found is that we want to use chpst rather than su to change user. It looks like a lot of the services are using su right now. Using su creates an intermediary process between runit and the actual service process. When runit goes to stop the service, it kills the su process which then abandons the service process rather than shutting it down.

@glinton
Copy link
Contributor Author

glinton commented Jul 5, 2017

It looks like there are still issues when using chpst. Apparently, one app reports issues with postgres every deploy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants