Posts by votdev

You didn't run omv-salt deploy run clamav.

It seems your system does not have internet connection.

Quote from ryecoaaron

maybe an additional boot option to disable ipv6 would be nice (if possible)?

I will check what i can do.

You should use the environment variable OMV_CLAMAV_CLAMD_MAXDIRECTORYRECURSION to customize it.

OMV installiert durch Abhängigkeiten nur die AppArmor Libraries, nicht aber den Service. Dass der Bug behoben ist hab ich auch gesehen, dennoch scheint mit der AppArmor Konfiguration für chrony etwas nicht zu stimmen. Mir scheint das Problem aber nur auf Dein System bezogen zu sein, da hier ansonsten öfters und schon vor langer Zeit solche Fehlermeldungen gemeldet gemeldet worden wären.

Das Problem ist AppAmor auf einem original Debian, OMV installiert dieses Paket nicht. Du solltest mal https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888038 anschauen. Wenn Du es ans laufen gebracht hast wäre es nett dies hier zu posten damit wir es in OMV einbauen können.

Have you rebooted the system after changing setting to static IP? I think the problem is that systemd-networkd and/or netplan.io (both are responsible for the network configuration) can not handle this correct without a reboot.

Die Konfiguration sieht gut aus. Steht sonst noch etwas im syslog? Kann leider mit Google nichts finden was den Fehler Could not open any command socket betrifft.

Kannst Du mal folgende Befehle in unterschiedlichen Terminals laufen lassen?

• journalctl -f
• systemctl restart chrony

Quote from evilred

How about fedora workstation?it has dist-upgrade

OMV will always Debian based.

The problem here is that ftpwho fails because the FTP service unit has been failed to start.

Does the output of systemctl status proftpd help to identify the reason of the error?

Was steht denn in der Datei /etc/chrony/chrony.conf?

Upgrade to openmediavault 5.5.11 and all problems should be solved.

Could you please execute omv-confdbadm read --prettify conf.system.filesystem.mountpoint and post the output here?

OMV will now prevent using shared folders containing blanks. See https://github.com/openmediava…1b994303a42858dc91621b7f4.

Quote from mweedon

/etc/monit/conf.d/openmediavault-filesystem.conf:47: Service name conflict, filesystem_srv_dev-disk-by-label-hdd6 already defined '"/srv/dev-disk-by-label-hdd6"' /etc/monit/conf.d/openmediavault-filesystem.conf:52

The problem seems to be that there are two filesystems with the label hdd6.

Quote from sw25481

Just had this same problem with a fresh install of OMV5 in a VMware virtual machine using openmediavault_5.3.9-amd64.iso although I had installed openmediavault-omvextrasorg_latest_all5.deb before I noticed the problem

You may fix that by running salt-call --local state.orchestrate omv.stage.setup.fixmode.

The problem is the blank in the directory name /srv/dev-disk-by-label-MX500SSD1/1tb-mx/Backup/Tv Box/, SaltStack does not like that, see https://github.com/saltstack/salt/issues/54508. Please rename the folder to TvBox.

If you have installed OMV from scratch it is not possible that the database error openmediavault.json.schema.SchemaValidationException: tls: Invalid value '0', allowed values are 'none, ssl, starttls, auto'. occurs because this change has been made in 5.2.0 and the latest ISO is 5.3.9. If you've installed OMV using an ARM image, this should also not happen because the latest package is installed. If you've installed an OMV version < 5.2.0 the database is migrated automatically. So, this error should NEVER appear, only if you install an older database file from an OMV < 5.2.0. I've tested the migration by installing 5.1.3 and upgraded to the latest version.

root@omv5box:~# dpkg -l | grep openmediavault
ii  openmediavault                  5.1.3-1                             all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring          1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
root@omv5box:~# cat /etc/openmediavault/config.xml | grep \<tls\>
            <tls>none|ssl|startssl|auto</tls>
      <tls>0</tls>
root@omv5box:~# apt-get install --reinstall openmediavault
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  openmediavault
1 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
Need to get 0 B/1707 kB of archives.
After this operation, 337 kB of additional disk space will be used.
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 45581 files and directories currently installed.)
Preparing to unpack .../openmediavault_5.5.10-1_all.deb ...
Unpacking openmediavault (5.5.10-1) over (5.1.3-1) ...
Setting up openmediavault (5.5.10-1) ...
Installing new version of config file /etc/apt/post-invoke.d/10install-cleanup ...
Installing new version of config file /etc/bash_completion.d/omv-salt ...
Installing new version of config file /etc/cron.daily/openmediavault-check_locked_users ...
Installing new version of config file /etc/cron.daily/openmediavault-cron-apt ...
Installing new version of config file /etc/cron.daily/openmediavault-flush-mailq ...
Installing new version of config file /etc/cron.daily/openmediavault-mdadm ...
Installing new version of config file /etc/cron.daily/openmediavault-pending_config_changes ...
Installing new version of config file /etc/cron.weekly/openmediavault-update-smart-drivedb ...
Installing new version of config file /etc/default/openmediavault ...
Installing new version of config file /etc/sysctl.d/99-openmediavault.conf ...
Installing new version of config file /etc/udev/rules.d/99-openmediavault-md-raid.rules ...
Installing new version of config file /etc/udev/rules.d/99-openmediavault-nonrot.rules ...
Installing new version of config file /etc/udev/rules.d/99-openmediavault-scheduler.rules ...
Creating configuration database ...
Migrating configuration database ...
  Running migration conf_5.2.0
  Running migration conf_5.5.0
  Running migration conf_5.5.3
WARNING: The node 'clients' already exists at XPath '/config/system/time/ntp'.
Setting up Salt environment ...
Processing system modifications ...
groupadd: group 'openmediavault-admin' already exists
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for openmediavault (5.5.10-1) ...
Restarting engine daemon ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
root@omv5box:~# cat /etc/openmediavault/config.xml | grep \<tls\>
            <tls>none|ssl|startssl|auto</tls>
      <tls>none</tls>

Then run omv-mkconf phpfpm nginx and monit restart omv-engined

Fixed in openmediavault 5.5.11, see https://github.com/openmediava…f26e712f6dc7d0047c4b15865.