• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

Queue not displaying (hanging) in web interface

Wildebeest

Member
The queue contents never load. I get the page headers, buttons etc; a spinner to the right of the "refresh button", under that is a spinner and "Loading queue data..." and a spinner to the right of the "view auto.log" button. Below that, in grey font, is "Last media scan: retrieving... -scanning every TBC minutes."

I've rebooted; I've run "fix-flash-packages"; I've deleted the queue file and the queue file has been successfully recreated.

Not a big deal as I can use the database browser on the "diag" page which displays the queue correctly (and it looks just fine).
 
Can you do a "View Source" or whatever it's called in your browser and post the last dozen or so lines?
Is there anything in the webif-error.log file?

I presume you mean the queue database by "queue file"?
fix-flash-packages isn't going to do anything as nothing to do with the queue is in flash.

"TBC minutes" might be a giveaway though. Possibly a problem with the /mod/etc/webif.db database.
 
Is there anything in the webif-error.log file?
No, it's empty.
Well - I'm sure it was a moment ago. I really wish the log entries were time-stamped. Anyway now it shows this:
Code:
/mod/webif/lib/settings.class:63: Error: database disk image is malformed
Traceback (most recent call last):
  File "/mod/webif/html/diag/queue/fetch.jim", line 9
    ::<reference.<setting>.00000000000000000000> autolast
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings autolast}
  File "/mod/webif/lib/settings.class", line 297, in settings autolast
    ::<reference.<setting>.00000000000000000000> _nval_setting autolast -1
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings _nval_setting} autolast -1
  File "/mod/webif/lib/settings.class", line 132, in settings _nval_setting
    {settings _safer_query} {...
  File "/mod/webif/lib/settings.class", line 63, in settings _safer_query
    ::sqlite.handle5 query {...
/mod/webif/lib/settings.class:63: Error: database disk image is malformed
Traceback (most recent call last):
  File "/mod/webif/html/diag/queue/fetch.jim", line 9
    ::<reference.<setting>.00000000000000000000> autolast
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings autolast}
  File "/mod/webif/lib/settings.class", line 297, in settings autolast
    ::<reference.<setting>.00000000000000000000> _nval_setting autolast -1
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings _nval_setting} autolast -1
  File "/mod/webif/lib/settings.class", line 132, in settings _nval_setting
    {settings _safer_query} {...
  File "/mod/webif/lib/settings.class", line 63, in settings _safer_query
    ::sqlite.handle5 query {...
/mod/webif/lib/settings.class:63: Error: database disk image is malformed
Traceback (most recent call last):
  File "/mod/webif/html/diag/queue/fetch.jim", line 9
    ::<reference.<setting>.00000000000000000000> autolast
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings autolast}
  File "/mod/webif/lib/settings.class", line 297, in settings autolast
    ::<reference.<setting>.00000000000000000000> _nval_setting autolast -1
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings _nval_setting} autolast -1
  File "/mod/webif/lib/settings.class", line 132, in settings _nval_setting
    {settings _safer_query} {...
  File "/mod/webif/lib/settings.class", line 63, in settings _safer_query
    ::sqlite.handle5 query {...
/mod/webif/lib/settings.class:63: Error: database disk image is malformed
Traceback (most recent call last):
  File "/mod/webif/html/diag/queue/fetch.jim", line 9
    ::<reference.<setting>.00000000000000000000> autolast
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings autolast}
  File "/mod/webif/lib/settings.class", line 297, in settings autolast
    ::<reference.<setting>.00000000000000000000> _nval_setting autolast -1
  File "/mod/lib/jim/oo.tcl", line 49, in ::<reference.<setting>.00000000000000000000>
    {settings _nval_setting} autolast -1
  File "/mod/webif/lib/settings.class", line 132, in settings _nval_setting
    {settings _safer_query} {...
  File "/mod/webif/lib/settings.class", line 63, in settings _safer_query
    ::sqlite.handle5 query {...
/mod/webif/html/db/index.jim:66: Error: database disk image is malformed
Traceback (most recent call last):
  File "/mod/webif/html/db/index.jim", line 108
    db_info /mod/etc/webif.db
  File "/mod/webif/html/db/index.jim", line 66, in db_info
    ::sqlite.handle9 query {SELECT * FROM settings order by 1}
So some rather suspicious "database disk image is malformed" messages 😳

I presume you mean the queue database by "queue file"?
Yes
fix-flash-packages isn't going to do anything as nothing to do with the queue is in flash.
Agreed, I did that because I'd had miscellaneous crashes with the message to fix, and whilst I didn't think it was in anyway related it was worth doing :-)
"TBC minutes" might be a giveaway though. Possibly a problem with the /mod/etc/webif.db database.
Agreed, it made my eyebrow rise but I didn't know what it might point to; I checked for anything on the "settings" page that looked relevant but couldn't see anything. Following your reply I looked at webif.db using the database browser (diag page) and it shows only this:

Remove filters

/mod/etc/webif.db

which of itself may be suspicious. If I delete the webif.db file will it recreate itself ok like the queue db file?
 
If I delete the webif.db file will it recreate itself ok like the queue db file?
Yes. Obviously you'll lose any settings that weren't the defaults. That should make everything work again.
I really wish the log entries were time-stamped.
I'll have to investigate how it works to see if there's an easy fix.
 
Back
Top