Socket connect error errno 2 no such file or directory - Исправление ошибок и поиск оптимальных решений проблем

Introduction

Actually, this is also another article discussing about how to solve an error message. This is actually not an error message where the solving step is in a specific action or solution. Instead, there is a sequence on executing the supervisor command before a certain command can work normally. Before further going on, supervisor itself is a tool where it is is a client/server system. It allows its users to monitor and control several processes on UNIX-like operating systems. Furthermore, it is also useful to control processes and it is an utility to to start program or service at boot time. There is an article for further reference in installing supervisor tool. It exist in this link with the title of ‘How to Install supervisord in Linux CentOS 7’. The following is the actual command execution which is causing the error message to appear :

[root@localhost etc]# supervisorctl reread
error: <class 'socket.error'>, [Errno 2] No such file or directory: file: /usr/lib64/python2.7/socket.py line: 224
[root@localhost etc]#

After the installation of the supervisor tool is a success, there is an additional step to change the supervisor configuration file. Normally, that yum configuration file exist in /etc/yum.conf. It is a command execution after configuring or changing the supervisor configuration file exist by adding the following entries in the bottom part of the file with the ‘program:gunicorn’ block :

...
...
...
[program:gunicorn]
directory=/home/django/project/myapps
command=/home/django/project/env/bin/gunicorn --workers 3 --bind unix:/home/django/project/myapps/apps.sock apps.wsgi:application
autostart=true
autorestart=true
stderr_logfile=/var/log/gunicorn/gunicorn.out.log
stdout_logfile=/var/log/gunicorn/gunicorn.err.log
user=root
group=django
environment=LANG=en_US.UTF-8,LC_ALL=en_US.UTF-8

[group:guni]
programs:gunicorn

Well, it does not have any direct impact to the error appear, but the command ‘supervisorctl reread’ is a command useful to instruct supervisor to read again the changes exist in the supervisor configuration file.

Actually, the contnet

Solution

So, the problem which is causing the problem above is just a matter of command sequence execution. In this case, there is a command execution using ‘supervisor’. Apparently, the solution is very simple. The error appear as soon as the installation of ‘supervisor’ is in a success as in the article in this link, changing the supervisor configuration file and execution the ‘supervisor reread’ command to instruct supervisor to read the changes exist in it. But in order for supervisor to do that, the supervisor service must be active and running while in this case it is not. This is a simple mistake where the supervisor service is not active and triggering the error. So, the solution is very easy. Just make sure the supervisor service is running. If it is not, just run the command for running the supervisor service. The command ‘supervisorctl reread’ will run properly if the supervisor service is currently running. So, run it as below :

[root@localhost ~]# systemctl start supervisord
[root@localhost ~]# systemctl status supervisord
● supervisord.service - Process Monitoring and Control Daemon
   Loaded: loaded (/usr/lib/systemd/system/supervisord.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2021-11-25 16:54:22 UTC; 3s ago
  Process: 2206 ExecStart=/usr/bin/supervisord -c /etc/supervisord.conf (code=exited, status=0/SUCCESS)
 Main PID: 2209 (supervisord)
   CGroup: /system.slice/supervisord.service
           ├─2209 /usr/bin/python /usr/bin/supervisord -c /etc/supervisord.conf
           ├─2219 /home/django/project/env/bin/python /home/django/project/env/bin/gunicorn --workers 3 --bind unix:/home/django/project/myapps/apps.sock apps.wsgi:appl...
           ├─2222 /home/django/project/env/bin/python /home/django/project/env/bin/gunicorn --workers 3 --bind unix:/home/django/project/myapps/apps.sock apps.wsgi:appl...
           └─2224 /home/django/project/env/bin/python /home/django/project/env/bin/gunicorn --workers 3 --bind unix:/home/django/project/myapps/apps.sock apps.wsgi:appl...

Nov 25 16:54:22 localhost systemd[1]: Starting Process Monitoring and Control Daemon...
Nov 25 16:54:22 localhost systemd[1]: Started Process Monitoring and Control Daemon.
[root@localhost log]# supervisorctl reread
No config updates to processes
[root@localhost log]#

Источник

Description

John Reiser

2010-02-16 22:13:10 UTC

Description of problem: Install from DVD aborts before graphical splash screen, soon after "Running anconda 13.26, the Fedora system installer - please wait."


Version-Release number of selected component (if applicable):
anaconda-13.26

How reproducible: every time


Steps to Reproduce:
1. Compose DVD from rawhide of 2010-02-16 (Tuesday) using pungi.
2. Boot DVD for install, proceed through text menu questions until "Running anaconda 13.26, ..."
3.
  
Actual results: Traceback (most recent call last):
  File "/usr/bin/anaconda", line 766, in <module>
    import anaconda_log
  File "/usr/lib/anaconda/anaconda_log.py", line 134, in <module>
    logger = AnacondaLog()
  File "/usr/lib/anaconda/anaconda_log.py", line 75, in __init__
    self.forwardToSyslog(self.logger)
  File "/usr/lib/anaconda/anaconda_log.py", line 130, in fowardToSyslog
    logger.name)
  File "/usr/lib/anaconda/anaconda_log.py:, line 58, in __init__
    SysLogHandler.__init__(self, address, facility)
  File "/usr/lib64/python2.6/logging/handlers.py", line 710, in __init__
    self._connect_unixsodket(address)
  File "/usr/lib64/python2.6/logging/handlers.py", line 725, in _connect_unixsocket
    self.socket.connect(address)
  File "<string>", line 1, in connect
