Hey everyone-
I screwed up.
I Installed the MariaDB RockOn as root to the Root store, and now none of the Rockstor services will start. Getting a “Page Not Found” error on the web interface. Is there any way to roll this back? I’m fairly new to Docker containers, but when I saw it installing and read “changing permissions” my heart jumped out onto my desk. Running a restart of the rockstor service now gives me this:
Mar 29 10:59:55 beekeeper systemd: Failed to start Rockstor bootstrapping tasks.
Mar 29 10:59:55 beekeeper systemd: Dependency failed for Docker Application Container Engine.
Mar 29 10:59:55 beekeeper systemd: Job docker.service/start failed with result 'dependency'.
Mar 29 10:59:55 beekeeper systemd: Unit rockstor-bootstrap.service entered failed state.
Mar 29 10:59:55 beekeeper systemd: rockstor-bootstrap.service failed.
Anyone have a clue on how to proceed? Here are the statuses of each service:
[root@beekeeper log]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Wed 2017-03-29 10:59:53 EDT; 11min ago
Docs: http://docs.docker.com
Main PID: 14578 (code=killed, signal=TERM)
Mar 29 10:57:07 beekeeper docker[14586]: [services.d] starting services
Mar 29 10:57:07 beekeeper docker[14586]: [services.d] done.
Mar 29 10:57:07 beekeeper docker[14586]: 170329 10:57:07 mysqld_safe Logging to syslog.
Mar 29 10:57:07 beekeeper docker[14586]: 170329 10:57:07 mysqld_safe Starting mysqld daemon with databases from /config/databases
Mar 29 10:59:42 beekeeper systemd[1]: Stopping Docker Application Container Engine...
Mar 29 10:59:42 beekeeper docker[14586]: [cont-finish.d] executing container finish scripts...
Mar 29 10:59:42 beekeeper docker[14586]: [cont-finish.d] done.
Mar 29 10:59:42 beekeeper docker[14586]: [s6-finish] syncing disks.
Mar 29 10:59:55 beekeeper systemd[1]: Dependency failed for Docker Application Container Engine.
Mar 29 10:59:55 beekeeper systemd[1]: Job docker.service/start failed with result 'dependency'.
[root@beekeeper log]# systemctl status rockstor
● rockstor.service - RockStor startup script
Loaded: loaded (/etc/systemd/system/rockstor.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-03-29 10:59:54 EDT; 11min ago
Main PID: 16248 (supervisord)
Memory: 163.7M
CGroup: /system.slice/rockstor.service
├─16248 /usr/bin/python /opt/rockstor/bin/supervisord -c /opt/rockstor/etc/supervisord.conf
├─16300 nginx: master process /usr/sbin/nginx -c /opt/rockstor/etc/nginx/nginx.conf
├─16301 /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=/op...
├─16302 /usr/bin/python /opt/rockstor/bin/data-collector
├─16304 nginx: worker process
├─16305 nginx: worker process
├─16318 /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=/op...
└─16319 /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=/op...
Mar 29 10:59:58 beekeeper supervisord[16248]: 2017-03-29 10:59:58,266 INFO success: data-collector entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
Mar 29 10:59:58 beekeeper supervisord[16248]: 2017-03-29 10:59:58,268 INFO spawned: 'ztask-daemon' with pid 16336
Mar 29 10:59:58 beekeeper supervisord[16248]: 2017-03-29 10:59:58,980 INFO exited: ztask-daemon (exit status 1; not expected)
Mar 29 11:00:00 beekeeper supervisord[16248]: 2017-03-29 11:00:00,988 INFO spawned: 'ztask-daemon' with pid 16343
Mar 29 11:00:01 beekeeper supervisord[16248]: 2017-03-29 11:00:01,673 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
Mar 29 11:00:01 beekeeper supervisord[16248]: 2017-03-29 11:00:01,673 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
Mar 29 11:00:01 beekeeper supervisord[16248]: 2017-03-29 11:00:01,724 INFO exited: ztask-daemon (exit status 1; not expected)
Mar 29 11:00:04 beekeeper supervisord[16248]: 2017-03-29 11:00:04,795 INFO spawned: 'ztask-daemon' with pid 16356
Mar 29 11:00:05 beekeeper supervisord[16248]: 2017-03-29 11:00:05,523 INFO exited: ztask-daemon (exit status 1; not expected)
Mar 29 11:00:06 beekeeper supervisord[16248]: 2017-03-29 11:00:06,525 INFO gave up: ztask-daemon entered FATAL state, too many start retries too quickly
[root@beekeeper log]#
In Hindsight, I totally should have created a new user and store for this. I guess some things have to be learned the hard way.
UPDATE:
Rebooted. That was a glorious mistake. By telling RockStor to use the root partition, it royally screwed up all of the file system permissions. No more SSH, Web, anything. I’m going to have to see if I can somehow do some kind of recovery.
Why is it an option to do this in the first place?