Posts by gwaitsi

the unit boot fine. it is the OMV part that doesn't start because of the dependencies

nothing. same result

it's not the boot disk. it is only a data drive

it comes up with a start job is running for the drive - which fails . then a bunch of dependency fails for the disk

My machine is booting to the point of asking for root password for maintenance, or ctl-d to continue.

I remove a data drive which has being used to transfer out the data and the drive has now been re-formatted ntfs.

why does the system become completing unusable for the loss of a data drive....crazy.

how do i get it now?

Quote from ryecoaaron

Did you look at the output of journalctl -u docker? The docker package failing to start isn't even the fault of OMV. OMV 5 is every bit as good as OMV 4. Volker has mentioned many times that the 4 to 5 upgrade is not supported. If you are willing to move to FreeNAS, why not consider a fresh install of OMV 5 first??

i installed a fresh version in a virtual box and suffered exactly the same problems.

losing plex was a disappointment. i preferred the plugin over docker. that's why i installed and removed docker in OMV4.

when i did a virtual setup of freenas, the plugins went first time without issue.

don't get me wrong, you guys have done a fabulous job over the years. i've gone from OMV2 through to the OMV 5 and aside from one disaster with the an initial raid failure (which moved me to rsync backups) she has worked liked a charm.

still failing with latest 4.7.1 update.

i've given up on OMV5 (shame 4 was superb) moving to freenas.

setting up docker-ce (5:19.03.9~3-0~debian-buster) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2020-05-20 23:12:40 CEST; 22ms ago
Docs: https://docs.docker.com
Process: 16658 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 16658 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Setting up libisccfg163:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u1) ...
Setting up libbind9-161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u1) ...

Getting the below error on my OMV4->5 upgrade, and exactly the same error on a fresh OMV5 VM install.

considering all i want is my plexserver back, OMV5 upgrade has been a disaster for me.

Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2020-05-15 10:09:05 CEST; 20ms ago
Docs: https://docs.docker.com
Process: 27629 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 27629 (code=exited, status=1/FAILURE)


May 15 10:09:05 eapenas.eapenet.lan systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1

so, stuffed if i can figure it out. the entries are in the syslog.

They don't display in the ui syslog choice (correct - i guess), but the also don't display in the ui smb choice (incorrect).

The recording in syslog is working and reflects the level of detail selected.

votdev hey man, i don't understand how it can be working.

the smbd_audit entries are being written to /var/syslog - in the default configuration

The code below, line 265 in openmediavault/deb/openmediavault/usr/share/openmediavault/engined/inc/90logfilespec.inc

shows it is looking for smbd_audit.log

That file exists, but is 0 - how are the entries supposed to get from syslog -> smbd_audit.log ?

