Londonist wrote: > Hello POMdev, I downloaded the lastest 'Main' version of your script and > copied onto my SBR. I copied the rcS.local. Example into etc/init.d and > substituted the existing rcS.local file. I've not made any other > changes. When I run the script I am getting the following error: > sh: 169: unknown operand > Have I missed a step? > > Even though something may not be quite right, the script is helping the > situation. When the network connection is dropped/blocked, the > connection is being recovered and the streaming resumes after 10 secs or > so. Problem is that the connection is dropping every 5 mins or so.
1/5 f/m x 60 m/h x 24 h/d = 288 failures / day, that's a lot, but not atypical. Your radio is suffering from your or your neighbor's new wifi protocols. See 'this user's post' (https://forums.slimdevices.com/showthread.php?97791-Squeezebox-Radio-keeps-losing-wireless-connection-and-won-t-reconnect-any-ideas&p=998939&viewfull=1#post998939) and 'his code' (https://github.com/castorfou/squeezebox_wlanpoke_plot) on GitHub to make your own graph. Regarding the 10 seconds to resume streaming, what is the source? What is it with a local "My Music" library? You may need to increase buffering (somehow) to make up for these breaks. With 4 synchronized (the worst case) radios here, there are occasional <1 (similar to turning a radio on) to 5 second pauses using Pandora or another web station, but not on the local library. In the last 2-3 days here, the seven radios here have logged the number of failed pings preceding a successful ping. There were 582395 successful pings that had no prior failures, and 3532 pings with one prior failure. (Ethernet connections have almost no failures.) However, wlanpoke detected and recovered from failures 455 times, with 78 times requiring a full reset. Fortunately for me, the environment here has improved a lot in the past few weeks, the earlier numbers were much higher, with clusters of failures a minute or so apart, followed by relative calm. Downloading the main (staging) branch (more recommended are the latest release or the development branch) and installing, the "sh: 169: unknown operand" error was not observed. I don't know what that '169' is: a line number, an operand? There is a variable test against '169' in the script ($IPFIRST == "169") to test for an unusable auto configuration address, but I don't see how '169' could become an operand, and line 169 of the script is a comment... So, to troubleshoot, how and when do you see this error? At launch? Periodically? What is the launch command line in local.rcS? Are you running a netcat (nc or ncat) tcp logging server? Any other info? ------------------------------------------------------------------------ POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
