FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › Connection failed to firefly-instance on Maxtor(please help)
- This topic has 20 replies, 4 voices, and was last updated 15 years, 9 months ago by RickV.
-
AuthorPosts
-
29/06/2008 at 2:21 PM #2533RickVParticipant
For a long time I only had minor problems but now I’m in trouble.
While browsing artists I did receive a browse-failure. In the past I could solve this by building the database again (deleting the songs.db)
After this rebuild I most of the times still got the browse-failure but sometimes not (I can’t think of a reason why…).Suddenly I realized that by deleting the songs.db the indexes had to be rebuild again. So I did the index-create (for the index on artist which I added in the past) while the server was running.
From that moment on I get an error connecting to the server. Also via explorer I can’t reach the mediaserver.Via putty I tried to start the server on the Maxtor MSS (as outlined in the wiki) but that either didn’t solve the problem.
Please can somebody help!
I use firefly svn-1344.01/07/2008 at 3:22 PM #17348RickVParticipantPlease, anyone an idea to solve this?
Offcourse I did a reset on the Roku but that doesn’t solve the problem either.
What can I do to listen to my music again?Is a new install the way to go? Can anybody tell me how to install a nightly, on the wiki about MSS install this is not mentioned.
Thanks in advance for answers
01/07/2008 at 4:14 PM #17349EVILRipperParticipantHave you tried stopping firefly, and restarting it? (As I could not conclude this from your post)
ps -aux | grep daap
Should give the process is running. If you only get the grep process, mt-daapd isn’t even running.
To check why firefly might not start you can check the logfile. (/var/log/mt-daapd.log?)
Also, if the log shows nothing or no clues, try raising the debuglevel up till 9 in your configfile (/etc/mt-daapd.conf?)
01/07/2008 at 7:02 PM #17350RickVParticipantHello EvilRipper,
Thank you for your response. I began to feel alone…
I’m not an expert but with a little help…As you asked I issued the ps-command which give the following output:
BusyBox v1.00-pre2 (2006.02.01-23:21+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.
# ps -aux | grep daap
265 root 140 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
266 root 160 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
269 root 160 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
270 root 160 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
291 root 160 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
24690 root 188 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
24693 root SW /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
26818 root 452 S grep daap
#From your comments I think mt-daapd is running, but is the number of lines correct, i can’t interpret them.
I can’t reach the web-interface, I don’t know how to stop the server in an other manner.
I have a second instance of firefly running and this instance is working although I get an browse failure when I browse artists. But if I search for a particular string in a song I can play those songs.
Before the problems started I did set the debug level to 9 (just before creating the index).
In the configfile I see the following lines:
always_scan = 0
logfile = /shares/mss-hdd/rick/music/rv240608.log
debuglevel = 9
truncate = 1
I did look before and then it seemed that nothing was written but now I see the following log-lines, hopefully you can give me further advise:
2008-07-01 11:41:35 (00000400): SocketDataReady got a packet from 192.168.2.100 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Query from 192.168.2.100 :5353 to 224.0.0.251 :5353 on 0x555E2158 with 2 Questions, 0 Answers, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): select(6, 1965632.281250)
2008-07-01 11:41:36 (00000400): SocketDataReady got a packet from 192.168.2.100 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Query from 192.168.2.100 :5353 to 224.0.0.251 :5353 on 0x555E2158 with 2 Questions, 0 Answers, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): select(6, 0.044921)
2008-07-01 11:41:36 (00000400): mDNS_Execute
2008-07-01 11:41:36 (00000400): select(6, 1965632.229492)
2008-07-01 11:41:36 (00000400): SocketDataReady got a packet from 192.168.2.47 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Response from 192.168.2.47 addressed to 224.0.0.251 on 555E2158 TTL 255 with 0 Questions, 2 Answers, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): select(6, 1965631.976562)
2008-07-01 11:41:36 (00000400): SocketDataReady got a packet from 192.168.2.100 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Query from 192.168.2.100 :5353 to 224.0.0.251 :5353 on 0x555E2158 with 2 Questions, 0 Answers, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): AddRecordToResponseList: (none).local. (Addr) already in list
2008-07-01 11:41:36 (00000400): Unicast Response: 0 Questions, 1 Answer, 0 Additionals to 192.168.2.100 :5353 on 555E2158/4
2008-07-01 11:41:36 (00000400): mDNS_Execute
2008-07-01 11:41:36 (00000400): SendResponses: Sending 0 Deregistrations, 0 Announcements, 1 Answer, 0 Additionals on 555E2158
2008-07-01 11:41:36 (00000400): SendResponses: Next in 2013265920 ticks
2008-07-01 11:41:36 (00000400): select(6, 0.097656)
2008-07-01 11:41:36 (00000400): SocketDataReady got a packet from 192.168.2.47 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Response from 192.168.2.47 addressed to 224.0.0.251 on 555E2158 TTL 255 with 0 Questions, 1 Answer, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): select(6, 0.042968)
2008-07-01 11:41:36 (00000400): SocketDataReady got a packet from 192.168.2.47 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Response from 192.168.2.47 addressed to 224.0.0.251 on 555E2158 TTL 255 with 0 Questions, 1 Answer, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): select(6, 0.041015)
2008-07-01 11:41:36 (00000400): SocketDataReady got a packet from 192.168.2.47 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:36 (00000400): Received Response from 192.168.2.47 addressed to 224.0.0.251 on 555E2158 TTL 255 with 0 Questions, 1 Answer, 0 Authorities, 0 Additionals
2008-07-01 11:41:36 (00000400): select(6, 0.037109)
2008-07-01 11:41:36 (00000400): select(6, 0.002929)
2008-07-01 11:41:36 (00000400): mDNS_Execute
2008-07-01 11:41:36 (00000400): select(6, 1965631.859375)
2008-07-01 11:41:37 (00000400): SocketDataReady got a packet from 192.168.2.47 to 224.0.0.251 on interface 192.168.2.47/eth0/2
2008-07-01 11:41:37 (00000400): Received Response from 192.168.2.47 addressed to 224.0.0.251 on 555E2158 TTL 255 with 0 Questions, 1 Answer, 0 Authorities, 0 Additionals
2008-07-01 11:41:37 (00000400): select(6, 1965631.001953)
2008-07-01 11:42:17 (00000400): Rows: 0
2008-07-01 11:42:17 (00000400): Executing: create index idx_path on songs(path,idx)
2008-07-01 11:42:18 (00000400): Query: create index idx_path on songs(path,idx)
2008-07-01 11:42:18 (00000400): Error: index idx_path already exists
2008-07-01 11:42:18 (00000400): Executing: create index idx_songid on playlistitems(songid)
2008-07-01 11:42:18 (00000400): Query: create index idx_songid on playlistitems(songid)
2008-07-01 11:42:18 (00000400): Error: index idx_songid already exists
2008-07-01 11:42:18 (00000400): Executing: create index idx_playlistid on playlistitems(playlistid,songid)
2008-07-01 11:42:18 (00000400): Query: create index idx_playlistid on playlistitems(playlistid,songid)
2008-07-01 11:42:18 (00000400): Error: index idx_playlistid already exists
2008-07-01 11:42:18 (00000400): Starting web server from /shares/mss-hdd/__opt/share/mt-daapd/admin-root on port 3689
2008-07-01 11:42:19 (00000400): Listening on port 3689
2008-07-01 11:42:19 (00000400): Listen port: Address already in use
2008-07-01 11:42:19 (00000400): Error staring web server: Address already in use
2008-07-01 11:42:19: Aborting
2008-07-01 11:42:19 (00000400): Processing rendezvous message
2008-07-01 11:42:19 (00000400): Rendezvous socket closed (daap server crashed?) Aborting.
2008-07-01 11:42:19: Aborting
02/07/2008 at 11:14 AM #17351EVILRipperParticipant2008-07-01 11:42:19 (00000400): Listening on port 3689
2008-07-01 11:42:19 (00000400): Listen port: Address already in use
2008-07-01 11:42:19 (00000400): Error staring web server: Address already in use
These lines from the config (last few lines) are the ones that could give you an idea.
First off when firefly starts, it (re)scans all the music. After that, it tries to start the webserver on port 3689.
However, when trying to ‘acquire’ port 3689, it sees it is already in use by something else, so it closes.This usually means mt-daapd is already running. However, you can say you can’t reach it.
Also, from the ps -aux command, it indeed seems mt-daapd is already running.
Kill the current running processes:kill 265
kill 266
kill 269
etc.Do another ps -aux | grep daap to check if no other mt-daapd processes are running (except the grep ofcourse).
Restart the server.
Then, if it still doesn’t work, post the log file from debuglevel 9.03/07/2008 at 5:18 PM #17352RickVParticipantAt first I thought the killing and restarting did solve the problem. I could access the web-interface again.
But then I closed the internet explorer. When I did start the internet explorer again I again couldn’t access the web-interface.
Looking at the processes a day later there were more daap processes then before. I started to kill them but when I check if they were killed I found 3 processes which weren’t killed. Killing again doesn’t show an error but the ps-commands show them again.
# ps -aux|grep daap
253 root 428 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
259 root 428 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
281 root 428 S /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-da
430 root 452 S grep daap
In the log-file the same errors are shown. “Error staring web server: Adress already in use”.
03/07/2008 at 5:44 PM #17353AnonymousInactiveDumb question, but have you tried just bouncing the host?
03/07/2008 at 6:47 PM #17354RickVParticipantPlease can you tell me what you mean with “bouncing the host”?
03/07/2008 at 8:38 PM #17355AnonymousInactive>Please can you tell me what you mean with “bouncing the host”?
Bounce as in power DOWN the Maxtor and then power back UP.
04/07/2008 at 7:10 AM #17356EVILRipperParticipantAKA
shutdown -r now
🙂
However, as you say, firefly ‘created’ new processes during the day.
I really have no idea why or how, as my firefly uses 1 process. It has never used more than 1 before. -
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.