-
Notifications
You must be signed in to change notification settings - Fork 49
Open
Description
I am trying to watch the Postgres process on my ec2 instance using sudo bluepill load pg.pill ...but I have noticed that bluepill keeps recycling the Postgres process. Anyone know what I could be doing wrong? I saw the same behavior in God and trying bluepill as an alternative, but I am seeing the same behavior.
When I run sudo bluepill status I see status switching between postgres(pid:): starting and postgres(pid:): down
This is the message in the logs...
[warning]: [postgresql:postgres] pid_file /tmp/postgres.pid does not exist or cannot be read
[warning]: [postgresql:postgres] pid_file /tmp/postgres.pid does not exist or cannot be read
[err]: [postgresql:postgres] Failed to signal process with code 0: no implicit conversion from nil to integer
# pg.pill
Bluepill.application('postgresql') do |app|
app.process('postgres') do |process|
process.start_command = 'sudo service postgresql restart'
process.stop_command = 'sudo service postgresql stop'
process.pid_file = '/tmp/postgres.pid'
process.start_grace_time = 20.seconds
process.stop_grace_time = 20.seconds
process.restart_grace_time = 20.seconds
end
endReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels