WebGUI unavailable

mumbedeus · Mar 8th 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.

Display More

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.

Display More

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

Display More

Thank you!

mumbedeus · Mar 10th 2020

Anyone?

ryecoaaron · Mar 10th 2020

What version of OMV?

mumbedeus · Mar 17th 2020

Quote from ryecoaaron

What version of OMV?

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

ryecoaaron · Mar 18th 2020

as root:

omv-salt deploy run nginx

omv-salt deploy run phpfpm

mumbedeus · Mar 19th 2020

Quote from 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

Display More

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

ryecoaaron · Mar 20th 2020

what is the output of:

ls -ld /var/log/nginx

mumbedeus · Mar 20th 2020

The output is as following:

Code

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

ryecoaaron · Mar 21st 2020

sudo mkdir /var/log/nginx

sudo omv-salt deploy run nginx

mumbedeus · Mar 23rd 2020

Holy cow! That worked!!!

What had happened to my system?

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

mumbedeus · Mar 23rd 2020

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

ryecoaaron · Mar 23rd 2020

Quote from Mumbedeus

Is this just a temporary fix?

It shouldn't have been. Run those commands one more time and then as root run: folder2ram -syncall

mumbedeus · Mar 23rd 2020

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

ryecoaaron · Mar 23rd 2020

what is the output of:

folder2ram -disablesystemd

run the commands from above again

folder2ram -enablesystemd

mumbedeus · Mar 23rd 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):

Quote from 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.

Display More

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.

Display More

ryecoaaron · Mar 23rd 2020

what is the output of: journalctl -u nginx

mumbedeus · Mar 23rd 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'.

Display More

mumbedeus · Mar 24th 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

ryecoaaron · Mar 24th 2020

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.

mumbedeus · Mar 25th 2020

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

WebGUI unavailable

mumbedeus Mar 17th 2020

Participate now!