Post edited 6:16 pm – July 23, 2010 by swinches1 Post edited 6:18 pm – July 23, 2010 by swinches1
Hello fellow VB forum members,
I would like to get your help with an issue I’ve had while restoring my music files back to my VB v1.4 system:
My system (VB v1.4) experiences a fatal crash while restoring music files from a previous VB v1.3 GUI backup residing on an external USB hard drive. The crash results in quite at lot of text (error log?) on the local VB screen however I am not able to capture it (not familiar with unix copy and paste). I can say that it mentions it killed a process called "mysqld" and there are several tables of information which I don’t understand. After crashing it no longer responds to text commands and the only way to reboot is to cycle the power on the VB machine. After restarting I get the typical login prompt but after about a minute it reports "squeezeserver is finally up…" but then shortly after results in the same screen of error text/log as during the original when copying files. The only way I have found to repair the system is to reinstall VB 1.4
After the system crashes neither the VB web GUI or the SB server are reachable and none of the VB network shares (i.e. vortexboxfiles… or vortexboxmovies, vortexboxmusic, or vortexboxpictures is available.
I have re-installed VB 1.4 (successfully) several times and tried performing the file restore; it always results in crash but never on the same file or length of time into the restore (random).
The source directory on my external USB drive is storagemusicmp3 and the destination directory on the VB system is \vortexboxfilesmusicmp3 (writable directory). I am attempting to restore 173 GB of files from my USB drive to the VB machines internal 320 GB hard drive.
I have tried two different methods to restore my files (both resulting in the same problem):
1) copying files from the external USB drive connected to networked PC over my wired network to the \vortexboxfilesmusicmp3 location
2) connecting the external USB drive directly to the VB machine and issuing the following commands locally (after logging in as "root" user):
mount /dev/sdb1 /backup
rsync -av /backup/storage/ /storage/
Hardware used;
VB 1.4 installed on a MSI Wind Nettop 100 with 2GB ram, 320 GB hard drive, DVD/RW drive
Networked PC running WinXP SP3
External 500GB USB 2.0 hard drive (contains backup from VB 1.3 web GUI)
Networked Squeezebox touch
Any help or suggestions would be greatly appreciated
I have not tried stopping squeezebox while restoring the files. I will try your suggestion and report back. In the mean time I have attached two screenshots I captured with a digital camera showing the error screen output. Hopefully it will help to diagnose the issue.
Still stuck with this issue . Tried stopping squeezebox server while copying but problem persists after restarting squeezebox server. Seems to be a problem with daap, mysql, or squeezebox server. It happens with both VB 1.3 or VB 1.4. Could it be my hardware??
Has anyone encountered these types of issues or have an idea of how to resolve it?
I have VB installed on a new MSI Wind Nettop 100 with 2GB ram and a 320 GB hard drive. If it is hardware related any idea on what I should be looking at/replacing first?
FYI – I have found that this problem presents itself after I have copying >200GB files onto the internal hard drive. Does VB 1.4 or mt-daap, mysqld, or squeezebox server have a limit to the amount of files they like to see in the /storage/music/mp3 folder?
Has anyone else run into this issue seen in the screenshot above?
Memory stick seems to be OK. I swapped it out with a new 2GB stick and had the same thing occur.
I also noticed that while copying files to the VB box uses 97% physical memory and 86% cached memory. The system grinds to a halt and then the software breaks (see screenshot in previous post). Again the VB is unreachable over the network and the system is down
Attached is a screenshot of the system information right before crashing:
Thank you for reviewing the system information and verifying it looks normal. I am still puzzled why squeezebox server is spontaneously shutting down and errors popping up from mysqld and mt-daap (see 1st screenshot above). I am also loosing the network access to the VB drive and web GUI when the mysqld/mt-daap/SBS errors appear. To date I have tried VB 1.3 and VB 1.4, swapped out the memory stick in the PC, swapped out the hard drive (320GB > 1TB) however all attempts result in the same problem once I copy files onto the VB harddrive (\vortexboxfilesmusicmp3) location.
If I leave the installation untouched without restoring the music files (i.e fresh install of VB 1.3 or VB 1.4) all is well however I don’t have access to my mp3’s via squeezebox server as they’re on an external drive.
Are there known issues with mysqld or mt-daap related to memory or the amount of files they can handle?
Are other VB users able to maintain large (>200GB) music folder directories without SBS shutting down? Hardware recommendations?
Thank you, now I can discount the idea that it has something to do with the size of the music library.
I can say after the system crashes and I initiate a shutdown from the front power button all the services shut properly accept for the daap server (and at times also the http and squeezebox server). Is there a way to re-install this service or repair it? Is there way to look at a server log file and see where the problem is and how do I find the log if it exists?
My unix knowledge is very limited, hopefully it's a simple fix.
Still trying to solve this crashing problem. Here are excerpts from my mt-daap.log and SB server.og at the time of the crash. Any help would be appreciated in troubleshooting this problem:
frame 19: Slim::Networking::IO::Select::__ANON__ (/usr/lib/perl5/vendor_perl/Slim/Networking/IO/Select.pm line 183) frame 20: (eval) (/usr/lib/perl5/vendor_perl/Slim/Networking/IO/Select.pm line 183) frame 21: Slim::Networking::IO::Select::loop (/usr/libexec/squeezeboxserver line 626) frame 22: main::idle (/usr/libexec/squeezeboxserver line 580) frame 23: main::main (/usr/libexec/squeezeboxserver line 1072)
[10-07-31 08:35:37.8973] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',…) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950 [10-07-31 08:35:37.9010] Slim::Schema::Storage::throw_exception (82) Backtrace:
frame 0: Slim::Utils::Log::logBacktrace (/usr/lib/perl5/vendor_perl/Slim/Schema/Storage.pm line 82) frame 1: Slim::Schema::Storage::throw_exception
.
.
Notice that SB could not connect to MySQL server and mt-daap reports that it crashed.
Total download size: 132 k Is this ok [y/N]: y Downloading Packages: mt-daapd-0.2.4.2-5.fc11.i586.rpm | 132 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test
Transaction Check Error: file /etc/mt-daapd.conf from install of mt-daapd-1:0.2.4.2-5.fc11.i586 conflicts with fi le from package vb-mt-daapd-1:0.2.4.2-1.i586 file /etc/rc.d/init.d/mt-daapd from install of mt-daapd-1:0.2.4.2-5.fc11.i586 conflicts with file from package vb-mt-daapd-1:0.2.4.2-1.i586 file /usr/sbin/mt-daapd from install of mt-daapd-1:0.2.4.2-5.fc11.i586 conflicts with fi le from package vb-mt-daapd-1:0.2.4.2-1.i586
Resolved. I was able to prevent the system from crashing by deleting all mt-daap related files including the PID file. Maybe not the most elegant solution but at least the system is stable now. Maybe something to keep an eye in future releases. Thank you all for the assistance.