Evening All,

I recently rebuilt my myth box with R5C7. Everything appears to be working for me except MythMusic. When I attempt to scan for music, The dialog box just seems to stop. Sometimes its 39%. Others its 18%. It even reached as far as 50%, but the end result is it locks up.

I decided to remote in and watch top and I saw the mythfrontend was running at 99.9%. At this point I can only restart the front end, gdm restart, and move on. After a subsequent try, I noticed that mythfrontend had 2 instance running, each at 49%.

I examined the system log and the myth backend logs to see if anything indicated any failure but I found none.

I thought this was related to the nfs mount where my music is stored. I have mounted a drive on my ubuntu pc in my office over a wireless network. My collection is around 30 GB and I did not want to replicate it on my myth box. As a test, I copied all of my music to an external usb harddrive. The same result; 39% and it just stops working.

Can anyone point me to any solution that may help me resolve this issue?

Thanks,

just a guess, but there maybe a file or directory name in your collection that the scan can't handle.

just a guess, but there may be a file or directory name in your collection that the scan can't handle.

Mac,
Thanks. The data on this drive was originally transfered from a winxp box. MusicMatch did use spaces in the directory paths. It will take some time but I will switch the spaces to underscores and then give it a shot.

Dan

Its not the spaces that are causing the problem. I have tons of them and it scans fine.
My guess is that there is something else in one of the names that killing it..

do a "find /mp3 | less" and look for unprintables. Where /mp3 is your music directory.

I am going through and looking now, but it will take some time for such a large collection. There were still some artifacts from my MusicMatch days, so I removed all of the album art and any desktop.ini files still around from window.

I am not sure why this would have worked prior to this. Previously, I was connecting to the same data over a samba share and it worked no problem. I don't see why moving it to a linux box would be such a problem.

One more thing. Is there any logging that I can enable to output where in the process my update might be failing?

Thanks,
Dan

that gives me an idea... since it was working over a samba mount -- why don't you copy
the mp3's over to mythtv box over a samba mount.

perhaps samba is doing some kind of file name translation on fly.

========= also maybe you could
attach a strace process to it after it gets hung up.. mabye you can see what it is munching on.

ie. "strace -p<pid>"

where is <pid> is the process id that you get from top.

======= also

look for clues with lsof

ie. "lsof -p <pid>"



to many companies ignore standards or use undocumented standards.

Mac,

Thanks alot for your help. As it turns out I ripped a cd with soundjuicer and the lame plugin and that caused my problem.

Your tip about lsof is what pointed me to the problem. The last entry in the list was the first track in that directory for the cd that I ripped. I didn't transfer the music to my myth box, I just left it on my nfs mount. lsof found the problem.

strace was not on my machine. Is that something I can get throught apt?

Prior to this post, I was unaware of those commands. Thanks for this too.

Dan