Bug #10475: service rudder restart does not work the first time on Debian 8 - Rudder - Issue Tracker

Actions

Copy link

Bug #10475

closed

service rudder restart does not work the first time on Debian 8

Added by Nicolas CHARLES about 7 years ago. Updated over 4 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Server components

Target version:

4.1.24

Pull Request:

https://github.com/Normation/rudder-p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Getting started - demo | first install | level 1 Techniques

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

On Debian 8, if I run service rudder restart, nothing happens the first time, the second time it does restart rudder, but without any output
/etc/init.d does output text

root@server:/home/vagrant# service rudder restart      //(this is instantaneous)
root@server:/home/vagrant# echo $?
0
root@server:/home/vagrant# service rudder status
● rudder.service - LSB: Rudder server
   Loaded: loaded (/etc/init.d/rudder)
   Active: active (exited) since Tue 2017-03-21 14:00:19 UTC; 54s ago
  Process: 31184 ExecStart=/etc/init.d/rudder start (code=exited, status=0/SUCCESS)

Mar 21 14:00:19 server systemd[1]: Starting LSB: Rudder server...
Mar 21 14:00:19 server rudder[31184]: Starting Rudder services:
Mar 21 14:00:19 server rudder[31184]: * rudder-slapd...        OK
Mar 21 14:00:19 server rudder[31184]: * postgresql...        OK
Mar 21 14:00:19 server rudder[31184]: * rudder-jetty...        OK
Mar 21 14:00:19 server rudder[31184]: * rudder-agent...        OK
Mar 21 14:00:19 server systemd[1]: Started LSB: Rudder server.

root@server:/home/vagrant# service rudder restart          (this is slow)
root@server:/home/vagrant# echo $?
0

root@server:/home/vagrant# /etc/init.d/rudder restart
Stopping Rudder services:
 * rudder-agent...    OK
 * rudder-jetty...    OK
 * postgresql...    OK
 * rudder-slapd...    OK

Starting Rudder services:
 * rudder-slapd...    OK
 * postgresql...    OK
 * rudder-jetty...    OK
 * rudder-agent...    OK
root@server:/home/vagrant#

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Nicolas CHARLES about 7 years ago

root@server:/home/vagrant# dpkg -l | grep systemd
ii  libsystemd0:amd64              215-17+deb8u1                     amd64        systemd utility library
ii  systemd                        215-17+deb8u1                     amd64        system and service manager
ii  systemd-sysv                   215-17+deb8u1                     amd64        system and service manager - SysV links

Actions

Copy link

Updated by François ARMAND about 7 years ago

Severity set to Minor - inconvenience | misleading | easy workaround
User visibility set to Getting started - demo | first install | level 1 Techniques

Actions

Copy link

Updated by Benoît PECCATTE about 7 years ago

Status changed from New to In progress
Assignee set to Benoît PECCATTE

Actions

Copy link

Updated by Benoît PECCATTE about 7 years ago

Status changed from In progress to Pending technical review
Assignee changed from Benoît PECCATTE to Nicolas CHARLES
Pull Request set to https://github.com/Normation/rudder-packages/pull/1316

PR https://github.com/Normation/rudder-packages/pull/1316

Actions

Copy link

Updated by François ARMAND about 7 years ago

Subject changed from Empty output of service rudder restart on Debian 8 to service rudder restart does not work the first time on Debian 8
Status changed from Pending technical review to New

The empty output is not a problem: with systemd, logs are not displayed on the output but must be looked for with journald (yeah...).

The fact that the restart does not work the first time seems to be just one other facet of #10506 i.e: there is something with the systemd / service compat layer on Debian that just not work the first time on Debian.

Actions

Copy link