Actions
Bug #15159
closedWebapp stops at ncf boot check
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
When trying to start the 5.1 webapp, it stalls with:
[2019-06-12 14:42:07] INFO application - registered property: user.home="/root" [2019-06-12 14:42:07] INFO application - registered property: user.language="en" [2019-06-12 14:42:07] INFO application - registered property: user.name="root" [2019-06-12 14:42:07] INFO application - registered property: user.timezone="UTC" [2019-06-12 14:42:08] INFO bootchecks - Check LDAP and PostgreSQL connection [2019-06-12 14:42:08] INFO bootchecks - LDAP and PostgreSQL connection are OK [2019-06-12 14:42:08] INFO bootchecks - Check mandatory DIT entries [2019-06-12 14:42:08] INFO bootchecks - All the required DIT entries are present in the LDAP directory [2019-06-12 14:42:08] INFO bootchecks - Check initialization of User Technique Library [2019-06-12 14:42:08] INFO bootchecks - Check event log migration format 5 -> 6 [2019-06-12 14:42:08] INFO bootchecks - Check existence of at least one archive of the configuration [2019-06-12 14:42:08] INFO bootchecks - First full archive of configuration-repository items done [2019-06-12 14:42:08] INFO bootchecks - Check rules archive directory in configuration-repository [2019-06-12 14:42:08] INFO bootchecks - Creating directory '/var/rudder/configuration-repository/ruleCategories' exists, done [2019-06-12 14:42:08] INFO bootchecks - Check for force reload of Techniques library [2019-06-12 14:42:08] INFO bootchecks - Flag file '/opt/rudder/etc/force_technique_reload' does not exist, do not Technique library will not be reloaded [2019-06-12 14:42:08] INFO bootchecks - Check that system group / directive / rules for Rudder 4.2 are agent-specific [2019-06-12 14:42:09] INFO migration - No migration detected by migration script (table 'migrationeventlog' is empty or does not exist) [2019-06-12 14:42:09] INFO bootchecks - Regenerate all ncf techniques [2019-06-12 14:42:19] WARN bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds [2019-06-12 14:42:24] WARN bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds [2019-06-12 14:42:29] WARN bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds [2019-06-12 14:42:34] WARN bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
It looks like it stops trying to authenticate and does nothing after the last log.
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2290
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|55240227b4b33d9f2175960ee0aaf3390dd92b10.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Actions