Actions
Bug #10531
closed
When upgrading Rudder to 4.1 on debian8, the web interface is not restarted after properties are modified, so it fails to run
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
-
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
After upgrading from 4.0 to 4.1, the web interface didn't work
Web interface logs said
Caused by:
com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'rudder.server'
at com.typesafe.config.impl.SimpleConfig.findKeyOrNull(SimpleConfig.java:152)
at com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:145)
install log said
INFO: Alternative source path added: /var/rudder/configuration-repository/ncf INFO: New configuration property rudder.server.relay.api added to /opt/rudder/etc/rudder-web.properties INFO: New configuration property rudder.hooks.ignore-suffixes added to /opt/rudder/etc/rudder-web.properties INFO: Checking PostgreSQL service status... OK INFO: Adding new 'compliances' table Done INFO: Checking LDAP service status... OK INFO: The migration has completed successfully. INFO: End of migration script INFO: Restarting Rudder webapp and inventory-endpoint... Done Setting up rudder-inventory-ldap (4.1.0-jessie0)
and unfortunately, the restart didn't occur
echo -n "INFO: Restarting Rudder webapp and inventory-endpoint..." service rudder-jetty start >/dev/null 2>&1 echo " Done"
restarting rudder-jetty, or waiting a bit solves the issue
Updated by Nicolas CHARLES about 7 years ago
- Related to Architecture #9820: Stop jetty before upgrading the webapp added
Updated by François ARMAND about 7 years ago
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
- User visibility changed from First impressions of Rudder to Operational - other Techniques | Technique editor | Rudder settings
Updated by François ARMAND about 7 years ago
Modification of priority because:
- severity minor: it starts to works without anything done by the user, or if run the agent or restart the webapp ;
- user visibility: operational, because it happens only during an upgrade, so people must have an install to upgrade.
Updated by Benoît PECCATTE about 7 years ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Priority changed from 0 to 36
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from New to Rejected
- Priority changed from 47 to 0
Rejecting, we now correctly restarts independently of the init system
Actions