#520 Crash WebGUI

v0.69x
closed
Volker
WebGUI (143)
5
2012-10-28
2009-02-28
wilhil
No

When on filebrowser in a new tab, I opened up the CPU graph in the original tab and then opened a thid tab for the network graph as I wanted to see resources being used during the file transfer (file was a 700meg video).

Upon opening the second graph, it just says "cannot get data about interface re0", and the download reports it is complete (in firefox download manager, it doesnt look like a fail / pause, just completed on 50MB)

The WebGUI just goes dead and does not come back alive.

I can still access files fine through SAMBA, and a restart of the NAS box fixes it fine.

I have been able to repeat this several times. I am using a celeron based machine with a integrated 100meg NIC.

Any help would be great and if you need any more information, please say.

Discussion

  • Volker
    Volker
    2009-03-01

    Hi,

    this has nothing to do with the graphs. It is a quixplorer/PHP problem. You are running in misc limitations (file disk space limitation, upload/download limitations in PHP.ini, ...) which will crash lighttpd. Quixplorer is not usable for such actions. Use an external application instead.

    Regards
    Volker

     
  • wilhil
    wilhil
    2009-03-01

    (hope this is how you add a followup)

    Thank you, and I understand what you are saying, however it does not stop the fact that it crashes the WebGUI and needs either a command or a reset.

    Is it at all possible to add a menu item to the console that would restart httpd? or even a "backup" web port(81!) that has a sole purpose of restarting the WebGUI?

     
  • Volker
    Volker
    2009-03-01

    Hi,

    there is no reason to add a new menu entry. Go to the console or login via SSH and execute

    /etc/rc.d/lighttpd restart

    Regards
    Volker

     
  • wilhil
    wilhil
    2009-03-01

    Thank you, but I have to say, I am a little bit disappointed by your response. I know it can be done by a command, I thought the whole point of the menu system was to make everyday commands easy.

    There can be a easy way around by extending the menu...

    My idea would be change the reset GUI password option to "WebGUI commands", and then you can have reset password, reset httpd server e.t.c.

    Or, change the file browser to not download files over a certain ammount...

    maybe even just add a tiny page to the website and a script which runs every 5 mins to check the page, and if no response, it restarts the web service.

    I love freenas and do not want to go on, but however you look at it, it must be a bug that a feature on the WebGUI can crash it?

     
  • Volker
    Volker
    2009-03-01

    Hi,

    extending the console menu would be a solution, but it is sensless in my eyes:

    • Most of the installations are headless, so console menu is only visible during installation, after that monitor is unplugged.

    • You know now why and what to do in your special case, so a menu to restart the webgui would be helpful for you. But most people do not know why and for what this menu should be.

    • The users who know why and how to fix problems do not need such an menu.

    • If the webgui and the lighttpd daemon crashes something has been went wrong. In the most cases a reboot will be the best solution for most users.

    • Adding more senseless code will increase maintenance expenses of not useful features.

    After thinking about that problem I come to the conclusion to disable the upload/download feature in Quixplorer. It makes more problems than it helps will all the existing limitations.

     
  • wilhil
    wilhil
    2009-03-01

    Thank you.

    I just want to say, I have tested many NAS products (dedicated devices and software), and Freenas is far amongst my favourites.

    I understand all the issues you raise, however the reason I thought this is important is because it is only the http that crashes. If this crashes, file access still works. From this point on, you can either restart the service or restart the server.

    If as you say most servers are headless (I have mine like that), how are you meant to restart other than go through the headache of connecting all the wires, OR just press the restart button (which can cause more problems!).

    ssh is a option, but if like me, you would not have turned this on until after you have had a problem!

    Anyway, the reason for reporting it is simply, I had a similar issue on a very expensive dedicated nas, I had to restart through power cycle. It was headless, and the gui crashed. It currupted the raid array and auto deleted everything... no point in saying more... The thing is, I love freenas and want to see it become the best NAS product... any feature that causes a problem such as this, should be removed/fixed...

    Thank you for listening!