socket.error: [Errno 2] No such file or directory
install exited abnormally [1/1]

Expected results: graphical splash screen and rest of install


Additional info:

Comment 1

Chris Lumens

2010-02-16 22:24:15 UTC

There were two problems with rsyslog not starting up:  (1) we were missing a library, resulting in needing to rebuild anaconda.  (2) rsyslog was having its own problems starting.  Did you pull both into your rebuild?

Comment 2

John Reiser

2010-02-16 22:34:33 UTC

Ummm, I didn't do anything special except run pungi (and comment-out all the Language support lines.)  So, I'll run pungi again.  What's the recipe for the workarounds/fixes?

Comment 4

John Reiser

2010-02-17 20:57:16 UTC

I re-ran the pungi compose today, but the new DVD still gets the same error when booted for install.

The console definitely says "Running anaconda-13.26, the Fedora system installer."

I watched; the compose downloaded rsyslog-4.4.2-6.fc13.x86_64 during the yumdownload portion of buildinstall.

The DVD/isolinux/initrd.img after "gzip -d" and "cpio -i --make-directories" has 
  $ find . -name '*syslog*'
  ./sbin/rsyslogd
  ./etc/rsyslog.conf
  ./lib64/rsyslog
  $ ldd ./sbin/rsyslogd  # not virtualized, but ...
	linux-vdso.so.1 =>  (0x00007fff859ff000)
	libz.so.1 => /lib64/libz.so.1 (0x00000038fcc00000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00000038fc000000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00000038fc400000)
	librt.so.1 => /lib64/librt.so.1 (0x00000038fc800000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003419800000)
	libc.so.6 => /lib64/libc.so.6 (0x00000038fb800000)
	/lib64/ld-linux-x86-64.so.2 (0x00000038fb400000)
and each of those DSOs [except for linux-vdso.so.1] is found in ./lib64.  I don't see where there is a library missing.

Comment 6

Ales Kozumplik

2010-02-18 07:31:35 UTC

Hi John,

you are seeing the exact same error as bug 564213, but with 13.26 this went away for other people. It looks like rsyslogd is still not starting on your machine:

1) Can you please share the failing .iso image with us? If that's too big then at least the initrd.img and install.img files.

2) Are you giving any extra command line parameters to the kernel?

Thank you,
Ales

Comment 7

John Reiser

2010-02-18 16:03:21 UTC

Hi Ales,

wget http://bitwagon.com/initrd.img    #  30380814 bytes
wget http://bitwagon.com/install.img   # 133619712 bytes
It will take about 3 hours of uploading for the full DVD, so please try those two .img first.  I've verified that my DVD still fails in the same way, and that those URLs give the correct files after a round-trip across the net.

Comment 8

John Reiser

2010-02-18 16:05:41 UTC

And 2): I just type <Enter> ["Install or upgrade ..."] at the boot screen, so there are no extra command line parameters to the kernel.

Comment 9

John Reiser

2010-02-22 02:53:31 UTC

anaconda-13.28-1.fc13.x86_64 lists
  
  usr/$LIBDIR/rsyslog

in the $KEEPFILE as a directory to be copied over  (/usr/lib/anaconda-runtime/upd-instroot line 499) but the library actually lives in

  /$LIBDIR/rsyslog

without the "/usr".

Comment 10

Ales Kozumplik

2010-02-22 08:10:22 UTC

Hi John,

You are mentioning the exact error that was fixed with bug #564213 and released in anaconda-13.26.

