no login available on ttys (systemd)

StretchDude · 2013-08-20 17:37:55

Hello,

I can no longer login to ttys (ctrl + alt + F1 - this is called a "tty" right?).
If I switch to one of the ttys I can still read some bootup messages I think.
The last one says

 [OK] listening on delayed shutdown socket

No login prompt or blinking cursor at all. all ttys (tty1 - tty6) look that way. If it may help understanding my problem I can type all of that messages into a post...
There is no problem switching back to X waiting on tty7. This makes me believe I do not have broken keyboard config or stuff.
Has anyone a hint, were i can look for some log output what i going wrong when I hit ctrl + alt + f[0-6]?

some research:

ben # systemctl list-units   | egrep -i "tty|login"
sys-devi...tty-ttyS0.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...tty-ttyS1.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...tty-ttyS2.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...tty-ttyS3.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS3
getty@tty1.service          loaded active running   Getty on tty1
getty@tty2.service          loaded active running   Getty on tty2
getty@tty3.service          loaded active running   Getty on tty3
getty@tty4.service          loaded active running   Getty on tty4
getty@tty5.service          loaded active running   Getty on tty5
getty@tty6.service          loaded active running   Getty on tty6
systemd-logind.service      loaded active running   Login Service
getty.target                loaded active active    Login Prompts

ben # ps au |  grep tty
root       365  0.0  0.0   9848   804 tty1     Ss+  18:34   0:00 /sbin/agetty --noclear tty1 38400 linux
root       379  1.5  0.7 212552 123820 tty7    Rs+  18:34   0:36 /usr/bin/X :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-BKoSkc
root       482  0.0  0.0   9848   796 tty3     Ss+  18:35   0:00 /sbin/agetty --noclear tty3 38400 linux
root       483  0.0  0.0   9848   792 tty4     Ss+  18:35   0:00 /sbin/agetty --noclear tty4 38400 linux
root       484  0.0  0.0   9848   800 tty5     Ss+  18:35   0:00 /sbin/agetty --noclear tty5 38400 linux
root       485  0.0  0.0   9848   800 tty6     Ss+  18:35   0:00 /sbin/agetty --noclear tty6 38400 linux
root      6130  0.0  0.0   9848   804 tty2     Ss+  18:52   0:00 /sbin/agetty --noclear tty2 38400 linux
root      9777  0.0  0.0  14692  1128 pts/0    S+   19:14   0:00 grep --colour=auto tty

ben # cat /etc/systemd/logind.conf  | grep -v "^#"
[Login]
NAutoVTs=6
ReserveVT=6

ben # systemctl status systemd-logind
systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
   Active: active (running) since Di 2013-08-20 18:34:55 CEST; 41min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           [url]http://www.freedesktop.org/wiki/Software/systemd/multiseat[/url]
 Main PID: 360 (systemd-logind)
   CGroup: name=systemd:/system/systemd-logind.service
           └─360 /usr/lib/systemd/systemd-logind

Aug 20 18:35:06 bendude systemd-logind[360]: New session 1 of user ben.
Aug 20 18:35:06 bendude systemd-logind[360]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.

And general system info

ben # uname -a 
Linux ben 3.10.7-1-ARCH #1 SMP PREEMPT Thu Aug 15 11:55:34 CEST 2013 x86_64 GNU/Linux

ben # pacman -Qsi systemd
local/initscripts 2012.10.1-1
    System initialization/bootup scripts
local/lib32-systemd 204-1
    system and service manager (32-bit)
local/systemd 204-3
    system and service manager
local/systemd-sysvcompat 204-3 (base)
    sysvinit compat for systemd

Thanks in advance,
Ben

lagagnon · 2013-08-20 19:16:52

I'm not sure if your problem is related but the latest update of glibc caused some redundancy in /dev/pts
If you have this line in your /etc/fstab file, or something similar to mount /dev/pts then remove that line or comment it out:

devpts                 /dev/pts      devpts    defaults            0      0

Last edited by lagagnon (2013-08-20 19:17:08)

StretchDude · 2013-08-20 21:19:20

