Docker not starting after 4.0.6 update

Troubleshooting
1

My Rockstor has been working very well for 54 days but I noticed a new version prompting me on the dashboard screen. I was on 4.0.4 so I updated to 4.0.6 by using the up arrow icon.

After that completed successfully I applied the Linux updates from the dashboard. Then I rebooted the machine only to get no working Rockstor.

I tried some analysis to find that docker was not starting anymore. Here are some details from my limited knowledge.

HomeData:~ # systemctl start docker
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xe” for details.

HomeData:~ # dockerd
WARN[2021-04-13T18:28:49.431950776+10:00] failed to load plugin io.containerd.snapshotter.v1.devmapper error=“devmapper not configured”
WARN[2021-04-13T18:28:49.433468754+10:00] could not use snapshotter devmapper in metadata plugin error=“devmapper not configured”
WARN[2021-04-13T18:28:49.461462158+10:00] Your kernel does not support swap memory limit
WARN[2021-04-13T18:28:49.461496298+10:00] Your kernel does not support cgroup rt period
WARN[2021-04-13T18:28:49.461503410+10:00] Your kernel does not support cgroup rt runtime
WARN[2021-04-13T18:28:49.461508582+10:00] Your kernel does not support cgroup blkio weight
WARN[2021-04-13T18:28:49.461514273+10:00] Your kernel does not support cgroup blkio weight_device

How do I fix the issue?

Tony

2

Hi @Tony_Cristiano,

Sorry you’re having issues… I quickly tried on my Rockstor-4.0.6 system and I didn’t have any trouble with starting docker, so let’s see if we can find the cause of what you’re experiencing.

Note that the messages you found are just warnings (WARN) and due to the fact that the docker daemon will try to load a lot of different plugins that are not necessarily enabled in all systems. For instance, here’s how a normal docker daemon start looks like on Rockstor-4.0.6, for instance:

rockdev:~ # journalctl -u docker
-- Logs begin at Tue 2021-04-13 09:04:21 EDT, end at Tue 2021-04-13 09:08:32 EDT. --
Apr 13 09:08:26 rockdev systemd[1]: Starting Docker Application Container Engine...
Apr 13 09:08:28 rockdev dockerd[2394]: time="2021-04-13T09:08:28.301727336-04:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
Apr 13 09:08:28 rockdev dockerd[2394]: time="2021-04-13T09:08:28.307933843-04:00" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
Apr 13 09:08:29 rockdev dockerd[2394]: time="2021-04-13T09:08:29.693250919-04:00" level=warning msg="Your kernel does not support swap memory limit"
Apr 13 09:08:29 rockdev dockerd[2394]: time="2021-04-13T09:08:29.694052439-04:00" level=warning msg="Your kernel does not support cgroup rt period"
Apr 13 09:08:29 rockdev dockerd[2394]: time="2021-04-13T09:08:29.694569965-04:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Apr 13 09:08:29 rockdev dockerd[2394]: time="2021-04-13T09:08:29.695107823-04:00" level=warning msg="Your kernel does not support cgroup blkio weight"
Apr 13 09:08:29 rockdev dockerd[2394]: time="2021-04-13T09:08:29.695153725-04:00" level=warning msg="Your kernel does not support cgroup blkio weight_device"
Apr 13 09:08:32 rockdev systemd[1]: Started Docker Application Container Engine.

Notice how I have the same warnings as you… nothing seemingly wrong here, then.

As a precaution, could you paste the relevant lines (the most recent ones if too long) of journalctl -u docker?

I’m actually intrigued by one of your sentences:

Could you describe further what you experience? Do you have Rockstor webUI running? You could verify Rockstor’s “status” by the following:

systemctl status -l rockstor*

Given you experienced this after applying updates, we might want to make sure they were all applied without problem. Do you still see updates available, for instance?

zypper ref && zypper lu

Let’s see if we can find something odd with these first and then we’ll adapt.

1 Like
3

Hi

Thanks for the assistance. The Rockstor webUI is not running.

