Project

General

Profile

Bug #7813

Reporting in server-components missing when restarting some services (ie jetty)

Added by Vincent MEMBRÉ about 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

Jetty was restarted during an agent run on my server and i didn't get any reporting about this

Here is the extract (surrounded by the reports before and after that component):

R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check apache boot script@@None@@2016-01-20 09:50:17+00:00##root@#Check apache boot starting parameters was correct
R: [ERROR] Promise could not be repaired, error encountered: Check if the service .*java.*/opt/rudder/jetty7/start.jar is started using ps
  notice: Q: "...in/service rudd": Setting umask to 0007
Q: "...in/service rudd": Starting Jetty: . . . . OK Wed Jan 20 10:50:43 CET 2016
R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check jetty boot script@@None@@2016-01-20 09:50:17+00:00##root@#Check jetty boot starting parameters was correct

I should have had:

R: @@server-roles@@result_repaired@@server-roles@@server-roles-directive@@3@@Check jetty process@@None@@2016-01-20 09:50:17+00:00##root@#The jetty process was started

This is because we miss a report case using the classes generated by the method "service_ensure_running_path("${initscript}", "${binary}")"

This is located in server-roles/1.0/init-check.st


Related issues

Related to Rudder - Architecture #5846: Add support for systemd in the Techniques (System ones)ReleasedJonathan CLARKE2014-11-27Actions
Related to Rudder - Bug #7821: Unexpected reports on "Check jetty process" component of system techniquesReleasedBenoît PECCATTE2016-01-21Actions
#1

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.11.18 to 2.11.19
#2

Updated by Jonathan CLARKE about 5 years ago

  • Status changed from New to In progress
#3

Updated by Jonathan CLARKE about 5 years ago

  • Related to Architecture #5846: Add support for systemd in the Techniques (System ones) added
#4

Updated by Jonathan CLARKE about 5 years ago

  • Target version changed from 2.11.19 to 3.0.14

This bug was introduced by #5846, so is only in 3.0+.

#5

Updated by Jonathan CLARKE about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/856
#6

Updated by Jonathan CLARKE about 5 years ago

  • Related to Bug #7821: Unexpected reports on "Check jetty process" component of system techniques added
#7

Updated by Jonathan CLARKE about 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.

#9

Updated by Jonathan CLARKE almost 5 years ago

  • Related to Bug #8178: Missing reporting in "check postgresql process" on rudder-db role added
#10

Updated by Jonathan CLARKE almost 5 years ago

  • Related to deleted (Bug #8178: Missing reporting in "check postgresql process" on rudder-db role)

Also available in: Atom PDF