|
The upstream project assumes the host system is an imbecile and doesn't
let it touch anything. The result is the system knows nothing about
what's going on and can't even do simple things like stop, start, log,
or monitor services.
In this case Gitlab comes with both its own little daemon supervisor
(which replicates what an init system needs to do anyway but does a poor
job of it) _and_ a SysVInit style start/stop script to call the daemon
monitor. This is such a hack job I don't even know where to start.
This bypasses the whole mess and just uses systemd to call the process
and pass it the correct values. The result is that a) the process
actually stops and starts when its supposed to, b) the log messages
actually end up in the system journal. This is already what we're doing
for the main Gitlab process, it just wasn't implemented for the Sidekiq
service the same way, but the problem and the solution are actually the
same for that too.
|