touch-packages team mailing list archive

[Elena Stepanova <1506206@xxxxxxxxxxxxxxxxxx>]

Correction to the initial scenario: it turns out that the service
restart (quick or not) is irrelevant. It was not obvious because the
problem happens sporadically, so after adding a delay the test was
passing by pure chance.

Further experiments have shown that to get the  pseudo-dead service, it
is enough to do

# After reboot, mariadb service is already running
sudo systemctl disable mariadb
# optional delay
sudo systemctl enable mariadb
# optional delay
sudo systemctl status mariadb

# At this point we have the "dead" service, further shutdown causes
systemd abort.

On my machine it failed in ~30-40% of runs, but it is highly volatile.

-- 
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/1506206

Title:
  systemd abort

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Fedora:
  Unknown

Bug description:
  ############################

  sudo systemctl stop mariadb

  # needs to be fast, do not sleep more than 1 sec

  sudo systemctl start mariadb

  # delay does not matter

  sudo systemctl disable mariadb

  # delay does not matter

  sudo systemctl enable mariadb

  # delay does not matter

  sudo systemctl status mariadb

  ############################

  Here the service starts showing the infamous

  ############################

  ● mariadb.service - MariaDB database server
      Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
  preset: enabled)
     Drop-In: /etc/systemd/system/mariadb.service.d
              └─migrated-from-my.cnf-settings.conf
      Active: inactive (dead) since Wed 2015-10-14 15:04:58 UTC; 58s ago
    Main PID: 880 (mysqld)
      Status: "Taking your SQL requests now..."
      CGroup: /system.slice/mariadb.service
              └─880 /usr/sbin/mysqld

  ############################

  If I then shut down the MariaDB server, e.g. via the shutdown command 
  (or just SIGTERM the process), I get

  ############################

  Broadcast message from systemd-journald@ubuntu-vivid-amd64 (Wed 
  2015-10-14 15:14:18 UTC):

  systemd[1]: Caught <ABRT>, dumped core as pid 960.

  
  Broadcast message from systemd-journald@ubuntu-vivid-amd64 (Wed 
  2015-10-14 15:14:18 UTC):

  systemd[1]: Freezing execution.

  ############################

  systemd:

  ii  libpam-systemd:amd64                219-7ubuntu3 
  amd64        system and service manager - PAM module
  ii  libsystemd0:amd64                   219-7ubuntu3 
  amd64        systemd utility library
  ii  systemd                             219-7ubuntu3 
  amd64        system and service manager
  ii  systemd-sysv                        219-7ubuntu3 
  amd64        system and service manager - SysV links

  
  with also occurs on Redhat - backtrace: https://bugzilla.redhat.com/show_bug.cgi?id=1271832

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