FS#32085 - [systemd] /dev/getty: No such file or directory

Attached to Project: Arch Linux
Opened by kkl2401 (kkl2401) - Friday, 19 October 2012, 09:33 GMT
Last edited by Dave Reisner (falconindy) - Monday, 05 November 2012, 02:19 GMT
Task Type Support Request
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I see a great amount of error messages concerning /dev/getty in my journal. Specifically:

Oct 19 11:26:09 rory systemd[1]: getty@getty.service holdoff time over, scheduling restart.
Oct 19 11:26:09 rory systemd[1]: Stopping Getty on getty...
Oct 19 11:26:09 rory systemd[1]: Starting Getty on getty...
Oct 19 11:26:09 rory systemd[1]: Started Getty on getty.
Oct 19 11:26:09 rory agetty[6627]: /dev/getty: No such file or directory

This is repeated every 10 seconds.

Perhaps my configuration is broken somewhere but I'm not sure where to start looking. The only thing I changed in
/etc/systemd/system/getty.target.wants/getty@.service
from default values is that I set TTYVTDisallocate to no.


Additional info:
linux 3.6.2-1
systemd 194-3
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 05 November 2012, 02:19 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Saturday, 20 October 2012, 12:07 GMT
systemctl status getty@getty.service

remove the offending file.
Comment by kkl2401 (kkl2401) - Saturday, 20 October 2012, 12:15 GMT
It says this:

$ systemctl status getty@getty.service
getty@getty.service - Getty on getty
Loaded: loaded (/etc/systemd/system/getty.target.wants/getty@.service; disabled)
Active: active (running) since Sat, 20 Oct 2012 14:11:45 +0200; 9s ago
Docs: man:agetty(8)
Main PID: 7688 (agetty)
CGroup: name=systemd:/system/getty@.service/getty
└ 7688 /sbin/agetty --noclear getty 38400

What should I remove? I don't really understand how this works.
Comment by Dave Reisner (falconindy) - Saturday, 20 October 2012, 12:17 GMT
If you want to override a unit, you need to put it in /etc/systemd/system, and enable it from there. You cannot put it in the .wants directory.
Comment by kkl2401 (kkl2401) - Sunday, 04 November 2012, 13:40 GMT
  • Field changed: Percent Complete (100% → 0%)
I decided to forget about overriding the unit for the time being. So I put everything to its previous state, namely I created back the symlink that used to be there and then I ran:

# systemctl disable getty@.service
rm '/etc/systemd/system/getty.target.wants/getty@.service'
# systemctl enable getty@.service
ln -s '/usr/lib/systemd/system/getty@.service' '/etc/systemd/system/getty.target.wants/getty@tty1.service'

I still get the same messages in the journal every 10 seconds. Running systemctl status says:

# systemctl status getty@getty.service
getty@getty.service - Getty on getty
Loaded: loaded (/usr/lib/systemd/system/getty@.service; enabled)
Active: active (running) since Thu, 25 Oct 2012 10:27:43 +0200; 3s ago
Docs: man:agetty(8)
Main PID: 20384 (agetty)
CGroup: name=systemd:/system/getty@.service/getty
└ 20384 /sbin/agetty --noclear getty 38400

Oct 25 10:27:43 rory systemd[1]: Stopping Getty on getty...
Oct 25 10:27:43 rory systemd[1]: Starting Getty on getty...
Oct 25 10:27:43 rory systemd[1]: Started Getty on getty.
Oct 25 10:27:43 rory agetty[20384]: /dev/getty: No such file or directory
Comment by Tom Gundersen (tomegun) - Sunday, 04 November 2012, 13:42 GMT
@bbl2401: do you have a symlink named getty@getty.service somewhere under /etc/systemd/system/ ? If so, that is invalid, just delete it.
Comment by kkl2401 (kkl2401) - Monday, 05 November 2012, 02:15 GMT
I did that and it didn't help, at least not right away. Neither did restarting the service. However, after updating kernel and systemd to newer version which were meanwhile released and therefore after rebooting the machine, it somehow resolved itself. Since then I have seen it once more but I couldn't pay much attention to it at the moment and then it again "disappeared on its own".

Loading...