[Bug 1816630] Re: systemd-timedated fails to start with /tmp as a symlink

Sebastien Bacher seb128 at ubuntu.com
Thu Feb 21 08:50:09 UTC 2019 

Thank for the debugging, I'm updating the title to reflect better the
issue and it's up to the systemd team then to see how important they
believe the issue to be

** Summary changed:

- Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut
+ systemd-timedated fails to start with /tmp as a symlink

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1816630

Title:
  systemd-timedated fails to start with /tmp as a symlink

Status in systemd package in Ubuntu:
  New

Bug description:
  When I try to start the `gnome-control-center`, then it hangs after a
  few seconds.

  I recently changed the timezone due to travelling. I can login
  normally.

  Another source of the error could be, that I symlinked the `/tmp` and
  `/opt` directory to another partition.

  ```
  $ gnome-control-center

  (gnome-control-center:29386): datetime-cc-panel-WARNING **: 10:13:23.508: could not get proxy for DateTimeMechanism: Fehler beim Aufruf von StartServiceByName für org.freedesktop.timedate1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms)
  **
  ERROR:../shell/cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child)
  Abgebrochen (Speicherabzug geschrieben)
  ```

  ```
  $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /org/freedesktop/timedate1
  Fehler: Zeitüberschreitung wurde erreicht
  ```

  ```
  $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /
  Fehler: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms)
  ```

  ```
  $ timedatectl
  Failed to query server: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms)
  ```

  ```
  $ timedatectl --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid
  ```

  systemd-timedated service is not starting:
  ```
  $ sudo systemctl status systemd-timedated.service
  ● systemd-timedated.service - Time & Date Service
     Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2019-02-19 10:47:33 CST; 2min 53s ago
       Docs: man:systemd-timedated.service(8)
             man:localtime(5)
             https://www.freedesktop.org/wiki/Software/systemd/timedated
    Process: 3618 ExecStart=/lib/systemd/systemd-timedated (code=exited, status=226/NAMESPACE)
   Main PID: 3618 (code=exited, status=226/NAMESPACE)

  Feb 19 10:47:33 home systemd[1]: Starting Time & Date Service...
  Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory
  Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory
  Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE
  Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Failed with result 'exit-code'.
  Feb 19 10:47:33 home systemd[1]: Failed to start Time & Date Service.
  ```

  ```
  $ journalctl -xe
  Feb 19 18:03:59 home ntpd[21785]: 176.221.42.125 local addr 192.168.0.102 -> <null>
  Feb 19 18:04:05 home sudo[17719]: sebastian : TTY=pts/0 ; PWD=/home/sebastian ; USER=root ; COMMAND=/bin/systemctl start systemd-timedated
  Feb 19 18:04:05 home sudo[17719]: pam_unix(sudo:session): session opened for user root by (uid=0)
  Feb 19 18:04:05 home systemd[1]: Starting Time & Date Service...
  -- Subject: Unit systemd-timedated.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-timedated.service has begun starting up.
  Feb 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory
  Feb 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory
  -- Subject: Process /lib/systemd/systemd-timedated could not be executed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- The process /lib/systemd/systemd-timedated could not be executed and failed.
  -- 
  -- The error number returned by this process is 2.
  Feb 19 18:04:05 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE
  Feb 19 18:04:05 home systemd[1]: systemd-timedated.service: Failed with result 'exit-code'.
  Feb 19 18:04:05 home systemd[1]: Failed to start Time & Date Service.
  -- Subject: Unit systemd-timedated.service has failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-timedated.service has failed.
  -- 
  -- The result is RESULT.
  Feb 19 18:04:05 home sudo[17719]: pam_unix(sudo:session): session closed for user root
  ```

  NTP deamon is running:
  ```
  $ sudo service ntp status
  ● ntp.service - Network Time Service
     Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2019-02-19 10:42:37 CST; 2min 54s ago
       Docs: man:ntpd(8)
    Process: 21763 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS)
   Main PID: 21785 (ntpd)
      Tasks: 2 (limit: 4915)
     CGroup: /system.slice/ntp.service
             └─21785 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 127:135

  Feb 19 10:42:40 home ntpd[21785]: Soliciting pool server 136.243.177.133
  Feb 19 10:42:40 home ntpd[21785]: Soliciting pool server 2001:638:504:2000::36
  Feb 19 10:42:41 home ntpd[21785]: Soliciting pool server 2001:418:3ff::53
  Feb 19 10:42:41 home ntpd[21785]: Soliciting pool server 78.46.231.23
  Feb 19 10:42:41 home ntpd[21785]: Soliciting pool server 129.70.132.32
  Feb 19 10:42:41 home ntpd[21785]: Soliciting pool server 51.15.191.239
  Feb 19 10:42:42 home ntpd[21785]: Soliciting pool server 129.70.132.33
  Feb 19 10:42:42 home ntpd[21785]: Soliciting pool server 2a02:c205:2009:8290::1
  Feb 19 10:42:42 home ntpd[21785]: Soliciting pool server 129.70.132.35
  Feb 19 10:42:42 home ntpd[21785]: Soliciting pool server 2001:67c:1560:8003::c8
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 10:13:56 2019
  InstallationDate: Installed on 2018-12-12 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1816630/+subscriptions

More information about the foundations-bugs mailing list