Beiträge von mumbedeus

mumbedeus · 27. März 2020

No, I just performed one single reboot... Do you want me to try several?

mumbedeus · 26. März 2020

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?

mumbedeus · 25. März 2020

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

This is what happens when trying to purge folder2ram:

Code

$ sudo apt-get purge openmediavault-flashmemory folder2ram
[sudo] password for mariusenglund:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  folder2ram* openmediavault-flashmemory*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 245 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 53315 files and directories currently installed.)
Removing openmediavault-flashmemory (5.0.7) ...

will now sync all mountpoints
/var/log unmounted, cannot comply
sync of /var/tmp successful!
sync of /var/lib/openmediavault/rrd successful!
sync of /var/spool successful!
sync of /var/lib/rrdcached successful!
sync of /var/lib/monit successful!
sync of /var/cache/samba successful!

will now stop all mountpoints
stop /var/log
/var/log already unmounted
stop /var/tmp
stop /var/lib/openmediavault/rrd
stop /var/spool
stop /var/lib/rrdcached
stop /var/lib/monit
stop /var/cache/samba
Warning: Can't execute disable on the unit file path. Proceeding with the unit name.
Removed /etc/systemd/system/basic.target.wants/folder2ram_startup.service.
Warning: Can't execute disable on the unit file path. Proceeding with the unit name.
Removed /etc/systemd/system/shutdown.target.wants/folder2ram_shutdown.service.
Removed /etc/systemd/system/reboot.target.wants/folder2ram_shutdown.service.
Removed /etc/systemd/system/halt.target.wants/folder2ram_shutdown.service.
Removing folder2ram (0.3.3) ...
/sbin/folder2ram: 980: /sbin/folder2ram: insserv: not found
/sbin/folder2ram: 996: /sbin/folder2ram: insserv: not found
dpkg: error processing package folder2ram (--remove):
 installed folder2ram package pre-removal script subprocess returned error exit status 127
Errors were encountered while processing:
 folder2ram
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

Alles anzeigen

mumbedeus · 25. März 2020

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?!

mumbedeus · 25. März 2020

Aaaah! Here is the output:

Zitat

$ sudo apt-cache policy openmediavault-flashmemory folder2ram

openmediavault-flashmemory:

Installed: (none)

Candidate: 5.0.7

Version table:

5.0.7 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

100 /var/lib/dpkg/status

5.0.6 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

5.0.5 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

5.0.4 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

5.0.3 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

5.0.2 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

5.0.1 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

5.0 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

folder2ram:

Installed: 0.3.3

Candidate: 0.3.3

Version table:

*** 0.3.3 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

100 /var/lib/dpkg/status

0.3.1 500

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages

500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages

$

Alles anzeigen

mumbedeus · 25. März 2020

Thank you so much! Yes it works now

Zitat von ryecoaaron

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?

mumbedeus · 25. März 2020

Would you like to help me out with the exact commands so that I don't mess up my system? ?

mumbedeus · 24. März 2020

Tonight I got this error by mail:

Code

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

mumbedeus · 23. März 2020

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

Code

Mar 23 21:25:07 SERVERNAME systemd[1]: Starting A high performance web server
Mar 23 21:25:08 SERVERNAME nginx[7011]: nginx: [alert] could not open error lo
Mar 23 21:25:08 SERVERNAME nginx[7011]: 2020/03/23 21:25:08 [emerg] 7011#7011:
Mar 23 21:25:08 SERVERNAME nginx[7011]: nginx: configuration file /etc/nginx/n
Mar 23 21:25:08 SERVERNAME systemd[1]: nginx.service: Control process exited,
Mar 23 21:25:08 SERVERNAME systemd[1]: nginx.service: Failed with result 'exit
Mar 23 21:25:08 SERVERNAME systemd[1]: Failed to start A high performance web
Mar 23 21:26:08 SERVERNAME systemd[1]: Starting A high performance web server
lines 71-93
Mar 23 21:22:06 SERVERNAME systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 23 21:23:07 SERVERNAME systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 23 21:23:07 SERVERNAME nginx[6412]: nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (2: No such file or directory)
Mar 23 21:23:07 SERVERNAME nginx[6412]: 2020/03/23 21:23:07 [emerg] 6412#6412: open() "/var/log/nginx/access.log" failed (2: No such file or directory)
Mar 23 21:23:07 SERVERNAME nginx[6412]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 23 21:23:07 SERVERNAME systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Mar 23 21:23:07 SERVERNAME systemd[1]: nginx.service: Failed with result 'exit-code'.

Alles anzeigen

mumbedeus · 23. März 2020

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):

Zitat von Mumbedeus

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

Code

The system monitoring needs your attention.


Host:        \SERVERNAME
Date:        Sun, 08 Mar 2020 18:48:00
Service:     nginx
Event:       Does not exist
Description: process is not running


This triggered the monitoring system to: restart


