Project

General

Profile

Actions
Copy link

Bug #8165

closed

rudder-init fails to report memory errors from jetty start

Added by Nicolas CHARLES over 8 years ago. Updated almost 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
System integration
Target version:
3.1.25
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
71
Name check:
Fix check:
Regression:

Description

When running rudder-init on a Debian 8, with 1.2 Go RAM, the script get stuck at 

Cleaning up temporary directories... done.
Restarting services...

ps outputs shows that the rudder-jetty scripts sleep for 4 secondes
Finally, script end successfully, but Jetty ain't started

Running mannualy init script says:

root@server:/home/vagrant# /etc/init.d/rudder-jetty start
Setting umask to 0007
WARNING: Not enough free memory to start Jetty (about 1422MB are needed). Trying anyway, but the application is likely to fail.
Starting Jetty: . . . . . . . . . . . . . . FAILED Sun Apr 10 19:51:29 UTC 2016

May happen on all versions

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #5617: Detecting and restarting Rudder on OOM (Out Of Memory Exception)ResolvedActions
Actions
Copy link

Also available in: Atom PDF