[SOLVED] /var/run/nologin created but not removed-cant logon

[gregbert]

After a recent update, i found that i could no longer ssh into my pogoplug w/archlinuxarm on it. I found that /var/run/nologin was the culprit - removing it allowed logins again.

But the file is re-created at every boot... so it needs to be manually removed

I found this in the journal:

$this->bbcode_second_pass_quote('', 's')ystemd[1]: systemd-tmpfiles-setup.service: Job systemd-tmpfiles-setup.service/stop deleted to break ordering cycle starting with var-lib-nfs-rpc_pipefs.mount/stop

[WarheadsSE]

We have noticed this on a few installations. What I am seeing is that systemd-tmpfiles makes this when the --boot is used (during boot), and it is expected that systemd-user-sessions.service will be tripped, removing this file. However, for some reason, multi-user.target is not tripping systemd-user-sessions.service. I am still looking into this myself.

$this->bbcode_second_pass_code('', '
[root@nsa320 boot] # systemctl list-dependencies systemd-user-sessions --reverse
systemd-user-sessions.service

[whse@arch-x64 ~]$ systemctl list-dependencies systemd-user-sessions --reverse
systemd-user-sessions.service
● └─multi-user.target
● └─graphical.target
')

[planeteater]

I too got hit by this, and also got these "Cannot add dependency..." messages in the log described in this topic:
http://archlinuxarm.org/forum/viewtopic.php?f=58&t=9411
Another symptom I noticed that there was no /dev/disk directory, despite all udev related services being in green (active) status.
After downgrading to systemd-226-3, everything went back to normal.

[WarheadsSE]

That (/dev/disk) is a particular system I had not noticed yet. But you're correct.

[gregbert]

my /dev/disk directory continues to exist... for the moment :-)

[gregbert]

and this was fascinating warning on my next pacman -Syu.. did we revert to 226-3.2 systemd from 227-1?

-------------------------------------------

gregbert@Pogoplug2 /mnt/HDD/Downloads % sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
alarm is up to date
aur is up to date
:: Starting full system upgrade...
warning: libsystemd: local (227-1) is newer than core (226-3.2)
warning: systemd: local (227-1) is newer than core (226-3.2)
warning: systemd-sysvcompat: local (227-1) is newer than core (226-3.2)
resolving dependencies...
looking for conflicting packages...

[Kabbone]

Yes, because there were some problems with 227-1. See this Thread http://archlinuxarm.org/forum/viewtopic.php?f=57&t=9394&start=30 for further information.

[gregbert]

thanks for pointing that thread out. Its a similar issue (can't ssh in), but i gather for different reasons b/c at least one person reports not ipv4 address being assigned. though tempting to think these two issues might be connected. Guess i'll just have to wait this out with everyone else.

[Kabbone]

I don't konw if it's connected. I just wanted to point to the probably reason for reverting from 227

[gregbert]

the latest upgrade, which included systemd 228-3, has resolved this issue for me.