Scan for New Music Hangs (7.6.1)

[bulletmark]

Is there a procedure anywhere somebody can point me to so I can try and address this problem? I have had my SB's for years and have always found SB server to be a bit dodgy but have never had the scanner play up like it does nowadays. Now I find that it just stops. I only have a tiny number of songs (~1700) but the scanner log always stops on the line

[12-04-29 19:33:03.0478] Slim::Utils::Scanner::Local::__ANON__ (410) Rescanning changed audio files (0)

Running strace shows the scanner locked in a futex() call:

mark@pc:/var/log/squeezeboxserver sudo strace -p 3725
Process 3725 attached - interrupt to quit
futex(0xb76ad400, FUTEX_WAIT_PRIVATE, 2, NULL^C <unfinished ...>

I have upgraded from v7.6 to v7.7 to v7.8 today but makes no difference. Can't see any permission problems and have cleared the cache. This whole SB software suite has become an ugly monster. Is there any other server option?

[Barnabas]

Have had the exact same problem.

I fixed it by:
1) stopping the squeezecenter server
2) deleting the db (sqllite) files.
3) starting the squeezcenter server
4) log into the server setup at initiate a full clean scan.

None of the server settings will be lost, they reside in a config file, not the db files.

What the exact difference between the old and the new db files was I did not examine.

[bulletmark]

Some months after my post above I upgraded to 7.7.2 and then rather than locking up, the scanner just prints a "terminated unexpectedly" on the screen. The actual scanner and server logs say little. I seem to have all my music scanned however.

I just shut the server down, cleared all those *.db and __* files in the cache, and started the server. Made no difference to me. I still get the above message when I do a scan.

[mark-in-seattle]

I've used LMS to send music files to old Squeezeboxes and one new duet in prior incarnations for about 7(?) years hosted by my Netgear ReadyNAS NV+.

Scanning new music files was always an iffy process for me until I learned that MP3 files can become encrusted with mangled tags which in turn gives various versions of the LMS scanning code a headache. My scans would sometimes work fine, but after upgrades would hang at various places, abort unexpectedly... yada ... yada. The only fix that worked for me was to purchase an MP3 (or similar music file format) tag scanning and repair app. Experts tell me that music libraries are commonly laced with dicey tag info in a myriad of fields embedded within music files. As mentioned above the LMS music scanner tries it's best to interpret (or ignore) mangled tags but this is more art than science and changes in my experience with successive code versions.

The Jaikoz Tag scanning app has a decent reputation and worked wonders for me (I have no affiliation with the company except as a satisfied customer). It found a bunch of tags of questionable character among my music library and fixed them at least well enough that my LMS v7.7.1 completed a scan, which it had not been able to do despite many hours of troubleshooting on my part.

Worked for me, ... YMMV.

[Pete7874]

Scanning new music files was always an iffy process for me until I learned that MP3 files can become encrusted with mangled tags which in turn gives various versions of the LMS scanning code a headache.

Sounds like a step backwards then since versions 7.5 and below had no such problems with scanning.

[NFLnut]

I have been having scan hangs daily for at least two months now. My HTPC shuts itself down for 5 hrs every morning and restarts itself, and that is when it starts a new scan and hangs. I have been unable to access my music folder every day unless I turn on my big TV to access the desktop and manually force-close "scanner.exe" in Task Manager. I have tried deleting what I thought to be "bad" shortcuts in my music folder, and other steps, but nothing has solved the problem. This is a MAJOR annoyance and it needs to be fixed yesterday! I am on the latest LMS (7.7.3).