This is weird, I think your anaconda-13.28 is not the real anaconda-13.28: I used yumdownloader with a rawhide repo like this this morning:

yumdownloader --enablerepo=rawhide anaconda

What it gave me was anaconda-13.28-1.fc14.i686.rpm. I unpacked that and looked at upd-instroot and it is in the fixed version already, of course.

I also downloaded the latest f13 version of anaconda from one of the official fedora mirrors here: 
http://ftp.linux.cz/pub/linux/fedora/linux/development/13/x86_64/os/Packages/

That's also fixed. Maybe you've got a customized anaconda version where somebody forgot to merge the latest patches? (but still release new versions... weird).

Going to close this as not a bug in a couple of days unless something new comes into light.

Ales

Comment 11

John Reiser

2010-02-22 21:47:59 UTC

The problem is caused by bug 567411, "/tmp contaminates the output DVD and CDs of pungi+buildinstall".

Comment 12

Ales Kozumplik

2010-02-23 08:20:53 UTC

Okay, I'm closing this one now.

Источник

I have been struggling with this for hours, but still cannot resolve the following error when I login to OMV 5 GUI. Steps:

1. Go to server IP using default port 80

2. Systems displays login page.

4. Enter admin/password.

5. There is some delay then it throws the following error:

Failed to connect to socket: No such file or directory
Error #0:OMVRpcException: Failed to connect to socket: No such file or directory in /usr/share/php/openmediavault/rpc/rpc.inc:141Stack trace:#0 /var/www/openmediavault/rpc/session.inc(57): OMVRpcRpc::call('UserMgmt', 'authUser', Array, Array, 2, true)#1 [internal function]: OMVRpcServiceSession->login(Array, Array)#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMVRpcServiceAbstract->callMethod('login', Array, Array)#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMVRpcRpc::call('Session', 'login', Array, Array, 3)#5 /var/www/openmediavault/rpc.php(45): OMVRpcProxyJson->handle()#6 {main}

I checked this board, and in the other case I found it said to check for unsupported plugins, which I did:

with these results:

ii  openmediavault                      5.5.16-1                            all          openmediavault - The open network attached storage solution
ii  openmediavault-flashmemory          5.0.7                               all          folder2ram plugin for OpenMediaVault
ic  openmediavault-keyring              1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg         5.4.2                               all          OMV-Extras.org Package Repositories for OpenMediaVault
ic  openmediavault-usbbackup            5.0.6-1                             all          openmediavault USB/eSATA backup plugin
ic  openmediavault-wol                  3.4.2                               all          OpenMediaVault WOL plugin

Note my configuration on Raspberry Pi 3:

Welcome to ARMBIAN 5.46 experimental Debian GNU/Linux 10 (buster) 5.4.72-v7+ 
System load:   0.00 0.00 0.00      Up time:       4:19 hours 
Memory usage:  10 % of 974MB      IP:            192.168.0.19
CPU temp:      55°C  
Usage of /:    34% of 7.2G       storage/:      6% of 1.8T

I also tried:

which threw a few errors at the end.

E: Failed to fetch file:/var/cache/openmediavault/archives/Packages.gz  Method gave a blank filename
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-all.gz  File not found - /var/cache/openmediavault/archives/Contents-all.gz (2: No such file or directory)
[tt]E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-armhf.gz  File not found - /var/cache/openmediavault/archives/Contents-armhf.gz (2: No such file or directory)
E: Some index files failed to download. They have been ignored, or old ones used instead.

Also rebooted after with errors:

[    2.311645] [vc_sm_connected_init]: start
[    2.315154] vc_vchi_sm_init: failed to open VCHI service (-1)
[    2.315162] [vc_sm_connected_init]: failed to initialize shared memory service
[    2.315411] [vc_sm_connected_init]: end - returning -1
-----------
[    6.558816] [vc_sm_connected_init]: start
[    6.560215] vc_sm_cma_vchi_init: failed to open VCHI service (-1)
[    6.560224] [vc_sm_connected_init]: failed to initialize shared memory service
----------
[    6.727110] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[    6.729200] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
----------
[    6.740826] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
----------
[    6.881086] sd 0:0:0:0: [sda] No Caching mode page found
[    6.881161] sd 0:0:0:0: [sda] Assuming drive cache: write through
----------
[    7.419621] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
----------
[    7.706032] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    7.721908] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

Alles anzeigen

Also you should know that when I use:

