Why does agetty fail to determine passwordon ubuntu 18.04.1?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0















I'm running a ubuntu server installation with a tty console, and sshd terminal logins.
Both ssh keys and passwords work for authenticating over sshd.
Lately, on the console, when I try to log in in text mode, I get a curious behavior:
I enter my login name. It prompts for the password. However, it very quickly prints a newline, and whatever part of the password I hadn't typed already is echoed in cleartext to the console.
Then, it prompts for login:, but quickly times out and prompts for login: again ... 5 times, until it goes back to clear the screen, and re-issue the agetty process.
At that point it's "stable" and waits for a username again, but entering a username and pressing enter re-starts the "timeout and newline" behavior.



The systemd log for getty@tty1 says the following:



-- Unit getty@tty1.service has finished starting up.
--
-- The start-up result is RESULT.
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): conversation failed
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): auth could not identify password for [jwatte]
Feb 08 12:12:50 xps15 login[1610]: FAILED LOGIN (1) on '/dev/tty1' FOR 'jwatte', Authentication failure
Feb 08 12:12:51 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:54 xps15 login[1610]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:55 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:58 xps15 login[1610]: FAILED LOGIN (3) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:59 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:03 xps15 login[1610]: FAILED LOGIN (4) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:03 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: FAILED LOGIN (5) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:06 xps15 login[1610]: TOO MANY LOGIN TRIES (5) on '/dev/tty1' FOR 'UNKNOWN'
Feb 08 12:13:06 xps15 login[1610]: pam_mail(login:session): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: pam_unix(login:session): close_session - error recovering username
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Service has no hold-off time, scheduling restart.
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit getty@tty1.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.


I imagine the problem is the first two lines:



pam_unix(login:auth): conversation failed
pam_unix(login:auth): auth could not identify password for [jwatte]


Why would this happen, and how can I best debug it?










share|improve this question

















  • 2





    Unfortunately you are suffering from a bug in kernel 4.15.0-43-generic and above. See TTY doesn't wait for password over on AskUbuntu and the bug report on launchpad.

    – PerlDuck
    Feb 8 at 20:46






  • 2





    … and unix.stackexchange.com/questions/498757 and unix.stackexchange.com/questions/499062 …

    – JdeBP
    Feb 9 at 0:33















0















I'm running a ubuntu server installation with a tty console, and sshd terminal logins.
Both ssh keys and passwords work for authenticating over sshd.
Lately, on the console, when I try to log in in text mode, I get a curious behavior:
I enter my login name. It prompts for the password. However, it very quickly prints a newline, and whatever part of the password I hadn't typed already is echoed in cleartext to the console.
Then, it prompts for login:, but quickly times out and prompts for login: again ... 5 times, until it goes back to clear the screen, and re-issue the agetty process.
At that point it's "stable" and waits for a username again, but entering a username and pressing enter re-starts the "timeout and newline" behavior.



The systemd log for getty@tty1 says the following:



-- Unit getty@tty1.service has finished starting up.
--
-- The start-up result is RESULT.
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): conversation failed
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): auth could not identify password for [jwatte]
Feb 08 12:12:50 xps15 login[1610]: FAILED LOGIN (1) on '/dev/tty1' FOR 'jwatte', Authentication failure
Feb 08 12:12:51 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:54 xps15 login[1610]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:55 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:58 xps15 login[1610]: FAILED LOGIN (3) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:59 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:03 xps15 login[1610]: FAILED LOGIN (4) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:03 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: FAILED LOGIN (5) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:06 xps15 login[1610]: TOO MANY LOGIN TRIES (5) on '/dev/tty1' FOR 'UNKNOWN'
Feb 08 12:13:06 xps15 login[1610]: pam_mail(login:session): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: pam_unix(login:session): close_session - error recovering username
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Service has no hold-off time, scheduling restart.
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit getty@tty1.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.


I imagine the problem is the first two lines:



