Rudder

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