• [6.7.0-rc4] Web Console Stops Working


    Taddeusz
    • Retest Annoyance

    I've had this happen once before. I will be using the console and it will all of a sudden freeze. I close the console window and try to re-open it but all I get is an empty white window. The console never re-opens. The only thing that seems to fix it is a reboot. I'm using the latest version of Chrome on macOS Mojave.

    unraid-diagnostics-20190221-1727.zip




    User Feedback

    Recommended Comments



    If by console you mean a terminal window, I also have had this happen on RC4.  Checked logs when it happened but no entries so didn't have any info to share.

    Edited by IamSpartacus
    Link to comment

    I didn’t see anything in my syslog either but it’s important to report it with your full diags. There may be something else in them that indicates the problem.

    Link to comment

    I had it once on the first day testing the RC4. Same behaviour, webterminal stopped responding, no log entry and a reboot fixed it. Last thing I did before it happenned was using a btrfs command to list my snapshots on an unassigned device and it froze. Sorry no diags. 

     

     

    Link to comment

    same here, no entries in log, just blank screen (about:blank) when trying to open webterminal again.

     

    ssh still working etc ...

     

    only final solution was a reboot.

    Link to comment

    It doesn't appear in the syslog. I also missed that at least in Chrome it shows in the lower left corner "Waiting for <my Unraid address>...". It just sits. According to DevTools it just has a pending connection to /webterminal.

    Screen Shot 2019-02-22 at 5.04.39 PM.png

    Link to comment
    36 minutes ago, Taddeusz said:

    It doesn't appear in the syslog.

    But what might appear is whether the process is still running.  This is captured by diags.

    Link to comment
    12 minutes ago, limetech said:

    But what might appear is whether the process is still running.  This is captured by diags.

    I did post my diags in my initial post

    Link to comment
    2 hours ago, limetech said:

    You're running zsh?  How are you doing that?

    Yes, I am. We've been through this before. I installed it through Nerd Pack.

     

    Seeing that other people are having this issue that likely aren't running zsh I don't understand how this is relevant.

    Link to comment
    1 hour ago, Taddeusz said:

    Seeing that other people are having this issue

    What other people?  Something similar was addressed in -rc1, meaning the issue where one couldn't open more than 8 windows.

     

    Your config is relevant to extent that if we can't reproduce an issue, very difficult to solve.  It's helpful if you can somehow make it happen on demand.

     

    That said, I have seen cases where terminal brings up a blank window.  In this case rebooting the client (windows) seemed to solve it, but we will keep an eye on this.

    Link to comment

    another browser didnt help here tooi checked another browser, typed in manually the webterminal address (the adress fiels stays about:blank

    i tried from another mashine, i waited till i was at home and tried also, same ...

    all other was still working, ssh through guacamole etc ... just the webterminal.

    i tried to find a way to restart web interface but afaik theres no way therefore ...

    Link to comment
    7 minutes ago, alturismo said:

    another browser didnt help here tooi checked another browser, typed in manually the webterminal address (the adress fiels stays about:blank

    i tried from another mashine, i waited till i was at home and tried also, same ...

    all other was still working, ssh through guacamole etc ... just the webterminal.

    i tried to find a way to restart web interface but afaik theres no way therefore ...

    Can you provide full diagnostics please.

    Link to comment

    i did ... happened 3 days ago, i ll next time.

     

    i checked syslog, no entry, i checked cpu loads, seemed fine, i checked ssh, was all good.

     

    thats why i didnt made a diag, next time i will.

    Link to comment

    The ttyd package as well as libwebsockets that it uses both have updates; however, we will be releasing 6.7.0-rc5 without these updated - will have to wait for next release.

    Link to comment

    ok, happened again now, i have the webterminal windows open where it "stalled", i opened a new window to see what happens and its the same behavior, about:blank ....

     

    happened in the middle of typing, not even executed anything ...

     

    heres a screenshot and diags attached

    image.thumb.png.8b03814e357ea1dde32223995aa6578c.png

     

    now, what to look for or what diags could be helpful, i keep all open for now ...

    alsserver-diagnostics-20190225-0609.zip

    Edited by alturismo
    diags attached
    Link to comment
    11 hours ago, alturismo said:

    heres a screenshot and diags attached

    Thank you.  Quick question: while in this state, do the CPU load bar graphs still jump around like normal, or are they too 'frozen'?

    Link to comment
    5 minutes ago, limetech said:

    Thank you.  Quick question: while in this state, do the CPU load bar graphs still jump around like normal, or are they too 'frozen'?

    On mine the CPU graphs still work.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • 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.