Media library not refreshing?

[popechild]

I don't know what changed, but recently after a long period of everything on my install working really well, the video library is no longer refreshing to show new files (or to not show deleted/moved files). This is even if I force a manual refresh or restart the server.

Typically I would download something I wanted to watch to one of the folders specified in the video library import folders list, then force a refresh (or wait however long I had the refresh interval set for) and it would show the new file. Now nothing seems to change regardless of how long I wait (even days).

The icon on the top that shows that a refresh is in progress never goes away either. It's there all the time.

I've even deleted every folder out of the list of imported folders in Sage, assuming that after a refresh it would quickly change to showing that there are no import folders, but it still shows (and plays) every video from every import folder that had previously been specified.

Any ideas? I really have no idea what to do short of a complete re-install from scratch, and I'd really love to not have to do that.

[Oddity]

Have you tried stopping the Sage service, then checking that there are no sage processes running. A reboot should also do the same.
If the problem still ocurs, take a copy of the wiz.bin file (whilst the service is stopped ) and remove it. Start the service, it should create a new one. Does it now scan correctly?

Check the folder permissions for the scan directories, although it does sound like a corrupt wiz.bin

[popechild]

I have restarted the Sage service (checking to make sure that there weren't any duplicates running) as well as rebooted the machine.

I'm not 100% sure I understand how wiz.bin works, but I did previously save wiz.bin as wiz.bin.OLD and renamed wiz.bak as wiz.bin. That didn't make any difference, but maybe that's not the same thing. When wiz.bin is deleted does it rebuild it by using wiz.bak and essentially just renaming it the way I did manually, or does it actually create a new wiz.bin from elsewhere? I'm assuming if wiz.bin was/is corrupt then so is wiz.bak at this point.

[egeller]

Do you have debug logging turned on? I know that corrupt Wiz.bin will cause messages in the log file. I have fought plenty of those battles from time to time. Does the media scan write messages also? Maybe there are log messages to look at.

[stuckless]

I've seen this myself... and typically when this has happened, it's because sagetv gets "stuck" on a corrupted media file. The sagetv_0.txt log file should should which file it last scanned, so you can try removing that file, and see what happens.