Here's the situation:

I'm using Amarok 1.4.2 on Kubuntu Dapper with all necessary packages up to date.  I'm using SQLite for my collection database.

My music collection is on an NTFS partition on a Windows machine on my LAN, which I am accessing by mounting it with samba.

Whenever Amarok trise to build a collection, it stops part way with the error "Sorry, the collection scan was aborted, since too many problems were detected".  There are simply too many files it stalls out on in my collection for me to remove them.

I tried using amarok-svn to update to the newest build, which installed properly, but it just errors out after 20 songs instead of 2, as explained in this thread:

http://amarok.kde.org/forum/index.php/t ... 855.0.html

I even completely reinstalled Kubuntu from scratch, did a package update, then updated Amarok to 1.4.2 with a fresh, up-to-date installation.  The exact same problem occurred.

Version 1.4.1 worked just fine.

This is by far the best media player I've EVER used; I'd hate to be forced to go back to something else because of this problem.

What should I do?

Try to move the problematic files out of your collection. What file type are they, btw?

They're almost all MP3s.

But I've tried removing them both physically and by simply not selecting them as part of my collection.  The problem is that there are so many that this simply isn't practical; it stalls out even if I add my collection one genre at a time.

As I said: it didn't do this with version 1.4.1.  What changed?

What should I do?

from investigation on IRC with a few other ppl who have had similar problems, although no solution was found other than to scan the collection in smaller batches, a couple of dirs at a time, this looks like it *might* be some kind of network/ntfs buffering problem.

Not sure why (or why it's suddenly showing up in 1.4.2), unless the collection scanner has suddenly become more greedy in terms of network bandwidth when actually scanning, and it definately requires further investigation.

Thanks so much, dangle.  All I was really hoping for is a confirmation of the problem and a "we're working on it".

I've tried adding it a directory at a time, and while I can get most of my collection online that way, it will still error out after I add my last directory and the scanner reaches 100%, but it will list mp3s in the error message that I had already added successfully in previously-added directories, as well as a few in the final directory added.

If that makes any sense whatsoever; that's some painful syntax.  Hehehe.

Weird, weird, weird, and very frustrating, as you can imagine.

A question:

Could switching from SQLite to MySQL possibly help the situation?

Just wanted to add that I have had the exact same problem with my samba mounted ntfs drive. I have also had the same result when trying to build my collection (same MP3s) from an ntfs formatted external usb (1.0) drive. Thanks for looking into this, it is, indeed, a massive pain.

Apparently the amarok patchset which was released recently should address some of these issues - it reverses an introduced problem where amarok collectionscanner would **** out after 2 errors, instead of continuing - the number of allowed errors has been increased back to 20 before a failure.
Check with your distro packages for a package update within the last week (since 1st Sept.) or try compiling yourself from svn. Instructions are on the amarok download page.

Hopefully that will help with some of these problems, or at least the early termination of the collection scanner.

Well, I've gotten all but about 10 percent of my collection online by adding it one directory at a time (excrutiatingly slowly).  That's as good as it's gonna get for me until something changes.

Thanks for the tips and the info, ya'll!

Here's to looking forward hopefully towards the next release. 

Hello everyone and thanks to the Amarok Team for this great piece of software!

After an upgrade to 1.4.2 under Arch Linux*, I encounter similar problems: The collection scan bails out, reporting too many errors. Running amarok under a terminal emulator, reveals this error (MySQL Backend):

Code: Select all

amarok:     [CollectionDB] MYSQL INSERT FAILED: Duplicate entry './apoikos/Music/New/Metal/Amorphis/Elegy [1996]/02 - Against Wid' for key 1
amarok: FAILED INSERT: INSERT INTO tags_temp ( url, dir, deviceid, createdate, modifydate, album, artist, composer, genre, year, title, comment, track, discnumber, bpm, sampler, length, bitrate, samplerate, filesize, filetype ) VALUES ('./apoikos/Music/New/Metal/Amorphis/Elegy [1996]/02 - Against Widows.mp3','./apoikos/Music/New/Metal/Amorphis/Elegy [1996]',4,1137949626,1137265947,104,1,1,5,'41','Against Widows','', 2 , 0 , 0 , NULL,245,192,44100,5896069,1)
amarok:     [CollectionDB] MYSQL INSERT FAILED: Duplicate entry './apoikos/Music/New/Metal/Amorphis/Elegy [1996]/02 - Against Wid' for key 1
amarok: FAILED INSERT: INSERT INTO embed_temp ( url, deviceid, hash, description ) VALUES ( './apoikos/Music/New/Metal/Amorphis/Elegy [1996]/02 - Against Widows.mp3', 4, '0460da25e9489b7c2987e89605c689a8', '' );

My collection is rougly 7000 files, residing on an ext3 partition (/home, ~2000 files) and an NFS share (~5000 files).

So far I have tried the following:

• Switching between the MySQL and the SQLite backend
• Deleting ~/.kde/share/conf/amarok*rc and ~/.kde/share/apps/amarok
• Restarting KDE, just in case there's something wrong with the Media Device Manager

From various experiments adding and removing directories, i've noticed the following:

• It's not NFS specific. I can add some directories from the NFS mount without a problem
• It's not backend specific, it occurs under MySQL as well as SQLite
• It's file-type independent: The error occurs for mp3 as well as FLAC and Ogg files
• It's file-count independent. I got combinations with 4200 files on the NFS share working, and others with 2000 bailing out.
• There don't seem to be any specific files trigerring this behaviour

I'm still working on it (though i'm afraid i will have a hard time hacking the code if needed) and I would be glad to assist anyone interested in fixing it with more feedback.

