From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#33592: "herd restart term-tty2" caused *all* processes to be killed Date: Sun, 02 Dec 2018 20:16:29 -0500 Message-ID: <87tvjvmmt3.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35057) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gTcsF-0001bV-Qw for bug-guix@gnu.org; Sun, 02 Dec 2018 20:18:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gTcs6-0002Q1-Rz for bug-guix@gnu.org; Sun, 02 Dec 2018 20:18:11 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:54279) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gTcs6-0002Px-OV for bug-guix@gnu.org; Sun, 02 Dec 2018 20:18:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gTcs6-0004tK-Jj for bug-guix@gnu.org; Sun, 02 Dec 2018 20:18:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gTcrY-0000iB-FA for bug-guix@gnu.org; Sun, 02 Dec 2018 20:17:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gTcrV-00025O-Bl for bug-guix@gnu.org; Sun, 02 Dec 2018 20:17:28 -0500 Received: from world.peace.net ([64.112.178.59]:57004) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gTcrV-00021O-7x for bug-guix@gnu.org; Sun, 02 Dec 2018 20:17:25 -0500 Received: from mhw by world.peace.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gTcrK-0003vt-2b for bug-guix@gnu.org; Sun, 02 Dec 2018 20:17:14 -0500 List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 33592@debbugs.gnu.org After killing a Wayland 'gnome-session' that I had launched from the command-line on tty2, the login prompt did not return as it normally does. I decided to try "herd restart term-tty2" to see if that would help. That turned out to be a serious mistake. It caused TERM to be sent to all processes, most filesystems to be unmounted, and many (all?) core services to be stopped. This left my system in a unusuable state, besides being able to switch between otherwise unresponsive text virtual terminals and issue SysRq commands. I took a picture of the display before resetting the machine. Fortunately I always use text virtual terminals for my root shells. Here's a hand-typed approximation of what shepherd printed to the console: --8<---------------cut here---------------start------------->8--- root@jojen ~# herd restart term-tty2 [200060.46xxxx] shepherd[1]: Service term-tty4 has been stopped. [200060.46xxxx] shepherd[1]: Service nscd has been stopped. [200060.47xxxx] shepherd[1]: Service guix-daemon has been stopped. [200060.47xxxx] shepherd[1]: Service term-tty2 has been stopped. [200060.47xxxx] shepherd[1]: Service console-font-tty1 has been stopped. [200060.48xxxx] shepherd[1]: Service term-tty1 has been stopped. [200060.48xxxx] shepherd[1]: Service console-font-tty5 has been stopped. [200060.48xxxx] shepherd[1]: Service term-tty5 has been stopped. [200060.49xxxx] shepherd[1]: sending all processes the TERM signal [200064.81xxxx] shepherd[1]: all processes have been terminated [200064.81xxxx] shepherd[1]: Service user-processes has been stopped. [200064.82xxxx] shepherd[1]: Service urandom-seed has been stopped. [200064.82xxxx] shepherd[1]: Service file-systems has been stopped. [200064.83xxxx] shepherd[1]: Service file-system-/dev/pts has been stopped. [200064.84xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/blkio has been stopped. [200064.86xxxx] shepherd[1]: Service file-system-/gnu/store has been stopped. [200064.88xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/freezer has been stopped. [200064.90xxxx] shepherd[1]: Service file-system-/run/systemd has been stopped. [200064.91xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/cpuset has been stopped. [200064.93xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/cpuacct has been stopped. [200064.95xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/devices has been stopped. [200064.96xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/perf_event has been stopped. [200064.98xxxx] shepherd[1]: Service file-system-/run/user has been stopped. [200065.00xxxx] shepherd[1]: Service file-system-/dev/shm has been stopped. [200065.01xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/memory has been stopped. [200065.03xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/elogind has been stopped. [200065.05xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup/cpu has been stopped. [200065.06xxxx] shepherd[1]: Service file-system-/sys/fs/cgroup has been stopped. [200065.06xxxx] shepherd[1]: system-error("kill" "~A" ("No such process") (3)) [200065.06xxxx] shepherd[1]: Service udev has been stopped. [200065.06xxxx] shepherd[1]: Service virtual-terminal has been stopped. [200065.19xxxx] shepherd[1]: closing log [200065.23xxxx] BTRFS info (device dm-0): disk space caching is enabled --8<---------------cut here---------------end--------------->8--- The 'xxxx' are of course more digits that I was too lazy to type. I would not have expected 'term-tty2' to have many dependents, except possibly for 'console-font-tty2'. It was a great surprise that restarting it caused so many other core services to be stopped. Any idea what went wrong here? Mark