Upgraded to -05. Can delete NFS shares now. systemctl status -l rockstor-pre says:
● rockstor-pre.service - Tasks required prior to starting Rockstor
Loaded: loaded (/etc/systemd/system/rockstor-pre.service; enabled; vendor preset: disabled)
Active: active (exited) since Tue 2017-04-18 09:24:45 BST; 1h 40min ago
Main PID: 3702 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/rockstor-pre.service
Apr 18 09:24:35 nas initrock[3702]: 2017-04-18 03:24:35,888: Running app database migrations…
Apr 18 09:24:44 nas initrock[3702]: 2017-04-18 03:24:44,185: Done
Apr 18 09:24:44 nas initrock[3702]: 2017-04-18 03:24:44,186: Running prepdb…
Apr 18 09:24:45 nas initrock[3702]: 2017-04-18 03:24:45,211: Done
Apr 18 09:24:45 nas initrock[3702]: 2017-04-18 03:24:45,212: stopping firewalld…
Apr 18 09:24:45 nas initrock[3702]: 2017-04-18 03:24:45,306: firewalld stopped and disabled
Apr 18 09:24:45 nas initrock[3702]: 2017-04-18 03:24:45,829: rockstor service looks correct. Not updating.
Apr 18 09:24:45 nas initrock[3702]: 2017-04-18 03:24:45,829: rockstor-bootstrap.service looks correct. Not updating.
Apr 18 09:24:45 nas initrock[3702]: default_if = nas03_team
Apr 18 09:24:45 nas initrock[3702]: ipaddr = #.#.#.#
Does “Active (Exited)” mean it has started successfully? Which genius Linux kernel dev dreamed up such an unintuitive status!? My guess is it’s started because has green text, not red. In any case, the “bootstrap” service in webui still shows stopped:
Other statuses, rockstor-bootstrap:
● rockstor-bootstrap.service - Rockstor bootstrapping tasks
Loaded: loaded (/etc/systemd/system/rockstor-bootstrap.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-04-18 11:04:48 BST; 12min ago
Process: 20213 ExecStart=/opt/rockstor/bin/bootstrap (code=exited, status=1/FAILURE)
Main PID: 20213 (code=exited, status=1/FAILURE)
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait
2 seconds and try again. Exception: [‘Internal Server Error: No JSON object could be decoded’]
Apr 18 11:04:48 nas bootstrap[20213]: Max attempts(15) reached. Connection errors persist. Failed to bootstrap. Error: [‘Internal Server Error: No JSON object could be decoded’]
and rockstor:
● rockstor.service - RockStor startup script
Loaded: loaded (/etc/systemd/system/rockstor.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2017-04-18 09:24:45 BST; 1h 52min ago
Main PID: 9367 (supervisord)
CGroup: /system.slice/rockstor.service
├─ 9367 /usr/bin/python /opt/rockstor/bin/supervisord -c /opt/rockstor/etc/supervisord.conf
├─10157 nginx: master process /usr/sbin/nginx -c /opt/rockstor/etc/nginx/nginx.con
├─10158 /usr/bin/python /opt/rockstor/bin/gunicorn --bind=127.0.0.1:8000 --pid=/run/gunicorn.pid --workers=2 --log-file=/opt/rockstor/var/log/gunicorn.log
–pythonpath=/opt/rockstor/src/rockstor --settings=settings --timeout=120 --graceful-timeout=120 wsgi:application
├─10159 /usr/bin/python /opt/rockstor/bin/data-collector
├─10160 /usr/bin/python2.7 /opt/rockstor/bin/django ztaskd --noreload --replayfailed -f /opt/rockstor/var/log/ztask.log
├─10161 nginx: worker process
├─10162 nginx: worker process
├─10226 /usr/bin/python /opt/rockstor/bin/gunicorn --bind=127.0.0.1:8000 --pid=/run/gunicorn.pid --workers=2 --log-file=/opt/rockstor/var/log/gunicorn.log
–pythonpath=/opt/rockstor/src/rockstor --settings=settings --timeout=120 --graceful-timeout=120 wsgi:application
└─10227 /usr/bin/python /opt/rockstor/bin/gunicorn --bind=127.0.0.1:8000 --pid=/run/gunicorn.pid --workers=2 --log-file=/opt/rockstor/var/log/gunicorn.log
–pythonpath=/opt/rockstor/src/rockstor --settings=settings --timeout=120 --graceful-timeout=120 wsgi:application
Apr 18 09:24:46 nas supervisord[9367]: 2017-04-18 09:24:46,405 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
Apr 18 09:24:46 nas supervisord[9367]: 2017-04-18 09:24:46,405 INFO supervisord started with pid 9367
Apr 18 09:24:47 nas supervisord[9367]: 2017-04-18 09:24:47,408 INFO spawned: ‘nginx’ with pid 10157
Apr 18 09:24:47 nas supervisord[9367]: 2017-04-18 09:24:47,410 INFO spawned: ‘gunicorn’ with pid 10158
Apr 18 09:24:47 nas supervisord[9367]: 2017-04-18 09:24:47,414 INFO spawned: ‘data-collector’ with pid 10159
Apr 18 09:24:47 nas supervisord[9367]: 2017-04-18 09:24:47,424 INFO spawned: ‘ztask-daemon’ with pid 10160
Apr 18 09:24:49 nas supervisord[9367]: 2017-04-18 09:24:49,432 INFO success: data-collector entered RUNNING state, process has stayed up for > than
2 seconds (startsecs)
Apr 18 09:24:49 nas supervisord[9367]: 2017-04-18 09:24:49,432 INFO success: ztask-daemon entered RUNNING state, process has stayed up for > than 2
seconds (startsecs)
Apr 18 09:24:52 nas supervisord[9367]: 2017-04-18 09:24:52,436 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
Apr 18 09:24:52 nas supervisord[9367]: 2017-04-18 09:24:52,436 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
Maybe I can just ignore bootstrap and assume this issue is benign, no other problems now.