Bug 726976 - Unable to start service getty
Summary: Unable to start service getty@xvc0.service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-31 17:02 UTC by David Kowis
Modified: 2011-08-31 01:26 UTC (History)
7 users (show)

Fixed In Version: systemd-26-9.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-31 01:26:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Kowis 2011-07-31 17:02:33 UTC
Description of problem:

I followed the instructions listed here: 
http://fedoraproject.org/wiki/Systemd#How_do_I_change_the_number_of_gettys_running_by_default.3F
to set up another getty, specifically for my /dev/xvc0 console, since this is a xen domU.

The systemctl start getty hangs and never starts. This shows up in the syslog
<syslog>
Jul 31 12:57:11 localhost systemd[1]: Job dev-xvc0.device/start timed out.
Jul 31 12:57:11 localhost systemd[1]: Job getty/start failed with result 'dependency'.
Jul 31 12:57:11 localhost systemd[1]: Job dev-xvc0.device/start failed with result 'timeout'.
</syslog>


Version-Release number of selected component (if applicable):
Fedora 15 x86_64 systemd 8.fc15


How reproducible:
Very:
Start up a domU, create the symlink, and then attempt to start the service
systemctl start getty
The console you issued that from will hang, and the syslog will report as listed above. 

Actual results:
getty is unable to start, systemd complains about not being able to find a dependency.

Expected results:
Getty should fire up on /dev/xvc0 allowing xm console logins

Additional info:
You can ctrl-c out of the systemctl command, and passing in --ignore-dependencies will get it to start.

Comment 1 Lennart Poettering 2011-08-01 18:20:29 UTC
What kind of tty device is /dev/xvc0?

This fails since these device nodes are not marked for exposure in systemd, and hence systemd will time out when it waits for them to show up. This us usually fixed by writing a small udev rule that adds the "systemd" tag to the device in the udev database. See the rules at the top of /lib/udev/rules.d/99-systemd.rules for more information.

If /dev/xvc0 is something like hvc0, then we should probably expose this by default.

Comment 2 Lennart Poettering 2011-08-01 18:31:00 UTC
Hmm, since this appears to be something where we automatically want to spawn a getty on I have now added this to git: we the xvc devices are now tagged "systemd" and hence show up as systemd units, and "serial-getty" is automatically started when xvc0 is available.

http://cgit.freedesktop.org/systemd/commit/?id=980fc73d1fcda8c2a494a18dbd3262fdb97f5fbe

Comment 3 David Kowis 2011-08-01 18:41:34 UTC
(In reply to comment #2)
> Hmm, since this appears to be something where we automatically want to spawn a
> getty on I have now added this to git: we the xvc devices are now tagged
> "systemd" and hence show up as systemd units, and "serial-getty"
> is automatically started when xvc0 is available.
> 
> http://cgit.freedesktop.org/systemd/commit/?id=980fc73d1fcda8c2a494a18dbd3262fdb97f5fbe

That sounds like it'll work. What would be the best way for me to test this?

And yeah, it's just like hvc0, just named differently for a different kernel. I don't remember the link that it used to be detailed on, it's possible that the xen wiki has changed and doesn't display the information anymore.

Comment 4 Lennart Poettering 2011-08-01 18:56:44 UTC
I'll probably make an update to F15 including this patch.

In the meantime, make the change as in the patch to your /lib/udev/rules.d/99-systemd.rules file. Then symlink /lib/systemd/serial-getty@.service to /etc/systemd/system/getty.target.wants/serial-getty, which will give you the same effect as the generator part of the patch, except that you configured it manually. Reboot.

Comment 5 David Kowis 2011-08-01 19:06:52 UTC
(In reply to comment #4)
> I'll probably make an update to F15 including this patch.
> 
> In the meantime, make the change as in the patch to your
> /lib/udev/rules.d/99-systemd.rules file. Then symlink
> /lib/systemd/serial-getty@.service to
> /etc/systemd/system/getty.target.wants/serial-getty, which will
> give you the same effect as the generator part of the patch, except that you
> configured it manually. Reboot.

It works perfectly. Thanks.

Comment 6 Fedora Update System 2011-08-23 15:46:43 UTC
systemd-26-9.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/systemd-26-9.fc15

Comment 7 Fedora Update System 2011-08-26 19:03:25 UTC
Package systemd-26-9.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-26-9.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/systemd-26-9.fc15
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2011-08-31 01:26:42 UTC
systemd-26-9.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.