I get a bunch of error messages saying the various .rrd files have timestamps in the future. Each time I run it, answering Yes to delete the files, it says it is deleting them (50 files each time), I can do this indefinitely, even between reboots. That doesn’t make sense to me.

«date» returns correct date, time and timezone and I am using a timeserver.

Any ideas? What should I try next?

Offizieller Beitrag
- #2
ic openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

Try
wget -O "/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc" https://packages.openmediavault.org/public/archive.key apt-key add "/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc" apt-get update

Thanks for the recommendation. After running the commands and a reboot, I am still getting the same exact errors logging into the GUI. Could this be a permissions issue? Also note that there were errors. Here is the terminal output of all three of the above commands with errors highlighted:

root@MediaServerPi1:~# wget -O "/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc" https://packages.openmediavault.org/public/archive.key
--2020-11-15 21:54:49--  https://packages.openmediavault.org/public/archive.key
Resolving packages.openmediavault.org (packages.openmediavault.org)... 178.254.11.33
Connecting to packages.openmediavault.org (packages.openmediavault.org)|178.254.11.33|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3134 (3.1K) [application/pgp-keys]
Saving to: ‘/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc’

/etc/apt/trusted.gpg.d/openmediavaul 100%[===================================================================>]   3.06K  --.-KB/s    in 0.001s  

2020-11-15 21:54:50 (4.07 MB/s) - ‘/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc’ saved [3134/3134]

root@MediaServerPi1:~# apt-key add "/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc"
OK
root@MediaServerPi1:~# apt-get update
Get:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
Get:2 file:/var/cache/openmediavault/archives  Release
Ign:2 file:/var/cache/openmediavault/archives  Release
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Contents (deb)
Ign:4 file:/var/cache/openmediavault/archives  Contents (deb)
Get:5 file:/var/cache/openmediavault/archives  Contents (deb)
Ign:5 file:/var/cache/openmediavault/archives  Contents (deb)
Hit:6 http://security.debian.org buster/updates InRelease
Hit:7 http://httpredir.debian.org/debian buster InRelease                                                                                       
Hit:8 http://security.debian.org/debian-security buster/updates InRelease                                                                       
Get:9 http://httpredir.debian.org/debian buster-updates InRelease [51.9 kB]                                                                     
Hit:10 https://download.docker.com/linux/debian buster InRelease                                                                                
Get:11 http://httpredir.debian.org/debian buster-backports InRelease [46.7 kB]                                                                  
Ign:12 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease                                                            
Get:14 https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release [4,363 B]                                                    
Hit:15 http://packages.openmediavault.org/public usul InRelease                                                                                 
Hit:16 https://archive.raspberrypi.org/debian buster InRelease                                                              
Hit:13 https://imola.armbian.com/apt buster InRelease                   
Get:17 http://httpredir.debian.org/debian buster-backports/main armhf Packages.diff/Index [16.0 kB]
Get:18 http://httpredir.debian.org/debian buster-backports/main armhf Packages 2020-11-16-0205.06.pdiff [1,671 B]
Get:18 http://httpredir.debian.org/debian buster-backports/main armhf Packages 2020-11-16-0205.06.pdiff [1,671 B]
Fetched 121 kB in 6s (19.8 kB/s)                                                                                                                
Reading package lists... Done
E: Failed to fetch file:/var/cache/openmediavault/archives/Packages.gz  Method gave a blank filename
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-all.gz  File not found - /var/cache/openmediavault/archives/Contents-all.gz (2: No such file or directory)
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-armhf.gz  File not found - /var/cache/openmediavault/archives/Contents-armhf.gz (2: No such file or directory)
E: Some index files failed to download. They have been ignored, or old ones used instead.
root@MediaServerPi1:~# reboot

Alles anzeigen

Here is the dpkg list:

root@MediaServerPi1:~# dpkg -l | grep openm
ii  openmediavault                      5.5.16-1                            all          openmediavault - The open network attached storage solution
ii  openmediavault-flashmemory          5.0.7                               all          folder2ram plugin for OpenMediaVault
ic  openmediavault-keyring              1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg         5.4.2                               all          OMV-Extras.org Package Repositories for OpenMediaVault
ic  openmediavault-usbbackup            5.0.6-1                             all          openmediavault USB/eSATA backup plugin
ic  openmediavault-wol                  3.4.2                               all          OpenMediaVault WOL plugin
root@MediaServerPi1:~#

It looks like the keyring version didn’t change.

Any other thoughts on how to resolve?

Offizieller Beitrag
- #4
Try «apt clean» from omv-firstaid