/edit: I get the impression that the quoted error is not the actual error. Everytime, before it starts dumping a list with all the files giving that error, it receives two RestartEvents without any sort of valuable information and then it starts giving out errors for all files. It seems it could be an irrelevant error misinterpreted by the collection scanner.

* The Arch Linux package has the recent patchset, so i actually count 20 restarts of the collection scanner before it bails out.

I think I got somewhere: It seems to me that if the collectionscanner crashes twice (because of two offending files for example), it resumes (MAX_RESTARTS is 20), but then something goes wrong with the database. Could it be a bug related with the Dynamic Collection perhaps?

Ahhh, where has this thread been my last week?!?

I've been looking for something like Amarok for a long time, my thanks.

My apologies if this is in the wrong thread. And at the length of this post.

So I didn't know this thread was about but here is an exert of my problem (seems a lot like everyone elses):

I use Ubuntu 6.06. I run kde on top for amarok because it seems to be more stable for me.

I mount the disk using:

How to mount/unmount network folders manually, and allow all users to read
Read #General Notes
Read #How to install Samba Server for files/folders sharing service
e.g. Assumed that network connections have been configured properly
Network computer's IP: 192.168.0.1
Network computer's Username: myusername
Network computer's Password: mypassword
Shared folder's name: linux
Local mount folder: /media/sharename
To mount network folder
sudo mkdir /media/sharename
sudo mount //192.168.0.1/linux /media/sharename/ -o username=myusername,password=mypassword

To unmount network folder
sudo umount /media/sharename/

source: http://ubuntuguide.org/wiki/Dapper#How_ ... rs_to_read

Okay so that works for me now but...
If I point Amarok to the collection Amarok doesn't seem to be able to build the database. I suspect there is just to many files there and it conks out. If I point it to a smaller subdirectory say one that only has 50 tracks it has no problems at all, works beautifully in fact (hence i'm so Amarok obsessed!). Any ideas anyone?

If I point it to build a collection off all the tracks it basically locks up. I then have to do a force terminate and the share dissapears (?!?). And I can't unmount it in the terminal because it says it's in use.

Network wise. I can stream music fine using rhythmbox in ubuntu, but it builds the database everytime and does have the same groovey functionality of Amarok. I've even streamed wirelessly, so I don't  believe it's my infrastructure problem. Would an earlier build perhaps help? Assuming, we/I can eventually get it working, do I have to enable the whole dynamic collection thing? It's one of the big reasons I like the idea of using Amarok.

My setup:

• Ubuntu 6.06 (latest) with kde kubuntu on top.
• Amarok 1.4.2
• NAS music (approx 7000 mp3 tracks) stored on a synology disk station 101j
• about 7000 songs

How is everyone else mounting their shares? Are we all using windows style ntfs? What's the difference between using MySQL and SQLite?

Cheers,
Chris

Well, 1.4.3 seems to have affected the problem, but not solved it.

Now the scanner still errors out, but it does so on different and a bit fewer files.

I really like the new look in the context menu, though!

I should have read this thread first. Whoops! I have the same problem here.

My db is MySQL on an ext3 partition but it seems to be limited to two files. I can remove them then scan them in later, but it sounds like it's a bug that's affecting several users.

Erm, upgrade to 1.4.3 then.