PDA

View Full Version : Scan does not stop even though all files are found



mudbone
2007-05-04, 08:24
I've been lurking since I bought my SB in Nov. I've been able to solve any issues by doing that.

Not this one. I need some assistance.

I owned a ReadyNAS 1TB model that was part of the SB bundle. I decided I wanted a 2TB model which I built from scratch using NAS approved HDs. Once I put the new NAS together I copied all songs which are FLAC files from the 1TB NAS to the 2TB NAS.

At that point I rescanned my entire library. The scan never completed. I have 12062 FLAC files in my music library. Slimserver kept hanging (sometimes stopping) at file 11896.

I finally thought I must have a corrupt file. (I have no playlists). I deleted the most current files to get below 11,896 files. I now have 11882 files. Slimsever now scans all of the files yet never says it has completed. It shows 11882 files.

I begian using the latest version of Slim (6.5.2 Apr 27). Based on my initial findings I went back to v6.5.1 which is what I’m running now.

I’m running WinXP SP2 off a wired laptop. The laptop and NAS talk to each other through a Netgear switch. Slimserver is tunning on the laptop.

Other info:

SlimServer Version: 6.5.1 - 11206 - Windows XP - EN - cp1252
Server IP address: 192.168.1.246
Perl Version: 5.8.8 MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt

I just ran a clear and scan after deleting my cache files having d_info and d_files to capture any problems.

Here’s top level info:

2007-05-04 10:33:08.4670 commit ineffective with AutoCommit enabled at C:\PROGRA~1\SLIMSE~1\server\CPAN/DBIx/Class/Storage/DBI.pm line 706.
2007-05-04 10:33:08.4671 Commmit ineffective while AutoCommit is on at C:\PROGRA~1\SLIMSE~1\server\CPAN/DBIx/Class/Storage/DBI.pm line 706.
2007-05-04 10:33:08.4673 ERROR: DBD::mysql::db commit failed: Commmit ineffective while AutoCommit is on at C:\PROGRA~1\SLIMSE~1\server\CPAN/DBIx/Class/Storage/DBI.pm line 706.

2007-05-04 10:33:08.4673 ERROR: Backtrace follows:



Question:

I thought d_files was supposed to report every file found yet I don’t see that.

Attached is the logfile from my latest scan.

This is frustrating as everything worked fine when I used the 1TB ReadyNAS.

Thanks for any help, advice, tips.

I hope I’ve provided enough info.

Dave-

Diana
2007-05-04, 15:25
...At that point I rescanned my entire library... Slimsever now scans all of the files yet never says it has completed.

Dave >>> I guess when you say the SS 'never says it has completed' you mean that the web interface does not update. This issue has been raised by some folk on the forums (including me!) before.

When using Windows, I used to open Task Manger and watch the activity of mysql and scanner.exe, and the CPU useage. Scanner stops; then mysql does some work; and when it stops and CPU usage drops back to pre-scan values, you know the scan is complete. You can then do Ctrl+F5 to refresh the web page, and the size of your library will display properly.

I also found I always had to do 'Clear and Rescan' ('Look for new/changed music' didn't seem to work well).

This doesn't seem to be a problem with Linux. But I (and some others) never seemed to get to the bottom of the problem with Windows - which clearly doesn't affect everyone. A mystery!

mudbone
2007-05-04, 15:55
Diana, thanks.

By "SS never stops" I mean that "SS is still scanning your database" continues to appear in the browser even after all songs have been scanned. IE7, btw.

I also check task manager. Scanner doesn't stop running.

As I said this wasn't an issue until I moved all my files to the new NAS.

I'm trying several different things now to achieve a successful scan but they certainly are time-consuming.

I'm almost certain I have a corrupt file somewhere.

Dave-

snarlydwarf
2007-05-04, 16:05
As I said this wasn't an issue until I moved all my files to the new NAS.

That sounds like a clue... (which you must know, since you brought it up...)



I'm almost certain I have a corrupt file somewhere.


Check your playlists. Some ripping software (annoyingly, IMHO) likes dumping m3u files into each album. And the regular ones may refer to files that no longer exist or otherwise confuse slimserver.

Slimserver can get into mindless loops if it gets confused by a playlist.

mudbone
2007-05-04, 16:41
The new server could be the issue although I see no "hardware" issues. I'm wondering if a file can/did get corrupted while I was copying 12k FLAC files from one server to another. I've done the best checking I can to see if a filetype is there that doesn't belong and I see none. I only see FLAC files.

I have no playlists and when I clear the library and rescan everything I keep the Playlist Folder blank so (even by error) I'm not looking for any.

As a test I created a small folder on the NAS, moved a few files there, and it scanned w/o issue.

Thanks for the tips.

Dave-

mudbone
2007-05-04, 16:43
One more thing.

If there's a switch I can turn on in Debug that would show any corrupt files I'd like to know about it.

Dave-

Diana
2007-05-04, 22:44
...As a test I created a small folder on the NAS, moved a few files there, and it scanned w/o issue. Dave-

Dave >>> You could try moving all the files our of the music folder and then copying them back in groups, rescanning after each group is added, to locate the suspect file. (The issue is sometimes to do with faulty tagging, which the debug tools may not detect.)

mudbone
2007-05-05, 05:58
Dave >>> You could try moving all the files our of the music folder and then copying them back in groups, rescanning after each group is added, to locate the suspect file. (The issue is sometimes to do with faulty tagging, which the debug tools may not detect.)

Odd you should mention that.

After I started this thread I decided to create 6 temp folders. I moved ~2000 files to each folder and scanned them. I detected no errors nor did I get the BACKTRACE error that I saw in my above attachment. I'm in the process of moving the files back to my main folder and doing a rescan on that each time I move a batch.

Is there a "main" db that SS creates when it scans? Maybe that became corrupt.

Does anyone know what causes that BACKTRACE error to be invoked?

Dave-

Diana
2007-05-06, 01:02
Is there a "main" db that SS creates when it scans? Maybe that became corrupt.

Yes. In XP (I assume that's what you're using) find

C:\Program Files\SlimServer\server\Cache

Stop SS, delete the whole folder, and restart SS. It will recreate the cache and scan your music.


...Does anyone know what causes that BACKTRACE error to be invoked?

Sorry, can't help with this.

mudbone
2007-05-06, 07:54
Yes. In XP (I assume that's what you're using) find

C:\Program Files\SlimServer\server\Cache

Stop SS, delete the whole folder, and restart SS. It will recreate the cache and scan your music.





Thanks. I've deleted those on several occasions in the past.

I saw a thread/post somewhere that mentioned "slimserver.db" and was curious what that contained. I searched my pc and that file didn't appear.

Dave-

mudbone
2007-05-07, 10:48
Well, I've had zero success.

As I said, I moved my music files to smaller folders and re-scanned each. All we successful so they are no "bad" tags or corrupt files.

I then moved each batch back into my music folder and did a re-scan each time. All "post-merged" scans worked well.

My final scan failed. Although SCANNER did quit properly it shows 11896 songs when I actually have 12060.

Anyone have any ideas? I've tried everything I know or have read in various threads here.

Dave-