Bug #10475
closed
service rudder restart does not work the first time on Debian 8
Added by Nicolas CHARLES over 7 years ago.
Updated almost 5 years ago.
Category:
Server components
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
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#
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
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- 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
- 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.
- Related to Bug #10506: Rudder 4.1 fails to install Ubuntu/Debian because of rudder-slapd service restart added
- Target version changed from 4.1.0 to 4.1.1
- Target version changed from 4.1.1 to 4.1.2
- Assignee deleted (
Nicolas CHARLES)
- Target version changed from 4.1.2 to 4.1.3
- Priority changed from 35 to 34
- Target version changed from 4.1.3 to 4.1.4
- Related to Bug #10758: No report on Debian 8 added
- Target version changed from 4.1.4 to 4.1.5
- Target version changed from 4.1.5 to 4.1.6
- Priority changed from 34 to 49
- Target version changed from 4.1.6 to 4.1.7
- Priority changed from 49 to 48
- Target version changed from 4.1.7 to 4.1.8
- Priority changed from 48 to 47
- Target version changed from 4.1.8 to 4.1.9
- Priority changed from 47 to 46
- Priority changed from 46 to 45
- Target version changed from 4.1.9 to 4.1.10
- Priority changed from 45 to 44
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 44 to 43
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 43 to 42
- Target version changed from 4.1.12 to 4.1.13
- Target version changed from 4.1.13 to 4.1.14
- Target version changed from 4.1.14 to 4.1.15
- Target version changed from 4.1.15 to 4.1.16
- Target version changed from 4.1.16 to 4.1.17
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 42 to 0
- Target version changed from 4.1.18 to 4.1.19
- Target version changed from 4.1.19 to 4.1.20
- Target version changed from 4.1.20 to 4.1.21
- Target version changed from 4.1.21 to 4.1.22
- Target version changed from 4.1.22 to 4.1.23
- Target version changed from 4.1.23 to 4.1.24
- Target version changed from 4.1.24 to 588
- Status changed from New to Rejected
Debian 8 is deprecated and support is removed in 5.1.
We won't fix this unless strongly required by a user.
- Target version changed from 588 to 4.1.24
Also available in: Atom
PDF