Arch Linux

tazmanian

Member

Registered: 2009-10-25

Posts: 39

[solved] Large number of services enabled during first boot

I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.

To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.

Any ideas as to what might be causing this?

Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.

Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711

Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.

Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.

Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-nspawn@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-rfkill@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable getty@.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-backlight@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about container-getty@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about serial-getty@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck@.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.

Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):

getty.target.wants:
  * getty@tty1.service

multi-user.target.wants:
  * dhcpcd@lan0.service
  * iptables.service
  * remote-fs.target
  * sshd.service

sysinit.target.wants:
  (none)

Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):

default.target.wants:
  * systemd-readahead-collect.service
  * systemd-readahead-replay.service

multi-user.target.wants:
  * dhcpcd.service	    * krb5-kpropd.service
  * fstrim.service          * nscd.service
  * ftpd.service            * rsyncd.service
  * gpm.service             * systemd-journal-upload.service
  * ip6tables.service       * systemd-networkd.service
  * krb5-kadmind.service    * systemd-resolved.service
  * krb5-kdc.service

sockets.target.wants:
  * krb5-kpropd.socket	    * systemd-journal-remote.socket
  * rlogin.socket           * talk.socket
  * rsh.socket              * telnet.socket
  * rsyncd.socket           * uuidd.socket
  * sshd.socket

sysinit.target.wants:
  * dm-event.service
  * systemd-timesyncd.service

system-update.target.wants:
  * systemd-readahead-drop.service

Explicitly installed packages:

dhcpcd	    iputils	  procps-ng   systemd-sysvcompat
diffutils   linux-grsec   psmisc      tar
dnsutils    logrotate     reflector   vim-systemd
file        mlocate       rsync       wget
gradm       mtr           s-nail      which
grub        openssh       screen      whois
inetutils   pacman

Last edited by tazmanian (2014-09-10 23:11:42)

mah0

Member

Registered: 2011-04-21

Posts: 47

Re: [solved] Large number of services enabled during first boot

