Posts by TheLostSwede

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    You mean this soup?


  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    I still seem to have write access, but why are my drives jumbled again?

    The OS drive is now sdd again after another reboot. This can't be right, can it?

    I thought these things were static.

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Ok, clean install, everything looks right.

    Installing updates.

    For some reason, linux-image-5.16.0-0.bpo.4-amd64 5.16.12-1~bpo11+1 and linux-image-amd64 5.16.12-1~bpo11+1 never wants to install.

    Besides that, all updates install just fine.

    System rebooted and working as intendend so far.

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Something really odd is going on, as the drives change name/mount points.

    The OS SSD is normally sde, but today it came up as sdd.

    I could mount it now, but the last command still failed.

    Different failure message though.

    After a reboot, the OS SSD is back as sde and the filesystem is read only.

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Nope, not working. I tried remounting the OS drive, which is sde2 for some reason now.

    Could it have something to do with folder2ram? I forgot I had installed that.


  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Quote from Zoki

    Did you try to fix the mount of the mergerfs? This is a storage device and it can not be mounted according to the logs.

    But a so much of the log file is missing, one can only guess.

    I wouldn't have the first clue how to do that. I'm not a Linux expert.

    I've reinstalled OMV about half a dozen times by now and this happens every time after I update OMV and installed mergerfs.

    Going to reinstall again tomorrow and we'll see what happens.

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Quote from Zoki

    I do not know if this is the reason:


    Code
    Apr  9 00:09:08 OMV systemd[1]: local-fs.target: Cannot add dependency job, ignoring: Unit srv-mergerfs-jbod.mount failed to load properly: File name too long.

    but try to fix it (by editing /etc/fstab) after you remount the os disk rw.

    If the system crashes, before the flashmemory plugin writes the logs back to the hard disk, these logs are lost.

    The drives are empty now, so that's something old from before I wiped them.

    I thought the old unionfs install was part of the problem.

    I would guess this is no longer an issue, since I changed to mergerfs.

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Quote from macom

    Did you check your filesystem?

    How? I mean, I don't have a clue what has gone wrong and keeps going wrong.

    Every single time I've installed OMV 6 and after the first reboot, this happens.


  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Quote from Zoki

    anything in the nginx logs?

    In a recent thrad the directory /run/php was missing, can you check that


    ls -l /run/php


    Code
    root@omv:~# ls -l /run/php/
insgesamt 4
srw------- 1 www-data www-data  0  2. Apr 13:55 php7.4-fpm-openmediavault-webgui.sock
-rw-r--r-- 1 root     root      4  2. Apr 13:55 php7.4-fpm.pid
srw-rw---- 1 www-data www-data  0  2. Apr 13:55 php7.4-fpm.sock
lrwxrwxrwx 1 root     root     30  2. Apr 13:55 php-fpm.sock -> /etc/alternatives/php-fpm.sock
    Code
    root@OMV:~# ls -l /run/php
total 4
srw------- 1 www-data www-data 0 Apr 13 07:10 php7.4-fpm-openmediavault-webgui.sock
-rw-r--r-- 1 root     root     4 Apr 13 07:10 php7.4-fpm.pid
srw-rw---- 1 www-data www-data 0 Apr 13 07:10 php7.4-fpm.sock

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

  • 500 - Internal Server Error Failed to connect to socket: No such file or directory

    Ok, I have no idea what's going on, but I keep running into this issue after I reboot my NAS with OMV 6.

    It prevents me from logging in through the web UI and I have no idea why it's happening.

    It seems like the file system goes into read only mode by itself and this has happened several times in a row and keeps happening.

    Yes, I'm aware this is a pre-release OS, but I wasn't going to install 5.x again after my NAS trashed itself for some weird reason explained in a different thread.

    Any suggestions would be welcome.

    Code
    500 - Internal Server Error
Failed to connect to socket: No such file or directory


    Code
    root@OMV:~# dpkg -l | grep openm
ii  openmediavault                   6.0.21-1                      all          openmediavault - The open network attached storage solution
ii  openmediavault-flashmemory       6.1                           all          folder2ram plugin for openmediavault
ii  openmediavault-keyring           1.0                           all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-mergerfs          6.1.1                         all          mergerfs plugin for openmediavault.
ii  openmediavault-omvextrasorg      6.0.8                         all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-snapraid          6.0.4                         all          snapraid plugin for OpenMediaVault.
ii  openmediavault-usbbackup         6.0-10                        all          openmediavault USB/eSATA backup plugin