Well, I visited https://wiki.omv-extras.org/ and found out that I needed to run the "sync" command through the plugin interface before anything else. After doing that, everything worked perfectly. Marking as resolved.
Posts by heinsenberg82
-
-
Hello everyone,
I'm trying to integrate Homarr with OpenMediaVault and I'm facing an authentication issue. I configured Homarr to connect to OpenMediaVault using the internal Docker network. I found that I can reach OpenMediaVault from my container using the IP
172.17.0.1
, which resolves to the host machine.However, when I try to authenticate, Homarr reports that my credentials are incorrect. I’m absolutely certain that I’m using the correct username and password because I can log in successfully to the OpenMediaVault web GUI with the same credentials.
Looking at the OpenMediaVault authentication logs, I found the following message:
Codeopenmediavault-webgui[17606]: Unauthorized login attempt from 172.18.0.6 [username=admin, user-agent=undici]
...where 172.18.0.6 is, in fact, homarr's internal IP.
This suggests that OpenMediaVault is receiving the request but rejecting the authentication.
Any guidance would be greatly appreciated!
Thanks in advance.
-
snapraid commands must be run as root or via sudo. I don't see you doing this.
This is how the SnapRaid plugin automatically configured the scheduled task. The command is running as root:
-
I’m getting an error when trying to run the scheduled task configured by SnapRAID plugin (for conf in /etc/snapraid/omv-snapraid-*.conf; do /usr/sbin/omv-snapraid-diff ${conf}; done).
This is my current SnapRAID configuration:
When I try to run the scheduled task manually, I get the following error:
Code
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=; export SHELL=/bin/sh; sudo --shell --non-interactive --user='root' -- /var/lib/openmediavault/cron.d/userdefined-57e13a3c-5a94-11ec-8153-3f587eab8e1f 2>&1' with exit code '1': 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=; export SHELL=/bin/sh; sudo --shell --non-interactive --user='root' -- /var/lib/openmediavault/cron.d/userdefined-57e13a3c-5a94-11ec-8153-3f587eab8e1f 2>&1' with exit code '1': in /usr/share/openmediavault/engined/rpc/cron.inc:198 Stack trace: #0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): Engined\Rpc\Cron->Engined\Rpc\{closure}() #1 /usr/share/openmediavault/engined/rpc/cron.inc(176): OMV\Rpc\ServiceAbstract->execBgProc() #2 [internal function]: Engined\Rpc\Cron->execute() #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array() #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod() #5 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call() #6 {main}
When I try to run the command sudo /usr/sbin/omv-snapraid-diff /etc/snapraid/default.confmanually, no error appears, although there is also no output in the terminal.
-
Install this on your dad's raspeberry and you won't need AnyDesk.
Have you found a really good guide about how to setup Wireguard on docker using IPV6? Because it is a nightmare....
Anyway, I'm trying something different than a VPN solution, because I want my domain to point to a single IPV6 address, that I can use from both inside the LAN and over the internet.
As I said, I'm already doing that with the x86 OMV6 machine I have in my home. I just can't do it with the Raspberry Pi.
-
Try using the multicast IPv6 address of the OMV box (They start with FF02::) when connecting from the LAN.
I will try that as soon as I can (when I'm there again or when my father is available on AnyDesk
), but meanwhile, I might found something relevant with regard to your suggestion:
I have my own OMV6 machine at my home, wich I can access from both LAN and internet using ipv6. This is the result of cat /etc/hosts:
Code
Display More# This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. 127.0.0.1 localhost.localdomain localhost 127.0.1.1 omv6.local omv6 # The following lines are desirable for IPv6 capable hosts. ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts
If I type ping ff02::1 (all nodes), then it pings a lot of hosts, including my OMV6 machine:
Code
Display MorePING ff02::1(ff02::1) 56 data bytes 64 bytes from fe80::bbbb:rrrr:mc50:5180%enp2s0: icmp_seq=1 ttl=64 time=0.055 ms 64 bytes from fe80::cccc:2776:qqqq:983%enp2s0: icmp_seq=1 ttl=64 time=0.265 ms 64 bytes from fe80::1%enp2s0: icmp_seq=1 ttl=64 time=0.634 ms 64 bytes from fe80::xxxx:yyyy:aaaa:1118%enp2s0: icmp_seq=1 ttl=64 time=1.16 ms 64 bytes from fe80::xxxx:yyyy:aaaa:16cc%enp2s0: icmp_seq=1 ttl=64 time=1.18 ms 64 bytes from fe80::xxxx:yyyy:aaaa:1848%enp2s0: icmp_seq=1 ttl=64 time=6.43 ms 64 bytes from fe80::xxxx:xxxx:106b%enp2s0: icmp_seq=1 ttl=64 time=106 ms ^C --- ff02::1 ping statistics --- 1 packets transmitted, 1 received, +6 duplicates, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.055/16.516/105.903/36.548 ms (addresses edited for security purposes)
If I try the same thing on the Raspberry Pi located at my parents' home, the ping is unsuccessfull - I get no packets received from anywhere:
CodePING ff02::1(ff02::1) 56 data bytes ^C --- ff02::1 ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 11445ms
By the way, this is the content of /etc/hosts on the RPi:
Code127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.1.1 raspberrypi
I hope this is useful.
-
First of all, let me say that I googled the hell out before posting this issue here. And it seems like very little people has this kind of issue. Usually, people have issues like not being able to access external ipv6 sites, or not being able to reach their device from the internet.
My issue is like the oposite of that. I have configured a OMV6 Raspberry Pi on my parents home. I can reach the device normally from my home (over the internet). I can SSH in the RPi and ping6 ipv6 sites normally. Everything seems to be ok on this matter.
However, when I'm in my parents home and try to access the RPi, that is, through the local network the RPi is hooked on, I just can't reach it .
Any insights will be appreciated, thank you.
-
Thank you all for your time. In a kind of a bittersweet situation, I'm sad and happy to say that the issue just... disapperead. I'm pretty sure I didn't do anything, but just now I clicked the "apply changes" button again and... it just worked. No warning banner anymore, and the drive is mounted. Go figure...
-
Do you have a 32-Bit-OMV?
Nope. 64-bit (Linux 5.14.0-0.bpo.2-amd64 kernel).
-
Just an update: I plugged the disk on another HD enclosure, and succesfully wiped and partitioned it using a software (Aomei Partition Manager). Then, I put it back on the Orico case hooked with the OpenmediaVault machine, and tried to mount it.
Now this weird thing happens: I get the same error, but the file system is being listed with the others. However, I can't get rid of the yellow warning message box that says "Pending configuration changes. You must apply these changes in order for them to take effect".
If I click on the apply button, I'm stuck with the same error. And I don't want to click on the roolback button (because I guess the filesystem had mounted succesfully). Is there a way to get rid of this warning yellow banner?
-
I''m trying to mount a 10Tb HD that is inside in a Orico Case hooked on a mini pc, but I'm keep receiving this long error:
I've already tried googling around about this quota issue, already tried the command sudo quotaoff -v /srv/*, but no luck yet. Any insights will be apreciated, thanks.
-
you need to download the Lite bullseye version to install OMV6
Nice to know man, thanks! I'll try that.
-
Yes, if you install Debian 11 Bullseye, 64 bits can also be installed (Google it for howto) and use the OMV install-script. It will then automatically install OMV 6 (beta).
I've tried doing that by downloading and installing the latest Rasperry Pi OS (a.k.a. Raspbian) image (using the "Raspberry Pi OS Imager" utility from https://www.raspberrypi.com/software/) on a brand new SD Card, and then running the install script ( sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash ), but got no luck. I get this error: "This system is running a desktop environment! This is not supported. Exiting..."
-
An installation on the host will allow you to support IPv6
Nice link, thank you for sharing! I was trying to avoid doing any installations outside the "docker | plugin" scheme, but I think I won't be able to avoid this for the vpn server.
-
Short answer is no. omv-extras plugins - porting progress to OMV 6.x
I have no interest in porting the openvpn plugin. I guess I could look at the wireguard plugin though. It isn't very flexible though.
Thanks for the feeback! A Wireguard plugin would be really awesome indeed, so fingers crossed..
-
Are there any plans to add an OpenVPN/Wireguard plugin to OMV6? I tried to use the linuxserver/wireguard container, but unfortunately I need IPV6 support.
-
This has been discussed on the forum:
omv-extras plugins - porting progress to OMV 6.x - Page 13 - Plugins - openmediavault
Hey man, thanks for pointing me to the right direction! I just put /srv/dev-disk-by-uuid-*/media/ in the "Paths" field of the plugin, and it worked!
-
I'm trying to use MergeFS plugin on my new OMV6 installation. When I merge 2 of my shared folders (each one pointing to a folder named "media" on different disks), everything is ok. However, if I try to add a third shared folder (again, pointing to a folder named "media" on a third different drive), then I get this error:
Code
Display MoreFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': debian: ---------- ID: configure_pool_dir Function: file.directory Name: /srv/mergerfs Result: True Comment: The directory /srv/mergerfs is in the correct state Started: 12:28:05.945908 Duration: 4.889 ms Changes: ---------- ID: remove_mergerfs_mount_files Function: module.run Result: True Comment: file.find: ['/etc/systemd/system/srv-mergerfs-media.mount'] Started: 12:28:05.951368 Duration: 2.54 ms Changes: ---------- file.find: - /etc/systemd/system/srv-mergerfs-media.mount ---------- ID: configure_mergerfs_media Function: file.managed Name: /etc/systemd/system/srv-mergerfs-media.mount Result: True Comment: File /etc/systemd/system/srv-mergerfs-media.mount updated Started: 12:28:05.954028 Duration: 35.597 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: systemd-reload_media Function: cmd.run Name: systemctl daemon-reload Result: True Comment: Command "systemctl daemon-reload" run Started: 12:28:05.990282 Duration: 239.331 ms Changes: ---------- pid: 11222 retcode: 0 stderr: stdout: ---------- ID: enable_media_mergerfs Function: service.enabled Name: srv-mergerfs-media.mount Result: True Comment: Service srv-mergerfs-media.mount is already enabled, and is in the desired state Started: 12:28:06.264423 Duration: 36.432 ms Changes: ---------- ID: restart_media_mergerfs Function: cmd.run Name: systemctl restart srv-mergerfs-media.mount Result: False Comment: Command "systemctl restart srv-mergerfs-media.mount" run Started: 12:28:06.301357 Duration: 15.783 ms Changes: ---------- pid: 11247 retcode: 1 stderr: Failed to restart srv-mergerfs-media.mount: Unit srv-mergerfs-media.mount failed to load properly: File name too long. See system logs and 'systemctl status srv-mergerfs-media.mount' for details. stdout: Summary for debian ------------ Succeeded: 5 (changed=4) Failed: 1 ------------ Total states run: 6 Total run time: 334.572 ms OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': debian: ---------- ID: configure_pool_dir Function: file.directory Name: /srv/mergerfs Result: True Comment: The directory /srv/mergerfs is in the correct state Started: 12:28:05.945908 Duration: 4.889 ms Changes: ---------- ID: remove_mergerfs_mount_files Function: module.run Result: True Comment: file.find: ['/etc/systemd/system/srv-mergerfs-media.mount'] Started: 12:28:05.951368 Duration: 2.54 ms Changes: ---------- file.find: - /etc/systemd/system/srv-mergerfs-media.mount ---------- ID: configure_mergerfs_media Function: file.managed Name: /etc/systemd/system/srv-mergerfs-media.mount Result: True Comment: File /etc/systemd/system/srv-mergerfs-media.mount updated Started: 12:28:05.954028 Duration: 35.597 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: systemd-reload_media Function: cmd.run Name: systemctl daemon-reload Result: True Comment: Command "systemctl daemon-reload" run Started: 12:28:05.990282 Duration: 239.331 ms Changes: ---------- pid: 11222 retcode: 0 stderr: stdout: ---------- ID: enable_media_mergerfs Function: service.enabled Name: srv-mergerfs-media.mount Result: True Comment: Service srv-mergerfs-media.mount is already enabled, and is in the desired state Started: 12:28:06.264423 Duration: 36.432 ms Changes: ---------- ID: restart_media_mergerfs Function: cmd.run Name: systemctl restart srv-mergerfs-media.mount Result: False Comment: Command "systemctl restart srv-mergerfs-media.mount" run Started: 12:28:06.301357 Duration: 15.783 ms Changes: ---------- pid: 11247 retcode: 1 stderr: Failed to restart srv-mergerfs-media.mount: Unit srv-mergerfs-media.mount failed to load properly: File name too long. See system logs and 'systemctl status srv-mergerfs-media.mount' for details. stdout: Summary for debian ------------ Succeeded: 5 (changed=4) Failed: 1 ------------ Total states run: 6 Total run time: 334.572 ms in /usr/share/php/openmediavault/system/process.inc:196 Stack trace: #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute() #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy() #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array) #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusLq...', '/tmp/bgoutput3c...') #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array) #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array) #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array) #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1) #12 {main}
If I run systemctl status srv-mergerfs-media.mount, I get this:
Codesrv-mergerfs-media.mount - MergerFS mount for media Loaded: error (Reason: Unit srv-mergerfs-media.mount failed to load properly: File name too long.) Active: inactive (dead) Where: /srv/mergerfs/media What: /srv/dev-disk-by-uuid-00259a2c-d4c1-4c25-8464-6f6d7e10ea74/media/:/srv/dev-disk-by-uuid-814e4bb0-de6d-4587-946d-c11316764bf5/media/:/srv/dev-disk-by-uuid-e3ba9cb9-e610-4b98-ad8f-87bc4e4099db/media/
(Notice the three paths I'm trying to merge, showed above. The third path I'm trying to add is the /srv/dev-disk-by-uuid-814e4bb0-de6d-4587-946d-c11316764bf5/media. If I just add the other two, I don't get this error)
I've tried to google this, but I have no clue where to start digging... Any help will be appreciated.
-
Maybe fixed in 6.0.5-3? From the changelog:
openmediavault (6.0.5-3) unstable; urgency=low
....snip
* Issue #1151: Increase user password strength.
Yeah, I think that's it! I noticed that it was an update available today. After the update, I can use the $ again
-
Thanks for the feedback guys. Since I'm able to login now, I will mark the issue as resolved. Later I will do some more tests and try to include the "$" again in my password.