HomeData:~ # systemctl status -l rockstor*
● rockstor-pre.service - Tasks required prior to starting Rockstor
Loaded: loaded (/etc/systemd/system/rockstor-pre.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2021-04-14 00:04:16 AEST; 9min ago
Process: 616 ExecStart=/opt/rockstor/bin/initrock (code=exited, status=1/FAILURE)
Main PID: 616 (code=exited, status=1/FAILURE)

Apr 14 00:04:16 HomeData initrock[616]: File “/opt/rockstor/src/rockstor/scripts/initrock.py”, line 475, in main
Apr 14 00:04:16 HomeData initrock[616]: run_command(fake_initial_migration_cmd + ["–database=default", “contenttypes”])
Apr 14 00:04:16 HomeData initrock[616]: File “/opt/rockstor/src/rockstor/system/osi.py”, line 201, in run_command
Apr 14 00:04:16 HomeData initrock[616]: raise CommandException(cmd, out, err, rc)
Apr 14 00:04:16 HomeData initrock[616]: system.exceptions.CommandException: Error running a command. cmd = /opt/rockstor/bin/django migrate --noinput --fake-initial --database=default contenttypes. rc = 1. stdout = [’’>
Apr 14 00:04:16 HomeData initrock[616]: ", line 49, in ensure_schema’, ’ if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):’, ’ File "/opt/rockstor/eggs/Django->
Apr 14 00:04:16 HomeData systemd[1]: rockstor-pre.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 00:04:16 HomeData systemd[1]: Failed to start Tasks required prior to starting Rockstor.
Apr 14 00:04:16 HomeData systemd[1]: rockstor-pre.service: Unit entered failed state.
Apr 14 00:04:16 HomeData systemd[1]: rockstor-pre.service: Failed with result ‘exit-code’.

HomeData:~ # journalctl -u docker
– Logs begin at Wed 2021-04-14 00:04:10 AEST, end at Wed 2021-04-14 00:06:14 AEST. –
Apr 14 00:04:16 HomeData systemd[1]: Starting Docker Application Container Engine…
Apr 14 00:04:16 HomeData dockerd[1109]: chmod /mnt2/Rockon-root: operation not permitted
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 00:04:16 HomeData systemd[1]: Failed to start Docker Application Container Engine.
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Unit entered failed state.
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Failed with result ‘exit-code’.
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Apr 14 00:04:16 HomeData systemd[1]: Stopped Docker Application Container Engine.
Apr 14 00:04:16 HomeData systemd[1]: Starting Docker Application Container Engine…
Apr 14 00:04:16 HomeData dockerd[1151]: chmod /mnt2/Rockon-root: operation not permitted
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 00:04:16 HomeData systemd[1]: Failed to start Docker Application Container Engine.
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Unit entered failed state.
Apr 14 00:04:16 HomeData systemd[1]: docker.service: Failed with result ‘exit-code’.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Apr 14 00:04:17 HomeData systemd[1]: Stopped Docker Application Container Engine.
Apr 14 00:04:17 HomeData systemd[1]: Starting Docker Application Container Engine…
Apr 14 00:04:17 HomeData dockerd[1183]: chmod /mnt2/Rockon-root: operation not permitted
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 00:04:17 HomeData systemd[1]: Failed to start Docker Application Container Engine.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Unit entered failed state.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Failed with result ‘exit-code’.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Apr 14 00:04:17 HomeData systemd[1]: Stopped Docker Application Container Engine.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Start request repeated too quickly.
Apr 14 00:04:17 HomeData systemd[1]: Failed to start Docker Application Container Engine.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Unit entered failed state.
Apr 14 00:04:17 HomeData systemd[1]: docker.service: Failed with result ‘exit-code’.

1 Like
4

I think this is the root cause there… let’s try to dig further. We can see an error with the Django migration, but the error message was unfortunately truncated, so could you paste the output of the following?

journalctl -b -u rockstor-pre

Also, what is the output of zypper info rockstor?

1 Like
5

HomeData:~ # zypper info rockstor
Loading repository data…
Reading installed packages…
Information for package rockstor:
Repository : Rockstor-Testing
Name : rockstor
Version : 4.0.6-0
Arch : x86_64
Vendor : YewTreeApps
Installed Size : 75.4 MiB
Installed : Yes
Status : up-to-date
Source package : rockstor-4.0.6-0.src
Summary : Btrfs Network Attached Storage (NAS) Appliance.
Description :
Software raid, snapshot capable NAS solution with built-in file integrity protection.
Allows for file sharing between network attached devices.

HomeData:~ # journalctl -b -u rockstor-pre >/tmp/bit
HomeData:~ #
HomeData:~ #
HomeData:~ # cat /tmp/bit
– Logs begin at Wed 2021-04-14 00:04:10 AEST, end at Wed 2021-04-14 01:00:21 AEST. –
Apr 14 00:04:13 HomeData systemd[1]: Starting Tasks required prior to starting Rockstor…
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,162: Checking for flash and Running flash optimizations if appropriate.
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,782: Updating the timezone from the system
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,782: system timezone = Australia/Brisbane
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,784: Updating sshd_config
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,785: SSHD_CONFIG Customization
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,786: sshd_config already has the updates. Leaving it unchanged.
Apr 14 00:04:15 HomeData initrock[616]: 2021-04-14 00:04:15,786: Running app database migrations…
Apr 14 00:04:16 HomeData initrock[616]: Traceback (most recent call last):
Apr 14 00:04:16 HomeData initrock[616]: File “/opt/rockstor/bin/initrock”, line 41, in
Apr 14 00:04:16 HomeData initrock[616]: sys.exit(scripts.initrock.main())
Apr 14 00:04:16 HomeData initrock[616]: File “/opt/rockstor/src/rockstor/scripts/initrock.py”, line 475, in main
Apr 14 00:04:16 HomeData initrock[616]: run_command(fake_initial_migration_cmd + ["–database=default", “contenttypes”])
Apr 14 00:04:16 HomeData initrock[616]: File “/opt/rockstor/src/rockstor/system/osi.py”, line 201, in run_command
Apr 14 00:04:16 HomeData initrock[616]: raise CommandException(cmd, out, err, rc)
Apr 14 00:04:16 HomeData initrock[616]: system.exceptions.CommandException: Error running a command. cmd = /opt/rockstor/bin/django migrate --noinput --fake-initial --database=default contenttypes.
rc = 1. stdout = [’’]. stderr = [‘Traceback (most recent call last):’, ’ File “/opt/rockstor/bin/django”, line 44, in ‘, " sys.exit(djangorecipe.manage.main(‘rockstor.settings’))", ’ Fi
le “/opt/rockstor/eggs/djangorecipe-1.9-py2.7.egg/djangorecipe/manage.py”, line 9, in main’, ’ management.execute_from_command_line(sys.argv)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg
/django/core/management/init.py”, line 354, in execute_from_command_line’, ’ utility.execute()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/init.py”, line
346, in execute’, ’ self.fetch_command(subcommand).run_from_argv(self.argv)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/base.py”, line 394, in run_from_argv’, ’
self.execute(*args, **cmd_options)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/base.py”, line 445, in execute’, ’ output = self.handle(*args, **options)’, ’ Fi
le “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/commands/migrate.py”, line 93, in handle’, ’ executor = MigrationExecutor(connection, self.migration_progress_callback)’, ’
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/executor.py”, line 19, in init’, ’ self.loader = MigrationLoader(self.connection)’, ’ File “/opt/rockstor/eggs/Django-1.
8.16-py2.7.egg/django/db/migrations/loader.py”, line 47, in init’, ’ self.build_graph()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/loader.py”, line 191, in bui
ld_graph’, ’ self.applied_migrations = recorder.applied_migrations()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/recorder.py”, line 59, in applied_migrations’, ’
self.ensure_schema()’, ’ File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/recorder.py
Apr 14 00:04:16 HomeData initrock[616]: ", line 49, in ensure_schema’, ’ if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):’, ’ File “/opt/r
ockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/base/base.py”, line 164, in cursor’, ’ cursor = self.make_cursor(self._cursor())’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/djan
go/db/backends/base/base.py”, line 135, in _cursor’, ’ self.ensure_connection()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/base/base.py”, line 130, in ensure_connect
ion’, ’ self.connect()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/utils.py”, line 98, in exit’, ’ six.reraise(dj_exc_type, dj_exc_value, traceback)’, ’ File “/opt/roc
kstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/base/base.py”, line 130, in ensure_connection’, ’ self.connect()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/bas
e/base.py”, line 119, in connect’, ’ self.connection = self.get_new_connection(conn_params)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/postgresql_psycopg2/base.py”,
line 176, in get_new_connection’, ’ connection = Database.connect(**conn_params)’, ’ File “/opt/rockstor/eggs/psycopg2-2.7.4-py2.7-linux-x86_64.egg/psycopg2/init.py”, line 130, in connect’,
’ conn = _connect(dsn, connection_factory=connection_factory, **kwasync)’, ‘django.db.utils.OperationalError: could not connect to server: No such file or directory’, ‘\tIs the server running loc
ally and accepting’, ‘\tconnections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”?’, ‘’, ‘’]
Apr 14 00:04:16 HomeData systemd[1]: rockstor-pre.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 00:04:16 HomeData systemd[1]: Failed to start Tasks required prior to starting Rockstor.
Apr 14 00:04:16 HomeData systemd[1]: rockstor-pre.service: Unit entered failed state.
Apr 14 00:04:16 HomeData systemd[1]: rockstor-pre.service: Failed with result ‘exit-code’.

6

My eyes are attracted by the following error:

‘django.db.utils.OperationalError: could not connect to server: No such file or directory’, ‘\tIs the server running locally and accepting’, ‘\tconnections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”?’

To me, that points to something wrong with you postgresql server install… Could you check the status of these packages?

zypper info postgresql10 postgresql10-server

and maybe try to force a reinstall of these?

zypper in --force postgresql10 postgresql10-server

… followed by restarting the rockstor service" systemctl start rockstor
Checking the journald logs at the same time using journactl -f on a separate ssh session would help track the progress and see if you still the same error.

@phillxnet, would you have an idea as to why we are seeing this postgresql error?

1 Like
7

@Flox Re:

Nothing springs to mind. Agreed it’s looking very much like the postgresql server is just not running. Hence no migration is possible. i have seen it segfault on some .initrock removals where we just delete the db from under the server (no ideal). And we have an issue open for this here:

But as stated in the issue that’s for source / developer builds not generic rpm updates and is bad behaviour on our part but is not associated with anything we do from an rpm install or update, except in the stated case of upgrading from a source install.

Hope that helps.

1 Like
8

Oh good point, thanks @phillxnet!

@Tony_Cristiano, would you mind checking the status of postgresql as well while we’re at it?

systemctl status postgresql

If it is showing errors (which is likely), then have a look at its specific logs:

journalctl -b -u postgresql
1 Like
9

This is PostgreSQL after I forced reinstall.

HomeData:~ # zypper info postgresql10 postgresql10-server
Loading repository data…
Reading installed packages…
Information for package postgresql10:
Repository : Leap_15_2_Updates
Name : postgresql10
Version : 10.16-lp152.2.15.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 6.2 MiB
Installed : Yes
Status : up-to-date
Source package : postgresql10-10.16-lp152.2.15.1.src
Summary : Basic Clients and Utilities for PostgreSQL
Description :
PostgreSQL is an advanced object-relational database management system
that supports an extended subset of the SQL standard, including
transactions, foreign keys, subqueries, triggers, and user-defined
types and functions.
This package contains the basic utility and client programs necessary
to maintain and work with local or remote PostgreSQL databases as well
as manual pages for the SQL commands that PostgreSQL supports. Full
HTML documentation for PostgreSQL can be found in the postgresql-docs
package.Information for package postgresql10-server:
Repository : Leap_15_2_Updates
Name : postgresql10-server
Version : 10.16-lp152.2.15.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 18.7 MiB
Installed : Yes
Status : up-to-date
Source package : postgresql10-10.16-lp152.2.15.1.src
Summary : The Programs Needed to Create and Run a PostgreSQL Server
Description :
PostgreSQL is an advanced object-relational database management system
that supports an extended subset of the SQL standard, including
transactions, foreign keys, sub-queries, triggers, and user-defined
types and functions.
This package includes the programs needed to create and run a
PostgreSQL server, which will in turn allow you to create and maintain
PostgreSQL databases.

And then…

HomeData:~ # systemctl start rockstor
A dependency job for rockstor.service failed. See ‘journalctl -xe’ for details.

HomeData:~ # journalctl -f
– Logs begin at Wed 2021-04-14 00:04:10 AEST. –
Apr 14 02:24:23 HomeData initrock[3637]: File “/opt/rockstor/src/rockstor/system/osi.py”, line 201, in run_command
Apr 14 02:24:23 HomeData initrock[3637]: raise CommandException(cmd, out, err, rc)
Apr 14 02:24:23 HomeData initrock[3637]: system.exceptions.CommandException: Error running a command. cmd = /opt/rockstor/bin/django migrate --noinput --fake-initial --database=default contenttypes.
rc = 1. stdout = [’’]. stderr = [‘Traceback (most recent call last):’, ’ File “/opt/rockstor/bin/django”, line 44, in ‘, " sys.exit(djangorecipe.manage.main(‘rockstor.settings’))", ’ F
ile “/opt/rockstor/eggs/djangorecipe-1.9-py2.7.egg/djangorecipe/manage.py”, line 9, in main’, ’ management.execute_from_command_line(sys.argv)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.eg
g/django/core/management/init.py”, line 354, in execute_from_command_line’, ’ utility.execute()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/init.py”, line
346, in execute’, ’ self.fetch_command(subcommand).run_from_argv(self.argv)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/base.py”, line 394, in run_from_argv’, ’
self.execute(*args, **cmd_options)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/base.py”, line 445, in execute’, ’ output = self.handle(*args, **options)’, ’ F
ile “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/core/management/commands/migrate.py”, line 93, in handle’, ’ executor = MigrationExecutor(connection, self.migration_progress_callback)’, ’
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/executor.py”, line 19, in init’, ’ self.loader = MigrationLoader(self.connection)’, ’ File “/opt/rockstor/eggs/Django-1
.8.16-py2.7.egg/django/db/migrations/loader.py”, line 47, in init’, ’ self.build_graph()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/loader.py”, line 191, in bu
ild_graph’, ’ self.applied_migrations = recorder.applied_migrations()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/recorder.py”, line 59, in applied_migrations’, ’
self.ensure_schema()’, ’ File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/migrations/recorder.py
Apr 14 02:24:23 HomeData initrock[3637]: ", line 49, in ensure_schema’, ’ if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):’, ’ File “/opt/
rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/base/base.py”, line 164, in cursor’, ’ cursor = self.make_cursor(self._cursor())’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/dja
ngo/db/backends/base/base.py”, line 135, in _cursor’, ’ self.ensure_connection()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/base/base.py”, line 130, in ensure_connec
tion’, ’ self.connect()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/utils.py”, line 98, in exit’, ’ six.reraise(dj_exc_type, dj_exc_value, traceback)’, ’ File “/opt/ro
ckstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/base/base.py”, line 130, in ensure_connection’, ’ self.connect()’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/ba
se/base.py”, line 119, in connect’, ’ self.connection = self.get_new_connection(conn_params)’, ’ File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/postgresql_psycopg2/base.py”,
line 176, in get_new_connection’, ’ connection = Database.connect(**conn_params)’, ’ File “/opt/rockstor/eggs/psycopg2-2.7.4-py2.7-linux-x86_64.egg/psycopg2/init.py”, line 130, in connect’,
’ conn = _connect(dsn, connection_factory=connection_factory, **kwasync)’, ‘django.db.utils.OperationalError: could not connect to server: No such file or directory’, ‘\tIs the server running lo
cally and accepting’, ‘\tconnections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”?’, ‘’, ‘’]
Apr 14 02:24:23 HomeData systemd[1]: rockstor-pre.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 02:24:23 HomeData systemd[1]: Failed to start Tasks required prior to starting Rockstor.
Apr 14 02:24:23 HomeData systemd[1]: Dependency failed for RockStor startup script.
Apr 14 02:24:23 HomeData systemd[1]: rockstor.service: Job rockstor.service/start failed with result ‘dependency’.
Apr 14 02:24:23 HomeData systemd[1]: rockstor-pre.service: Unit entered failed state.
Apr 14 02:24:23 HomeData systemd[1]: rockstor-pre.service: Failed with result ‘exit-code’.

HomeData:~ # systemctl status postgresql
● postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled; vendor preset: disabled)
Active: inactive (dead)

HomeData:~ # journalctl -b -u postgresql
– Logs begin at Wed 2021-04-14 00:04:10 AEST, end at Wed 2021-04-14 02:24:23 AEST. –
– No entries –

It doesn’t look good to me :thinking:

10

@Tony_Cristiano I can chip in on this one hopefully.
This:

is an exact repeat of what we had before, database service not started (or found), but from your:

We have an indication that the postgresql service is not actually enabled (at boot) and is also not running (started): as per the Rockstor service error report. And from the “vendor preset: disabled” this is the default state of this service.

Try enabling the postgresql service (so it starts at boot) and starting it (so it’s running now) then try the rockstor service start.

systemctl enable postgresql
systemctl start postgresql

Then the rockstor bit:

systemctl start rockstor

or just reboot. Which you should do anyway to ensure you have proper/expected function from power-on.

Hope that helps and let us know how that looks.

3 Likes
11

That PostgreSQL starting was the answer. Everything is working now after reboot.

Thanks for all your prompt support.

3 Likes
12

Just wanted to throw in that I had a similar issue over this weekend - pulled my rockstor 3 drive and updated a fresh drive to rockstor 4 - had to update to a newer kernel and version of btrfs progs because I had them updated to 5.11 on my rockstor 3 instance, but after all that when I tried to get my rockons working it kept failing with “exit code” in the systemctl info. So I looked at the dockerd:

rockstor1:~ # dockerd
failed to load listeners: can’t create unix socket /var/run/docker.sock: is a directory

Looking at the output of ls -al /var/run/docker.sock and sure enough it is a directory.

rockstor1:~ # ls -al /var/run/docker.sock
total 0
drwxr-xr-x 2 root root 40 Apr 19 10:30 .
drwxr-xr-x 25 root root 840 Apr 19 10:43 …

Removing that folder and a systemctl restart docker.service and I’m back in action!

2 Likes