is there anyway I can get thios partially working, namely the web gui so that I can remember all of my configurations etc to copy over when I setup the new install?
I don't know, but maybe it will help you to make a copy of:
/etc/openmediavault/config.xml
At least it will help you to consult the previous configuration values and to be able to copy.
Yes, you have only to redo the config, the data stays on the disk. Take a copy of /etc/config.xml to remember how you did it before.
Yes, you have only to redo the config, the data stays on the disk. Take a copy of /etc/config.xml to remember how you did it before.
i think i'm doing this wrong. i'm using the nano command to access that file but honestly i dont know what i'm really doing
on that broken drive in the etc folder, there doesn't seem to be a config file
The correct route is the one I told you before. Look at the previous post.
how are youaccessing the drive?
Boot linux live cd from usb stick? Then the question is where to put the copy. Maybe you can add snother usb stick which you can read on your other computer.
Then use the file manager to copy the file. /my_broken_disk/etc/openmediavault/config.xml to that usb. unplug the usb and try to read the file from windows.
how are youaccessing the drive?
Boot linux live cd from usb stick? Then the question is where to put the copy. Maybe you can add snother usb stick which you can read on your other computer.
Then use the file manager to copy the file. /my_broken_disk/etc/openmediavault/config.xml to that usb. unplug the usb and try to read the file from windows.
i've setup a new omv installation from a usb stick, then using nano to read the config file but I wanted to copy the contents into a text file some how but it wont allow me to copy the contents from nano
I do not understand. config.xml is essentially a text file.
you can type it to the console with cat /path/to/config.xml
Following the nginx errors I had last week, which was tracked down to a faulty hard drive, I did a new install last week on a new USB drive.
Its been working fine all week but today I was presented with over 80 nginx error/fail emails.
I've run all of the PC tests through the BIOS which passed.
On the bootup - I noticed this error, not sure if its relat
I also noticed these outputs:
root@OMV:~# dmesg | grep error
[ 9.009450] EXT4-fs (sdg1): re-mounted. Opts: errors=remount-ro
[ 10.813203] platform regulatory.0: Direct firmware load for regulatory.db fai led with error -2
root@OMV:~# dmesg | grep fail
[ 10.813106] platform regulatory.0: firmware: failed to load regulatory.db (-2)
[ 10.813203] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 10.813204] cfg80211: failed to load regulatory.db
root@OMV:~#Can anyone shed any light why I keep getting these nginx issues (not sure what nginx is) ?
Description: loadavg (1min) of 15.5 matches resource limit [loadavg (1min) > 8.0]
That message is simply a notice of CPU load averaging. https://en.euro-linux.com/blog…-process-states-on-linux/
If it bothers you, you can disable it in the GUI.
That message is simply a notice of CPU load averaging. https://en.euro-linux.com/blog…-process-states-on-linux/
If it bothers you, you can disable it in the GUI.
It doesn't bother me. I thought it was might be related to the constant nginx failure, I've been getting, which in turn means I cant access my system per #29
nginx is the web server that OMV uses to display the interface in your browser.
Have you installed any application directly on the host?
Have you installed a desktop system?
nginx is the web server that OMV uses to display the interface in your browser.
Have you installed any application directly on the host?
Have you installed a desktop system?
No. The hardware is only used for OMV5.
Initially I had OMV5 installed for a couple of years but got this error a week ago (see earlier posts) which was traced to a bad system drive.
So I did a fresh install of OMV5 onto a new USB flash drive. Was back up and running and everything worked fine for a week but then started getting the emails etc again yesterday.
A load of 15 is rather high for a simple nas. Do you still have troubles with a disk where the kernal waits for timeouts?
A load of 15 is rather high for a simple nas. Do you still have troubles with a disk where the kernal waits for timeouts?
Not that I'm aware.
But not sure if this could be an issue. The original drive which failed last week is the internal drive and I have not removed this as I'd need to open the desktop and physicall remove it. However, BIOS sequence is setup to boot from USB (the new OMV5 installation), which is does. The failed internal drive is not mounted, so OMV should be ignoring it.
Can you check the logs in /var/log/nginx?
Can you check the logs in /var/log/nginx?
The only thing that was happening around that time is a scheduled job of Clam AV running for one of my data folders.
root@OMV:~# cat /var/log/nginx/error.log
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1156 exited on signal 9
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1155 exited on signal 9
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1157 exited on signal 9
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1158 exited on signal 9
2022/02/06 10:13:28 [alert] 16515#16515: worker process 16517 exited on signal 9Something is killing your worker processes with sigkill.
Check dmesg | grep "Out of" for out of memory, which is still the only reason I have seen this happening.
Don’t have an account yet? Register yourself now and be a part of our community!