—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Alles anzeigen

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

Code

The system monitoring needs your attention.


Host:        \SERVERNAME
Date:        Sun, 08 Mar 2020 18:48:31
Service:     nginx
Event:       Execution failed
Description: failed to start (exit status 1) -- '/bin/systemctl start nginx': Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.




This triggered the monitoring system to: alert


—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Alles anzeigen

mumbedeus · 23. März 2020

I ran the commands, but still same problem when reboot...

mumbedeus · 23. März 2020

Btw: After a reboot, I have to do the two last commands one more time. Is this just a temporary fix?

mumbedeus · 23. März 2020

Holy cow! That worked!!!

What had happened to my system?

Thank you so, so much, ryecoaaron! You are skilled!

mumbedeus · 20. März 2020

The output is as following:

Code

$ ls -ld /var/log/nginx
ls: cannot access '/var/log/nginx': No such file or directory

mumbedeus · 19. März 2020

Zitat von ryecoaaron

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:

Code

----------
          ID: test_nginx_service_config
    Function: cmd.run
        Name: nginx -t
      Result: False
     Comment: Command "nginx -t" run
     Started: 16:04:58.245857
    Duration: 80.561 ms
     Changes:
              ----------
              pid:
                  17610
              retcode:
                  1
              stderr:
                  nginx: [alert] could not open error log file: open() "/var/log                                                                                                         /nginx/error.log" failed (2: No such file or directory)
                  nginx: the configuration file /etc/nginx/nginx.conf syntax is                                                                                                          ok
                  2020/03/19 16:04:58 [emerg] 17610#17610: open() "/var/log/ngin                                                                                                         x/access.log" failed (2: No such file or directory)
                  nginx: configuration file /etc/nginx/nginx.conf test failed
              stdout:
----------
          ID: restart_nginx_service
    Function: service.running
        Name: nginx
      Result: False
     Comment: One or more requisite failed: omv.deploy.nginx.default.test_nginx_                                                                                                         service_config
     Started: 16:04:58.376095
    Duration: 0.026 ms
     Changes:
----------
          ID: monitor_nginx_service
    Function: module.run
        Name: monit.monitor
      Result: False
     Comment: One or more requisite failed: omv.deploy.nginx.default.restart_ngi                                                                                                         nx_service
     Started: 16:04:58.381140
    Duration: 0.026 ms
     Changes:

Summary for rock64
------------
Succeeded: 5 (changed=4)
Failed:    3
------------
Total states run:     8
Total run time:   8.645 s

Alles anzeigen

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?

Mumbedeus

mumbedeus · 17. März 2020

Zitat von ryecoaaron

What version of OMV?

OMV 5. Everything works, but I can not access the OMV GUI...

mumbedeus · 10. März 2020

Anyone?

mumbedeus · 8. März 2020

Hello!

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

Code

The system monitoring needs your attention.


Host:        \SERVERNAME
Date:        Sun, 08 Mar 2020 18:48:00
Service:     nginx
Event:       Does not exist
Description: process is not running


This triggered the monitoring system to: restart


—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Alles anzeigen

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

Code

The system monitoring needs your attention.


Host:        \SERVERNAME
Date:        Sun, 08 Mar 2020 18:48:31
Service:     nginx
Event:       Execution failed
Description: failed to start (exit status 1) -- '/bin/systemctl start nginx': Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.




This triggered the monitoring system to: alert


—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Alles anzeigen

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

RUNNING COMMAND "systemctl status nginx.service"

Code

$ sudo systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: en
   Active: failed (Result: exit-code) since Sun 2020-03-08 18:57:04 CET; 28s ago
     Docs: man:nginx(8)
  Process: 5458 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process


Mar 08 18:57:04 SERVERNAME systemd[1]: Starting A high performance web server
Mar 08 18:57:04 SERVERNAME nginx[5458]: nginx: [alert] could not open error lo
Mar 08 18:57:04 SERVERNAME nginx[5458]: 2020/03/08 18:57:04 [emerg] 5458#5458:
Mar 08 18:57:04 SERVERNAME nginx[5458]: nginx: configuration file /etc/nginx/n
Mar 08 18:57:04 SERVERNAME systemd[1]: nginx.service: Control process exited,
Mar 08 18:57:04 SERVERNAME systemd[1]: nginx.service: Failed with result 'exit
Mar 08 18:57:04 SERVERNAME systemd[1]: Failed to start A high performance web

Alles anzeigen

Thank you!

mumbedeus · 15. Januar 2020

Zitat von votdev

Seems to be a bug in the SMART database that is downloaded automatically. I assume they will fix that asap, because OMV can not do anything here.

Ok, that's good! Crossing fingers

mumbedeus · 15. Januar 2020

Hello!

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

Code

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, www.smartmontools.org /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
Marius

Beiträge von mumbedeus

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

WebGUI unavailable

S.M.A.R.T. - ERROR

S.M.A.R.T. - ERROR