Project

General

Profile

Bug #6263

Startup links for rudder-server-root on Ubuntu are not correct - before 3.1

Added by Dennis Cabooter about 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
1
Category:
System integration
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

Rudder provides a very nice init script: rudder-server-root. This script starts all required components for the Rudder server.
However, Ubuntu (unlike RHEL/CentOS) defaults to create startup links for every package it installs. So, by default all required
components for the Rudder server are started twice at boot (at least they're trying to do so).

AFAIK there's two sulotions to solve this:

  • remove the rudder-server-root startup links and leave the others
  • Remove the indivual startup links and only leave the rudder-server-root startup link

The rudder-server-root script already can do all the work, so personally I'd prefer to remove the other startup links. I found
this out because after rebooting jetty didn't come up correctly. I did the following so solve it, rebooted the Rudder server, and
all services came up fine.

root@rudder-server-root:~# update-rc.d -f slapd remove
 Removing any system startup links for /etc/init.d/slapd ...
root@rudder-server-root:~# update-rc.d -f postgresql remove
 Removing any system startup links for /etc/init.d/postgresql ...
   /etc/rc0.d/K21postgresql
   /etc/rc1.d/K21postgresql
   /etc/rc2.d/S19postgresql
   /etc/rc3.d/S19postgresql
   /etc/rc4.d/S19postgresql
   /etc/rc5.d/S19postgresql
   /etc/rc6.d/K21postgresql
root@rudder-server-root:~# update-rc.d -f rudder-agent remove
 Removing any system startup links for /etc/init.d/rudder-agent ...
   /etc/rc0.d/K20rudder-agent
   /etc/rc1.d/K20rudder-agent
   /etc/rc2.d/S20rudder-agent
   /etc/rc3.d/S20rudder-agent
   /etc/rc4.d/S20rudder-agent
   /etc/rc5.d/S20rudder-agent
   /etc/rc6.d/K20rudder-agent
root@rudder-server-root:~# update-rc.d -f rudder-jetty remove
 Removing any system startup links for /etc/init.d/rudder-jetty ...
   /etc/rc0.d/K20rudder-jetty
   /etc/rc1.d/K20rudder-jetty
   /etc/rc2.d/S20rudder-jetty
   /etc/rc3.d/S20rudder-jetty
   /etc/rc4.d/S20rudder-jetty
   /etc/rc5.d/S20rudder-jetty
   /etc/rc6.d/K20rudder-jetty

Related issues

Related to Rudder - Bug #6448: Error 404 after rebooting systemRejected2015-03-27Actions
Related to Rudder - User story #6513: Generic rudder init script Released2015-05-04Actions

Associated revisions

Revision 9dede85f (diff)
Added by Matthieu CERDA over 4 years ago

Fixes #6263: Disable other init scripts in rudder-server-root to prevent issues in startup ordering

Revision 0e405943
Added by Vincent MEMBRÉ over 4 years ago

Merge pull request #674 from Kegeruneku/bug_6263/int/6263_fix_startup_on_ubuntu_all_in_one_servers

Fixes #6263: Disable other init scripts in rudder-server-root to prev…

History

#1

Updated by Matthieu CERDA about 5 years ago

  • Status changed from New to 8
  • Priority changed from 1 to 2

Thanks for the report Dennis, I'm taking a look at this.

#2

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.11 to 2.10.12
#3

Updated by François ARMAND almost 5 years ago

  • Reproduced set to No

Matthieu, I think you worked a lot on ubuntu compliance with Rudder. Was that ticket part of the work ?

#4

Updated by Matthieu CERDA almost 5 years ago

Nope, I reproduce the issue but I can not find why it happens yet...

#5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.12 to 2.10.13
#6

Updated by Matthieu CERDA almost 5 years ago

  • Related to Bug #6448: Error 404 after rebooting system added
#7

Updated by Benoît PECCATTE almost 5 years ago

  • Status changed from 8 to New
#8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.13 to 2.10.14
#9

Updated by Dennis Cabooter almost 5 years ago

  • Priority changed from 2 to 1
  • Target version changed from 2.10.14 to 3.0.5

I already provided solutions. All packages are installed in Ubuntu are started at boot by default. You need to remove them (with Rudder Agent) or make sure rudder-server-root script does not start at boot. Please fix this ASAP. It's still a big prob in 3.0.4 and related to http://www.rudder-project.org/redmine/issues/6448

#10

Updated by Nicolas CHARLES almost 5 years ago

I don't understand - ubuntu can't possibly create startup link for every package you install; otherwise having vim or emacs started at boot would cause trouble.

#11

Updated by Nicolas CHARLES almost 5 years ago

I think it's a package parameter, but i'm not packager to be sure of that. I'm not sure of the best solution, but I guess that if rudder-server-root is there, other start up link should be disables (in case of distributed server, they need to be still there)

Matthieu, I recall you were doing some great work in with this script, could you tell me more.

#12

Updated by Dennis Cabooter almost 5 years ago

I think only rudder-server-root should be started at boot. This to be sure services start in the right order. On my Rudder server i removed all startup links, apart from rudder-server-root and now all seems to work just fine. :D

#13

Updated by François ARMAND almost 5 years ago

  • Subject changed from Startup links for rudder-server-root on Ubuntu are not correct to Startup links for rudder-server-root on Ubuntu are not correct - before 3.1
  • Target version changed from 3.0.5 to 2.11.11

Target is 2.11 because the distribution is not supported in 2.10.

Solution chosen:

- in rudder-server-root post install, disable rudder-slapd, rudder-jetty, rudder-agent starting at launch so that:

- distributed configuration or Rudder works as before
- stand alone rudder is corrected
#14

Updated by François ARMAND almost 5 years ago

#15

Updated by François ARMAND almost 5 years ago

Matthieu, could you explain where you are on that one ?

#16

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.11 to 2.11.12
#17

Updated by Matthieu CERDA over 4 years ago

  • Status changed from New to In progress
#18

Updated by Matthieu CERDA over 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Benoît PECCATTE
  • % Done changed from 0 to 100
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/674
#19

Updated by Matthieu CERDA over 4 years ago

  • Status changed from Pending technical review to Pending release
#21

Updated by Dennis Cabooter over 4 years ago

Unfortunatly, stupid Ubuntu always re-enable a startup-link when upgrading for example PostGres. So the other way round may be better.

#22

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.12, 3.0.7 and 3.1.0 which were released today.

Also available in: Atom PDF