the log output, as far as it went, looks perfectly ok to me - and as may be expected.
data should be being posted to wunderground - so not sure what you mean when you say data is not being posted! where is it not 'posting' to?? what do you mean when you say it is not being posted?? The log snippet was not long enough to see what happened at your next archive interval ie next posting occasion, and the snippet did not say what your archive interval was either as the snippet started too late in the startup sequence!!! On Tuesday, 15 May 2018 06:00:58 UTC+3, Mark Roberts wrote: > > you don't want to know! ha! ran the command to see the log and I think I > know why it's not posting. posting isn't enabled... > > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog > May 14 21:52:29 raspberrypi weewx[20789]: restx: StationRegistry: Station > will not be registered: no station_url specified. > May 14 21:52:29 raspberrypi weewx[20789]: restx: Wunderground-PWS: Data > for station KTXBEDFO19 will be posted > May 14 21:52:29 raspberrypi weewx[20789]: restx: PWSweather: Posting not > enabled. > May 14 21:52:29 raspberrypi weewx[20789]: restx: CWOP: Posting not enabled. > May 14 21:52:29 raspberrypi weewx[20789]: restx: WOW: Posting not enabled. > May 14 21:52:29 raspberrypi weewx[20789]: restx: AWEKAS: Posting not > enabled. > May 14 21:52:29 raspberrypi weewx[20789]: engine: Starting up weewx > version 3.8.0 > May 14 21:52:29 raspberrypi weewx[20789]: engine: Clock error is 2.05 > seconds (positive is fast) > May 14 21:52:30 raspberrypi weewx[20789]: engine: Starting main packet > loop. > May 14 21:57:56 raspberrypi weewx[20789]: vantage: LOOP try #1; error: > Expected to read 99 chars; got 85 instead > > > On Monday, May 14, 2018 at 9:56:03 PM UTC-5, Andrew Milner wrote: >> >> the user guide says >> sudo weewxd weewx.conf >> >> what error do you get? >> >> >> >> On Tuesday, 15 May 2018 05:50:23 UTC+3, Andrew Milner wrote: >>> >>> ok - so you have found the command line, and you have started the weewx >>> daemon >>> >>> there should be no more output to the screen from weewx when it is >>> running as a daemon. >>> >>> there will be entries in the log though. >>> >>> if you want to see weewx output on the screen >>> 1. stop weewx with sudo /etc/init.d/weewx stop >>> 2. run weewx from the command line >>> >>> >>> >>> On Tuesday, 15 May 2018 05:43:52 UTC+3, Mark Roberts wrote: >>>> >>>> I think you're right - I need some serious linux work. I thought maybe >>>>> this was a lot simpler than it is - was hoping for a "type this and it'll >>>>> run" kinda thing. LOL >>>>> >>>> >>>> this command >>>> >>>> sudo ls /usr/share/weewx >>>> >>>> got me a file listing of some daemon stuff and a bunch of weewx stuff. >>>> >>>> I guess that's good but I don't know what to do next. >>>> >>>> I ran this command (after reading the docs for the 50th time) >>>> >>>> sudo /etc/init.d/weewx start >>>> >>>> and it says "starting weewx service." >>>> >>>> doesn't seem like it's coming back online though. >>>> >>>> thanks everyone for all their help! >>>> >>> -- 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.
