With a freshly-booted up to date trusty VM (ubuntu-trusty-daily- amd64-server-20170130-disk1.img, then dist-upgraded for libssl1.0.0 openssl), simply installing systemd seems to be sufficient to cause the file to exist.
ubuntu@pjdc-test:~$ ls -l /var/run/nologin ls: cannot access /var/run/nologin: No such file or directory ubuntu@pjdc-test:~$ sudo apt-get install systemd sudo: unable to resolve host pjdc-test Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd-journal0 Suggested packages: systemd-ui The following NEW packages will be installed: libsystemd-journal0 systemd 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,476 kB of archives. After this operation, 9,229 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://prodstack-zone-2.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main libsystemd-journal0 amd64 204-5ubuntu20.22 [51.0 kB] Get:2 http://prodstack-zone-2.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main systemd amd64 204-5ubuntu20.22 [1,425 kB] Fetched 1,476 kB in 0s (17.6 MB/s) Selecting previously unselected package libsystemd-journal0:amd64. (Reading database ... 51302 files and directories currently installed.) Preparing to unpack .../libsystemd-journal0_204-5ubuntu20.22_amd64.deb ... Unpacking libsystemd-journal0:amd64 (204-5ubuntu20.22) ... Selecting previously unselected package systemd. Preparing to unpack .../systemd_204-5ubuntu20.22_amd64.deb ... Unpacking systemd (204-5ubuntu20.22) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Setting up libsystemd-journal0:amd64 (204-5ubuntu20.22) ... Setting up systemd (204-5ubuntu20.22) ... Initializing machine ID from D-Bus machine ID. systemd start/running, process 3110 Processing triggers for libc-bin (2.19-0ubuntu6.9) ... Processing triggers for ureadahead (0.100.0-16) ... ubuntu@pjdc-test:~$ ls -l /var/run/nologin -rw-r--r-- 1 root root 21 Feb 1 01:31 /var/run/nologin ubuntu@pjdc-test:~$ -- 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/1660573 Title: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I've installed snapd on an up-to-date Ubuntu 14.04 server system running LTS enablement kernel. After toying with snapd and some simple snaps I logged out (so far everything was OK). I returned to the console after a while (I'm not sure if I logged out but I suspect I had to) and I saw the login prompt. After entering my username a line was printed "System is booting up" and I was kicked back ot the login prompt (It never asked for my password). After rebooting the problem went away. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1660573/+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
