4th November 2005 at 7:37 pm #121
after a while, the web-admin interface (the status page) loses contact with the back-end …
I was playing music for over 3 hours, when I looked at the status page, it told me it was not streaming music …5th November 2005 at 1:08 am #3778
Three hours? That’s making it difficult to reproduce 😉
Well, for one thing, the status page will get an overhaul anyway… but: are you sure that’s not a browser thing? Did the page actually continue to reload every 10 seconds, or did it maybe just stop earlier?5th November 2005 at 1:25 am #3779
Yes, I am sure. The page continues to reload fine, the clock is updating …
But, the connected client which is listening to a stream is not always displayed … After a while it disappears.
I know this is difficult to reproduce, especially since not many people use OSX 10.4.3 Server edition on an xServe dual G4 @ 1.33 GHz …
If I detect some in the debug logging I’ll let you know …
BTW, isn’t it a good Idea to open a forum dedicated to (beta)testing and building ?
Eddie5th November 2005 at 8:35 am #3780
does it still *work*?
Or does all of mt-daapd stop working?5th November 2005 at 2:03 pm #3781
Ron, it does not stop streaming or advertising to iTunes …5th November 2005 at 10:16 pm #3782
You were also reporting the hangs, right? Were you in the web interface at that time?
Maybe the deadlock is in the web side, not the db side.
Interesting. You also said you were running a dual-cpu box, right? If it’s a deadlock problem, that might make it show up quicker.
I have a g4 dual — I’ll set that up as a test box and pound it over the weekend and see if I can see where it’s coming from.
— Ron5th November 2005 at 11:04 pm #3783
indeed, the xServe is a dual G4 @1.33GHz …
It is streaming for over 5 hours to my stereo right now.
The only problem today is the web interface not telling wich song it is streaming …
The forum ‘Nightlies Feedback’ is closed to new topics and replies.