[Pkg-shinken-maint] Bug#782587: shinken: scheduler fails to start on reboot

Arthur Lutz arthur.lutz at logilab.fr
Tue Apr 14 13:58:41 UTC 2015


Package: shinken
Version: 2.0.3-4
Severity: normal

Dear Maintainer,

   * What led up to the situation?

reboot

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

reboot

   * What was the outcome of this action?

# service shinken status
● shinken.service - LSB: Shinken monitoring daemon
   Loaded: loaded (/etc/init.d/shinken)
   Active: failed (Result: exit-code) since mar. 2015-04-14 13:50:04 UTC; 7min ago
  Process: 303 ExecStart=/etc/init.d/shinken start (code=exited, status=1/FAILURE)

avril 14 13:50:00 shinken2 shinken[303]: Starting scheduler:
avril 14 13:50:02 shinken2 shinken[303]: FAILED: valid pidfile exists (pid=777) and not forced to replace. Exiting. (full output is in /tmp/bad_sta...cheduler)
avril 14 13:50:02 shinken2 shinken[303]: failed!
avril 14 13:50:02 shinken2 shinken[303]: Starting poller:
avril 14 13:50:02 shinken2 shinken[303]: Already running ... (warning).
avril 14 13:50:02 shinken2 shinken[303]: Starting reactionner:
avril 14 13:50:02 shinken2 shinken[303]: Already running ... (warning).
avril 14 13:50:02 shinken2 shinken[303]: Starting broker:
avril 14 13:50:02 shinken2 shinken[303]: Already running ... (warning).
avril 14 13:50:02 shinken2 shinken[303]: Starting receiver:
avril 14 13:50:02 shinken2 shinken[303]: Already running ... (warning).
avril 14 13:50:02 shinken2 shinken[303]: Starting arbiter:
avril 14 13:50:04 shinken2 shinken[303]: .
avril 14 13:50:04 shinken2 systemd[1]: shinken.service: control process exited, code=exited status=1
avril 14 13:50:04 shinken2 systemd[1]: Failed to start LSB: Shinken monitoring daemon.
avril 14 13:50:04 shinken2 systemd[1]: Unit shinken.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

# more /tmp/bad_start_for_scheduler 
[1429019402] Info :    Trying to initialize additional groups for the daemon
valid pidfile exists (pid=777) and not forced to replace. Exiting.


   * What outcome did you expect instead?

All components to be restarted


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (990, 'testing-updates'), (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages shinken depends on:
ii  shinken-common                             2.0.3-4
pn  shinken-mod-auth-cfg-password              <none>
ii  shinken-mod-pickle-retention-file-generic  1.4.1-2
ii  shinken-mod-webui [shinken-mod-sqlitedb]   1.0-3

shinken recommends no packages.

Versions of packages shinken suggests:
pn  shinken-doc  <none>

-- no debconf information



More information about the Pkg-shinken-maint mailing list