Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#207 WebGUI fsck problem

v0.684b
closed
WebGUI (143)
5
2012-10-28
2007-06-13
digitalvoid
No

If I do a fsck (with unmount first) on the webGUI, the fsck action is indeed done (it takes a while to check almost 900GB of stored data in my case), but I never see the result text of the fsck action on the webGUI. Only the first line is shown. In the log file there is some related error about this. If I do fsck with the CLI it's no problem at all and all the info is shown.

The funny thing is, if there is much less stored data on the graid5 array (say less then ~500GB) the result of the fsck action is indeed showing on the webGUI. (It takes lesser time to check the disk array and the webGUI is updated correctly)

It looks like it is taking to long for the webpage script to update it's self. (bug?)

Discussion

  • Logged In: YES
    user_id=1370551
    Originator: NO

    All cli error message are send the lighttpd error log and are not displayed.
    I think that is related to a ligttpd configuration, but I didn't find how to fix it.

     
  • Dan Merschi
    Dan Merschi
    2007-08-22

    Logged In: YES
    user_id=1512153
    Originator: NO

    By default the lighttpd timeout is set to 360 seconds(global). If fsck need over 360 sec, the results will be lost.
    Error .... We waited 360 seconds. If this a problem increase server.max-write-idle
    http://trac.lighttpd.net/trac/wiki/server.max-write-idleDetails

    Regards,
    Dan