bpa wrote: > @CameronD - Sorry if I wasn't clear. I assumed you'd reply to my post as > you had mentioned wireshark
Happy to give you captures (attached), but, since I can't make -any -version work, they all look the same. IP Addrs in my system are (last octet): - .40 : squeezebox - .203: new server (running V8.1) - .224: old server (running 7.8.1) There are 4 captures included: - -old server V7.8.1, short test- - -old server V7.8.1-, longer test including SB rebooting - -2-at-once- - capture on new server, but both LMS versions were running on separate PCs - -V81 - discovery-100ms-sleep- - new server only, code modified to insert 0.1 second delay before reply. I have smokeping running as well from the same VM as runs LMS 8.1, so you can see bursts of pings directed at the SB - if it is not in the middle of rebooting then it replies to all. There is one aspect that confused me for a while - pings unicast to the SB appearing on the old server - then I realised the ethernet line would be dropped during a reboot to the switch would be lost and just shoving the packets out every active port. > > My understanding is the SB1 used to work OK under 7.9.0 under Centos but > stopped working when you moved to Debian and a later version of LMS. Had > the Debian system new faster hardware compared to Centos ? I think it's unlikely, the old server is a Xeon E3, the new one an i5. CPU speed is not a lot different, although newer memory, and NVMe make bits of it faster. I only replaced the old one because I thought it had a motherboard fault. > > Since it was working with 7.9.0 - I think there is little to be gained > by trying older versions of LMS. That was as much about trying to use the oldest hardware I could find and trying to avoid OS and hardware compatibility issues. 7.8 was giving me all sorts of problems that I think were 32-bit vs 64-bit related. > > There are three areas where the fault may lie and the probelm may > involve all 3. > * the SB1 has a fault > * LMS post 7.9.0 SB1 startup is unreliable > * there is a network/firewall issue. > > Since yeomanspc and patja have some similar SB1 issues - it seems there > is a LMS part of the problem. If the issue that yeomanspc and patja see > can be eliminated then it may make resolving any other issues on your > system easier. > As networks and processors have got much faster since SB1 launch - > timing could well be the issue (e.g. is LMS too fast at replying and SB1 > isn't ready for reply). I think I disproved that with the inserted delay. > > A wireshark file of the exchange will show exactly what is happening > (timing and packets) in your failing system. If the packet are OK, then > we may be able to offer patches to code to change the timing to see if > it change the problem. > A log of SB1 exchange with LMS (e.g. 8.1) logging with > network.protocol.slimproto set to DEBUG is also useful. SB1 should be > ONLY player on network and SB1 should be powered up (i.e. unplug/plugin > main) as part of the test. This will show what LMS is doing. I could not get much diagnostic logging output at all. I tried following instructions for customLog. Other command line options imply they are on by default but then say "compiled out". +-------------------------------------------------------------------+ |Filename: SB2-captures.zip | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=32774| +-------------------------------------------------------------------+ ------------------------------------------------------------------------ CameronD's Profile: http://forums.slimdevices.com/member.php?userid=65245 View this thread: http://forums.slimdevices.com/showthread.php?t=113533 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
