Bug #7645
closed
Missing reporting for jetty and slapd on relay
Added by Alexis Mousset almost 9 years ago.
Updated almost 9 years ago.
Category:
System techniques
Description
On a Centos6 relay:
Check jetty boot script
Status
None Checking jetty boot settings is unnecessary on this machine, skipping... Unexpected
and
Check slapd boot script
Status
None Checking slapd boot settings is unnecessary on this machine, skipping... Unexpected
- Status changed from New to In progress
- Assignee set to Alexis Mousset
The problem is there are currently no checking that jetty and slapd are set to start at boot (contrary to apache and postgresql), and the messages in the case they are not needed (on a relay) are hence unexpected.
We should add a generic_process_check_bootstart for slapd and postgresql if the server has the matching roles.
- Target version changed from 3.2.0~rc1 to 3.1.6
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/826
- Related to Bug #6833: System techniques tries to add old services at boot added
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Related to Bug #7597: When upgrading from 2.11 to 3.1.5, the root server gets components in No Reports added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.6 and 3.2.0 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by