What is the problem with starting a process after a system restart?

Question

linux

I configured supervisord to start the process at system startup, but the following happens:

2016-01-03 14:57:25,077 CRIT Supervisor running as root (no user in config file)
2016-01-03 14:57:25,280 INFO RPC interface 'supervisor' initialized
2016-01-03 14:57:25,280 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2016-01-03 14:57:25,280 INFO RPC interface 'supervisor' initialized
2016-01-03 14:57:25,281 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-01-03 14:57:25,283 INFO daemonizing the supervisord process
2016-01-03 14:57:25,283 INFO supervisord started with pid 1816
2016-01-03 14:57:26,287 INFO spawned: 'ws_server' with pid 1819
2016-01-03 14:57:27,725 INFO success: ws_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-03 14:59:44,742 WARN received SIGTERM indicating exit request
2016-01-03 14:59:44,744 INFO waiting for ws_server to die
2016-01-03 14:59:44,744 INFO stopped: ws_server (terminated by SIGTERM)

If supervisord is then restarted, then the process starts normally. What could be the problem?

Answer 1

Apparently in the environment - when loading the environment variables are the same, when restarting from under the user, they are different. IMHO ws_server needs something that supervisord cannot give at startup (not configured).