894577 - respond to SIGHUP by stopping, reloading config, then continuing

Status: RESOLVED FIXED

(Socorro :: Backend, task)

Description

[K Lars Lohn [:lars] [:klohn]]

in current Socorro applications, SIGTERM and SIGHUP signals both will cause an app to shut down.  Traditionally (though not originally), SIGHUP is used to cause an app to reload its configuration and continue.  

It is a rather simple matter to make Socorro apps behave in this manner.

Comment 1

[Robert Helmer [:rhelmer]]

We should add "reload" subcommands to the init scripts too, they just need to do something like:

killproc -p ${pidfile} $httpd -HUP

Comment 2

[Robert Helmer [:rhelmer]]

(In reply to Robert Helmer [:rhelmer] from comment #1)
> We should add "reload" subcommands to the init scripts too, they just need
> to do something like:
> 
> killproc -p ${pidfile} $httpd -HUP

Well not $httpd, sorry grabbed an example from Apache's init script :)

Comment 3

[K Lars Lohn [:lars] [:klohn]]

PR 1340 (https://github.com/mozilla/socorro/pull/1340) shows how simple of a change it really is.  I've tested this on the processor and a stand alone collector.  In both cases, I started the apps, then edited the ini file, and then `kill -s 1 $PID`.  The apps picked up their new configs, reconnected to all their resources and continued from where they had left off.

Comment 4

[[github robot]]

Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/a50836064800b894a3e25677158963bc4fe685d6
Merge pull request #1340 from twobraids/sighup

fixes Bug 894577 - add config reload behavior to all Socorro apps