systemd-246.7-2.fc33.x86_64 could you guys start read your syslogs given that i can even on minimal setups with no production or practical use intention? "sys-module-fuse.device" and "modprobe" on a minimal setup? what the hell is that and why is more and more stuff thrown into the system? [root@rawhide ~]# system-errors.sh Dec 21 18:30:18 rawhide systemd[1]: sys-module-configfs.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe is masked. Dec 21 18:30:18 rawhide systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe is masked. [root@rawhide ~]# rpm -q --filesbypkg systemd | grep fuse systemd /usr/lib/systemd/system/sys-fs-fuse-connections.mount systemd /usr/lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount -------------------------------------------------- god knows where this is coming from at all [root@rawhide ~]# systemctl status modprobe ● modprobe Loaded: masked (Reason: Unit modprobe is masked.) Active: inactive (dead)
what about fix that annoying shit? [root@rawhide ~]# system-errors.sh Jan 12 18:34:22 rawhide systemd[1]: sys-module-configfs.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe is masked. Jan 12 18:34:22 rawhide systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe is masked.
that nonsense now also appears on F32 with systemd-245.9-1.fc32.x86_64 frankly you have no business to touch anything fuse-related on a server setup to begin with [Sat Feb 6 13:00:31 2021] systemd[1]: sys-fs-fuse-connections.mount: Failed to check directory /sys/fs/fuse/connections: No such file or directory [Sat Feb 6 13:00:31 2021] systemd[1]: sys-fs-fuse-connections.mount: Failed with result 'exit-code'. [Sat Feb 6 13:00:31 2021] systemd[1]: Failed to mount FUSE Control File System. Feb 06 13:00:31 firewall.esx.vmware.local systemd[1]: sys-fs-fuse-connections.mount: Failed to check directory /sys/fs/fuse/connections: No such file or directory Feb 06 13:00:31 firewall.esx.vmware.local systemd[1]: sys-fs-fuse-connections.mount: Failed with result 'exit-code'. Feb 06 13:00:31 firewall.esx.vmware.local systemd[1]: Failed to mount FUSE Control File System. Feb 06 13:00:32 firewall.esx.vmware.local systemd[1]: sys-module-configfs.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe is masked.
after "systemctl unmask modprobe@.service" the fuse kernel-module is now loaded at boot on every bare machine with nothing installed and active bsides socket activated sshd - why?
And on F33 "systemctl mask sys-module-fuse.device sys-fs-fuse-connections.mount" is even ignored and the fuse-kernel module still loaded - oh come on [root@rawhide ~]# system-errors.sh Feb 8 19:17:01 rawhide systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount is masked. [root@rawhide ~]# systemctl status sys-module-fuse.device ● sys-module-fuse.device - /sys/module/fuse Loaded: masked (Reason: Unit sys-module-fuse.device is masked.) Active: active (plugged) since Mon 2021-02-08 19:17:00 CET; 25s ago Device: /sys/module/fuse
and to top that all you load the fuse module on a bare install even if it#s completly blacklisted [root@rawhide ~]# cat /etc/modprobe.d/blacklist-lounge-vm.conf | grep fuse blacklist fuse install fuse /usr/bin/true [root@rawhide ~]# system-errors.sh Feb 8 19:26:08 rawhide systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount is masked. [root@rawhide ~]# lsmod | grep fuse fuse 163840 0
even if you *delete* the "sysinit.target.wants/sys-fs-fuse-connections.mount" no, basic target don't want fuse [harry@srv-rhsoft:~]$ rawhide [root@rawhide ~]# system-errors.sh Feb 8 19:32:20 rawhide systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount is masked. [root@rawhide ~]# rpm -q --filesbypkg systemd | grep fuse systemd /usr/lib/systemd/system/sys-fs-fuse-connections.mount systemd /usr/lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount [root@rawhide ~]# rm /usr/lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount [root@rawhide ~]# rm /usr/lib/systemd/system/sys-fs-fuse-connections.mount [root@rawhide ~]# reboot [root@rawhide ~]# system-errors.sh Feb 8 19:33:19 rawhide systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount is masked. [root@rawhide ~]# systemctl status sys-module-fuse.device sys-fs-fuse-connections.mount ● sys-module-fuse.device - /sys/module/fuse Loaded: masked (Reason: Unit sys-module-fuse.device is masked.) Active: active (plugged) since Mon 2021-02-08 19:33:18 CET; 1min 42s ago Device: /sys/module/fuse Feb 08 19:33:19 rawhide.vmware.local systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount is masked. ● sys-fs-fuse-connections.mount Loaded: masked (Reason: Unit sys-fs-fuse-connections.mount is masked.) Active: inactive (dead) [root@rawhide ~]#
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.