pocki wrote:@dipidiplop: can you tell how you set up the log file to find the faulty mp3 file?
I'm not dipidiplop but I have been fighting to get the iTunes server working on my NAS again as well.
Here are the steps you need to take to get started:
And as always... Make sure you have a backup before you start. If you are not comfortable or something does not make sense to you; don't do it.
Nothing here should break anything.
From the admin screen select Application Servers > iTunes Server
Enable Server should be checked.
Check the "After enabling this service, click the following link to enter iTunes Web Server configuration page. " This will enable the iTunes admin web page.
Set the password you want to use. PLEASE NOTE: This password SHOULD not be the same password as you use for your NAS admin account. This password is NOT SECURE, it is stored and transmitted in plain text.
This will start the server. You might be able to get to the iTunes management page now. http://NAS.ip.Address:3689
If you are able to reach the iTunes/Firefly page do the following:
If you are not able to reach the Firefly page you will need to make the modifications to the config file manualy. That is beyond the scope of this posting. Some Google searchs for Firefly or mt-daapd should get you headed in the right direction.
Go to the configuration tab and then at the top of that page select "Show advanced config"
This will expand the window and show you the other options you need to set.
Set the location for your log file if not already set. should be /var/log/mt-daapd.log
You may want to set the "Truncate Logfile" to Yes. This will help you when you start looking at the log later as it will only have the events from that session.
Set the Debug Level - Level 9 is the most verbose and will show you the faulty file if that is what is stopping the iTunes server.
You may also want to make sure that your "Music Folder" is correct. This will need to be changed if you do not have your files in the default /share/Multimedia location.
Save the changes.
Now comes the fun part.
Now go back to the NAS admin screen select and select Application Servers > iTunes Server
Un-check "Enable iTunes Server"
Apply the change.
Now make sure that you have SSH enabled. You will need this to look at the logs. Go to Network Services Telnet/SSH Set the option to Allow SSH and enable SFTP.
Now reboot the NAS. You can do this from System Administration>Power Management and select the Reboot button.
The NAS will reboot.
Now you can use Putty or SCP to connect to the NAS via SSH. If you don't have them a quick search will lead you to them.
SSH into the NAS use admin and then the admin password.
from the command prompt enter: ps | grep mt-daapd
This will show you if mt-daapd (the iTunes/Firefly server is running)
It should not be running. If it is enter the following from the command line: mt-daapd stop
Now you need to start mt-daapd in the foreground so that you can see the errors or file that it is causing the problem.
from the command prompt enter: mt-daapd -d 9 -c /etc/mt-daapd.conf -f
Now you should see all the messages scrolling past...
You need to look for a error "segmentation fault"
If you see this; you have a file that mt-daapd does not like. Look at your log file, some lines above where the segmentation fault happened, you will see the last file that was processed. This should be the "bad" file. You should move or remove this file from the share.
You can/should use WinSCP for this if you are not comfortable using the shell.
If you are having problems finding the file in the log, you can pull the log file into a text editor to make things easy. the log file is in /var/log/mt-daapd.log if you configured as above.
After you have deleted the file that is causing mt-daapd to stop, you can restart mt-daapd again and see if it stops on another file or completes.
use "ctrl-c" to stop mt-daapd when it is running in the forground.
You should also look at your files for any non-media/music files such as .m3u or others. mt-daapd has problems with them if they are not formatted correctly. Another thing to look for is any file with an accent or non-standard character like "á, É, Ö, Ø to name a few. These characters can also cause problems with mt-daapd when in the meta-data or ID3 Tag.
If you don't want SSH/SFTP running; you should disable them after you complete.
Hope this helps...
Maybe QNap will move to another more reliable and feature rich iTunes server like forked-daapd that is still supported and does not have as many problems. Let's hope...