Same here. Installed arch at work today and noticed few failed services during startup (ftpd, iptables, ip6tables and a few more I don't remember).

johnso51

Member

Registered: 2014-08-27

Posts: 2

Re: [solved] Large number of services enabled during first boot

I am running in to the same issue. I am installing arch in a lab at work on a few systems. Still testing so I have been reinstalling over the past few days. Today was the first time I ran into this issue. The services added by default (and fail due to missing files) are:

dhcpcd@eno1.service
ip6tables.serivce
iptables.service
krb5-kadmind.service
krb5-kdc.service
mdadm.service
systemd-journal-upload.service

Also, in the install script I wrote, I diabled these services. First boot they did not run/fail, but then after I ran my second part of the install script and rebooted, the services came back.

Last edited by johnso51 (2014-08-27 17:37:46)

tazmanian

Member

Registered: 2009-10-25

Posts: 39

Re: [solved] Large number of services enabled during first boot

mah0, johnso51, and anyone else experiencing this: please up-vote the bug report so the package maintainers know this affects more than just me.

tazmanian

Member

Registered: 2009-10-25

Posts: 39

Re: [solved] Large number of services enabled during first boot

Until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.

yuvadm

Member

From: Tel Aviv-Jaffa, Israel

Registered: 2012-08-08

Posts: 102

Website

Re: [solved] Large number of services enabled during first boot

+1 same problem on clean install, upvoted the ticket as well.

serfraviros

Member

Registered: 2014-08-29

Posts: 4

Re: [solved] Large number of services enabled during first boot

+1 same problem on fresh install, issues with:

ip6tables.service
iptables.service
krb5-kadmind.service
krb5-kdc.service
mdadm.service
systemd-journal-upload.service

ryzion

Member

Registered: 2012-03-20

Posts: 95

Re: [solved] Large number of services enabled during first boot

same for me

Aug 29 22:11:26 T20 systemd[1]: Unit krb5-kdc.service entered failed state.
Aug 29 22:11:26 T20 systemd[1]: Unit ip6tables.service entered failed state.
Aug 29 22:11:26 T20 systemd[1]: Unit krb5-kdc.service entered failed state.
Aug 29 22:11:26 T20 systemd[1]: Unit krb5-kadmind.service entered failed state.
Aug 29 22:11:26 T20 systemd[1]: Unit iptables.service entered failed state.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [solved] Large number of services enabled during first boot

Please stop with the empty posts. The bug has been filed, adding +1 here is not contributing anything...
https://wiki.archlinux.org/index.php/Fo … mpty_Posts

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

ANOKNUSA

Member

Registered: 2010-10-22

Posts: 2,141

Re: [solved] Large number of services enabled during first boot

Until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.

Ignore this. The problem doesn't seem to impact anyone in any way other than unwanted services being enabled; going through some workaround for a non-problem is pointless. Just follow the bug report; it looks like an upstream problem.

Last edited by ANOKNUSA (2014-08-29 20:53:01)

---

Linux != Windows  ::  Ask Questions the Smart Way  ::  Configs

jeff story

Member

Registered: 2009-05-31

Posts: 237

Website

Re: [solved] Large number of services enabled during first boot

Until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.

Ignore this. The problem doesn't seem to impact anyone in any way other than unwanted services being enabled; going through some workaround for a non-problem is pointless. Just follow the bug report; it looks like an upstream problem.

Please correct me if I'm missing something here, but this is a problem for all the people installing a new (current snapshot) Arch install.

Not sure how this effects people updating their Arch installs as I'm holding off until this is resolved. If it causes, "unwanted services being enabled", for everyone updating, I see this as a big problem to not be ignored. If this is the case, there should be an official notice to let people know whats going on.

ie: networkmanager + dhcpcd enabled = no network

Why would you recommend to not follow a perfectly reasonable and easy workaround that eliminates the problems until the actual problem is resolved?

Notice: Arch does not support holding back packages and the workaround may cause other unknown issues.

.

Last edited by jeff story (2014-08-29 22:15:24)

---

Check out my website for info on the Arch Linux Installer

snormett

Member

From: Sweden

Registered: 2014-08-30

Posts: 1

Re: [solved] Large number of services enabled during first boot

Hi

When installing run 'systemd-machine-id-setup' in chroot (arch-chroot) to fix the problem

teateawhy

Member

From: GER

Registered: 2012-03-05

Posts: 1,138

Website

Re: [solved] Large number of services enabled during first boot

When installing run 'systemd-machine-id-setup' in chroot (arch-chroot) to fix the problem

Is this something that should be added to the beginners guide/installation guide?

ANOKNUSA

Member

Registered: 2010-10-22

Posts: 2,141

Re: [solved] Large number of services enabled during first boot

Please correct me if I'm missing something here, but this is a problem for all the people installing a new (current snapshot) Arch install.

Depends on how you define "problem." No one's said it affects anything beyond the very first boot of a new install using the August 2014 installation image.

If it causes, "unwanted services being enabled", for everyone updating, I see this as a big problem to not be ignored.

It doesn't, so it's not.

Why would you recommend to not follow a perfectly reasonable and easy workaround that eliminates the problems until the actual problem is resolved?

Notice: Arch does not support holding back packages and the workaround may cause other unknown issues.

Seems you answered your own question. Instructing people to go through some unsupported and convoluted install-downgrade-upgrade process to avoid a "problem" that (apparently) lasts all of ten seconds before resolving itself is just dumb.

Is this something that should be added to the beginners guide/installation guide?

It was fixed before you posted.

---

Linux != Windows  ::  Ask Questions the Smart Way  ::  Configs

DoubleT

Member

From: Afyonkarahisar, Turkey

Registered: 2014-08-31

Posts: 7

Website

Re: [solved] Large number of services enabled during first boot

It was fixed before you posted.

Is it fixed? Can i install arch now? I'm asking because systemd 216-1 still in repo and systemd 216-2 is in testing. I have to wait systemd 216-2? Sorry i'm noob for these. And thank you.

midixinga

Member

Registered: 2014-01-18

Posts: 193

Re: [solved] Large number of services enabled during first boot

I would wait

wuxb

Member

Registered: 2012-09-13

Posts: 29

Re: [solved] Large number of services enabled during first boot

+1.
Here is the ports these services are listening:
$ ss -tpl
State      Recv-Q Send-Q                                                                                                       Local Address:Port                                                                                                           Peer Address:Port   
LISTEN     0      128                                                                                                                      *:llmnr                                                                                                                     *:*       
LISTEN     0      128                                                                                                                      *:ssh                                                                                                                       *:*       
LISTEN     0      128                                                                                                                     :::llmnr                                                                                                                    :::*       
LISTEN     0      128                                                                                                                     :::19532                                                                                                                    :::*       
LISTEN     0      128                                                                                                                     :::tell                                                                                                                     :::*       
LISTEN     0      128                                                                                                                     :::ssh                                                                                                                      :::*       
LISTEN     0      128                                                                                                                     :::telnet                                                                                                                   :::*       
LISTEN     0      128                                                                                                                     :::login                                                                                                                    :::*       
LISTEN     0      128                                                                                                                     :::shell                                                                                                                    :::*       
LISTEN     0      128                                                                                                                     :::rsync                                                                                                                    :::*       
LISTEN     0      128                                                                                                                     :::git                                                                                                                      :::*

jeff story

Member

Registered: 2009-05-31

Posts: 237

Website

Re: [solved] Large number of services enabled during first boot

As of late last night, my testing indicates this problem has not been fixed.

Tried both systemd-216-1 in a current base install, and upgraded to systemd-216-2 from the testing repo.

ANOKNUSA, could you please be more specific as to exactly what has been fixed? Are we talking about the same problem here?

Last edited by jeff story (2014-08-31 15:32:03)

---

Check out my website for info on the Arch Linux Installer

midixinga

Member

Registered: 2014-01-18

Posts: 193

Re: [solved] Large number of services enabled during first boot

I think, the main question is:
Is a re-installation of an affected system after publication of systemd 216-2 the only safe and clean solution ?
Or is it also clean and safe to run systemd-machine-id-setup before leaving chroot during a re-installation with the current systemd version.
Or are there for now other clean and safe solutions for an affected system ?

Maybe there is an Arch developer, who could answer the question ? Would be great.

Last edited by midixinga (2014-08-31 22:55:14)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,704

Website

Re: [solved] Large number of services enabled during first boot

Maybe there is an Arch developer, who could answer the question ? Would be great.

Mailing lists?
I don't think the devs visit here often...

---

Para todos todo, para nosotros nada

butler360

Member

Registered: 2012-09-08

Posts: 29

Re: [solved] Large number of services enabled during first boot

Just installed earlier today and this really tripped me up, especially dhcpcd being enabled when I had installed NetworkManager. Thanks for the very detailed writeup.

So is there any way to fix this for an existing install besides manually going through and disabling what you don't need?

Kat

Member

Registered: 2014-08-30

Posts: 3

Re: [solved] Large number of services enabled during first boot

Just installed earlier today and this really tripped me up, especially dhcpcd being enabled when I had installed NetworkManager. Thanks for the very detailed writeup.

So is there any way to fix this for an existing install besides manually going through and disabling what you don't need?

If you enable testing there is an update 216-2
Works great

Last edited by Kat (2014-08-31 23:26:24)

---

Kat

"The general population doesn’t know what’s happening, and it doesn’t even know that it doesn’t know."Noam Chomsky

hokasch

Member

Registered: 2007-09-23

Posts: 1,461

Re: [solved] Large number of services enabled during first boot

Is a re-installation of an affected system after publication of systemd 216-2 the only safe and clean solution ?

No, just disable all the unneeded cruft. Annoying, but not really a reason to reinstall. For example, this is what I currently have on a single-user desktop machine. You might want to enable some services I have disabled, and vice versa, but just to give you a general idea - that bug enabled a crapload of stuff by default. If in doubt, look at the unit file (systemctl cat <unit>) and/or google the service.

So is there any way to fix this for an existing install besides manually going through and disabling what you don't need?

I was quite baffled last week by this as well, but just disabled them all manually. You can move all symlinks to another directory and then move back the ones you need, instead of running "systemctl disable <unit>"  individually. 

"ls /etc/systemd/system/*.wants/" gives you an overview of enabled services.

If you enable testing there is an update 216-2
Works great

Updating systemd will not fix the problem on installs made with systemd<216-2 (only for new installs).

Last edited by hokasch (2014-08-31 23:41:59)

maseone

Member

Registered: 2014-08-27

Posts: 11

Re: [solved] Large number of services enabled during first boot

Hi

When installing run 'systemd-machine-id-setup' in chroot (arch-chroot) to fix the problem

Cool, didn't think there was access to that yet while at the "arch-chroot" step (from the install guide).  I personally got around this last night by using a workaround mentioned by Reisner.  During the "arch-chroot" step create a file "/usr/lib/systemd/system-preset/99-default.preset" and add:

disable *

This tells systemd to NOT enable excessive services due to the /etc/machine-id check that fails due to "chicken before the egg" syndrome.  (ok - this is my newb layman explanation).  Only downside to this method is you'll probably have to manually enable DHCP that would otherwise be enable by default during an Arch install (following the install guide)

This would be done after exiting arch-chroot and booting into your new system:

# systemctl enable dhcpcd.service
# systemctl start dhcpcd.service

Anyway, if snormett's suggestion works for all use-cases, that would probably be a better bet.

midixinga

Member

Registered: 2014-01-18

Posts: 193

Re: [solved] Large number of services enabled during first boot

Is a re-installation of an affected system after publication of systemd 216-2 the only safe and clean solution ?

No, just disable all the unneeded cruft.

Yes, disabling all the unneeded units works, but I asked also for all the beginners, who installed Arch the last days.

Annoying, but not really a reason to reinstall. For example, this is what I currently have on a single-user desktop machine.

I checked your command on my KDE5-Testsystem and  it really differs from your system:

$ ls /etc/systemd/system/*.wants/
/etc/systemd/system/getty.target.wants/:
getty@tty1.service

/etc/systemd/system/multi-user.target.wants/:
acpid.service         cronie.service  dhcpcd@enp0s3.service  ntpd.service      
avahi-daemon.service  cups.path       remote-fs.target

/etc/systemd/system/printer.target.wants/:
cups.service

/etc/systemd/system/sockets.target.wants/:
acpid.socket  avahi-daemon.socket  cups.socket

/etc/systemd/system/sysinit.target.wants/:

You might want to enable some services I have disabled, and vice versa, but just to give you a general idea - that bug enabled a crapload of stuff by default. If in doubt, look at the unit file (systemctl cat <unit>) and/or google the service.

on the other hand, you are right, it's a good opportunity to learn the own system. (but it's not fair )

You can move all symlinks to another directory and then move back the ones you need, instead of running "systemctl disable <unit>"  individually.

That sounds good, I know to little about this bug to evaluate all impacts.