Beiträge von votdev
-
-
Can you please open the file /lib/systemd/system/openmediavault-issue.service and replace the content with
Code
Alles anzeigen[Unit] Description=Generate the prelogin message Wants=network-online.target After=network-online.target Before=getty.target [Service] Type=oneshot ExecStart=/usr/sbin/omv-salt deploy run issue RemainAfterExit=yes [Install] WantedBy=getty.target
Reboot the system after that and check if the IP addresses are listed in the welcome message.
-
When I start it by hand it still gives me the same error on the first try. On the second try it starts.
Can not reproduce this. Can you provide more information, e.g. syslog output or something else that might help to identify the problem.
Can you please post the whole output of the command
-
-
The problem is a timing issue. If someone is encouraged to improve the issue, then look into the openmediavault-issue.service systemd unit.
-
Fixed in openmediavault 4.1.25, see https://github.com/openmediava…c51fed49a8759336e247cf2cc.
-
Thx, good to know. Will add the line again in the next version.
-
Can you please verify if the issue is fixed when we re-add the After=zfs-mount.service?
-
This command is only available in OMV5.
-
Note, i only got it running after i've enabled 'No session reuse required'. See https://stefankonarski.de/cont…te-nicht-empfangen-werden.
-
You've hit a bug. Will be fixed in openmediavault 5.0.9, see https://github.com/openmediava…9289fd93ea441c3e2758cdf53.
-
Have never seen that, but maybe Google can help you.
-
The root filesystem is surely full.
-
Probably it is not necessary, but people do it if they are not aware it will cause problems. So maybe an error message when creating the label would help. At least in those cases where the label is added using OMV.
The OMV UI does not allow blanks for labels when creating new filesystem since ages.
-
I've opened a bugreport in SaltStack: https://github.com/saltstack/salt/issues/54508
-
It seems to be that SaltStack can not handle blanks in device names and mount dirs properly. Need to find a workaround and maybe a bug fix for the upstream project.
I really can’t understand why it is necessary to use blanks in filesystem labels or file names. As SaltStack has it’s problems with it i think blanks in filenames are not widely used in Linux and it seems to me that this absurdity comes from the Windows world.
-
You've found a bug. Filesystem labels with blanks were not handled properly. Fixed in openmediavault 5.0.8, see https://github.com/openmediava…1c38188f45b30dfbbea38dc57 and https://github.com/openmediava…cf5184f624cce8b67dece6b83.
-
does it mean that plugins like rsnapshot or nginx should point to /srv/xxx/yyy and never to /sharedfolders/yy ?
Yes
-
The problem is that the mount point configuration is not valid, this seems to be raised by an invalid shared folder name.
-
Please provide a detailed step by step instruction how we can reproduce this issue. Starting from creating the shared folders (names, paths) and so on.