FS#50424 - [systemd] 231-1 is breaking connman startup

Attached to Project: Arch Linux
Opened by david cheung (scruffidog) - Wednesday, 17 August 2016, 18:29 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 08 October 2016, 14:52 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: systemd-231-1 breaks connman as follows:

systemd[1]: Starting Connection service...
Aug 17 12:29:38 hydra systemd[373]: connman.service: Failed at step NAMESPACE spawning /usr/bin/connmand: Too many levels of symbolic links
Aug 17 12:29:38 hydra systemd[1]: connman.service: Main process exited, code=exited, status=226/NAMESPACE
Aug 17 12:29:38 hydra systemd[1]: Failed to start Connection service.
Aug 17 12:29:38 hydra systemd[1]: connman.service: Unit entered failed state.
Aug 17 12:29:38 hydra systemd[1]: connman.service: Failed with result 'exit-code'.

this works find under systemd-230-7. The "level of symbolic links" error mesg seems to be indicative of /var/tmp-> /tmp, but not in this case and does not explain the errors appearing/disappearing after upgrade/downgrade.

Additional info:
* package version(s)

dbus 1.10.10-3
connman 1.33-1
systemd 230-7

* config and/or log files etc.


Steps to reproduce:

pacman -S libsystemd-231-1 systemd-231-1 systemd-sysvcompat-231-1
restart and **kablooey***
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 08 October 2016, 14:52 GMT
Reason for closing:  No response
Additional comments about closing:  ...and given the lack of +1, this is probably user configuration, not a problem with systemd/connman
Comment by Doug Newgard (Scimmia) - Thursday, 18 August 2016, 03:21 GMT
How do you figure this is a systemd problem?
Comment by Dave Reisner (falconindy) - Thursday, 18 August 2016, 12:57 GMT
/var/tmp cannot be a symlink to /tmp. That's just not supported, and hasn't ever been. I don't know why this used to work for you.

https://bugs.archlinux.org/task/31301
https://bugs.archlinux.org/task/30229
Comment by david cheung (scruffidog) - Thursday, 18 August 2016, 21:02 GMT
@falconindy: I know /var/tmp is not supposed to be linked to /tmp.
I stated that the error mesg is related to that particular configuration based on google searches, NOT my configuration.
Repeat: this is not how my system is setup. Based on google searches for that error mesg, this was the diagnosis that came up most often.

this problem occurs when I upgrade systemd and related dependencies (libsystemd, systemd-sysvcompat) from version 230-7 to version 231-1
with no other changes to the system. Those were the resulting error mesgs in the log. It may be possible that connman is broken, but it is
working under the previous version of systemd.
Comment by Dave Reisner (falconindy) - Thursday, 18 August 2016, 23:18 GMT
Do you have any symlinks for other canonical directories? /home, /root, /usr or anything else?

https://github.com/systemd/systemd/issues/3867
Comment by david cheung (scruffidog) - Friday, 19 August 2016, 00:30 GMT
those are all real directories; although /home is loopback mounted.
only other remotely related directories that are symlinked:
/var/lock -> /run/lock
/var/run -> /run
Comment by Dave Reisner (falconindy) - Friday, 19 August 2016, 13:56 GMT
And if you disable the Protect* settings in the unit?

Please pare this down to the minimum reproducible...
Comment by Dave Reisner (falconindy) - Monday, 03 October 2016, 23:56 GMT
Ping? Any progress on debugging this?

Loading...