No, fstab looks pretty clean and simple. But mount spits out some stuff:

ben # mount | grep -v "sd"
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8149004k,nr_inodes=2037251,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
none on /tmp type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)

I don't know what every line is for but they don't look evil to me.

Thanks,
Ben

Scimmia · 2013-08-21 00:42:28

How do you still have initscripts installed? The filesystem update back at the beginning of June should have made you remove that. You can't be that far out of date since you're running the latest kernel, have you been doing partial updates?

cfr · 2013-08-21 02:44:31

Are you sure the messages haven't just over written the prompt? That is, have you tried pressing enter?

StretchDude · 2013-08-21 05:27:46

@cfr: No I tried that many times. There is no visual response. And even typing like when doing a root login and reboot or similar doesn't do anything. So it's not that someout is just blocking Stdout.
@Scimmia: Good point. i will take a look at this.

Thanks,
Ben

StretchDude · 2013-08-21 14:56:31

Update:
I removed the initscripts packages. now my LAN doesn't start automatically any more. but that's a different story -> will be fixed.
Still no login possible on the TTYs.

WonderWoofy · 2013-08-21 14:58:22

lagagnon wrote:

I'm not sure if your problem is related but the latest update of glibc caused some redundancy in /dev/pts
If you have this line in your /etc/fstab file, or something similar to mount /dev/pts then remove that line or comment it out:
devpts                 /dev/pts      devpts    defaults            0      0

Did you see this post here? I think it might have gone unnoticed.

Scimmia · 2013-08-21 15:36:21

StretchDude wrote:

Update:
I removed the initscripts packages. now my LAN doesn't start automatically any more. but that's a different story -> will be fixed.
Still no login possible on the TTYs.

My question was not about one package, but about what that one package represented. Let me ask more bluntly: Is your entire system up to date? Or have you just been updating certain things?

WonderWoofy wrote:

lagagnon wrote:
I'm not sure if your problem is related but the latest update of glibc caused some redundancy in /dev/pts
If you have this line in your /etc/fstab file, or something similar to mount /dev/pts then remove that line or comment it out:
devpts                 /dev/pts      devpts    defaults            0      0
Did you see this post here? I think it might have gone unnoticed.

Unnoticed because it's irrelevant. /dev/pts relates to psudo-terminals, not ttys.

Last edited by Scimmia (2013-08-21 16:16:20)

parchedas · 2013-08-22 08:16:25

I am having the same problem, what should I check? I have similar results to Ben (no initscripts though). I have been doing full system upgrades and don't have devpts in my fstab.

Cheers,
James

cfr · 2013-08-22 21:33:45

@parchedas,
How similar? Similar symptoms? Or you get the same output from some or all of those commands? Or what?

parchedas · 2013-08-22 22:08:41

Well, all ttys display the Welcome to Arch linux screen with the last message being

[  OK  ] Listening on LVM2 metadata daemon socket.

[james@arch ~]$ systemctl list-units   | egrep -i "tty|login"
sys-devi...tty-ttyS1.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...tty-ttyS2.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...tty-ttyS3.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS3
sys-devi...tty-ttyS0.device loaded active plugged   /sys/devices/pnp0/00:0a/tty/ttyS0
getty@tty1.service          loaded active running   Getty on tty1
getty@tty2.service          loaded active running   Getty on tty2
getty@tty5.service          loaded active running   Getty on tty5
systemd-logind.service      loaded active running   Login Service
getty.target                loaded active active    Login Prompts

with each getty@tty service being loaded when I try to access them

[james@arch ~]$ ps au |  grep tty
root       264  0.0  0.0   7904   800 tty1     Ss+  09:53   0:00 /sbin/agetty --noclear tty1 38400 linux
root       273 12.9  2.1 502284 176900 tty7    Ss+  09:53   0:58 /usr/sbin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root       947  0.0  0.0   7904   792 tty5     Ss+  09:55   0:00 /sbin/agetty --noclear tty5 38400 linux
root      1104  0.0  0.0   7904   796 tty2     Ss+  09:58   0:00 /sbin/agetty --noclear tty2 38400 linux
james     1145  0.0  0.0  10684  1072 pts/0    S+   10:00   0:00 grep tty

