Public bug reported:
Following update to the latest package today (245.4-4ubuntu3.18) on
focal, systemd-resolved and systemd-timesyncd (at least) can't start
Ubuntu 20.04
x86_64
kernel 5.4.0-122-generic
logs:
Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited,
code=exited, status=226/NAMESPACE
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job,
restart counter is at 5.
Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated
too quickly.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Following update to the latest package today (245.4-4ubuntu3.18) on
focal, systemd-resolved and systemd-timesyncd can't start
Ubuntu 20.04
x86_64
kernel 5.4.0-122-generic
logs:
Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited,
code=exited, status=226/NAMESPACE
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
- Sep 23 10:48:53 curie systemd[1]: systemd-resolved.service: Scheduled restart
job, restart counter is at 5.
+ Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job,
restart counter is at 5.
Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated
too quickly.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
** Description changed:
Following update to the latest package today (245.4-4ubuntu3.18) on
- focal, systemd-resolved and systemd-timesyncd can't start
+ focal, systemd-resolved and systemd-timesyncd (at least) can't start
Ubuntu 20.04
x86_64
kernel 5.4.0-122-generic
logs:
Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited,
code=exited, status=226/NAMESPACE
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job,
restart counter is at 5.
Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated
too quickly.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990659
Title:
Systemd component broken following update
Status in systemd package in Ubuntu:
New
Bug description:
Following update to the latest package today (245.4-4ubuntu3.18) on
focal, systemd-resolved and systemd-timesyncd (at least) can't start
Ubuntu 20.04
x86_64
kernel 5.4.0-122-generic
logs:
Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited,
code=exited, status=226/NAMESPACE
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job,
restart counter is at 5.
Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated
too quickly.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990659/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