pam_unix(login:auth): conversation failed
pam_unix(login:auth): auth could not identify password for [jwatte]


Why would this happen, and how can I best debug it?










share|improve this question

















  • 2





    Unfortunately you are suffering from a bug in kernel 4.15.0-43-generic and above. See TTY doesn't wait for password over on AskUbuntu and the bug report on launchpad.

    – PerlDuck
    Feb 8 at 20:46






  • 2





    … and unix.stackexchange.com/questions/498757 and unix.stackexchange.com/questions/499062 …

    – JdeBP
    Feb 9 at 0:33













0












0








0








I'm running a ubuntu server installation with a tty console, and sshd terminal logins.
Both ssh keys and passwords work for authenticating over sshd.
Lately, on the console, when I try to log in in text mode, I get a curious behavior:
I enter my login name. It prompts for the password. However, it very quickly prints a newline, and whatever part of the password I hadn't typed already is echoed in cleartext to the console.
Then, it prompts for login:, but quickly times out and prompts for login: again ... 5 times, until it goes back to clear the screen, and re-issue the agetty process.
At that point it's "stable" and waits for a username again, but entering a username and pressing enter re-starts the "timeout and newline" behavior.



The systemd log for getty@tty1 says the following:



-- Unit getty@tty1.service has finished starting up.
--
-- The start-up result is RESULT.
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): conversation failed
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): auth could not identify password for [jwatte]
Feb 08 12:12:50 xps15 login[1610]: FAILED LOGIN (1) on '/dev/tty1' FOR 'jwatte', Authentication failure
Feb 08 12:12:51 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:54 xps15 login[1610]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:55 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:58 xps15 login[1610]: FAILED LOGIN (3) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:59 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:03 xps15 login[1610]: FAILED LOGIN (4) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:03 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: FAILED LOGIN (5) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:06 xps15 login[1610]: TOO MANY LOGIN TRIES (5) on '/dev/tty1' FOR 'UNKNOWN'
Feb 08 12:13:06 xps15 login[1610]: pam_mail(login:session): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: pam_unix(login:session): close_session - error recovering username
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Service has no hold-off time, scheduling restart.
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit getty@tty1.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.


I imagine the problem is the first two lines:



pam_unix(login:auth): conversation failed
pam_unix(login:auth): auth could not identify password for [jwatte]


Why would this happen, and how can I best debug it?










share|improve this question














I'm running a ubuntu server installation with a tty console, and sshd terminal logins.
Both ssh keys and passwords work for authenticating over sshd.
Lately, on the console, when I try to log in in text mode, I get a curious behavior:
I enter my login name. It prompts for the password. However, it very quickly prints a newline, and whatever part of the password I hadn't typed already is echoed in cleartext to the console.
Then, it prompts for login:, but quickly times out and prompts for login: again ... 5 times, until it goes back to clear the screen, and re-issue the agetty process.
At that point it's "stable" and waits for a username again, but entering a username and pressing enter re-starts the "timeout and newline" behavior.



The systemd log for getty@tty1 says the following:



-- Unit getty@tty1.service has finished starting up.
--
-- The start-up result is RESULT.
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): conversation failed
Feb 08 12:12:47 xps15 login[1610]: pam_unix(login:auth): auth could not identify password for [jwatte]
Feb 08 12:12:50 xps15 login[1610]: FAILED LOGIN (1) on '/dev/tty1' FOR 'jwatte', Authentication failure
Feb 08 12:12:51 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:54 xps15 login[1610]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:55 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:12:58 xps15 login[1610]: FAILED LOGIN (3) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:12:59 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:03 xps15 login[1610]: FAILED LOGIN (4) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:03 xps15 login[1610]: pam_securetty(login:auth): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: FAILED LOGIN (5) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Feb 08 12:13:06 xps15 login[1610]: TOO MANY LOGIN TRIES (5) on '/dev/tty1' FOR 'UNKNOWN'
Feb 08 12:13:06 xps15 login[1610]: pam_mail(login:session): cannot determine username
Feb 08 12:13:06 xps15 login[1610]: pam_unix(login:session): close_session - error recovering username
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Service has no hold-off time, scheduling restart.
Feb 08 12:13:06 xps15 systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit getty@tty1.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.