nothing set in logind.conf

[james@arch ~]$ systemctl status systemd-logind
systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
   Active: active (running) since Fri 2013-08-23 09:53:18 NZST; 11min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 257 (systemd-logind)
   CGroup: name=systemd:/system/systemd-logind.service
           └─257 /usr/lib/systemd/systemd-logind

[james@arch ~]$ uname -a 
Linux arch 3.10.7-1-ARCH #1 SMP PREEMPT Thu Aug 15 11:55:34 CEST 2013 x86_64 GNU/Linux
[james@arch ~]$ pacman -Qsi systemd
local/lib32-systemd 204-1
    system and service manager (32-bit)
local/netctl 1.3-1 (base)
    Profile based systemd network management
local/systemd 204-3
    system and service manager
local/systemd-sysvcompat 204-3 (base)
    sysvinit compat for systemd

What other info can I give you?

cfr · 2013-08-22 22:18:58

What do

systemctl --full list-units | egrep -i "console"
systemctl status systemd-ask-password-console.path

give?
Does systemctl --failed show any results?

karol · 2013-08-22 22:24:35

In both cases agetty is being used - '/sbin/agetty --noclear ttyX 38400 linux' - maybe there's some issue here.
Are you logging to tty automatically or do you type in login and password?

FYI, you can drop the 'i' from 'pacman -Qsi'.

parchedas · 2013-08-22 22:25:01

[james@arch ~]$ systemctl --full list-units | egrep -i "console"
systemd-ask-password-console.path                                                                                loaded active waiting   Dispatch Password Requests to Console Directory Watch
systemd-vconsole-setup.service                                                                                   loaded active exited    Setup Virtual Console

[james@arch ~]$ systemctl status systemd-ask-password-console.path
systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch
   Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-console.path; static)
   Active: active (waiting) since Fri 2013-08-23 09:53:18 NZST; 31min ago
     Docs: man:systemd-ask-password-console.service(8)

[james@arch ~]$ systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

karol · 2013-08-22 22:26:49

Please paste the full output of 'systemctl --full list-units | egrep -i "console"' - does it say 'loaded active waiting', 'loaded active exited' etc.

parchedas · 2013-08-22 22:31:24

karol wrote:

In both cases agetty is being used - '/sbin/agetty --noclear ttyX 38400 linux' - maybe there's some issue here.
Are you logging to tty automatically or do you type in login and password?

FYI, you can drop the 'i' from 'pacman -Qsi'.

Sorry I'm not sure what you mean exactly? The only place I login is with lightdm which is started automatically on tty7, there is no option to login at the other ttys.

Ok I just copied his, I have an alias for that anyway.

parchedas · 2013-08-22 22:32:44

[james@arch ~]$ systemctl --full list-units | egrep -i "console"
systemd-ask-password-console.path                                                                                loaded active waiting   Dispatch Password Requests to Console Directory Watch
systemd-vconsole-setup.service                                                                                   loaded active exited    Setup Virtual Console

karol · 2013-08-22 22:34:25

What happens if you kill X? I noticed you're using X in on vt7.
Have you tried logging in to the tty instead of straight to X?

parchedas · 2013-08-22 22:43:03

Ok so I disabled the lightdm service and then restarted and then after the welcome to arch screen all I get is a blank screen on all ctrl+alt+Fx. Luckily I also have ubuntu installed so I'm using that now. I can mount the arch partition and enable lightdm by a symlink right?

cfr · 2013-08-22 22:52:08

What graphics card are you using? If you add nomodeset to the kernel command line, can you boot to multi-user.target successfully and see the login?

parchedas · 2013-08-22 23:07:04

Oh god I feel dumb, nomodeset fixes the problem. I'm using an AMD card with the catalyst drivers, it says in the wiki to set nomodeset but I must have skipped over that when I installed because Ubuntu handles my grub. Funny thing is it used to work oh well.

cfr · 2013-08-22 23:23:33

Well nomodeset isn't really a solution but it is a useful work around for emergencies, for sure. (I've had machines on which it was the only way to boot an install disk - never mind an installed operating system.)

