Posts by mumbedeus

    Ok, so now I have done what you said. After purging both flashmemory and folder2ram, I checked if they were still installed with apt-cache policy openmediavault-flashmemory folder2ram. Neither of them was.

    After a reboot, I installed the flashmemory plugin from web interface, as you told me to, and did a new reboot.

    Now the interface is gone. Again.

    I then run the same apt-cache policy openmediavault-flashmemory folder2ram code via SSH, and now both flashmemory and folder2ram is installed. I swear I didn't manually installed folder2ram - it was removed the moment before I installed flashmemory.

    Any idea what is happening?

    Sorry, I didn't read the log properly earlier...

    This is what happens when trying to purge folder2ram:

    No, I haven't reinstalled anything. Hm...

    I just reinstalled the flashmemory plugin in the GUI and rebooted. Now the GUI is unavaliable again. Received a couple of e-mails too... Ha-ha, wtf?!

    Aaaah! Here is the output:

    Thank you so much! Yes it works now 8)

    Obviously something is deleting all of sub-directories in /var/log causing this problem. I would purge openmediavault-flashmemory and folder2ram, create the directories, and see if it works after reboot. If that is working, then re-install flashmemory.

    As you wrote in an earlier post; "If that is working, then re-install flashmemory.". If I did what you said, is flashmemory reinstalled too?

    Tonight I got this error by mail:

    touch: cannot touch '/var/log/cron-apt/log': No such file or directory
    /usr/sbin/cron-apt: 155: /usr/sbin/cron-apt: cannot create /var/log/cron-apt/log: Directory nonexistent
    /usr/sbin/cron-apt: 155: /usr/sbin/cron-apt: cannot create /var/log/cron-apt/log: Directory nonexistent
    /usr/sbin/cron-apt: 155: /usr/sbin/cron-apt: cannot create /var/log/cron-apt/log: Directory nonexistenttouch: cannot touch '/var/log/cron-apt/log': No such file or directory

    The output was much more longer than this, but all look the same:

    I ran those four commands just now, and couldn't see anything fail during the prosess. However, the problem still exists, and I get the same two mail from the OMV-system (and WebGUI is gone):

    FIRST EMAIL: [SERVERNAME] Monitoring restart -- Does not exist nginx

    SECOND EMAIL: [SERVERNAME] Monitoring alert -- Execution failed nginx

    as root:

    omv-salt deploy run nginx

    omv-salt deploy run phpfpm

    Thank you! I just ran the commands, but among all the green text, there was some processes that failed (red text). Look below.

    Part of output (the red text) with sudo omv-salt deploy run nginx with sudo user:

    When running sudo omv-salt deploy run phpfpm there was no red text - only blue and green. Nothing failed.

    Still I cannot access the GUI...

    Do you have an idea why nginx is failing?



    After taking an upgrade to my system recently, OMV's WebGUI is unavailable.
    My private mail box is spammed by the OMV system telling me something is wrong. Does anyone know what I should do to get the GUI up running?

    (Root login are disabled in the GUI, but I have an active user connected to the SSH and SUDO group.)

    FIRST EMAIL: [SERVERNAME] Monitoring restart -- Does not exist nginx

    SECOND EMAIL: [SERVERNAME] Monitoring alert -- Execution failed nginx

    There is obviously something wrong with nginx, but I need help to solve it...

    RUNNING COMMAND "systemctl status nginx.service"

    Thank you! :D


    After upgrading my system to the most recent update yesterday, I get the following error when visiting the S.M.A.R.T. page:

    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; smartctl -x '/dev/sda' -d sat 2>&1' with exit code '1': smartctl 6.6 2017-11-05 r4594 [aarch64-linux-5.3.11-rockchip64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, /var/lib/smartmontools/drivedb/drivedb.h(1): Syntax error, invalid char 'n'

    Am I the only one facing this?

    The error makes reading hard drive temperatures impossible...

    Best regards