[systemd-devel] remote-fs dependency/ordering on network
Is remote-fs.target somehow dependent/ordered on network.target or network-online.target? I can't find anything that would suggest it actually is. Cheers, -- Jan Synacek Software Engineer, Red Hat signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd is trying to break mount ordering
I have the following setup on a freshly updated Fedora Rawhide machine with systemd-220-9.fc23.x86_64. # cat /etc/fstab [comments left out] UUID=d5ac823b-d0bd-4f7f-bf4b-5cc82d585a92 / btrfs subvol=root 0 0 UUID=ec79f233-055c-40fa-98e5-e2d77314913a /boot ext4 defaults1 2 UUID=d5ac823b-d0bd-4f7f-bf4b-5cc82d585a92 /home btrfs subvol=home 0 0 192.168.122.1:/srv/nfs /mnt/nfs nfs defaults 0 0 /var/tmp/test.iso /mnt/nfs/content iso9660 loop,ro 0 0 Notice the last two lines. There is an NFS mount mounted to /mnt/nfs and an ISO filesystem mounted into /mnt/nfs/content, which makes it dependent on the NFS mount. After booting the machine, there are the following lines in the journal: [snip...] Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on local-fs.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on mnt-nfs-content.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on mnt-nfs.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on network.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on firewalld.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Breaking ordering cycle by deleting job sockets.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with firewalld.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found ordering cycle on network.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on systemd-networkd.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on dbus.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on dbus.socket/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on sysinit.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on fedora-autorelabel-mark.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on local-fs.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on mnt-nfs-content.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on mnt-nfs.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Found dependency on network.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: network.target: Breaking ordering cycle by deleting job systemd-networkd.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: systemd-networkd.service: Job systemd-networkd.service/start deleted to break ordering cycle starting with network.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found ordering cycle on firewalld.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on basic.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on dnf-makecache.timer/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on sysinit.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on fedora-autorelabel-mark.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on local-fs.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on mnt-nfs-content.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on mnt-nfs.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on network.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on firewalld.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Breaking ordering cycle by deleting job dnf-makecache.timer/start Jun 15 10:37:55 rawhide-virt systemd[1]: dnf-makecache.timer: Job dnf-makecache.timer/start deleted to break ordering cycle starting with firewalld.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found ordering cycle on firewalld.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on basic.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on sysinit.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on fedora-autorelabel-mark.service/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on local-fs.target/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on mnt-nfs-content.mount/start Jun 15 10:37:55 rawhide-virt systemd[1]: firewalld.service: Found dependency on mnt-nfs.mount/start Jun
[systemd-devel] Messed up PR references on Github
See https://github.com/systemd/systemd/pull/5. There are multiple references to this PR that say user referenced this pull request from a commit in commit, which is hilarious, as those clearly are not references to this PR. Their commit messages contain the string #5 and Github thinks it means a reference. I'm pretty sure this will mess up a lot of pull requests in the future. Is there a way to fix this? -- Jan Synacek Software Engineer, Red Hat signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd from git doesn't boot properly in fedora rawhide
Hello, From the following commit onward, systemd doesn't boot properly in Rawhide. Some device units time out and I'm then dropped into an emergency shell. commit f4ac4d1a82e2c468761fffa23841ad886221 Author: Tom Gundersen t...@jklm.no Date: Wed Apr 1 13:55:20 2015 +0200 libudev: device - replace by a thin wrapper around sd-device All I can see is that a job is running for some of the device units and then it times out. Log from journalctl and one of the failed device units can be found at [1] and [2]. Any idea what might be wrong or how to debug this any further? [1] https://jsynacek.fedorapeople.org/systemd/journalctl.log [2] https://jsynacek.fedorapeople.org/systemd/device-unit.log Cheers, -- Jan Synacek Software Engineer, Red Hat signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] SELinux labels on unix sockets
Hello, when systemd creates a socket file, it explicitly calls a selinux procedure to label it. I don't think that is needed, as the kernel does the right thing when the socket is created. Am I missing something? Why is the explicit labeling in place? Cheers, -- Jan Synacek Software Engineer, Red Hat signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] libsystemd-network tests failing in mock
Hi,
test-dhcp-{client,server} are failing in mock:
FAIL: test-dhcp-client
==
Assertion 'client' failed at ../src/libsystemd-network/sd-dhcp-client.c:138,
function sd_dhcp_client_set_request_option(). Ignoring.
Assertion 'client' failed at ../src/libsystemd-network/sd-dhcp-client.c:169,
function sd_dhcp_client_set_request_address(). Ignoring.
Assertion 'client' failed at ../src/libsystemd-network/sd-dhcp-client.c:182,
function sd_dhcp_client_set_index(). Ignoring.
Assertion 'interface_index 0' failed at
../src/libsystemd-network/sd-dhcp-client.c:185, function
sd_dhcp_client_set_index(). Ignoring.
Assertion 'interface_index 0' failed at
../src/libsystemd-network/sd-dhcp-client.c:185, function
sd_dhcp_client_set_index(). Ignoring.
Assertion 'interface_index 0' failed at
../src/libsystemd-network/sd-dhcp-client.c:185, function
sd_dhcp_client_set_index(). Ignoring.
DHCP CLIENT (0x0): FREE
DHCP CLIENT (0xbe31128b): STARTED on ifindex 42
DHCP CLIENT (0xbe31128b): DISCOVER
DHCP CLIENT (0xbe31128b): STOPPED
DHCP CLIENT (0x0): FREE
DHCP CLIENT (0x45d3fd67): STARTED on ifindex 42
DHCP CLIENT (0x45d3fd67): DISCOVER
DHCP CLIENT (0x45d3fd67): OFFER
DHCP CLIENT (0x45d3fd67): REQUEST (requesting)
DHCP CLIENT (0x45d3fd67): ACK
DHCP CLIENT (0x45d3fd67): lease expires in 9min 57.698157s
DHCP CLIENT (0x45d3fd67): T2 expires in 8min 42.895614s
DHCP CLIENT (0x45d3fd67): T1 expires in 5min 101.292ms
DHCP CLIENT (0x45d3fd67): STOPPED: Operation not permitted
Assertion 'event == DHCP_EVENT_IP_ACQUIRE' failed at
../src/libsystemd-network/test-dhcp-client.c:367, function
test_addr_acq_acquired(). Aborting.
SKIP: test-dhcp-server
==
Assertion '!server-event' failed at
../src/libsystemd-network/sd-dhcp-server.c:179, function
sd_dhcp_server_attach_event(). Ignoring.
Assertion '!server-event' failed at
../src/libsystemd-network/sd-dhcp-server.c:179, function
sd_dhcp_server_attach_event(). Ignoring.
Assertion 'server-address != htobe32(INADDR_ANY)' failed at
../src/libsystemd-network/sd-dhcp-server.c:932, function
sd_dhcp_server_start(). Ignoring.
Assertion 'address-s_addr' failed at
../src/libsystemd-network/sd-dhcp-server.c:59, function
sd_dhcp_server_set_address(). Ignoring.
Assertion 'prefixlen = 32' failed at
../src/libsystemd-network/sd-dhcp-server.c:60, function
sd_dhcp_server_set_address(). Ignoring.
Assertion 'server-address == htobe32(INADDR_ANY)' failed at
../src/libsystemd-network/sd-dhcp-server.c:61, function
sd_dhcp_server_set_address(). Ignoring.
Assertion 'address-s_addr' failed at
../src/libsystemd-network/sd-dhcp-server.c:39, function
sd_dhcp_server_set_lease_pool(). Ignoring.
Assertion 'size' failed at ../src/libsystemd-network/sd-dhcp-server.c:40,
function sd_dhcp_server_set_lease_pool(). Ignoring.
Assertion 'server-pool_start == htobe32(INADDR_ANY)' failed at
../src/libsystemd-network/sd-dhcp-server.c:41, function
sd_dhcp_server_set_lease_pool(). Ignoring.
DHCP SERVER: STOPPED
DHCP SERVER: UNREF
DHCP SERVER: STOPPED
Any ideas about how to fix those?
Cheers,
--
Jan Synacek
Software Engineer, Red Hat
signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] emergency, rescue and single-user
Hello, what is the difference between emergency, rescue and single-user? On F21, systemd-216-12.fc21.x86_64, they all boot into something that presents itself as Welcome to emergency mode! and they all require a root password. In case of booting into emergency.target, I can see Starting Emergency Shell in the console output. In single-user and rescue.target, I can see Starting Rescue Shell, but they all look the same. systemd.special(7) doesn't help much. Cheers, -- Jan Synacek Software Engineer, Red Hat signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Expected behavior when systemd cannot load SELinux policy
Hello, currently, when SELINUX=enforcing and SELINUXTYPE=invalid value are set in /etc/selinux/config, systemd refuses to boot with Failed to load SELinux policy. Freezing. Is this really what should happen? If SELINUX is set to permissive or disabled, though, systemd happily continues booting. I think that that's what should happen when SELINUX is set to enforcing as well. Plus a big warning in the log, or maybe even on the console, of course. What do you think? Cheers, -- Jan Synacek Software Engineer, Red Hat signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Switch root slowness
Hello, commit 539618a0ddc2dc7f0fbe28de2ae0e07b34c81e60 Author: Lennart Poettering lenn...@poettering.net Date: Wed Oct 29 17:06:32 2014 +0100 util: make use of the new getrandom() syscall if it is available when needing entropy Doesn't require an fd, and could be a bit faster, so let's make use of it, if it is available. Beginning from this commit, switch root takes about a minute on my machine. Excerpts from the journal: Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: random: systemd urandom read with 10 bits of entropy available Oct 30 13:08:37 fedora-rawhide-systemd-virt systemd-journal[109]: Journal started Oct 30 13:08:37 fedora-rawhide-systemd-virt dracut-cmdline[105]: dracut-22 (Rawhide) dracut-038-36.git20140815.fc22 Oct 30 13:08:37 fedora-rawhide-systemd-virt dracut-cmdline[105]: Using kernel command line parameters: Oct 30 13:08:37 fedora-rawhide-systemd-virt systemd-udevd[158]: starting version 216 This line is pretty weird too, this commit is after v217 had been tagged. Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] Initialized drm 1.1.0 20060810 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] Device Version 0.0 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] Compression level 0 log level 0 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] Currently using mode #0, list at 0x488 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] 12286 io pages at offset 0x100 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] 16777216 byte draw area at offset 0x0 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] RAM header offset: 0x3ffe000 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] rom modes offset 0x488 for 128 modes Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [TTM] Zone kernel: Available graphics memory: 1024780 kiB Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [TTM] Initializing pool allocator Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [TTM] Initializing DMA pool allocator Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] qxl: 16M of VRAM memory size Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] qxl: 63M of IO pages memory ready (VRAM domain) Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] qxl: 64M of Surface memory size Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] main mem slot 1 [f400,3ffe000] Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] surface mem slot 2 [f800,400] Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] No driver support for vblank timestamp query. Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] fb mappable at 0xF400, size 3145728 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] fb: depth 24, pitch 4096, width 1024, height 768 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: fbcon: qxldrmfb (fb0) is primary device Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: Console: switching to colour frame buffer device 128x48 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: qxl :00:02.0: fb0: qxldrmfb frame buffer device Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: qxl :00:02.0: registered panic notifier Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: [drm] Initialized qxl 0.1.0 20120117 for :00:02.0 on minor 0 Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: PM: Starting manual resume from disk Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: PM: Hibernation image partition 8:2 present Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: PM: Looking for hibernation image. Oct 30 13:08:37 fedora-rawhide-systemd-virt systemd-fsck[198]: /dev/sda3: clean, 83696/853440 files, 1149042/3410688 blocks Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: PM: Image not found (code -22) Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: PM: Hibernation image not present or could not be loaded. Oct 30 13:08:37 fedora-rawhide-systemd-virt kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) Oct 30 13:08:38 fedora-rawhide-systemd-virt systemd[1]: Switching root. Oct 30 13:08:38 fedora-rawhide-systemd-virt systemd-journal[109]: Journal stopped Hangs here for a while with no output. Oct 30 13:09:44 fedora-rawhide-systemd-virt systemd-journal[279]: Runtime journal is using 8.0M (max allowed 100.0M, trying to leave 150.1M free of 992.7M available → current limit 100.0M). Oct 30 13:09:44 fedora-rawhide-systemd-virt systemd-journal[279]: Runtime journal is using 8.0M (max allowed 100.0M, trying to leave 150.1M free of 992.7M available → current limit 100.0M). Oct 30 13:09:44 fedora-rawhide-systemd-virt systemd-journald[109]: Received SIGTERM from PID 1 (systemd). snip a lot of selinux related stuff Oct 30 13:09:44 fedora-rawhide-systemd-virt kernel: random:
