I installed the snapshot plugin to create a daily backup of my Docker folder. I configured everything correctly, choosing the source directory, the destination directory, and the frequency (daily). However, I'm unsure about the automation. I haven't found any option to schedule or choose a time to perform this backup. Where can I find this information? From what I've seen, it's performing the backup at 3:30 AM, but I need it to do it in the morning.
Posts by Sandro_Rocha
-
-
Display More
How is OMV's network connection configured? If it's via DHCP try setting a static address instead.
A description of your OMV hardware might be helpful.
What network related tests have you run on the OMV machine when this happens and what results do you get?
Just saying that it doesn't work isn't going to be very helpful.
The server already has a static IP address, via MAC address on the router.
My server has a mini-ITX motherboard with a J4105 processor and 8GB of RAM. The network card has an RTL 8111H chip. It has a CNVi wireless connection, but I keep it disabled, only enabling it when I need to move the server and maintain the network connection.
The only test I do to check for connection loss is running a ping command.
As I said, the connection loss is random, it happens occasionally and is resolved by restarting the server.
PS: I was thinking of running some command to check the connection from time to time (like every hour) and, if the server is inaccessible, restart the network service. What command could I schedule for this purpose?
-
Exactly what does this mean? Be extremely specific as to what you are doing when this happens, and what is the system telling you.
This means that I can access the services and the web interface via the internal network IP. But the server simply loses internet access. For example, I can access the interface via IP 192.168.50.x:xx, but when I tell OMV to search for updates or download a file via torrent or directly, I don't have internet access. All other devices maintain the connection except for OMV. And it happens randomly; out of nowhere, OMV loses its internet connection, and I don't know how to identify the problem or where to look.
-
I have OMV 7 installed. Randomly, it's losing its internet connection. I can still access it via my home network, but the server simply can't access the internet. Since this happens without a pattern, I don't know where to look for the problem. Any tips on how to identify the culprit or at least minimize this problem?
-
In the shell run this command:
Codesudo e2label /dev/sdb1 new-label-name-hereDoes the mount point (/dev/sdx) not change with each reboot?
-
I had 101 GB of space on a disk. I used FileZilla to transfer 6 files totaling 1.45 GB to a folder on that disk. It gave a transfer error, as if there wasn't enough space, and then the disk space dropped to 38 GB. I checked for temporary files, files in .recycle or .trash, any cache, etc., but found nothing unusual. Has anyone else experienced this? Was it a problem with the FTP? Any clues as to what might have happened?
-
77 updates appeared to be required. I updated, but the server prompted me to apply them, but it gave an error. I've restarted the server, but the prompt to apply them persists and continues to give an error. How to solve?
CodePending configuration changes You must apply these changes in order for them to take effect. The following modules will be updated: rsyslog sambaCode
Display MoreFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color rsyslog 2>&1' with exit code '1': debian: ---------- ID: configure_rsyslog_main Function: file.managed Name: /etc/rsyslog.conf Result: True Comment: File /etc/rsyslog.conf is in the correct state Started: 11:24:19.485302 Duration: 546.282 ms Changes: ---------- ID: divert_rsyslog_main Function: omv_dpkg.divert_add Name: /etc/rsyslog.conf Result: True Comment: Leaving 'local diversion of /etc/rsyslog.conf to /tmp/_etc_rsyslog.conf' Started: 11:24:20.038083 Duration: 80.666 ms Changes: ---------- ID: configure_rsyslog_pamfaillock Function: file.managed Name: /etc/rsyslog.d/openmediavault-pamfaillock.conf Result: True Comment: File /etc/rsyslog.d/openmediavault-pamfaillock.conf is in the correct state Started: 11:24:20.119073 Duration: 560.105 ms Changes: ---------- ID: configure_rsyslog_remote Function: file.managed Name: /etc/rsyslog.d/openmediavault-remote.conf Result: True Comment: File /etc/rsyslog.d/openmediavault-remote.conf is in the correct state Started: 11:24:20.679469 Duration: 428.879 ms Changes: ---------- ID: test_rsyslog_config Function: cmd.run Name: rsyslogd -N1 Result: False Comment: Command "rsyslogd -N1" run Started: 11:24:21.110776 Duration: 37.348 ms Changes: ---------- pid: 13728 retcode: 1 stderr: rsyslogd: version 8.2302.0, config validation run (level 1), master config /etc/rsyslog.conf rsyslogd: module 'imuxsock' already in this config, cannot be added [v8.2302.0 try https://www.rsyslog.com/e/2221 ] stdout: ---------- ID: start_rsyslog_service Function: module.run Result: True Comment: service.restart: True Started: 11:24:21.150673 Duration: 246.601 ms Changes: ---------- service.restart: True Summary for debian ------------ Succeeded: 5 (changed=2) Failed: 1 ------------ Total states run: 6 Total run time: 1.900 s [ERROR ] Command 'rsyslogd' failed with return code: 1 [ERROR ] stderr: rsyslogd: version 8.2302.0, config validation run (level 1), master config /etc/rsyslog.conf rsyslogd: module 'imuxsock' already in this config, cannot be added [v8.2302.0 try https://www.rsyslog.com/e/2221 ] [ERROR ] retcode: 1 [ERROR ] {'pid': 13728, 'retcode': 1, 'stdout': '', 'stderr': "rsyslogd: version 8.2302.0, config validation run (level 1), master config /etc/rsyslog.conf\nrsyslogd: module 'imuxsock' already in this config, cannot be added [v8.2302.0 try https://www.rsyslog.com/e/2221 ]"} OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color rsyslog 2>&1' with exit code '1': debian: ---------- ID: configure_rsyslog_main Function: file.managed Name: /etc/rsyslog.conf Result: True Comment: File /etc/rsyslog.conf is in the correct state Started: 11:24:19.485302 Duration: 546.282 ms Changes: ---------- ID: divert_rsyslog_main Function: omv_dpkg.divert_add Name: /etc/rsyslog.conf Result: True Comment: Leaving 'local diversion of /etc/rsyslog.conf to /tmp/_etc_rsyslog.conf' Started: 11:24:20.038083 Duration: 80.666 ms Changes: ---------- ID: configure_rsyslog_pamfaillock Function: file.managed Name: /etc/rsyslog.d/openmediavault-pamfaillock.conf Result: True Comment: File /etc/rsyslog.d/openmediavault-pamfaillock.conf is in the correct state Started: 11:24:20.119073 Duration: 560.105 ms Changes: ---------- ID: configure_rsyslog_remote Function: file.managed Name: /etc/rsyslog.d/openmediavault-remote.conf Result: True Comment: File /etc/rsyslog.d/openmediavault-remote.conf is in the correct state Started: 11:24:20.679469 Duration: 428.879 ms Changes: ---------- ID: test_rsyslog_config Function: cmd.run Name: rsyslogd -N1 Result: False Comment: Command "rsyslogd -N1" run Started: 11:24:21.110776 Duration: 37.348 ms Changes: ---------- pid: 13728 retcode: 1 stderr: rsyslogd: version 8.2302.0, config validation run (level 1), master config /etc/rsyslog.conf rsyslogd: module 'imuxsock' already in this config, cannot be added [v8.2302.0 try https://www.rsyslog.com/e/2221 ] stdout: ---------- ID: start_rsyslog_service Function: module.run Result: True Comment: service.restart: True Started: 11:24:21.150673 Duration: 246.601 ms Changes: ---------- service.restart: True Summary for debian ------------ Succeeded: 5 (changed=2) Failed: 1 ------------ Total states run: 6 Total run time: 1.900 s [ERROR ] Command 'rsyslogd' failed with return code: 1 [ERROR ] stderr: rsyslogd: version 8.2302.0, config validation run (level 1), master config /etc/rsyslog.conf rsyslogd: module 'imuxsock' already in this config, cannot be added [v8.2302.0 try https://www.rsyslog.com/e/2221 ] [ERROR ] retcode: 1 [ERROR ] {'pid': 13728, 'retcode': 1, 'stdout': '', 'stderr': "rsyslogd: version 8.2302.0, config validation run (level 1), master config /etc/rsyslog.conf\nrsyslogd: module 'imuxsock' already in this config, cannot be added [v8.2302.0 try https://www.rsyslog.com/e/2221 ]"} in /usr/share/php/openmediavault/system/process.inc:247 Stack trace: #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute() #1 /usr/share/openmediavault/engined/rpc/config.inc(187): OMV\Engine\Module\ServiceAbstract->deploy() #2 [internal function]: Engined\Rpc\Config->applyChanges() #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array() #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(155): OMV\Rpc\ServiceAbstract->callMethod() #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}() #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(152): OMV\Rpc\ServiceAbstract->execBgProc() #7 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg() #8 [internal function]: Engined\Rpc\Config->applyChangesBg() #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array() #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod() #11 /usr/sbin/omv-engined(546): OMV\Rpc\Rpc::call() #12 {main} -
As I said, for now I wanted to connect the server while on the same network. Later I'll see how to connect it while off it.
After fiddling around a bit, I think it worked, with some reservations. I configured the app with my server's MAC, with UDP port 9 and set the server's IP as the destination and the transmitter as 255.255.255.255.255. It worked, the server connected. The caveat is that, despite having opened port 9 to my server's address, it worked even without me having activated this redirection. So I don't know if there is a problem with my router's firmware, which opens ports even though the rule is disabled, or if the router woke up the first device with WoL enabled that it found, ignoring the server's MAC that I configured in the app.
-
The WAN address is the public IP address that your router gets from your ISP.
Your broadcast address would be 192.168.1.255 or you can use 255.255.255.255
I want to wake up the server while on the same network. My provider blocks my external access, so that I need to use a VPN to do anything on the server if I'm away from home. In this case, what addresses do I need to use?
-
Display More
May not work if your router will not accept broadcast packets from the internet or your OMV NIC does not support WOL.
1) Configure your router to forward port 9 UDP to the broadcast address of your LAN.
2) From your phone, send the WOL packet to the WAN address of your router.
Good luck.
Can you be more specific? For example, my server has the IP 192.168.50.95 and the router's IP is 192.168.50.1. In this case, what would be the broadcast address and the WAN address?
-
I would like a step-by-step guide on how to configure Wake on LAN. My idea is to be able to turn on the server via my cell phone, but I don't know how to do it. I have already activated the option in the BIOS, in the OMV web network interface, installed the plug-in and installed an app on my cell phone to do this, but some questions have arisen. For example, the app asks for the IP address of the host (I think the device that will send the command), the machine (which will be woken up, I think) and the port (9 comes by default). The plug-in screen shows some devices connected to the same network. Do I need to include the device that will send the wake-up command in this list? Do I need to configure the router? Do I need to configure this port in some OMV configuration?
-
Display More
you can use: (the --dry-run FLAG will only simulate what will happen without making any changes)
Post the output INSIDE A CODEBOX
[How-To] Post content in a code box - Guides - openmediavault
of:
sudo apt purge openmediavault-wakealarm openmediavault-wol --dry-run
I decided to install the plugins and now everything is fine. There is just one detail: only the WakeonAlarm configuration page appears. WOL doesn't have a configuration page?
-
There's wol and wakealarm still on v6.
Run the fix script.
I looked here and these plugins do not seem to be installed or if they are, their respective configuration pages are no longer available. In fact, I remember installing them but never stopped to set up or use. They won’t be missed by the hour and versions 7 are available for download. How do I remove these "ghost" plugins?
-
There's wol and wakealarm still on v6.
Run the fix script.
I ran the script but it didn’t change.
dpkg -l | grep openme
ii openmediavault 7.4.17-2 all openmediavault - The open network attached storage solution
ii openmediavault-apttool 7.1.1 all apt tool plugin for OpenMediaVault.
ii openmediavault-autoshutdown 7.0.1 all OpenMediaVault AutoShutdown Plugin
ii openmediavault-backup 7.1.4 all backup plugin for OpenMediaVault.
ii openmediavault-compose 7.3.1 all OpenMediaVault compose plugin
ii openmediavault-downloader 7.0 all OpenMediaVault downloader plugin
ii openmediavault-flashmemory 7.0.1 all folder2ram plugin for openmediavault
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-mergerfs 7.0.5 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 7.0 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-remotemount 7.0.2 all Remote mount plugin for OpenMediaVault.
ii openmediavault-resetperms 7.1 all Reset Permissions
ii openmediavault-rsnapshot 7.0.1 all OpenMediaVault rsnapshot backup plugin.
ii openmediavault-sharerootfs 7.0-1 all openmediavault share root filesystem plugin
ii openmediavault-symlinks 7.0 all OpenMediaVault symlinks plugin
ic openmediavault-wakealarm 6.0.1 all wakealarm plugin for OpenMediaVault.
ii openmediavault-wetty 7.0-2 all openmediavault WeTTY (Web + TTY) plugin
ic openmediavault-wol 6.1.3 all OpenMediaVault WOL plugin
-
Display More
Run dpkg -l | grep openme to see the versions installed.
Check the GUI plugins page and confirm they show v7
You can run the fix script that it will clear any issues
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix6to7upgrade | sudo bash
dpkg -l | grep openme
ii openmediavault 7.4.17-2 all openmediavault - The open network attached storage solution
ii openmediavault-apttool 7.1.1 all apt tool plugin for OpenMediaVault.
ii openmediavault-autoshutdown 7.0.1 all OpenMediaVault AutoShutdown Plugin
ii openmediavault-backup 7.1.4 all backup plugin for OpenMediaVault.
ii openmediavault-compose 7.3.1 all OpenMediaVault compose plugin
ii openmediavault-downloader 7.0 all OpenMediaVault downloader plugin
ii openmediavault-flashmemory 7.0.1 all folder2ram plugin for openmediavault
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-mergerfs 7.0.5 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 7.0 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-remotemount 7.0.2 all Remote mount plugin for OpenMediaVault.
ii openmediavault-resetperms 7.1 all Reset Permissions
ii openmediavault-rsnapshot 7.0.1 all OpenMediaVault rsnapshot backup plugin.
ii openmediavault-sharerootfs 7.0-1 all openmediavault share root filesystem plugin
ii openmediavault-symlinks 7.0 all OpenMediaVault symlinks plugin
ic openmediavault-wakealarm 6.0.1 all wakealarm plugin for OpenMediaVault.
ii openmediavault-wetty 7.0-2 all openmediavault WeTTY (Web + TTY) plugin
ic openmediavault-wol 6.1.3 all OpenMediaVault WOL plugin
Do I need to run that second command or is it OK?
-
Display More
If you are so concern about losing anything, make sure you have a complete backup of all the important DATA.
Make a clone of the OS drive and test it to see if its good.
Bring down all docker containers to have less running apps.
Run the upgrade locally OR via SSH inside a screen session to prevent "lost connection".
The upgrade takes some time but should run flawless.
It will end when showing "Reboot the server"
After, check the GUI and accept the yellow banner and just confirm that all is OK.
Bring UP all the containers.
If issues happen, ask here and they'll be sorted.
There's a few (lot) of threads on the forum on upgrade.
Good luck
I ran the command and after 25 minutes OMV 7 went up and apparently everything OK. I'm still testing but it looks like everything is working cool. Thanks!
-
No. omv-release-upgrade does.
I have MergerFS, some Docker containers, a few other plugins installed and some smb shares configured. If I upgrade via the command line, will I have any problems, will I lose anything?
-
Try instead
sudo omv-salt deploy run omvextras
And again
omv-upgrade
The "apt update" command is no longer giving a signature error. Will this omv-upgrade command upgrade the version from 6 to 7?
-
I have to look this up everytime because I don't remember how these old versions work.
Run: sudo omv-salt deploy omvextras
sudo omv-salt deploy omvextras
Usage: omv-salt deploy [OPTIONS] COMMAND [ARGS]...
Try 'omv-salt deploy --help' for help.
Error: No such command 'omvextras'.
-
Display More
[EDIT] Some food for thoughts:
How to fix GPG NO_PUBKEY Error: "The following signatures couldn't be..."A good command to run is:
sudo apt update -o Debug::Acquire::gpgv=true
This will show more about the error.
Just for INFO, don't go doing things that you don't know or understand and make it worse than it is.
As for safety, just make sure you have a proper working clone of the OS drive, just in case you need to revert any mistakes.
[/EDIT]
Almost certain it will fail.
The main reason I've seen for errors with the gpg signatures is due to hybrid systems (mix of 32 and 64bit and on Pis)
Doesn't mean it's the case here.
To check that, post the output of
dpkg --print-architecture
uname -a
grep -r developers /etc/apt/*
omv-aptclean repos
grep -r developers /etc/apt/* (Yes, again to check the differences after the clean repos)
.