und dann nochmal

apt-get update

Hi, Ran suggested commands and got some errors:

apt clean:

E: Failed to fetch file:/var/cache/openmediavault/archives/Packages.gz  Method gave a blank filename
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-armhf.gz  File not found - /var/cache/openmediavault/archives/Contents-armhf.gz (2: No such file or directory)
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-all.gz  File not found - /var/cache/openmediavault/archives/Contents-all.gz (2: No such file or directory)
E: Some index files failed to download. They have been ignored, or old ones used instead.
ERROR: Command 'omv-aptclean' returned non-zero exit status 100.

apt-get update produced similar errors:

E: Failed to fetch file:/var/cache/openmediavault/archives/Packages.gz  Method gave a blank filename
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-armhf.gz  File not found - /var/cache/openmediavault/archives/Contents-armhf.gz (2: No such file or directory)
E: Failed to fetch file:/var/cache/openmediavault/archives/Contents-all.gz  File not found - /var/cache/openmediavault/archives/Contents-all.gz (2: No such file or directory)
E: Some index files failed to download. They have been ignored, or old ones used instead.

Are these critical errors?

Thanks for your help with this!

Offizieller Beitrag
- #6
Thanks for your help with this!

Not so much of help

Tagging ryecoaaron
Offizieller Beitrag
- #7
I really dislike these trainwreck rpi installs… Did you install with the install script or update from 4.x??

sudo rm /etc/apt/sources.list.d/openmediavault-local.list

sudo omv-aptclean

wget http://packages.openmediavault.org/public/pool/main/o/openmediavault-keyring/openmediavault-keyring_1.0_all.deb

sudo dpkg -i openmediavault-keyring_1.0_all.deb

sudo apt-get update

sudo apt-get install openmediavault-usbbackup openmediavault-wol

I updated from OMV 4, and I am truly sorry for the trouble.

I executed all the commands. Rebooted and cleared my browser cache. None of the commands threw errors, but the problem remains. Note that the I am able to access shared directories and media files using VMC, so it seems the underlying services are running, just can’t use the web interface. I tried changing the port in omv-firstaid and it threw an error as well.

ERROR: Failed to connect /var/lib/openmediavault/engined.sock: [Errno 2] No such file or directory.

GUI Login throws the same error as before:

Error #0:
OMVRpcException: Failed to connect to socket: No such file or directory in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(57): OMVRpcRpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMVRpcServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMVRpcRpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMVRpcProxyJson->handle()
#6 {main}

Results for

dpkg -l | grep openm

ii  openmediavault                      5.5.16-1                            all          openmediavault - The open network attached storage solution
ii  openmediavault-flashmemory          5.0.7                               all          folder2ram plugin for OpenMediaVault
ii  openmediavault-keyring              1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg         5.4.2                               all          OMV-Extras.org Package Repositories for OpenMediaVault
ic  openmediavault-usbbackup            5.0.6-1                             all          openmediavault USB/eSATA backup plugin
ic  openmediavault-wol                  3.4.2                               all          OpenMediaVault WOL plugin

Should the keyring version be 1.0?

- #9
I finally got it working. The problem was that openmediavault-engined was somehow masked and was not starting. I have no idea how this happened.

First I unmasked the file:

Systemctl umask openmediavault-engined
Systemctl unmask openmediavault-engined Systemctl start openmediavault-engined
I was then able to login, even after a reboot, but things were missing from the GUI.

So I ran

Rebooted, cleared cache, and we are up and running.
Offizieller Beitrag
- #10
All’s well that ends well.

For future ref; a clean install results in a clean and healthy OS and, in most cases, it actually saves time. (As you may have discovered.)
- #11
It took me a long time to get it working the first time. Thought the upgrade would be the smoothest path. Admittedly I was wrong about that. Glad I had some linux skills from long ago…saved my bacon.
- #12
I finally got it working. The problem was that openmediavault-engined was somehow masked and was not starting. I have no idea how this happened.

First I unmasked the file:

Systemctl umask openmediavault-engined

Systemctl umask openmediavault-engined Systemctl start openmediavault-engined

I was then able to login, even after a reboot, but things were missing from the GUI.

So I ran

Rebooted, cleared cache, and we are up and running.

Alles anzeigen
This works for me, I’ve been plagued by this problem for two weeks now, thank you so much!
- #13
There are some little problems with the code, which should actually be
systemctl unmask openmediavault-engined systemctl start openmediavault-engined

Источник