johnny66

Here are the files present: http://10.1.130.125>ls /log [/log *.*] A.LOG 32497 ERRORA.LOG 898755 ERRORC.LOG 1046585 ERRORB.LOG 1046645 http://10.1.130.125>

A few days ago I cleared the log file (Tools/Clear Log). I had never previously cleared the log and it was huge, with at least a year of events in it. But I could easily view it in Excel. Now when I attempt to view the log (Tools/Log), the admin console goes from "Ready" to "System Busy" for a second, but then nothing happens. So I'm unable to view the log. Also, it appears my charts are all empty now, whereas previously they displayed at least a year of events. I rebooted the ISY and cleared my Java cache but this didn't help. I'm running 3.2.6 on an ISY99i. I downgraded from 3.3.10 to 3.2.6 a few days ago. FWIW, Event Viewer still seems to work fine. Any suggestions? Thanks.

Michael, I downgraded to 3.2.6 but continue to observe the same behavior. Did you look at the packet capture? This is the data on the wire. To me, looking at the packet capture in Wireshark, it's readily apparent why the request from the ISY is failing: because the request contains an illegal un-encoded space. When a web browser requests a URL containing a space it replaces these with characters which represent or encode the space, "%20". But the ISY is failing to do that. The packet capture shows a PC making a request a minute after the ISY's failed request. The request from the PC is completely identical to the ISY's request except it doesn't contain a space, and it succeeds. As to the question of WHY my ISY is making this malformed request, that I don't know. The host and URI for Weatherbug aren't exposed in the ISY GUI, so there's no way for a user to modify them. But perhaps they're corrupted. Some references to spaces in URLs http://en.wikipedia.org/wiki/Query_string http://tools.ietf.org/html/rfc1738 http://stackoverflow.com/questions/5442 ... es-in-urls

Inspecting the packet capture of the Weatherbug request from the ISY (doesn't work) versus the PC (works), it appears that the request from the ISY is malformed. The request from the ISY has a space between the hostname (datafeed.weatherbug.com:80) and the URI (/GetXml.aspx?...). Most webservers disallow spaces and consider a request containing spaces to be malformed. So the Weatherbug webserver is unable to parse the request from the ISY. See attached packet capture which contains Weatherbug requests from both ISY (10.1.130.125) and PC (10.1.130.113). From ISY: http://datafeed.weatherbug.com:80 /GetXml.aspx?RequestType=3&PartnerId=3faff2bf-c622-41bd-9d46-f1a23cd089d0&StationId=LSNGL&UnitType=0 From PC: http://datafeed.weatherbug.com/GetXml.a ... UnitType=0 EDIT -- I just downgraded to 3.2.6 but unfortunately I'm observing the same behavior. Requests to Weatherbug still failing. 130527-0050_ISY-to-Internet_packetcapture.cap.txt

Thanks Michael for your suggestions. I power cycled the ISY and rebooted my router. But this doesn't appear to have helped, the ISY is still failing to retrieve Weatherbug data. I just noticed that the last date that Weatherbug worked for me, 5/12, was right before I upgraded from 3.2.6 to 3.3.10, 5/13. Previous to this Weathbug had been reliable for months. It looks like the misbehavior is associated with this upgrade. Perhaps I should revert back to 3.2.6? This misbehavior is a bit painful for us because we're running EZFlora units with 10 irrigation zones and the program I'm using relies on Weatherbug data.

I'm running 3.3.10 on an ISY99i. For the last two weeks Weatherbug hasn't been working for me. It repeatedly shows in the event viewer "No response from datafeed.weatherbug.com." Name resolution and NTP are working OK so internet access isn't the problem here. On my router I did a packet capture of the unit's Weatherbug data requests. See attached (change the txt file extension to cap). It's requesting URL: http://datafeed.weatherbug.com/GetXml.a ... UnitType=0 The packet capture shows that in response to the request the ISY only receives a SYN-ACK back from the server at datafeed.weatherbug.com, it doesn't receive data back from the Weatherbug server. The ISY then waits for a while, then makes the same request. Over and over again. It never receives data back. However, when I request the same URL in a browser on my PC, the request succeeds and returns the expected XML fully populated with the expected weather data. I've tried clearing my Java cache, choosing different nearby stations, rebooting the ISY, etc. This doesn't help, I observe the same behavior. What should I try next? 130526-1445_ISY-to-Internet_packetcapture.txt