User story #5359
Updated by Jonathan CLARKE about 10 years ago
With a list of action (essentially checks) executed when Rudder web application starts. But at boot time, Rudder is not saying that it is doing things, and we just think that it stalled. So we want to have output saying "existing blabla" Moreover, it may be intersting to know how much time each of these action is taking to help identifies bad behaviour for debugging (so at debug level). The output in info level is: <pre> [2014-09-30 13:30:03] INFO bootactions - Check mandatory DIT entries [2014-09-30 13:30:04] INFO application - All the required DIT entries are present in the LDAP directory [2014-09-30 13:30:04] INFO bootactions - Check initialization of User Technique Library [2014-09-30 13:30:04] INFO bootactions - Check event log migration format 4 -> 5 </pre> And in debug: <pre> [2014-09-30 13:16:15] INFO bootchecks - [#0] Check mandatory DIT entries [2014-09-30 13:16:16] INFO application - All the required DIT entries are present in the LDAP directory [2014-09-30 13:16:16] DEBUG bootchecks - [#0] Check mandatory DIT entries: OK in [951 ms] [2014-09-30 13:16:16] INFO bootchecks - [#1] Check initialization of User Technique Library [2014-09-30 13:16:16] DEBUG bootchecks - [#1] Check initialization of User Technique Library: OK in [51 ms] [2014-09-30 13:16:16] INFO bootchecks - [#2] Check event log migration format 4 -> 5 [2014-09-30 13:16:16] INFO migration - No migration detected by migration script (table 'migrationeventlog' is empty or does not exists) [2014-09-30 13:16:16] DEBUG bootchecks - [#2] Check event log migration format 4 -> 5: OK in [105 ms] </pre>