Bug 735047

Summary:	systemd-logind.service failed on zLinux
Product:	[openSUSE] openSUSE 12.2	Reporter:	Berthold Gunreben <bg>
Component:	Basesystem	Assignee:	Frederic Crozat <fcrozat>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	aj, crrodriguez, dhorak
Version:	Factory
Target Milestone:	---
Hardware:	S/390-64
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Berthold Gunreben 2011-12-06 11:08:01 UTC

There is no tty0 on zLinux, only the console device:

Dec  6 12:00:30 s390t05 sshd[26219]: Accepted publickey for root from 10.10.102.189 port 40087 ssh2
Dec  6 12:00:30 s390t05 dbus[626]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec  6 12:00:30 s390t05 dbus-daemon[626]: dbus[626]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec  6 12:00:30 s390t05 systemd-logind[26221]: Failed to open /sys/class/tty/tty0/active: No such file or directory
Dec  6 12:00:30 s390t05 systemd-logind[26221]: Failed to fully start up daemon: No such file or directory
Dec  6 12:00:30 s390t05 systemd[1]: systemd-logind.service: main process exited, code=exited, status=1
Dec  6 12:00:30 s390t05 systemd[1]: Unit systemd-logind.service entered failed state.
Dec  6 12:00:55 s390t05 dbus[626]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Dec  6 12:00:55 s390t05 dbus-daemon[626]: dbus[626]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Dec  6 12:00:55 s390t05 sshd[26219]: pam_systemd(sshd:session): Failed to create session: Activation of org.freedesktop.login1 timed out

Comment 1 Frederic Crozat 2011-12-08 10:26:47 UTC

since I'm not versed into zLinux at all, are there several vt or just one (which would explain why only "console" device is available ?

systemd-logind is mostly used to monitor opened vt, so we might need to teach it how to deal with zLinux.

Comment 3 Frederic Crozat 2011-12-19 16:44:52 UTC

could you test latest package from home:fcrozat:systemd / systemd (updated 1/2h ago), it contains a fix for not requiring /dev/tty0 for logind which should fix the issue on S/390 (it fixes a similar issue on Xen).

Comment 4 Dan Horák 2011-12-22 15:40:52 UTC

(In reply to comment #3)
> could you test latest package from home:fcrozat:systemd / systemd (updated 1/2h
> ago), it contains a fix for not requiring /dev/tty0 for logind which should fix
> the issue on S/390 (it fixes a similar issue on Xen).

Frederic, does a systemd bug exist for this issue? We have the same problem in Fedora ...

Comment 5 Frederic Crozat 2012-01-03 12:54:37 UTC

(In reply to comment #4)
> Frederic, does a systemd bug exist for this issue? We have the same problem in
> Fedora ...

No, I didn't fill a bug report since I already sent a mail on systemd-devel mailing list with the patch fixing the issue for Xen (and I was waiting for S/390 confirmation). Feel free to ask Lennart to review it :)

Comment 6 Dan Horák 2012-01-04 08:16:19 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > Frederic, does a systemd bug exist for this issue? We have the same problem in
> > Fedora ...
> 
> No, I didn't fill a bug report since I already sent a mail on systemd-devel
> mailing list with the patch fixing the issue for Xen (and I was waiting for
> S/390 confirmation). Feel free to ask Lennart to review it :)

Not sure what you did, but it is fixed in systemd master branch for few hours :-)

Comment 7 Cristian Rodríguez 2012-01-07 03:51:18 UTC

This bug is fixed, updated packages has been relased and a fix is in systemd upstream by now.

Comment 8 Frederic Crozat 2012-01-09 13:36:04 UTC

reopening, until we confirm the fix in working on our package on S/390 (which is not using the exact same fix as upstream)

Comment 9 Frederic Crozat 2012-03-14 16:44:59 UTC

update released