Actions
Bug #24970
closed
rudder fails to start because of timeout
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
179
Name check:
To do
Fix check:
To do
Regression:
Yes
Description
rudder-jetty is a bit slower to start in Rudder 8.1, and can hit the built-in 1m30 systemd timeout when starting
https://issues.rudder.io/issues/24649 didn't take care of systemd
Updated by Nicolas CHARLES 7 months ago
- Status changed from New to Rejected
it's because the config file is masked by /etc/systemd/system/rudder-jetty.service
i'm rejecting it
Actions