I imagine the problem is the first two lines:



pam_unix(login:auth): conversation failed
pam_unix(login:auth): auth could not identify password for [jwatte]


Why would this happen, and how can I best debug it?







ubuntu systemd getty agetty






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 8 at 20:19









Jon WatteJon Watte

12425




12425







  • 2





    Unfortunately you are suffering from a bug in kernel 4.15.0-43-generic and above. See TTY doesn't wait for password over on AskUbuntu and the bug report on launchpad.

    – PerlDuck
    Feb 8 at 20:46






  • 2





    … and unix.stackexchange.com/questions/498757 and unix.stackexchange.com/questions/499062 …

    – JdeBP
    Feb 9 at 0:33












  • 2





    Unfortunately you are suffering from a bug in kernel 4.15.0-43-generic and above. See TTY doesn't wait for password over on AskUbuntu and the bug report on launchpad.

    – PerlDuck
    Feb 8 at 20:46






  • 2





    … and unix.stackexchange.com/questions/498757 and unix.stackexchange.com/questions/499062 …

    – JdeBP
    Feb 9 at 0:33







2




2





Unfortunately you are suffering from a bug in kernel 4.15.0-43-generic and above. See TTY doesn't wait for password over on AskUbuntu and the bug report on launchpad.

– PerlDuck
Feb 8 at 20:46





Unfortunately you are suffering from a bug in kernel 4.15.0-43-generic and above. See TTY doesn't wait for password over on AskUbuntu and the bug report on launchpad.

– PerlDuck
Feb 8 at 20:46




2




2





… and unix.stackexchange.com/questions/498757 and unix.stackexchange.com/questions/499062 …

– JdeBP
Feb 9 at 0:33





… and unix.stackexchange.com/questions/498757 and unix.stackexchange.com/questions/499062 …

– JdeBP
Feb 9 at 0:33










1 Answer
1






active

oldest

votes


















-1














This turns out to be caused by: https://askubuntu.com/questions/1113704/tty-doesnt-wait-for-password



I don't have mojo points enough to mark this question to redirect there, but thanks to @PerlDuck for providing the answer!






share|improve this answer






















    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
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499554%2fwhy-does-agetty-fail-to-determine-passwordon-ubuntu-18-04-1%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    -1














    This turns out to be caused by: https://askubuntu.com/questions/1113704/tty-doesnt-wait-for-password



    I don't have mojo points enough to mark this question to redirect there, but thanks to @PerlDuck for providing the answer!






    share|improve this answer



























      -1














      This turns out to be caused by: https://askubuntu.com/questions/1113704/tty-doesnt-wait-for-password



      I don't have mojo points enough to mark this question to redirect there, but thanks to @PerlDuck for providing the answer!






      share|improve this answer

























        -1












        -1








        -1







        This turns out to be caused by: https://askubuntu.com/questions/1113704/tty-doesnt-wait-for-password



        I don't have mojo points enough to mark this question to redirect there, but thanks to @PerlDuck for providing the answer!






        share|improve this answer













        This turns out to be caused by: https://askubuntu.com/questions/1113704/tty-doesnt-wait-for-password



        I don't have mojo points enough to mark this question to redirect there, but thanks to @PerlDuck for providing the answer!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 11 at 21:06









        Jon WatteJon Watte

        12425




        12425



























            draft saved

            draft discarded
















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499554%2fwhy-does-agetty-fail-to-determine-passwordon-ubuntu-18-04-1%23new-answer', 'question_page');

            );

            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






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?