Posts by votdev

Sorry, did not realize that these are not the signatures of the OMV repo. You need to check the docker docs and omv-extras.org how to get their signatures.

ryecoaaron Can you say anything related to your repo?

Go to CLI and run apt-get install --reinstall --allow-unauthenticated openmediavault-keyring.

May I ask what you are working on?

You have to install them on you test system.

You can use Vagrant to setup a local test system. Then simply SSH into the system, cd /home/vagrant/openmediavault/openmediavault-<PLUGIN>

Test Salt an UI code

cp -rv srv/* /srv
cp -rf usr/* usr

Debug your PHP code

monit stop omv-engined
omv-engined -d -f

You can use a container to build the plugin for final tests.

OMV does not use the OS root device for data storage by design. As ryecoaaron mentioned the sharerootfs plugin can be used to use that device as well.

The fix is already in progress, check https://github.com/openmediavault/openmediavault/pull/1559.

/etc/resolv.conf does not show any name servers because this is handled by systemd-resolved internally.

Your DNS seems still not correct. What have you entered in the DNS field in the network interface page?

Please provide us with examples, e.g. device names, serial numbers, screenshots, whatever. I don't know what you are meaning with hexadecimal numbers.

OMV is using systemd-resolved for DNS resolution.

If no DNS servers are set this sounds like you are using static IP and no DHCP. In that case go to the network interface page and add the dns server per interface. The nice thing in systemd-resolved is that you are able to use different DNS servers per nic.

Check out this to easily integrate whatever service as notification target.

openmediavault/deb/openmediavault/usr/share/openmediavault/notification/sink.d at master · openmediavault/openmediavault

openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux. It contains services like SSH, (S)FTP, SMB/CIFS, DAAP…

github.com

Notifications — openmediavault 6.x.y documentation

Apodaca and compose are sub-shared folders of system. Ate all of them on a BTRFS file system? The error messages occur when you access which share via SMB?

Can you confirm that the shared folder you are accessing has other BTRFS subvolumes below? As far as I found out the mentioned error only appears if the device number of a path has changed regarding the configured root path of the SMB share.

References:

• https://savannah.gnu.org/bugs/?50859

OMV is displaying what sysfs or UDEV provides. OMV does not call external commands like smartctl or other tools by intention because calling those commands is very expensive.

The system time is translated into the browser local time.

Quote from striscio

I tried your command and my server become unreachable. Luckily I have kvm interface and I connected through that and I see that my network interfaces are down. I tried to reissue your command and I got this (sorry for the jpeg but I couldn't copy and paste from the kvm app).ù

I also tried omv-firstaid to reconfigure at least one of the two network interfaces but I still have the error.

Now I'm stuck...

Just a little update: I rebooted and the first interface I reconfigured with omv-firstaid came up correctly.

I re-run the omv-salt command you suggested and I still get errors (see the second error screenshot)

Another update: the web interface gave me some pending configuration changes.

So I checked the dirtymodules.json

Code

root@omv:~# cat /var/lib/openmediavault/dirtymodules.json 
[
    "nut",
    "avahi",
    "collectd",
    "halt",
    "hosts",
    "issue",
    "systemd-networkd",
    "task"

So I issued a

Code

omv-salt deploy run nut avahi collectd halt issue systemd-networkd hosts 

I had another netplan error and my interface went offline again... I rebooted through KVM and I ran the single modules

I tried and succeded with nut, avahi, collectd, halt, issue, hosts.

I tried with 'task' and I had ERROR: The state 'task' does not exist

I tried finally with systemd-networkd and it took waaaay longer than the other modules. My network interface went down again and I had to reboot through the KVM console to have my server back online.

Last resort: I configured my network interface through the web interface and gave it a static address. Every config update that was pending in the interface ran successfully. I even tried to re-run your omv-salt deploy run hosts systemd-networkd: it succeeded and completed in a short amount of time.

Than I configured my bridge interface on the second network adapter. and it seems ok. Let's wait and see.

Is there a reason why configuring the network adapter through omv-firstaid led to a netplan error?

Sorry for the long post but I really would want to fix this.

Display More

Maybe https://www.openmediavault.org/?p=3492 is the reason.

Let's see if OMV can do anything here. I wantto avoid that suggested workaround to add /etc/fstab entries.

• https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1735953
  
• https://bugzilla.samba.org/show_bug.cgi?id=10541

Yesterday i did some more research on how systemd-resolved works. There were some design decisions related to single-label hostnames. The problem is that if the DHCP server of your router does not deliver a domainname, resolving such single-label hostnames will not be successful. So if this does not work, check the DHCP server if it acts correct.

If there are still problems with resolving single-labels, there is a workaround by adding

ResolveUnicastSingleLabel=yes

to /etc/systemd/resolved.conf.d/foo-bar-baz.conf and restart systemd-resolved. But this is a security problem with public DNS servers; so use this only if your DNS server is your own.

References:

• https://github.com/systemd/sys…es#issuecomment-179203186
• https://askubuntu.com/a/1230195
• https://www.freedesktop.org/so…Protocols%20and%20Routing
• https://wiki.archlinux.org/tit…_hostnames_without_suffix

Quote from striscio

My system is on a Xeon processor, 32 Gb RAM and a ssd disk.

It's not apt commands or kernel module building that are very slow, but the various salt command at the end of the update process.

To be clearer, it's when I have the "Pending changes" notification in the GUI or, when I use the cli, the various salt passages after the packages are installed.

This morning I had two packages to be installed (openmediavault and openmediavault-nut).

I edited /etc/salt/minion file and I added debug log.

I also added another option that helped when I had the same problem in the past which is

Code

enable_fqdns_grains: False

This time the update took a reasonable amount of time (under a minute).

Code

# time omv-upgrade

real    0m54.915s
user    0m21.385s
sys    0m5.316s

thanks.

Display More

Disabling grains is not a good idea because hostname is used e.g. when postfix is deployed. You should do a omv-salt deploy run systemd-networkd hosts. There were some changes in resolving DNS info, so every getaddr is now much faster which speeds up Salt startup process.