Hello, I'm experiencing a problem with supervisor and my spring application that invoke a system.exit(1) in case of a wrong initialisation. The problem is that supervisor doesn't restart the application even if add ```autorestart=true``` to my supervisor config file. I'm on Ubuntu 14.04 using 3.0b2 installed via apt. the supervisor log doesn't contains anything useful for debugging: ``` 2015-11-06 15:19:29,596 CRIT Supervisor running as root (no user in config file) 2015-11-06 15:19:29,597 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2015-11-06 15:19:29,628 INFO RPC interface 'supervisor' initialized 2015-11-06 15:19:29,628 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2015-11-06 15:19:29,629 INFO supervisord started with pid 1 2015-11-06 15:19:30,631 INFO spawned: 'java' with pid 8 2015-11-06 15:19:30,633 INFO spawned: 'email_renderer' with pid 9 2015-11-06 15:19:30,634 INFO spawned: 'nginx' with pid 10 2015-11-06 15:19:31,706 INFO success: java entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-11-06 15:19:31,711 INFO success: email_renderer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-11-06 15:19:31,711 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) ``` Thanks in advance for any help.
-- Luigi --- “The only way to get smarter is by playing a smarter opponent.”
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org https://lists.supervisord.org/mailman/listinfo/supervisor-users
