Bug #8295
closed
rudder init script reports wrong status if run as non-root
Added by Jonathan CLARKE almost 8 years ago.
Updated almost 8 years ago.
Category:
System integration
Description
Running the rudder init script as a non root user told me the wrong status:
$ /etc/init.d/rudder status
Component status:
* Agent Not running, please restart with "service rudder-agent restart"
* LDAP DB Not running, please restart with "service rudder-slapd restart"
* SQL DB Not running, please restart with "service postgresql restart"
* Application Not running, please restart with "service rudder-jetty restart"
- Target version set to 3.1.10
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
- Status changed from In progress to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/929
- Status changed from Pending technical review to In progress
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request changed from https://github.com/Normation/rudder-packages/pull/929 to https://github.com/Normation/rudder-packages/pull/930
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
Also available in: Atom
PDF
Updated by 
Updated by