Gary, On Thursday, January 18, 2018 at 5:43:29 AM UTC-6, gjr80 wrote: > > Keith, > > Hmm, that log is not very helpful. Like I said I know next to nothing of > Macs, though on thinking some more I thought I remember someone else have > issues obtaining logs on a Mac. Did some searching and I think this is the > thread > <https://groups.google.com/d/msg/weewx-user/Fv7sl2H5FfY/qlbkmM4_AQAJ>, > not very encouraging when you read the last post in the thread. The macOS > install instructions <http://weewx.com/docs/macos.htm> in the User's > Guide mentions '*Run the Console application and select All Messages*' to > view the log, I guess you went to this section to do your install so I > don't know if it will help. > > I ran Console / All Messages and it look pretty much the same as system.log
> Not to worry, let's work on weewx.conf. At the moment you have two copies > of gauge-data.txt being produced; one copy is produced during each report > cycle (ie every 5 minutes) by the weeWX SteelSeries Gauges skin and a > second copy is produced by the realtime gauge data (rtgd) extension. The > rtgd extensions produces a loop based gauge-data.txt every loop period. > No problems with both being there, as long as they are not trying to write > to the same location. Ultimately though, when we get the guages working > with one or the other you should (at the very least) disable the other or > uninstall it. > > I would like to try to work out where the two gauge-data.txt files are > being generated. I suspect the SteelSeries Gauges skin is placing > gauge-data.txt in /Users/keith/Sites/weewx/ > public_html/ss, if so this file would be being updated every 5 minutes. I > suspect that the rtgd extension should be placing gauge-data.txt in > /Users/keith/Sites/weewx/public_html and this file would be being updated > every 2 odd seconds. Can you confirm that these files are where I suspect > and that they are being updated as stated? The files will be similar but > have some differences as there are some fields in gauge-data.txt that the > SteelSeries Gauges skins does not provide but the rtgd extension does. > > Yes, your right on both locations. I was hoping to use both so as to have the standard on one web page and realtime on another. I've seen that on a couple to sites. Now as for as getting rtgd up and going. After getting the steel series running well then install rtgd as mentioned before. I set the realTimeUrlWeewx file (like you explained before) to ‘/ss/gauge-data.txt’ and that kills gauges. All gauges return to the ‘0’ position(fully CCW). > I tried ‘ss/gauge-data.txt’ and ‘../gauge-data.txt’ but the same results. >> If I leave it as ‘gauge-data.txt’ the file is updated in public_html. the >> data file in public_html/ss is up dated also but they appear different. I >> guess that because only the changed data in placed there. The gauges do >> update but instead of 2.5 sec. as I have set in realtiemInterval, it only >> updated ever 5 mins. >> > > In trying various realTimeUrlWeewx settings did you find one that > correctly displayed data on the gauges? If so what setting worked, I would > have expected 'gauge-data.txt' to work. > Yes, 'gauge-data.txt works just updates the gauges every 5 mins. I was looking at my Sites/logs/access.log where I have apache reporting and it was doing this... 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/index.html HTTP/1.1" 200 9749 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/css/gauges-ss.css HTTP/1.1" 200 15722 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/scripts/language.min.js HTTP/1.1" 200 79862 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/scripts/RGraph.rose.min.js HTTP/1.1" 200 21244 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/scripts/RGraph.common.core.min.js HTTP/1.1" 200 36577 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/scripts/steelseries_tween.min.js HTTP/1.1" 304 - 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/scripts/gauges.js HTTP/1.1" 304 - 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787619 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/dayinouttemp.png?1516281787763 HTTP/1.1" 200 4075 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/dayouttemphum.png?1516281787763 HTTP/1.1" 200 6395 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/dayrain.png?1516281787763 HTTP/1.1" 200 2623 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/dayrainrate.png?1516281787763 HTTP/1.1" 200 2444 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/dayinouthum.png?1516281787763 HTTP/1.1" 200 4265 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/daywind.png?1516281787763 HTTP/1.1" 200 5313 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/daywinddir.png?1516281787763 HTTP/1.1" 200 4477 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/daywindvec.png?1516281787763 HTTP/1.1" 200 5660 10.254.70.1 - - [18/Jan/2018:07:23:07 -0600] "GET /weewx/ss/daybarometer.png?1516281787763 HTTP/1.1" 200 4324 10.254.70.1 - - [18/Jan/2018:07:23:10 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787620 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:12 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787621 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:15 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787622 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:17 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787623 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:20 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787624 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:22 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787625 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:25 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787626 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:28 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787627 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:30 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787628 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:33 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787629 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:35 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787630 HTTP/1.1" 200 2319 10.254.70.1 - - [18/Jan/2018:07:23:38 -0600] "GET /weewx/ss/gauge-data.txt?_=1516281787631 HTTP/1.1" 200 2319 So various parts seem to be working. I checked the error.log for that time and saw no errors. I've looked at all of the suggested links the new logging system, still can't see weewx messages. Another thing to work on. Yes, Apple in their divine wisdom makes a lot of changes. As they did when the upgrade to Sierra came along, they had change the command to start processes. Say WHAT?? Took a while to dig that out. Thanks all, Keith -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
