| Summary: | sys-apps/gentoo-systemd-integration-4 - gentoo-local-baselayout1.service is often not executed | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
| Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Juergen Rose
2014-10-05 20:29:34 UTC
If I try to start gentoo-local-baselayout1.service manually:
root@gepard:/root(29)# systemctl start gentoo-local-baselayout1.service
it simply hangs. The contents of /run/systemd/generator/gentoo-local-baselayout1.service is also strange for me:
root@gepard:/root(30)# cat /run/systemd/generator/gentoo-local-baselayout1.service
[Unit]
Description=Service for local.d/baselayout1.*
After=multi-user.target graphical.target gentoo-local-99mount.service
ConditionFileIsExecutable=/etc/local.d/baselayout1.stop
[Service]
Type=forking
RemainAfterExit=on
TimeoutSec=0
ExecStart=/bin/true
ExecStop=/usr/bin/env /etc/local.d/baselayout1.stop
root@gepard:/root(31)#
What means after
After=multi-user.target graphical.target gentoo-local-99mount.service ?
Does the gentoo-local-99mount.service not belong to /etc/local.d/99mount.stop?
On the other hand neither the multi-user.target nor graphical.target seems to run.
root@gepard:/root(31)# systemctl status multi-user.target
● multi-user.target - Multi-User System
Loaded: loaded (/usr/lib64/systemd/system/multi-user.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
root@gepard:/root(32)# systemctl status graphical.target
● graphical.target - Graphical Interface
Loaded: loaded (/usr/lib64/systemd/system/graphical.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
Nevertheless there is no problem to login as user rose via ssh or su to root.
Also the multi-user.target seems to be started only sometimes: root@gepard:/root(36)# journalctl -u multi-user.target | tail -n 30 -- Reboot -- Oct 03 21:40:00 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 04 15:20:30 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 04 17:30:10 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 04 17:31:01 gepard systemd[1]: Starting Multi-User System. Oct 04 17:31:01 gepard systemd[1]: Reached target Multi-User System. Oct 04 18:38:27 gepard systemd[1]: Stopping Multi-User System. Oct 04 18:38:27 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 05 08:12:24 gepard systemd[1]: Starting Multi-User System. Oct 05 08:12:24 gepard systemd[1]: Reached target Multi-User System. Oct 05 18:32:56 gepard systemd[1]: Stopping Multi-User System. Oct 05 18:32:56 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 05 18:33:49 gepard systemd[1]: Starting Multi-User System. Oct 05 18:33:49 gepard systemd[1]: Reached target Multi-User System. Oct 05 18:42:05 gepard systemd[1]: Stopping Multi-User System. Oct 05 18:42:05 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 05 19:16:20 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 05 19:17:13 gepard systemd[1]: Starting Multi-User System. Oct 05 19:17:13 gepard systemd[1]: Reached target Multi-User System. Oct 05 19:37:20 gepard systemd[1]: Stopping Multi-User System. Oct 05 19:37:20 gepard systemd[1]: Stopped target Multi-User System. -- Reboot -- Oct 05 20:14:54 gepard systemd[1]: Stopped target Multi-User System. Any hint? Why do you have all those scripts in /etc/local.d? You must have put them there at some point. This is probably behaving strangely due to some error in the /etc/local.d/baselayout1 script. As for multi-user.target: it will not be "started" if any of its dependencies fail to start. (In reply to Mike Gilbert from comment #3) > Why do you have all those scripts in /etc/local.d? You must have put them > there at some point. > > This is probably behaving strangely due to some error in the > /etc/local.d/baselayout1 script. OpenRC creates those on update from baselayout1. mv "${EROOT}"etc/conf.d/local.start "${EROOT}"etc/local.d/baselayout1.start mv "${EROOT}"etc/conf.d/local.stop "${EROOT}"etc/local.d/baselayout1.stop (In reply to Mike Gilbert from comment #3) > Why do you have all those scripts in /etc/local.d? You must have put them > there at some point. Yes, these are my scripts. And I expect, that I can put several *.start and *.stop scripts under /etc/local.d, which are executed in lexical order during boot up and shut down (http://wiki.gentoo.org/wiki/Local.d). I have them there for several years since the old pre systemd times. And with the gentoo-local-baselayout1.service they seem also to work with systemd, at least on my other systems, e.g. rose@lynx:/home/rose(4)$ systemctl status gentoo-local-baselayout1.service ● gentoo-local-baselayout1.service - Service for local.d/baselayout1.* Loaded: loaded (/run/systemd/generator/gentoo-local-baselayout1.service) Active: active (exited) since Di 2014-09-30 15:28:15 CEST; 5 days ago Process: 2811 ExecStart=/bin/true (code=exited, status=0/SUCCESS) rose@lynx:/home/rose(5)$ journalctl -u gentoo-local-baselayout1.service | tail -n 30 Jun 12 19:15:05 lynx env[3370]: /etc/local.d/baaselayout1.stop: before end -- Reboot -- Jun 12 22:28:22 lynx systemd[1]: Starting Service for local.d/baselayout1.*... Jun 12 22:28:22 lynx systemd[1]: Started Service for local.d/baselayout1.*. Jun 13 07:38:08 lynx systemd[1]: Stopping Service for local.d/baselayout1.*... Jun 13 07:38:08 lynx env[3536]: /etc/local.d/baaselayout1.stop: before end Jun 13 07:38:08 lynx systemd[1]: Stopped Service for local.d/baselayout1.*. -- Reboot -- Jun 13 07:43:10 lynx systemd[1]: Starting Service for local.d/baselayout1.*... Jun 13 07:43:10 lynx systemd[1]: Started Service for local.d/baselayout1.*. Jun 13 12:01:48 lynx env[30962]: /etc/local.d/baaselayout1.stop: before end -- Reboot -- Jun 13 12:15:37 lynx systemd[1]: Starting Service for local.d/baselayout1.*... Jun 13 12:15:37 lynx systemd[1]: Started Service for local.d/baselayout1.*. Jun 13 13:24:35 lynx systemd[1]: Stopping Service for local.d/baselayout1.*... Jun 13 13:24:35 lynx systemd[1]: Stopped Service for local.d/baselayout1.*. Jun 13 13:24:36 lynx env[3747]: /etc/local.d/baaselayout1.stop: before end -- Reboot -- Jun 13 13:27:39 lynx systemd[1]: Starting Service for local.d/baselayout1.*... Jun 13 13:27:39 lynx systemd[1]: Started Service for local.d/baselayout1.*. Jun 13 14:36:12 lynx systemd[1]: Stopping Service for local.d/baselayout1.*... Jun 13 14:36:12 lynx env[18098]: /etc/local.d/baaselayout1.stop: before end Jun 13 14:36:12 lynx systemd[1]: Stopped Service for local.d/baselayout1.*. -- Reboot -- Jun 13 14:40:05 lynx systemd[1]: Starting Service for local.d/baselayout1.*... Jun 13 14:40:05 lynx systemd[1]: Started Service for local.d/baselayout1.*. Jun 13 16:14:59 lynx env[24803]: /etc/local.d/baaselayout1.stop: before end -- Reboot -- Jun 13 16:16:34 lynx systemd[1]: Starting Service for local.d/baselayout1.*... Jun 13 16:16:34 lynx systemd[1]: Started Service for local.d/baselayout1.*. At the the other systems I have almost the same scripts under /etc/local.d with two exeptions: at the faulty system gepard I added some echo commands to the scripts which write to /boot_local-d.log and an addional script 99local_finisch.start, which should rename /boot_local-d.log to /boot_local-d_`date`.log. I suppose, that not the files under /etc/local.d/ are responsible for the issue but something deeper in the system configuration. I also get several: Oct 06 09:51:37 gepard systemd[1]: Unit systemd-logind.service entered failed state. Oct 06 09:53:06 gepard org.a11y.atspi.Registry[3145]: ** (at-spi2-registryd:3148): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Oct 06 09:53:08 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. Oct 06 09:53:08 gepard systemd[1]: Unit systemd-logind.service entered failed state. Oct 06 09:53:32 gepard dbus[1834]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out Oct 06 09:54:05 gepard dbus[1834]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out Oct 06 09:54:38 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. So maybe I should disable gentoo-local-baselayout1.service and look for the remaining errors. > This is probably behaving strangely due to some error in the > /etc/local.d/baselayout1 script. > > As for multi-user.target: it will not be "started" if any of its > dependencies fail to start. I don't really think bugzilla is the right place to diagnose whatever problem you are having. Please reopen this if you are able to identify an actual bug. |
