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
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
|
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
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
https://bugs.archlinux.org/task/31301
https://bugs.archlinux.org/task/30229
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.
https://github.com/systemd/systemd/issues/3867
only other remotely related directories that are symlinked:
/var/lock -> /run/lock
/var/run -> /run
Please pare this down to the minimum reproducible...