Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getty ttyS0 message pollutes logs #139

Closed
ZubairLK opened this issue Aug 7, 2018 · 1 comment
Closed

getty ttyS0 message pollutes logs #139

ZubairLK opened this issue Aug 7, 2018 · 1 comment

Comments

@ZubairLK
Copy link
Contributor

ZubairLK commented Aug 7, 2018

For this device

root@462a4e8:~# cat /etc/os-release
ID="resin-os"
NAME="Resin OS"
VERSION="2.13.6+rev1"
VERSION_ID="2.13.6"
PRETTY_NAME="Resin OS 2.13.6+rev1"
RESIN_BOARD_REV="c561fa5"
META_RESIN_REV="e167839"
SLUG="intel-nuc"
MACHINE="genericx86-64"
VARIANT="Development"
VARIANT_ID="dev"

The log is full of these error messages

root@462a4e8:~# journalctl -f -a
-- Logs begin at Tue 2018-08-07 06:29:29 UTC. --
Aug 07 11:27:35 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:27:35 462a4e8 agetty[14865]: /dev/ttyS0: not a tty
Aug 07 11:27:45 462a4e8 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time, scheduling restart.
Aug 07 11:27:45 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:27:45 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:27:45 462a4e8 agetty[14903]: /dev/ttyS0: not a tty
Aug 07 11:27:55 462a4e8 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time, scheduling restart.
Aug 07 11:27:55 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:27:55 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:27:55 462a4e8 agetty[14904]: /dev/ttyS0: not a tty
Aug 07 11:28:05 462a4e8 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time, scheduling restart.
Aug 07 11:28:05 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:28:05 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:28:05 462a4e8 agetty[14907]: /dev/ttyS0: not a tty
Aug 07 11:28:15 462a4e8 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time, scheduling restart.
Aug 07 11:28:15 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:28:15 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:28:15 462a4e8 agetty[14943]: /dev/ttyS0: not a tty
Aug 07 11:28:25 462a4e8 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time, scheduling restart.
Aug 07 11:28:25 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:28:25 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:28:25 462a4e8 agetty[14945]: /dev/ttyS0: not a tty
@ZubairLK ZubairLK changed the title getty ttyS0 message pollute logs getty ttyS0 message pollutes logs Aug 7, 2018
@ZubairLK
Copy link
Contributor Author

This happens on my VM. And I had no serial port configured. i.e. ttyS0 didn't exist.
So the getty process would die silently causing this.

Attaching a com port in VM made these go away. I guess this is more a configuration issue rather than an OS issue. While there might be a graceful way of handling this. I'll close this issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant