agetty : not a tty in auth.log file
Clash Royale CLAN TAG#URR8PPP
I was checking my auth.log file when I saw multiple lines like this one : Jul 30 22:34:08 <server-name> agetty[31666]: /dev/ttyS1: not a tty
Those lines are logged 4 times every 10 seconds, and it just doesn't stop.
I have a server running with Linux Debian9
debian logs tty authentication
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
asked Jul 30 '17 at 23:21
CaracalCaracal
32
add a comment |
I was checking my auth.log file when I saw multiple lines like this one : Jul 30 22:34:08 <server-name> agetty[31666]: /dev/ttyS1: not a tty
Those lines are logged 4 times every 10 seconds, and it just doesn't stop.
I have a server running with Linux Debian9
debian logs tty authentication
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
asked Jul 30 '17 at 23:21
CaracalCaracal
32
add a comment |
I was checking my auth.log file when I saw multiple lines like this one : Jul 30 22:34:08 <server-name> agetty[31666]: /dev/ttyS1: not a tty
Those lines are logged 4 times every 10 seconds, and it just doesn't stop.
I have a server running with Linux Debian9
debian logs tty authentication
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
asked Jul 30 '17 at 23:21
CaracalCaracal
32
I was checking my auth.log file when I saw multiple lines like this one : Jul 30 22:34:08 <server-name> agetty[31666]: /dev/ttyS1: not a tty
Those lines are logged 4 times every 10 seconds, and it just doesn't stop.
I have a server running with Linux Debian9
debian logs tty authentication
debian logs tty authentication
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
asked Jul 30 '17 at 23:21
CaracalCaracal
32
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
asked Jul 30 '17 at 23:21
CaracalCaracal
32
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
edited Dec 16 '18 at 3:42
Rui F Ribeiro
39.4k1479131
39.4k1479131
asked Jul 30 '17 at 23:21
CaracalCaracal
32
asked Jul 30 '17 at 23:21
CaracalCaracal
32
asked Jul 30 '17 at 23:21
CaracalCaracal
32
32
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The most likely cause on Debian 9 is that you have a console=ttyS1 setting on your kernel command line, which systemd-getty-generator is picking up, causing it to instantiate a serial-getty@ttyS1 service. This service runs Weitse Venema's agetty against the ttyS1 device. But you do not actually have a /dev/ttyS1 terminal character device on your server. The file (apparently) exists, but it is not a terminal character device file.
Further reading
- https://unix.stackexchange.com/a/248313/5132
- https://unix.stackexchange.com/a/316279/5132
- https://unix.stackexchange.com/a/194218/5132
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
add a comment |
Try
systemctl stop getty@ttyS1
systemctl disable getty@ttyS1
answered Dec 30 '18 at 21:37
vladluvladlu
1
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f382825%2fagetty-not-a-tty-in-auth-log-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The most likely cause on Debian 9 is that you have a console=ttyS1 setting on your kernel command line, which systemd-getty-generator is picking up, causing it to instantiate a serial-getty@ttyS1 service. This service runs Weitse Venema's agetty against the ttyS1 device. But you do not actually have a /dev/ttyS1 terminal character device on your server. The file (apparently) exists, but it is not a terminal character device file.
Further reading
- https://unix.stackexchange.com/a/248313/5132
- https://unix.stackexchange.com/a/316279/5132
- https://unix.stackexchange.com/a/194218/5132
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
add a comment |
The most likely cause on Debian 9 is that you have a console=ttyS1 setting on your kernel command line, which systemd-getty-generator is picking up, causing it to instantiate a serial-getty@ttyS1 service. This service runs Weitse Venema's agetty against the ttyS1 device. But you do not actually have a /dev/ttyS1 terminal character device on your server. The file (apparently) exists, but it is not a terminal character device file.
Further reading
- https://unix.stackexchange.com/a/248313/5132
- https://unix.stackexchange.com/a/316279/5132
- https://unix.stackexchange.com/a/194218/5132
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
add a comment |
The most likely cause on Debian 9 is that you have a console=ttyS1 setting on your kernel command line, which systemd-getty-generator is picking up, causing it to instantiate a serial-getty@ttyS1 service. This service runs Weitse Venema's agetty against the ttyS1 device. But you do not actually have a /dev/ttyS1 terminal character device on your server. The file (apparently) exists, but it is not a terminal character device file.
Further reading
- https://unix.stackexchange.com/a/248313/5132
- https://unix.stackexchange.com/a/316279/5132
- https://unix.stackexchange.com/a/194218/5132
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
The most likely cause on Debian 9 is that you have a console=ttyS1 setting on your kernel command line, which systemd-getty-generator is picking up, causing it to instantiate a serial-getty@ttyS1 service. This service runs Weitse Venema's agetty against the ttyS1 device. But you do not actually have a /dev/ttyS1 terminal character device on your server. The file (apparently) exists, but it is not a terminal character device file.
Further reading
- https://unix.stackexchange.com/a/248313/5132
- https://unix.stackexchange.com/a/316279/5132
- https://unix.stackexchange.com/a/194218/5132
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
answered Aug 1 '17 at 11:32
JdeBPJdeBP
33.6k469158
33.6k469158
add a comment |
add a comment |
Try
systemctl stop getty@ttyS1
systemctl disable getty@ttyS1
answered Dec 30 '18 at 21:37
vladluvladlu
1
add a comment |
Try
systemctl stop getty@ttyS1
systemctl disable getty@ttyS1
answered Dec 30 '18 at 21:37
vladluvladlu
1
add a comment |
Try
systemctl stop getty@ttyS1
systemctl disable getty@ttyS1
answered Dec 30 '18 at 21:37
vladluvladlu
1
Try
systemctl stop getty@ttyS1
systemctl disable getty@ttyS1
answered Dec 30 '18 at 21:37
vladluvladlu
1
answered Dec 30 '18 at 21:37
vladluvladlu
1
answered Dec 30 '18 at 21:37
vladluvladlu
1
answered Dec 30 '18 at 21:37
vladluvladlu
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f382825%2fagetty-not-a-tty-in-auth-log-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
