Hi Ron,
Can you browse by anything else?
No, all of the browse-functionality is failing. Also via search nothing is found.
When you have that problem, does the server crash? Or is it still running?
The server doesn’t crash. It was running now for about 1 day and 10 hours.
Also, you can try going into the configuration editor and setting a log file. Maybe put it in the same directory as your mp3 files. Then stop and start hte server.
I did what you asked, although I am not sure on how to start it again.
First I ran another IE-session and the web interface showed up. But nothing happened. When I closed the session and tried to go to the web interface again I got a not found.
Then I started the server again via a telnet session and the “/opt/etc/init.d/S60mt-daapd” command as told in the Wiki. After some time I could enter the web-interface again which was telling that the server was running.
Below you find the information in the log-file, I just inserted some carriage
returns to make it more readable:
2006-12-05 11:39:10 (00000400): Stopping gracefully
2006-12-05 11:39:10 (00000400): Stopping rendezvous daemon
2006-12-05 11:39:10 (00000400): Closing database
2006-12-05 11:39:16 (00000400): Done!
2006-12-05 11:39:16 (00000400): Stopping signal handler
2006-12-05 11:39:16 (00000402): Got shutdown signal. Notifying daap server.
2006-12-05 11:42:08 (00000400): Firefly Version svn-1433: Starting with debuglevel 2
2006-12-05 11:42:09 (00000400): Starting rendezvous daemon
2006-12-05 11:42:09 (00000400): Starting signal handler
2006-12-05 11:42:09 (00000402): Signal handler started
2006-12-05 11:42:10 (00000400): Initializing database
2006-12-05 11:47:35 (00000400): Starting web server from /shares/mss-hdd/__opt/share/mt-daapd/admin-root on port 3689
2006-12-05 11:47:35 (00000400): Registering rendezvous names
2006-12-05 11:47:42 (00000400): Serving 23250 songs. Startup complete in 327 seconds
2006-12-05 11:47:42 (00000400): Rescanning database
2006-12-05 11:50:20 (00000c04): Thread 0: Entering ws_returnerror (401: Unauthorized)So it’s a authorisation issue, hopefully you know how to solve this.
All the browsing via the Roku is still not working.
Greetings,
Rick