\OMV\System\LogFileSpec::registerSpecification("smbdaudit", [
  "command" => "export SYSTEMD_COLORS=0; journalctl --quiet --no-pager ".
    "--priority='notice' --identifier='smbd_audit' --output=short",
  "filename" => "smbd_audit.log",
  "regex" => "/^(\S+\s+\d+\s+\d{2}:\d

Quote from votdev

Using the facility in the query is not necessary to get the wanted data.

If the query works for your with SYSLOG_FACILITY=3

No, not necessary.

IMO another indication that something with your syslog and/or systemd settings differ to an Debian 10. But i have no idea where to start searching. Because of such issues there is no official migration from Debian 9 to 10.

Sure, but that's much work. I would unplug the main device of your NAS, connect it to a Linux box and mount the NAS root filesystem, then i would setup the OMV Vagrant box and mount the root filesystem of that image, too. Finally you could run a diff tool atop of both filesystems.

Display More

sounds like i might be better off to do a clean install and restore the key settings i.e. kernel options.

is there are way to backup just the omv config e.g. config.xml and other key files, then restore them onto a clean install

on another note. to get the amd64-microcode installed i had to modify sources.list

from

deb http://ftp.de.debian.org/debian/ buster main

To

deb http://ftp.de.debian.org/debian/ buster main non-free

to be able to get it. If i put them both in, it complained about duplicate sources.

shouldn't that be available from the initial install

I see you modified the code base to remove the sys_log=23

https://github.com/openmediava…9ac38c006b49aab6f49239b72

I have just made the change to my system to see if it works, but no effect. Do i have to run any commands to see it picked up, or just what till next release

So implementing this change didn't fix it on my side, nor did setting the value to 3.

The UPS log doesn't show anything in the user interface either.

is there a way to compare the files that are on the system vs the current omv build to show which ones are different.

My system has come from 3->4->5 and i wonder if there are residue that is breaking things. docker doesn't work for me either.

Quote from votdev

The OMV default configuration of the audit_full VFS module is full_audit:facility = local7 which is SYSLOG_FACILITY=23 (https://en.wikipedia.org/wiki/Syslog#Message_components).

hey votdev , i tried my luck with cycling through the syslog_facility numbers and they show up under 3 not 23.
file open, nt status ok, etc.

could this be legacy config settings from earlier OMV3 or OMV4?

I had installed docker in my OMV4 install (only for plex) and removed it for my preference of the plex plugin (no longer available in OMV5)

I recently upgraded to OMV5 from 4 and the docker component refuses to install. (don't know if the above is relevant)

i've tried uninstalling the plugin from gui, dpkg purging, etc. tried to install via CLI and gui - results are the same.

Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2020-05-12 15:33:37 CEST; 20ms ago
     Docs: https://docs.docker.com
  Process: 32292 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 32292 (code=exited, status=1/FAILURE)

May 12 15:33:37 nas.net.lan systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Setting up golang-docker-credential-helpers (0.6.1-2) ...
Setting up python3-dockerpycreds (0.3.0-1) ...
Setting up python3-docker (3.4.1-4) ...
Setting up docker-compose (1.21.0-3) ...
Processing triggers for systemd (241-7~deb10u4) ...
Processing triggers for man-db (2.8.5-2) ...

cool. thx

thx. so the run xxx is basically the xml header section of the config you want?

is there some docs with all the commands?

i found only statements about switching to salt from mkconf

I keep getting occasional communications errors when applying settings.

the result, half my firewall rules are missing now.

omv-firstaid restore backup says there is no backup.

so i re-pasted the entire <iptables> section from yesterday's backup

do i have to run an omv-salt command to make them take effect?

Quote from votdev

I'm sorry, i'm out now. The issue works for me on several machines and i know that users are using this feature. So the problem seems to exist only on your machine.

if i remove the SYSLOG_FACILITY=23 i get output showing connections from different machines...

Quote from votdev

Can you please use the following command line for testing. The output should then look like this.

Code

# journalctl --quiet --no-pager --priority='notice' SYSLOG_FACILITY=23 SYSLOG_IDENTIFIER='smbd_audit'
May 11 06:32:09 omv5box smbd_audit[1248]: vot|192.172.16.1|arrakis|/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-0-1-part1/test|test|unlink|ok|/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-0-1-part1/test/dummy_data.json

just dropped straight back to command prompt and didn|t display anything

Quote from votdev

- Undo ALL your customizations, enable the Audit switch for all shares you want and run omv-salt deploy run samba

- Start journalctl -f --quiet --no-pager SYSLOG_IDENTIFIER='smbd_audit' in a shell

So they are definitely being logged, but they are not displayed through the gui syslogs - SMB Audit selection

May 11 07:51:42 nas.net.lan smbd_audit[1502]: media closed file FamilyVideos/MVI_1857.mkv (numopen=1) NT_STATUS_OK
May 11 07:51:46 nas.net.lan smbd_audit[1502]: [2020/05/11 07:51:46.064229,  2] ../source3/smbd/close.c:802(close_normal_file)
May 11 07:51:46 nas.net.lan smbd_audit[1502]: media closed file FamilyVideos/MVI_1857.mkv (numopen=0) NT_STATUS_OK

Quote from votdev

Please try the following, the problem is surely not the smb.conf created by OMV, it's something with your system that is not working correct.

- Is journald running? systemctl status systemd-journal

I think there is something wrong with that line. i get

Unit journal.service could not be found

but if i run journalctl -ax i get items at the current time from the current boot