Ok stopped docker servicer and then restarted rockstor service:
Here’s the cat of stderr:
[root@warehouse13 log]# cat supervisord_nginx_stderr.log
Package upgrade
Package upgrade
Package upgrade
Package upgrade
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
nginx: [emerg] no “events” section in configuration
Here’s the cat of stdout:
[root@warehouse13 log]# cat supervisord_nginx_stdout.log
Package upgrade
Package upgrade
Package upgrade
Package upgrade
Also here’s supervisord.log which might have some clue, definitely shows nginx failure:
2017-11-30 16:34:11,838 WARN received SIGTERM indicating exit request
2017-11-30 16:34:11,838 INFO waiting for data-collector, gunicorn, ztask-daemon to die
2017-11-30 16:34:11,841 INFO exited: data-collector (terminated by SIGTERM; not expected)
2017-11-30 16:34:11,846 INFO stopped: ztask-daemon (terminated by SIGTERM)
2017-11-30 16:34:11,896 INFO exited: gunicorn (exit status 0; expected)
2017-11-30 16:34:52,895 CRIT Supervisor running as root (no user in config file)
2017-11-30 16:34:52,904 INFO RPC interface ‘supervisor’ initialized
2017-11-30 16:34:52,904 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2017-11-30 16:34:52,904 INFO supervisord started with pid 2908
2017-11-30 16:34:53,906 INFO spawned: ‘nginx’ with pid 2920
2017-11-30 16:34:53,907 INFO spawned: ‘gunicorn’ with pid 2921
2017-11-30 16:34:53,908 INFO spawned: ‘data-collector’ with pid 2922
2017-11-30 16:34:53,909 INFO spawned: ‘ztask-daemon’ with pid 2923
2017-11-30 16:34:53,917 INFO exited: nginx (exit status 1; not expected)
2017-11-30 16:34:54,919 INFO spawned: ‘nginx’ with pid 2957
2017-11-30 16:34:54,932 INFO exited: nginx (exit status 1; not expected)
2017-11-30 16:34:55,933 INFO success: data-collector entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
2017-11-30 16:34:55,933 INFO success: ztask-daemon entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
2017-11-30 16:34:56,936 INFO spawned: ‘nginx’ with pid 3049
2017-11-30 16:34:56,949 INFO exited: nginx (exit status 1; not expected)
2017-11-30 16:34:58,951 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2017-11-30 16:34:59,954 INFO spawned: ‘nginx’ with pid 3050
2017-11-30 16:34:59,967 INFO exited: nginx (exit status 1; not expected)
2017-11-30 16:35:00,968 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2017-12-01 00:19:03,080 WARN received SIGTERM indicating exit request
2017-12-01 00:19:03,080 INFO waiting for data-collector, gunicorn, ztask-daemon to die
2017-12-01 00:19:03,082 INFO exited: data-collector (terminated by SIGTERM; not expected)
2017-12-01 00:19:03,082 INFO exited: ztask-daemon (terminated by SIGTERM; not expected)
2017-12-01 00:19:03,134 INFO exited: gunicorn (exit status 0; expected)
2017-12-01 00:19:03,296 CRIT Supervisor running as root (no user in config file)
2017-12-01 00:19:03,303 INFO RPC interface ‘supervisor’ initialized
2017-12-01 00:19:03,304 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2017-12-01 00:19:03,304 INFO supervisord started with pid 18593
2017-12-01 00:19:04,306 INFO spawned: ‘nginx’ with pid 18605
2017-12-01 00:19:04,308 INFO spawned: ‘gunicorn’ with pid 18606
2017-12-01 00:19:04,310 INFO spawned: ‘data-collector’ with pid 18607
2017-12-01 00:19:04,312 INFO spawned: ‘ztask-daemon’ with pid 18608
2017-12-01 00:19:04,319 INFO exited: nginx (exit status 1; not expected)
2017-12-01 00:19:05,322 INFO spawned: ‘nginx’ with pid 18641
2017-12-01 00:19:05,333 INFO exited: nginx (exit status 1; not expected)
2017-12-01 00:19:06,335 INFO success: data-collector entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
2017-12-01 00:19:06,335 INFO success: ztask-daemon entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
2017-12-01 00:19:07,337 INFO spawned: ‘nginx’ with pid 18746
2017-12-01 00:19:07,349 INFO exited: nginx (exit status 1; not expected)
2017-12-01 00:19:09,352 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2017-12-01 00:19:10,354 INFO spawned: ‘nginx’ with pid 19067
2017-12-01 00:19:10,369 INFO exited: nginx (exit status 1; not expected)
2017-12-01 00:19:11,370 INFO gave up: nginx entered FATAL state, too many start retries too quickly
The other logs seemed to have nothing useful.