yesterday I clicked AlbumView, and it started the sequence you described. Only to hang on 6% adding albums to BDP. Had to restart to get my BDP back to respond to anything, restarted the Album building and it still hangs, and is not available to anything on the network. Finder, MPOD, Manic Moose, nothing loads. Have to reboot again i guess.
Could this have to do with a rather large library, and the fact BDP1 only has a limited amount of memory? Diskspace is in available in abundance...
M
Hi Marius,
Could be the number of files, but unlikely due to how the "database" and files are generated; however I will test it with the larger 38,000 song database at work as it seems to work with my database at home (4,000 songs) with my BDP-1. One thing I have noticed with the BDP-2 processing my work database is a few times on the second half it pauses for 15 or 20 seconds.
Perhaps if you ran the command manual after making some minor edits to the program, the BDP should be sharing its filesystem from the root as a share labeled "ROOT". open the file found at /var/www/mpd/albums.php; line 143 should be empty and will be just after
logDone('Sorting music into Bryston DB:'.round($songsDone/$songCount*100).'%<br>'.$file);
add
echo $file."\n";
on line 143 just below the logDone line
then go down to line 242 which i think is also empty and again should be just after a logDone call and add
echo $album."\n";
This should tell us where it crashes if its something in the database causing it, then hopefully we can fix.
Once done editing the file open two terminal windows and ssh into the BDP from both of them. In the first one run the "top" command, you'll use this to monitor resource usage while the albums.php program runs. in the other terminal window issue "php -f /var/www/albums.php" and your scree should fill up with output and display that last thing it was working on and how much of the memory was being used when it crashes.
Alternatively to all this you can place the BDP into service mode and i can take a look at.
Cheers,
Chris