Have you tried early KMS or was that suggested earlier in the thread?

In any case, you might want to start a new thread - unless the OP really does turn out to have the same issue - to avoid hijacking this one.

EDIT: Just realised the post said the user was using Catalyst which does require nomodeset according to the wiki. So this is probably the solution. KMS won't work here, I think.

Last edited by cfr (2013-08-26 13:15:27)

StretchDude · 2013-08-26 05:57:27

Back again...
1. The init->systemd migration howto didn't turn out very helpful for me.
2. But i have tried "nomodeset" and i looks like it workarounds my problem too. I'm using nvidia driver (and did not manage to enable opengl properly with steam games. I didn't care about that so far but maybe it's releated somehow..?!).
The Wiki doesn't say "nomodeset" for nvidia. An because I have a dual-display set up - which was a pain in the ass to configure back than (different resolution and so on) - I am a little bit scarred to play around with that stuff to much.
So, what does that mean? You say this is just a work around. But at least it should help to point out some stuff one can try out. I'll take a look at that "early KMS" later, after work or tomorrow. Anything else I can take a look?

3. I'm really calm now about breaking my X and at least have a work around to log in and fix it.

Thank you very much,
Ben

cfr · 2013-08-26 13:22:57

(1) What does that mean? Is there a question here?

(2) I'm not sure. I think nomodeset is required for Catalyst because AMD's drivers don't use KMS so that's probably the solution in that case. As you say, it doesn't say that for nvidia. But you'd need to say more about what you tried to do to enable OpenGL and what errors you got.

I said it is a workaround just because for open source drivers using nomodeset either makes it impossible to start X or severely impacts on various things. So you can pass nomodeset in these cases but in lots of cases it cripples the system. It is still useful if it gets you to a prompt you can troubleshoot from rather than being unable to do anything, though! I'm not at all sure about nvidia - I've only used nouveau with their cards which requires KMS to work properly.

Make sure you have the right drivers installed and that the version of X you are using is supported. Look in/post relevant log files (e.g. X's log).

Arch Linux

#1 2013-08-20 17:37:55

no login available on ttys (systemd)

#2 2013-08-20 19:16:52

Re: no login available on ttys (systemd)

#3 2013-08-20 21:19:20

Re: no login available on ttys (systemd)

#4 2013-08-21 00:42:28

Re: no login available on ttys (systemd)

#5 2013-08-21 02:44:31

Re: no login available on ttys (systemd)

#6 2013-08-21 05:27:46

Re: no login available on ttys (systemd)

#7 2013-08-21 14:56:31

Re: no login available on ttys (systemd)

#8 2013-08-21 14:58:22

Re: no login available on ttys (systemd)

#9 2013-08-21 15:36:21

Re: no login available on ttys (systemd)

#10 2013-08-22 08:16:25

Re: no login available on ttys (systemd)

#11 2013-08-22 21:33:45

Re: no login available on ttys (systemd)

#12 2013-08-22 22:08:41

Re: no login available on ttys (systemd)

#13 2013-08-22 22:18:58

Re: no login available on ttys (systemd)

#14 2013-08-22 22:24:35

Re: no login available on ttys (systemd)

#15 2013-08-22 22:25:01

Re: no login available on ttys (systemd)

#16 2013-08-22 22:26:49

Re: no login available on ttys (systemd)

#17 2013-08-22 22:31:24

Re: no login available on ttys (systemd)

#18 2013-08-22 22:32:44

Re: no login available on ttys (systemd)

#19 2013-08-22 22:34:25

Re: no login available on ttys (systemd)

#20 2013-08-22 22:43:03

Re: no login available on ttys (systemd)

#21 2013-08-22 22:52:08

Re: no login available on ttys (systemd)

#22 2013-08-22 23:07:04

Re: no login available on ttys (systemd)

#23 2013-08-22 23:23:33

Re: no login available on ttys (systemd)

#24 2013-08-26 05:57:27

Re: no login available on ttys (systemd)

#25 2013-08-26 13:22:57

Re: no login available on ttys (systemd)

Board footer