Jump to content
  • Unraid-Server login[3651]: ILLEGAL ROOT LOGIN on '/dev/pts/8'


    nuhll
    • Minor
    limetech

    Please be aware that these comments were copied here from another source and that the date and time shown for each comment may not be accurate.

    Message added by limetech



    User Feedback

    Recommended Comments

    I thought it was fixed, but IIRC there was an issue where you could only hit terminal so many times and then that message would begin to pop up.   Reboot is the solution.

    Share this comment


    Link to comment
    Share on other sites

    I know. i already did.

     

    Still this is a bug, which is very... dumb for a 24/7 server?!

    Share this comment


    Link to comment
    Share on other sites

    Just tried it and it works properly.  Once you hit 8 windows open at a time (including any from docker containers) you hit that.  Closing windows and it'll let you back in.

    Share this comment


    Link to comment
    Share on other sites

    Definitely some funny business going on with terminal windows.  First of all "8" comes from the default "legacy pty count" we configured in the linux kernel.  This can be changed via a kernel command line option, for example to set to 20:

    pty.legacy_count=20

    Next, the opening/closing of windows seems to be stack-like.  That is suppose you open 8 windows: 1..8.  If you try to open next window it will fail with login not accepted.  If you then close 8, you can open it again - makes sense.  But if you close any/all windows besides number 8, it still won't let you open another window until number 8 is closed.  At this point, you can now open as many windows from 8 down until you hit an open window again.  So yeah, we'll look into this.

     

    Is the this the behavior you're seeing?  BTW doesn't seem to make a difference how window is closed (either by typing 'exit' for by clicking 'X').

    Share this comment


    Link to comment
    Share on other sites

    Not really i didnt had any window open, besides that window what showed after some "lag" "cant login" or something.

     

    If i open terminal, i open it, when im finished i close it... server had some uptime, so i guess it could be that it didnt registered that i close the windows long time ago...?

    Share this comment


    Link to comment
    Share on other sites

    Just wondering... if it would be better to just use '/bin/bash -l' vs 'login -f root' as the ttyd terminal?

    Share this comment


    Link to comment
    Share on other sites

    Its happening again... serve rhas uptime of 1 1/2 day... i use the terminal every day, but i close it after im finished, i dont get it.

     

    You need diagnostic again?

    Share this comment


    Link to comment
    Share on other sites
    9 hours ago, nuhll said:

    Its happening again... serve rhas uptime of 1 1/2 day... i use the terminal every day, but i close it after im finished, i dont get it.

     

    You need diagnostic again?

    Are you using the Unraid terminal (via Terminal button on menu bar) or the Console drop-down selection of a running Docker container, or both?

     

    Can you come up with a sequence of opening/closing that reliably demonstrates this, similar to what I came up with?

    Share this comment


    Link to comment
    Share on other sites

    99% im using the terminal button in unraid. Sometime the Docker console. But since i restartet i never used the console of the container.

     

    What u mean?

     

    I should restart and then open and close terminals ervival times and then give diagnosis?

    Share this comment


    Link to comment
    Share on other sites

    This just happened to me yesterday.  Opened a terminal session, got an "incorrect login" message and it closed.

     

    Earlier, I had opened and closed a couple of terminal sessions, but, no other terminal sessions were open when I received the error.  After that, terminal could not be opened and even attempting to open an SSH session via PuTTY resulted in the same error.

     

    As mentioned, I figured a reboot would clear it, so, today I attempted to shut down the server through the GUI.  It took almost 10 minutes before the shutdown even started.  I thought I was going to have to run shutdown from the console as again, I could not even login through PuTTY - incorrect login.  However 10 minutes later, I noticed on the console that the shutdown was starting  Once it started, it took five minutes to complete the process (hung for a very long time on stopping emhttp) and I noticed that it saved diagnostics to the flash drive during shutdown.

     

    After the reboot, everything is fine again.  Until I hit the terminal bug yesterday, 6.6.6 had been running for me without issue since I upgraded the day it was released.

     

    Attached are the diagnostics saved to my flash drive during shutdown in case they are useful.

     

    Not a showstopper by any means.  I just thought I would add one more data point to the bug report.

     

     

    medianas-diagnostics-20190106-1310.zip

    Share this comment


    Link to comment
    Share on other sites

    I think its a big problem if you cant reach your server via ssh. I mean, if the serve rwould have online for 3000 days and this problem pops up, okay.

     

    But after 3 days uptime, or 7 days??? (dont know how long ur server was on?)

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, nuhll said:

    But after 3 days uptime, or 7 days??? (dont know how long ur server was on?)

    It has been running since 6.6.6 was released on December 3, so, about 33 days.

     

    It's the first and only time it has happened.  I will definitely keep an eye on it and try to reproduce.  I generally have reason to open a terminal window every day and it has never failed until a couple of days ago.

    Edited by Hoopster

    Share this comment


    Link to comment
    Share on other sites

    I also dont do it every day, but recently i needed to do it more then normal because i changed mb and the fans are driving me crazy. 

    Share this comment


    Link to comment
    Share on other sites
    On 1/7/2019 at 8:30 AM, nuhll said:

    I also dont do it every day, but recently i needed to do it more then normal

    Referring to opening terminal windows right (I hope)?  ;)

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, limetech said:

    Referring to opening terminal windows right (I hope)?  ;)

    haha lol. yes.

     

    What i also use is user script to run differnt scripts every 5 minutes or every day. Maybe thats part of the problem?


    Can you fix this problem?

    Edited by nuhll

    Share this comment


    Link to comment
    Share on other sites

    What is this user script doing exactly?

    Does it open terminal sessions without closing them or what?

    Share this comment


    Link to comment
    Share on other sites

    Not that i know.

     

    Its a rclone upload script, some curl scripts, some mounting script for mountfs, script which clears my archives, move scripts and a fancontrol script.

     

    Share this comment


    Link to comment
    Share on other sites

    If u want we can teamviewer and u look over the scripts to see if its could be caused by that.

    Share this comment


    Link to comment
    Share on other sites


    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.