[weewx-user] Re: One month later another serious Weewx upload failure

2021-04-23 Thread Peter Dougherty
Sorry, I hit send before completing the post

After stopping the service again, and invoking the wee_device --dump and  
wee_device --clear-memory commands, and then restarting weewx, it started 
working again. Both CWOP And WU are getting data. And while that's great, 
it's hinting at a reliability problem that had never existed until last 
month. Is there anything I can do to solve this permanently and get it back 
to the way it always was?

Conversely, is there any sort of black-box device or  that I can 
use to just send this info out without needing to play with Linux? I don't 
want to replace the weather station; the hardware outside is fine, but the 
the convoluted way it reports to WU and CWOP are a headache I don't want, 
especially if it's turning into a monthly circus.

On Friday, April 23, 2021 at 11:24:24 PM UTC-4 Peter Dougherty wrote:

> Last month (Mar. 22) I was experiencing upload problems to CWOP. Today a 
> similar (worse) problem. Nothing was done to the Pi since the end of last 
> month's troubles. It just stopped uploading to both CWOP and WU about an 
> hour ago.
>
> I've tried unplugging the console, restarting the process, restarting the 
> pi and nothing is working. Again. This ran for years without corruption and 
> now twice in a month. What can I do to get it working again, and how on 
> Earth can I get this back to be the reliable device it was for almost four 
> years in a row? Linux is massively out of my comfort zone.
>
> The relevant part of my config file and the last few lines of my log 
> follow:
>
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 Tom Keffer 
> # See the file LICENSE.txt for your rights.
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 1
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 3.6.2
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
> 
> # Description of the station location
> location = "West Caldwell, NJ"
> 
> # Latitude and longitude in decimal degrees
> latitude = 40.8615
> longitude = -74.2775
> 
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 261, foot
> 
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file with a 'driver' parameter indicating the driver to be 
> used.
> station_type = Vantage
> 
> # If you have a website, you may specify an URL
> #station_url = http://www.example.com
> 
> # The start of the rain year (1=January; 10=October, etc.). This is
> # downloaded from the station if the hardware supports it.
> rain_year_start = 1
> 
> # Start of week (0=Monday, 6=Sunday)
> week_start = 6
>
>
> ##
>
> [Vantage]
> type = serial
> port = /dev/ttyUSB0
> driver = weewx.drivers.vantage
> 
> 
> # The time (in seconds) between LOOP packets.
> loop_interval = 2.5
>
>
>
> ##
>
> #   This section is for uploading data to Internet sites
>
> [StdRESTful]
> 
> [[StationRegistry]]
> # To register this weather station with weewx, set this to true
> register_this_station = true
> 
> [[AWEKAS]]
> # This section is for configuring posts to AWEKAS.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a username and password.
> enable = false
> username = replace_me
> password = replace_me
> 
> 
> [[CWOP]]
> # This section is for configuring posts to CWOP.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify the station ID (e.g., CW1234).
> enable = true
> station = W2IRT
> post_interval = 300
> log_success = True
> log_failure = True
> server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, 
> cwop.aprs.net:14580, swop.aprs.net:23
>  

[weewx-user] One month later another serious Weewx upload failure

2021-04-23 Thread Peter Dougherty
Last month (Mar. 22) I was experiencing upload problems to CWOP. Today a 
similar (worse) problem. Nothing was done to the Pi since the end of last 
month's troubles. It just stopped uploading to both CWOP and WU about an 
hour ago.

I've tried unplugging the console, restarting the process, restarting the 
pi and nothing is working. Again. This ran for years without corruption and 
now twice in a month. What can I do to get it working again, and how on 
Earth can I get this back to be the reliable device it was for almost four 
years in a row? Linux is massively out of my comfort zone.

The relevant part of my config file and the last few lines of my log follow:

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.6.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "West Caldwell, NJ"

# Latitude and longitude in decimal degrees
latitude = 40.8615
longitude = -74.2775

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 261, foot

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
station_type = Vantage

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Vantage]
type = serial
port = /dev/ttyUSB0
driver = weewx.drivers.vantage


# The time (in seconds) between LOOP packets.
loop_interval = 2.5


##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
enable = false
username = replace_me
password = replace_me


[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = W2IRT
post_interval = 300
log_success = True
log_failure = True
server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, 
cwop.aprs.net:14580, swop.aprs.net:23

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
passcode = [removed by me]


[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = true
station = w2irt
password = [removed for privacy]

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = false
station = replace_me
password = replace_me

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
enable = true
station = KNJWESTC2
password = [removed for privacy]

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = True

#[[Twitter]]
#oauth_token_secret = OAUTH_TOKEN_SECRET
#oauth_token = OAUTH_TOKEN
#app_key_secret = APP_KEY_SECRET
#app_key = APP_KEY




LOG 

RE: [weewx-user] Not uploading to CWOP - still not working

2021-03-22 Thread Peter Dougherty
Yes! So far so good!

 

- pjd

 

From: weewx-user@googlegroups.com  On Behalf Of 
John Kline
Sent: Monday, March 22, 2021 10:57 PM
To: weewx-user@googlegroups.com
Subject: Re: [weewx-user] Not uploading to CWOP - still not working

 

It looks like every 5 minutes to me, no?

http://www.findu.com/cgi-bin/raw.cgi?call=W2IRT

 

 





On Mar 22, 2021, at 7:03 PM, Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:



Sorry to be so daft, but I honestly could not understand this. I’m a 
“set-it-and-forget-it” user so I’m not up on all the terminology, I’m afraid. I 
last did anything of consequence to this RPi in 2019, and it was built by a 
Linux-competent friend in 2017. 

I did tell the weewx config file to upload to CWOP every 300 seconds, but it 
only seems to show up every 600s (10 minutes) instead.

 

- pjd

 

From: weewx-user@googlegroups.com <mailto:weewx-user@googlegroups.com>  
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Tom Keffer
Sent: Monday, March 22, 2021 9:57 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Not uploading to CWOP - still not working

 

It should have put the data right in your database. You should be able to tell 
by looking at the image plots.

 

Mind you: they are refreshed only as often as the aggregation interval. If you 
want to see them right away, delete them and they will be automatically 
regenerated in the next reporting cycle.

 

-tk

 

On Mon, Mar 22, 2021 at 6:54 PM Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:

I did use the - -  dump command. But (a) I don’t know where it put the data, 
(b) how to recover it, or (c) does it need to even be recovered now?

 

- pjd

 

From: weewx-user@googlegroups.com <mailto:weewx-user@googlegroups.com>  
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Tom Keffer
Sent: Monday, March 22, 2021 9:30 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Not uploading to CWOP - still not working

 

If you did the "wee_device --dump" command as suggested by the Wiki, you should 
have recovered all the data off the logger.

 

If not, you can use wee_import 
<http://www.weewx.com/docs/utilities.htm#wee_import_utility>  to recover from 
the Weather Underground.

 

-- 
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 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/062f01d71f87%2475641be0%24602c53a0%24%40gmail.com
 
<https://groups.google.com/d/msgid/weewx-user/062f01d71f87%2475641be0%24602c53a0%24%40gmail.com?utm_medium=email_source=footer>
 .

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/h0AhMSztDvI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEC1-FaM%3D04BFBiNvZaxDO_HsZTyggCaMt-96_VAUfA9cQ%40mail.gmail.com
 
<https://groups.google.com/d/msgid/weewx-user/CAPq0zEC1-FaM%3D04BFBiNvZaxDO_HsZTyggCaMt-96_VAUfA9cQ%40mail.gmail.com?utm_medium=email_source=footer>
 .

-- 
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 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/064401d71f88%24c678ae50%24536a0af0%24%40gmail.com
 
<https://groups.google.com/d/msgid/weewx-user/064401d71f88%24c678ae50%24536a0af0%24%40gmail.com?utm_medium=email_source=footer>
 .

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/h0AhMSztDvI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9F506130-A298-4627-9FFE-CA831FAA1C7F%40johnkline.com
 
<https://groups.google.com/d/msgid/weewx-user/9F506130-A298-4627-9FFE-CA831FAA1C7F%40johnkline.com?utm_medium=email_source=footer>
 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubsc

RE: [weewx-user] Not uploading to CWOP - still not working

2021-03-22 Thread Peter Dougherty
Sorry to be so daft, but I honestly could not understand this. I’m a 
“set-it-and-forget-it” user so I’m not up on all the terminology, I’m afraid. I 
last did anything of consequence to this RPi in 2019, and it was built by a 
Linux-competent friend in 2017. 

I did tell the weewx config file to upload to CWOP every 300 seconds, but it 
only seems to show up every 600s (10 minutes) instead.

 

- pjd

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Monday, March 22, 2021 9:57 PM
To: weewx-user 
Subject: Re: [weewx-user] Not uploading to CWOP - still not working

 

It should have put the data right in your database. You should be able to tell 
by looking at the image plots.

 

Mind you: they are refreshed only as often as the aggregation interval. If you 
want to see them right away, delete them and they will be automatically 
regenerated in the next reporting cycle.

 

-tk

 

On Mon, Mar 22, 2021 at 6:54 PM Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:

I did use the - -  dump command. But (a) I don’t know where it put the data, 
(b) how to recover it, or (c) does it need to even be recovered now?

 

- pjd

 

From: weewx-user@googlegroups.com <mailto:weewx-user@googlegroups.com>  
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Tom Keffer
Sent: Monday, March 22, 2021 9:30 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Not uploading to CWOP - still not working

 

If you did the "wee_device --dump" command as suggested by the Wiki, you should 
have recovered all the data off the logger.

 

If not, you can use wee_import 
<http://www.weewx.com/docs/utilities.htm#wee_import_utility>  to recover from 
the Weather Underground.

 

-- 
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 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/062f01d71f87%2475641be0%24602c53a0%24%40gmail.com
 
<https://groups.google.com/d/msgid/weewx-user/062f01d71f87%2475641be0%24602c53a0%24%40gmail.com?utm_medium=email_source=footer>
 .

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/h0AhMSztDvI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEC1-FaM%3D04BFBiNvZaxDO_HsZTyggCaMt-96_VAUfA9cQ%40mail.gmail.com
 
<https://groups.google.com/d/msgid/weewx-user/CAPq0zEC1-FaM%3D04BFBiNvZaxDO_HsZTyggCaMt-96_VAUfA9cQ%40mail.gmail.com?utm_medium=email_source=footer>
 .

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/064401d71f88%24c678ae50%24536a0af0%24%40gmail.com.


RE: [weewx-user] Not uploading to CWOP - still not working

2021-03-22 Thread Peter Dougherty
I did use the - -  dump command. But (a) I don’t know where it put the data, 
(b) how to recover it, or (c) does it need to even be recovered now?

 

- pjd

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Monday, March 22, 2021 9:30 PM
To: weewx-user 
Subject: Re: [weewx-user] Not uploading to CWOP - still not working

 

If you did the "wee_device --dump" command as suggested by the Wiki, you should 
have recovered all the data off the logger.

 

If not, you can use wee_import 
  to recover from 
the Weather Underground.

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/062f01d71f87%2475641be0%24602c53a0%24%40gmail.com.


RE: [weewx-user] Not uploading to CWOP (Long log file attached)

2021-03-22 Thread Peter Dougherty
So…a tiny bit of progress (maybe??)

I stopped the Vantage console for a few minutes and pulled out the batteries. 
Restarted it, then unplugged the RPi and reconnected it. It seems to have 
started adding the missing data and I’m seeing “restx” messages again, but 
after 10 minutes, nothing seems to actually have gotten posted to CWOP.

So I stopped Weewx and restarted it again, a few seconds before the 19:35EDT 
update time. Nothing seems to have gotten posted to CWOP, however; I have 
refreshed the page numerous times since.

Once again, there are no restx messages being displayed. Log follows:

Mar 22 19:12:01 wx weewx[3062]: vantage: LOOP try #1; error: Expected to read 
99 chars; got 0 instead
Mar 22 19:12:01 wx weewx[3062]: vantage: Requesting 200 LOOP packets.
Mar 22 19:12:05 wx weewx[3062]: vantage: retry  #0 failed
Mar 22 19:12:09 wx weewx[3062]: vantage: retry  #1 failed
Mar 22 19:12:13 wx weewx[3062]: vantage: retry  #2 failed
Mar 22 19:12:17 wx weewx[3062]: vantage: retry  #3 failed
Mar 22 19:12:17 wx weewx[3062]: vantage: Unable to wake up console
Mar 22 19:12:17 wx weewx[3062]: vantage: LOOP try #2; error: Unable to wake up 
Vantage console
Mar 22 19:12:17 wx weewx[3062]: vantage: Requesting 200 LOOP packets.
Mar 22 19:12:21 wx weewx[3062]: vantage: retry  #0 failed
Mar 22 19:12:25 wx weewx[3062]: vantage: retry  #1 failed
Mar 22 19:12:29 wx weewx[3062]: vantage: retry  #2 failed
Mar 22 19:12:33 wx weewx[3062]: vantage: retry  #3 failed
Mar 22 19:12:33 wx weewx[3062]: vantage: Unable to wake up console
Mar 22 19:12:33 wx weewx[3062]: vantage: LOOP try #3; error: Unable to wake up 
Vantage console
Mar 22 19:12:33 wx weewx[3062]: vantage: Requesting 200 LOOP packets.
Mar 22 19:12:37 wx weewx[3062]: vantage: retry  #0 failed
Mar 22 19:12:41 wx weewx[3062]: vantage: retry  #1 failed
Mar 22 19:12:45 wx weewx[3062]: vantage: retry  #2 failed
Mar 22 19:12:49 wx weewx[3062]: vantage: retry  #3 failed
Mar 22 19:12:49 wx weewx[3062]: vantage: Unable to wake up console
Mar 22 19:12:49 wx weewx[3062]: vantage: LOOP try #4; error: Unable to wake up 
Vantage console
Mar 22 19:12:49 wx weewx[3062]: vantage: LOOP max tries (4) exceeded.
Mar 22 19:12:49 wx weewx[3062]: engine: Main loop exiting. Shutting engine down.
Mar 22 19:12:49 wx weewx[3062]: engine: Shutting down StdReport thread
Mar 22 19:12:49 wx weewx[3062]: engine: StdReport thread has been terminated
Mar 22 19:12:49 wx weewx[3062]: restx: Shut down CWOP thread.
Mar 22 19:12:49 wx weewx[3062]: restx: Shut down PWSWeather thread.
Mar 22 19:12:49 wx weewx[3062]: restx: Shut down Wunderground-RF thread.
Mar 22 19:12:49 wx weewx[3062]: engine: Caught WeeWxIOError: Max tries exceeded 
while getting LOOP data.
Mar 22 19:12:49 wx weewx[3062]:   Waiting 60 seconds then retrying...
Mar 22 19:13:49 wx weewx[3062]: engine: retrying...
Mar 22 19:13:49 wx weewx[3062]: engine: Using configuration file 
/etc/weewx/weewx.conf
Mar 22 19:13:49 wx weewx[3062]: engine: Initializing engine
Mar 22 19:13:49 wx weewx[3062]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 22 19:13:49 wx weewx[3062]: vantage: driver version is 3.0.9
Mar 22 19:13:49 wx weewx[3062]: vantage: Opened up serial port /dev/ttyUSB0; 
baud 19200; timeout 4.00
Mar 22 19:13:53 wx weewx[3062]: vantage: retry  #0 failed
Mar 22 19:13:57 wx weewx[3062]: vantage: retry  #1 failed
Mar 22 19:14:01 wx weewx[3062]: vantage: retry  #2 failed
Mar 22 19:14:05 wx weewx[3062]: vantage: retry  #3 failed
Mar 22 19:14:05 wx weewx[3062]: vantage: Unable to wake up console
Mar 22 19:14:05 wx weewx[3062]: import of driver failed: Unable to wake up 
Vantage console ()
Mar 22 19:14:05 wx weewx[3062]: engine: Unable to load driver: Unable to wake 
up Vantage console
Mar 22 19:14:05 wx weewx[3062]:   Exiting...
Mar 22 19:17:13 wx weewx[575]: Starting weewx weather system: weewxerror: 
unexpectedly disconnected from boot status daemon
Mar 22 19:17:16 wx weewx[784]: engine: Initializing weewx version 3.6.2
Mar 22 19:17:16 wx weewx[784]: engine: Using Python 2.7.9 (default, Sep 16 
2019, 18:29:54) #012[GCC 4.9.2]
Mar 22 19:17:16 wx weewx[784]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Mar 22 19:17:16 wx weewx[784]: engine: pid file is /var/run/weewx.pid
Mar 22 19:17:16 wx weewx[1053]: engine: Using configuration file 
/etc/weewx/weewx.conf
Mar 22 19:17:16 wx weewx[1053]: engine: Initializing engine
Mar 22 19:17:16 wx weewx[1053]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 22 19:17:16 wx weewx[575]: .
Mar 22 19:17:16 wx weewx[1053]: vantage: driver version is 3.0.9
Mar 22 19:17:16 wx weewx[1053]: vantage: Opened up serial port /dev/ttyUSB0; 
baud 19200; timeout 4.00
Mar 22 19:17:16 wx weewx[1053]: vantage: gentle wake up of console successful
Mar 22 19:17:16 wx weewx[1053]: vantage: _setup; hardware type is 16
Mar 22 19:17:16 wx weewx[1053]: engine: Loading service 
weewx.engine.StdTimeSynch
Mar 22 19:17:16 wx weewx[1053]: engine: Finished loading service 

RE: [weewx-user] Not uploading to CWOP (continued from previous post)

2021-03-22 Thread Peter Dougherty
I will de-power the Vantage for 5 minutes and see what happens, and reboot the 
Raspberry Pi once the Vantage console is back on line.

 

- pjd

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Monday, March 22, 2021 7:08 PM
To: weewx-user 
Subject: Re: [weewx-user] Not uploading to CWOP (continued from previous post)

 

As suspected (and as I guessed in your original thread), you are using 
RapidFire. It uses LOOP packets, and so will be unaffected by a corrupt logger.

 

Again, as noted in the other thread, clear the logger 
<https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>
  and all will be well.

 

-tk

 

 

On Mon, Mar 22, 2021 at 4:05 PM Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:

OK, now that is bizarre. Why would it just suddenly disappear, I wonder? I will 
post over there but there’s gotta be more involved.

The end goal is to have the data not just posted to CWOP itself, but also 
disseminated to the APRS network.

 

- pjd

 

From: weewx-user@googlegroups.com <mailto:weewx-user@googlegroups.com>  
mailto:weewx-user@googlegroups.com> > On Behalf 
Of John Kline
Sent: Monday, March 22, 2021 7:01 PM
To: weewx-user@googlegroups.com <mailto:weewx-user@googlegroups.com> 
Subject: Re: [weewx-user] Not uploading to CWOP (continued from previous post)

 

I don’t see W2IRT listed here:

http://www.wxqa.com/members.txt

 

I’m not sure; but perhaps it is no longer registered?  A better place to ask 
that question (is it registered), is here:

https://www.wxforum.net/index.php?board=15.0

 

 

On Mar 22, 2021, at 3:38 PM, Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:

It occurred to me that you might also need to see the log from process start, 
so I stopped the service and restarted it, and have pasted the relevant portion 
of the log below. This is from within 3 minutes of my typing out this post.

 

Mar 22 18:34:16 wx weewx[2460]: engine: Received signal TERM.

Mar 22 18:34:16 wx weewx[2460]: engine: Main loop exiting. Shutting engine down.

Mar 22 18:34:16 wx weewx[2460]: engine: Shutting down StdReport thread

Mar 22 18:34:16 wx weewx[2460]: engine: StdReport thread has been terminated

Mar 22 18:34:16 wx weewx[2460]: restx: Shut down CWOP thread.

Mar 22 18:34:16 wx weewx[2460]: restx: Shut down PWSWeather thread.

Mar 22 18:34:16 wx weewx[2460]: restx: Shut down Wunderground-RF thread.

Mar 22 18:34:16 wx weewx[2460]: engine: Terminating weewx version 3.6.2

Mar 22 18:34:22 wx weewx[2980]: Stopping weewx weather system: weewx..

Mar 22 18:35:06 wx weewx[3058]: engine: Initializing weewx version 3.6.2

Mar 22 18:35:06 wx weewx[3058]: engine: Using Python 2.7.9 (default, Sep 16 
2019, 18:29:54) #012[GCC 4.9.2]

Mar 22 18:35:06 wx weewx[3058]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0

Mar 22 18:35:06 wx weewx[3058]: engine: pid file is /var/run/weewx.pid

Mar 22 18:35:06 wx weewx[3048]: Starting weewx weather system: weewx.

Mar 22 18:35:06 wx weewx[3062]: engine: Using configuration file 
/etc/weewx/weewx.conf

Mar 22 18:35:06 wx weewx[3062]: engine: Initializing engine

Mar 22 18:35:06 wx weewx[3062]: engine: Loading station type Vantage 
(weewx.drivers.vantage)

Mar 22 18:35:06 wx weewx[3062]: vantage: driver version is 3.0.9

Mar 22 18:35:06 wx weewx[3062]: vantage: Opened up serial port /dev/ttyUSB0; 
baud 19200; timeout 4.00

Mar 22 18:35:06 wx weewx[3062]: vantage: gentle wake up of console successful

Mar 22 18:35:06 wx weewx[3062]: vantage: _setup; hardware type is 16

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.engine.StdTimeSynch

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdTimeSynch

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service weewx.engine.StdConvert

Mar 22 18:35:06 wx weewx[3062]: engine: StdConvert target unit is 0x1

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdConvert

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.engine.StdCalibrate

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdCalibrate

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service weewx.engine.StdQC

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdQC

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.wxservices.StdWXCalculate

Mar 22 18:35:06 wx weewx[3062]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware

Mar 22 18:35:06 wx weewx[3062]: wxcalculate: The following algorithms will be 
use

RE: [weewx-user] Not uploading to CWOP (continued from previous post)

2021-03-22 Thread Peter Dougherty
OK, now that is bizarre. Why would it just suddenly disappear, I wonder? I will 
post over there but there’s gotta be more involved.

The end goal is to have the data not just posted to CWOP itself, but also 
disseminated to the APRS network.

 

- pjd

 

From: weewx-user@googlegroups.com  On Behalf Of 
John Kline
Sent: Monday, March 22, 2021 7:01 PM
To: weewx-user@googlegroups.com
Subject: Re: [weewx-user] Not uploading to CWOP (continued from previous post)

 

I don’t see W2IRT listed here:

http://www.wxqa.com/members.txt

 

I’m not sure; but perhaps it is no longer registered?  A better place to ask 
that question (is it registered), is here:

https://www.wxforum.net/index.php?board=15.0

 





On Mar 22, 2021, at 3:38 PM, Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:

It occurred to me that you might also need to see the log from process start, 
so I stopped the service and restarted it, and have pasted the relevant portion 
of the log below. This is from within 3 minutes of my typing out this post.

 

Mar 22 18:34:16 wx weewx[2460]: engine: Received signal TERM.

Mar 22 18:34:16 wx weewx[2460]: engine: Main loop exiting. Shutting engine down.

Mar 22 18:34:16 wx weewx[2460]: engine: Shutting down StdReport thread

Mar 22 18:34:16 wx weewx[2460]: engine: StdReport thread has been terminated

Mar 22 18:34:16 wx weewx[2460]: restx: Shut down CWOP thread.

Mar 22 18:34:16 wx weewx[2460]: restx: Shut down PWSWeather thread.

Mar 22 18:34:16 wx weewx[2460]: restx: Shut down Wunderground-RF thread.

Mar 22 18:34:16 wx weewx[2460]: engine: Terminating weewx version 3.6.2

Mar 22 18:34:22 wx weewx[2980]: Stopping weewx weather system: weewx..

Mar 22 18:35:06 wx weewx[3058]: engine: Initializing weewx version 3.6.2

Mar 22 18:35:06 wx weewx[3058]: engine: Using Python 2.7.9 (default, Sep 16 
2019, 18:29:54) #012[GCC 4.9.2]

Mar 22 18:35:06 wx weewx[3058]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0

Mar 22 18:35:06 wx weewx[3058]: engine: pid file is /var/run/weewx.pid

Mar 22 18:35:06 wx weewx[3048]: Starting weewx weather system: weewx.

Mar 22 18:35:06 wx weewx[3062]: engine: Using configuration file 
/etc/weewx/weewx.conf

Mar 22 18:35:06 wx weewx[3062]: engine: Initializing engine

Mar 22 18:35:06 wx weewx[3062]: engine: Loading station type Vantage 
(weewx.drivers.vantage)

Mar 22 18:35:06 wx weewx[3062]: vantage: driver version is 3.0.9

Mar 22 18:35:06 wx weewx[3062]: vantage: Opened up serial port /dev/ttyUSB0; 
baud 19200; timeout 4.00

Mar 22 18:35:06 wx weewx[3062]: vantage: gentle wake up of console successful

Mar 22 18:35:06 wx weewx[3062]: vantage: _setup; hardware type is 16

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.engine.StdTimeSynch

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdTimeSynch

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service weewx.engine.StdConvert

Mar 22 18:35:06 wx weewx[3062]: engine: StdConvert target unit is 0x1

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdConvert

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.engine.StdCalibrate

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdCalibrate

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service weewx.engine.StdQC

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdQC

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.wxservices.StdWXCalculate

Mar 22 18:35:06 wx weewx[3062]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware

Mar 22 18:35:06 wx weewx[3062]: wxcalculate: The following algorithms will be 
used for calculations: altimeter=aaNOAA, maxSolarRad=RS

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate

Mar 22 18:35:06 wx weewx[3062]: engine: Loading service weewx.engine.StdArchive

Mar 22 18:35:06 wx weewx[3062]: engine: Archive will use data binding wx_binding

Mar 22 18:35:06 wx weewx[3062]: engine: Record generation will be attempted in 
'hardware'

Mar 22 18:35:06 wx weewx[3062]: engine: Using archive interval of 300 seconds 
(specified by hardware)

Mar 22 18:35:06 wx weewx[3062]: engine: Use LOOP data in hi/low calculations: 1

Mar 22 18:35:06 wx weewx[3062]: engine: Using binding 'wx_binding' to database 
'weewx.sdb'

Mar 22 18:35:06 wx weewx[3062]: manager: Starting backfill of daily summaries

Mar 22 18:35:06 wx weewx[3062]: manager: Daily summaries up to date

Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdArchive

Mar 22 18:35

Re: [weewx-user] Not uploading to CWOP (continued from previous post)

2021-03-22 Thread Peter Dougherty
:35:06 wx weewx[3062]: engine: Loading service weewx.restx.StdCWOP
Mar 22 18:35:06 wx weewx[3062]: restx: CWOP: Data for station W2IRT will be 
posted
Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.restx.StdCWOP
Mar 22 18:35:06 wx weewx[3062]: engine: Loading service weewx.restx.StdWOW
Mar 22 18:35:06 wx weewx[3062]: restx: WOW: Posting not enabled.
Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.restx.StdWOW
Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.restx.StdAWEKAS
Mar 22 18:35:06 wx weewx[3062]: restx: AWEKAS: Posting not enabled.
Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.restx.StdAWEKAS
Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.engine.StdPrint
Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdPrint
Mar 22 18:35:06 wx weewx[3062]: engine: Loading service 
weewx.engine.StdReport
Mar 22 18:35:06 wx weewx[3062]: engine: Finished loading service 
weewx.engine.StdReport
Mar 22 18:35:06 wx weewx[3062]: engine: Starting up weewx version 3.6.2
Mar 22 18:35:06 wx weewx[3062]: vantage: gentle wake up of console 
successful
Mar 22 18:35:06 wx weewx[3062]: engine: Clock error is -0.86 seconds 
(positive is fast)
Mar 22 18:35:06 wx weewx[3062]: vantage: Getting archive packets since 
2021-03-14 03:00:00 EDT (1615705200)
Mar 22 18:35:06 wx weewx[3062]: vantage: gentle wake up of console 
successful
Mar 22 18:35:08 wx weewx[3062]: vantage: Retrieving 513 page(s); starting 
index= 1
Mar 22 18:35:08 wx weewx[3062]: vantage: DMPAFT complete: page timestamp 
2021-03-13 20:15:00 EST (1615684500) less than final timestamp 2021-03-14 
03:00:00 EDT (1615705200)
Mar 22 18:35:08 wx weewx[3062]: vantage: Catch up complete.
Mar 22 18:35:08 wx weewx[3062]: engine: Starting main packet loop.
Mar 22 18:35:08 wx weewx[3062]: vantage: gentle wake up of console 
successful
Mar 22 18:35:09 wx weewx[3062]: vantage: Requesting 200 LOOP packets.
Mar 22 18:35:09 wx weewx[3062]: vantage: gentle wake up of console 
successful


On Monday, March 22, 2021 at 6:13:41 PM UTC-4 Peter Dougherty wrote:

> OK, set to debug and the results will be found below.
>
> My Weather Underground page is
> https://www.wunderground.com/dashboard/pws/KNJWESTC2
> And as you can see, data has been continuous for quite some time. I had 
> stopped and restarted the server a few times in an attempt to maybe get 
> things running which could explain the earlier time jump.
>
> These are pastes from two sections of my config file:
>
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 Tom Keffer mailto:tke...@gmail.com
> # See the file LICENSE.txt for your rights.
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 1
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 3.6.2
>
> and
>
> # This section is for uploading data to Internet sites
>
> [StdRESTful]
>
> [[StationRegistry]]
> # To register this weather station with weewx, set this to true
> register_this_station = true
>
> [[AWEKAS]]
> # This section is for configuring posts to AWEKAS.
>
> # If you wish to do this, set the option 'enable' to true,
> # and specify a username and password.
> enable = false
> username = replace_me
> password = replace_me
>
>
> [[CWOP]]
> # This section is for configuring posts to CWOP.
>
> # If you wish to do this, set the option 'enable' to true,
> # and specify the station ID (e.g., CW1234).
> enable = true
> station = W2IRT
> post_interval = 300
> log_success = True
> log_failure = True
> server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, 
> cwop.aprs.net:14580, swop.aprs.net:23
>
> # If this is an APRS (radio amateur) station, uncomment
> # the following and replace with a passcode (e.g., 12345).
> passcode = (removed)
>
>
> [[PWSweather]]
> # This section is for configuring posts to PWSweather.com.
>
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station and password.
> enable = true
> station = w2irt
> password = (removed for this troubleshooting session)
>
> [[WOW]]
> # This section is for configuring posts to WOW.
>
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station and password.
> enable = false
> station = replace_me
> password = replace_me
>
> [[Wunderground]]
> # This section is for co

RE: [weewx-user] Not uploading to CWOP

2021-03-22 Thread Peter Dougherty
OK, set to debug and the results will be found below.

My Weather Underground page is
https://www.wunderground.com/dashboard/pws/KNJWESTC2
And as you can see, data has been continuous for quite some time. I had stopped 
and restarted the server a few times in an attempt to maybe get things running 
which could explain the earlier time jump.

These are pastes from two sections of my config file:

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer mailto:tkef...@gmail.com
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.6.2

and

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
enable = false
username = replace_me
password = replace_me


[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = W2IRT
post_interval = 300
log_success = True
log_failure = True
server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, 
cwop.aprs.net:14580, swop.aprs.net:23

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
passcode = (removed)


[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = true
station = w2irt
password = (removed for this troubleshooting session)

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = false
station = replace_me
password = replace_me

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
enable = true
station = KNJWESTC2
password = (removed for this troubleshooting session)

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = True

#[[Twitter]]
#oauth_token_secret = OAUTH_TOKEN_SECRET
#oauth_token = OAUTH_TOKEN
#app_key_secret = APP_KEY_SECRET
#app_key = APP_KEY

Next, there are going to be two pastes below. The first (immediately below) 
will be the two most recent reporting cycles from the log with debug set to 1. 
The second (prefaced with the text string of ) will be a portion of a 
previous log wherein the last references to “restx” were mentioned. The “restx” 
line has not appeared in any log entry since Mar. 14 at 0300:16. The last data 
received at CWOP was on the 15th (the relevant paste from the CWOP web site 
will be after that second section).

Mar 22 18:00:15 wx weewx[2460]: vantage: Getting archive packets since 
2021-03-14 03:00:00 EDT (1615705200)
Mar 22 18:00:15 wx weewx[2460]: vantage: gentle wake up of console successful
Mar 22 18:00:17 wx weewx[2460]: vantage: Retrieving 513 page(s); starting 
index= 4
Mar 22 18:00:17 wx weewx[2460]: vantage: DMPAFT complete: page timestamp 
2021-03-13 19:40:00 EST (1615682400) less than final timestamp 2021-03-14 
03:00:00 EDT (1615705200)
Mar 22 18:00:17 wx weewx[2460]: vantage: Catch up complete.
Mar 22 18:00:17 wx weewx[2460]: reportengine: Running reports for latest time 
in the database.
Mar 22 18:00:17 wx weewx[2460]: vantage: Requesting 200 LOOP packets.
Mar 22 18:00:17 wx weewx[2460]: reportengine: Running report StandardReport
Mar 22 18:00:17 wx weewx[2460]: reportengine: Found configuration file 
/etc/weewx/skins/Standard/skin.conf for report StandardReport
Mar 22 18:00:17 wx weewx[2460]: vantage: gentle wake up of console successful
Mar 22 18:00:17 wx weewx[2460]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 

[weewx-user] Not uploading to CWOP

2021-03-22 Thread Peter Dougherty
Hi all,
About 8 days ago weewx stopped uploading data to CWOP without explanation. 
It has continued to report to Weather Underground without issue so the 
station itself, the Pi, weewx, and the Internet connection are obviously 
still good.

I'm not sure what went wrong. I didn't change any files or even access the 
Pi in the last 6 months or so. I restarted it and no change since. Any 
suggestions? Please and thanks.

There is nothing in the log that looks out of place: 
Mar 22 12:17:15 wx weewx[666]: engine: Initializing weewx version 3.6.2
Mar 22 12:17:15 wx weewx[666]: engine: Using Python 2.7.9 (default, Sep 16 
2019, 18:29:54) #012[GCC 4.9.2]
Mar 22 12:17:15 wx weewx[666]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Mar 22 12:17:15 wx weewx[666]: engine: pid file is /var/run/weewx.pid
Mar 22 12:17:15 wx weewx[582]: Starting weewx weather system: weewx.
Mar 22 12:17:15 wx weewx[1050]: engine: Using configuration file 
/etc/weewx/weewx.conf
Mar 22 12:17:15 wx weewx[1050]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 22 12:17:16 wx weewx[1050]: engine: StdConvert target unit is 0x1
Mar 22 12:17:16 wx weewx[1050]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardw$
Mar 22 12:17:16 wx weewx[1050]: wxcalculate: The following algorithms will 
be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Mar 22 12:17:16 wx weewx[1050]: engine: Archive will use data binding 
wx_binding
Mar 22 12:17:16 wx weewx[1050]: engine: Record generation will be attempted 
in 'hardware'
Mar 22 12:17:16 wx weewx[1050]: engine: Using archive interval of 300 
seconds (specified by hardware)
Mar 22 12:17:17 wx weewx[1050]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Mar 22 12:17:17 wx weewx[1050]: manager: Starting backfill of daily 
summaries
Mar 22 12:17:17 wx weewx[1050]: manager: Daily summaries up to date
Mar 22 12:17:17 wx weewx[1050]: restx: StationRegistry: Station will not be 
registered: no station_url specified.
Mar 22 12:17:17 wx weewx[1050]: restx: Wunderground-RF: Data for station 
KNJWESTC2 will be posted
Mar 22 12:17:17 wx weewx[1050]: restx: PWSWeather: Data for station w2irt 
will be posted
Mar 22 12:17:17 wx weewx[1050]: restx: CWOP: Data for station W2IRT will be 
posted
Mar 22 12:17:17 wx weewx[1050]: restx: WOW: Posting not enabled.
Mar 22 12:17:17 wx weewx[1050]: restx: AWEKAS: Posting not enabled.
Mar 22 12:17:17 wx weewx[1050]: engine: Starting up weewx version 3.6.2
Mar 22 12:17:17 wx weewx[1050]: engine: Clock error is 677.10 seconds 
(positive is fast)
Mar 22 12:17:17 wx weewx[1050]: vantage: Clock set to 2021-03-22 12:17:18 
EDT (1616429838)
Mar 22 12:28:38 wx weewx[1050]: engine: Starting main packet loop.
Mar 22 12:28:50 wx weewx[1050]: cheetahgenerator: Generated 14 files for 
report StandardReport in 10.44 seconds
Mar 22 12:28:58 wx weewx[1050]: genimages: Generated 36 images for 
StandardReport in 8.20 seconds
Mar 22 12:28:59 wx weewx[1050]: reportengine: copied 9 files to 
/var/www/html/weewx
Mar 22 12:30:20 wx weewx[1050]: cheetahgenerator: Generated 14 files for 
report StandardReport in 2.68 seconds
Mar 22 12:30:28 wx weewx[1050]: genimages: Generated 36 images for 
StandardReport in 7.88 seconds
Mar 22 12:30:28 wx weewx[1050]: reportengine: copied 0 files to 
/var/www/html/weewx
Mar 22 12:35:20 wx weewx[1050]: cheetahgenerator: Generated 14 files for 
report StandardReport in 2.85 seconds
Mar 22 12:35:28 wx weewx[1050]: genimages: Generated 36 images for 
StandardReport in 8.20 seconds
Mar 22 12:35:28 wx weewx[1050]: reportengine: copied 0 files to 
/var/www/html/weewx


And the config file is in order too (with password removed for posting 
here): 

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
enable = false
username = replace_me
password = replace_me


[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = W2IRT
post_interval = 300
log_success = True
log_failure = True
server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, 
cwop.aprs.net:14580, swop.aprs.net:23

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
passcode = (my password)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To 

Re: [weewx-user] Re: System has stopped reporting everywhere

2017-05-29 Thread Peter Dougherty
Just a quick reply to say thanks, everything's working again, and the 
wunderfixer option is running OK. I have no idea what the end part of that 
command means, but I can see the result of the daily run in the log so 
that's all that matters. Thanks again for your assistance.

On Wednesday, May 24, 2017 at 10:26:40 PM UTC-4, gjr80 wrote:
>
> wunderfixer is included with weeWX, its location will be depend on how 
> weeWX was installed, it will most likely be in the /home/weewx/bin 
> directory but it could be in /usr/share/weewx if you installed from a 
> .deb or .rpm package. To run wunderfixer:
>
> $ /home/weewx/bin/wunderfixer --test
>
> if this generates an error it could be because the currently logged in 
> user does not have permission to do some of the things wunderfixer does 
> so in that case try running as root using:
>
> $ sudo /home/weewx/bin/wunderfixer --test
>
> the --test option gets wunderfixer to check WU for any missing records 
> for the current day and give you a summary report of what it found and what 
> it would do ('fix') but not actually do anything. By default wunderfixer 
> checks the current day. The --date option lets you specify another date 
> to check. So to check 17 May 2017 you would use:
>
> $  sudo /home/weewx/bin/wunderfixer --test --date=2017-05-17
>
> If you have 6 or 7 days to 'fix' then you will need to run wunderfixer 6 
> or 7 times, one for each day. To actually 'fix' a day just remove the 
> --test option. All of the other options can probably be left alone, 
> though the --query option can be helpful if you think your weeWX data may 
> be suspect, as you will be asked to confirm (y/n) before each WU record is 
> updated (if you have a whole day to 'fix' at 5 minute intervals that is 288 
> confirmations). Be aware that once data is published to WU you cannot 
> change it other than deleting it. So if you have any basis for thinking you 
> weeWX data is suspect, it is best to fix your weeWX data before using 
> wunderfixer.
>
> You can safely run wunderfixer for a give day as many times as you want, 
> at worst WU will ignore any attempted 'fixes' for data already recorded. I 
> always find it funny that if you run wunderfixer 5 times for a given day 
> the chances are you will get 5 different results in terms on number of 
> missing records - just the vagaries of WU.
>
> Having wunderfixer run as a cron job is easily setup. Best to have it run 
> under the root user cron so open the root user crontab using:
>
> $ sudo crontab -e
>
> Go to the bottom of the file and type something like (assuming wunderfixer 
> is in /home/weewx/bin):
>
> # Run wunderfixer at 1158pm daily
> 58 23 * * * /home/weewx/bin/wunderfixer --log weewx > /dev/null 2>&1
>
> This will run wunderfixer at 11:58pm each night, you can change it to 
> suit your requriements, but on a 5 minute interval system 11:58pm captures 
> all records for that particular day. Save the file (most likely Control-O 
> followed by enter then Control-X though depends on your editor). Note that 
> it is a good idea to run wunderfixer at least once from the command line 
> without the --test option before setting up the cron job, that way you 
> know that the WU credentials in your weewx.conf work fine with wunderfixer
> .
>
> Gary
>
> On Thursday, 25 May 2017 11:28:56 UTC+10, Peter Dougherty wrote:
>>
>> Hi Gary,
>> I've read through that link you sent until my eyes bled, and I just don't 
>> understand how to use it. Like I said up top, Linux and I aren't friends, 
>> we just tolerate each other's existence and call it a draw. So where do I 
>> go to get a copy of wunderfixer, how do I install it, configure it to look 
>> for every single piece of missing data and then run it? There are about 
>> 1,800 updates that never got sent to WU in the 6+ days it was down.
>>
>> On Tuesday, May 23, 2017 at 9:44:05 PM UTC-4, gjr80 wrote:
>>>
>>> Can't say much other than 'yes it is not posting to WU' without seeing 
>>> more of the log ie from weeWX startup. You can use wunderfixer 
>>> <http://weewx.com/docs/utilities.htm#wunderfixer_utility> to re-post to 
>>> WU. In fact it is a good idea to set up wunderfixer to run by cron on a 
>>> daily basis, I run it at 23:58 each night. WU is by no means perfect and 
>>> despite seeing 288 posts to WU each day in my logs some just don't make it.
>>>
>>> As to your previous questions. Twitter should not be that hard to set to 
>>> work, I would be getting everything else back and stable before worrying 
>>> about twitter. The error in the log indicates that python cannot find the 
>>> requests_oauthlib modul

Re: [weewx-user] Re: System has stopped reporting everywhere

2017-05-24 Thread Peter Dougherty
Hi Gary,
I've read through that link you sent until my eyes bled, and I just don't 
understand how to use it. Like I said up top, Linux and I aren't friends, 
we just tolerate each other's existence and call it a draw. So where do I 
go to get a copy of wunderfixer, how do I install it, configure it to look 
for every single piece of missing data and then run it? There are about 
1,800 updates that never got sent to WU in the 6+ days it was down.

On Tuesday, May 23, 2017 at 9:44:05 PM UTC-4, gjr80 wrote:
>
> Can't say much other than 'yes it is not posting to WU' without seeing 
> more of the log ie from weeWX startup. You can use wunderfixer 
> <http://weewx.com/docs/utilities.htm#wunderfixer_utility> to re-post to 
> WU. In fact it is a good idea to set up wunderfixer to run by cron on a 
> daily basis, I run it at 23:58 each night. WU is by no means perfect and 
> despite seeing 288 posts to WU each day in my logs some just don't make it.
>
> As to your previous questions. Twitter should not be that hard to set to 
> work, I would be getting everything else back and stable before worrying 
> about twitter. The error in the log indicates that python cannot find the 
> requests_oauthlib module. This is not included in the standard python 
> install, did you ever install it separately? Re-installing it would be a 
> good starting point. You may also find more info by searching the forums 
> for 'twitter' or maybe by looking at any comments at the start of the 
> bin/user/twitter.py 
> file.
>
> I think Tom covered the downloading of data from the logger, another easy 
> way to tell if the last 27 hours of data has been downloaded OK is to look 
> at your daily plots. They default to 27 hours of data with no aggregation 
> and any (extended) missing data will show up as one or more gaps. Week, 
> month and year plots use aggregated data so gaps may not be apparent there.
>
> Gary
>
> On Wednesday, 24 May 2017 11:22:12 UTC+10, Peter Dougherty wrote:
>>
>> It's doesn't appear to be sending any of the missing data to Weather 
>> Underground, but it *is* sending current data. The station went back 
>> online around 18:29 today (23 May) and had been offline starting around 
>> 05:00 on 17 May. Three hours after going back online I cannot find the 
>> missing data on the WU site.
>>
>> This is a log excerpt. It appears as if it's trying to send the backlog 
>> (there are hundreds of these entries in the log).
>>
>> .
>> May 23 18:34:32 wx weewx[1905]: manager: added record 2017-05-22 02:20:00 
>> EDT (1495434000) to database 'weewx.sdb'
>> May 23 18:34:32 wx weewx[1905]: manager: added record 2017-05-22 02:20:00 
>> EDT (1495434000) to daily summary in 'weewx.sdb'
>> May 23 18:34:32 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:15:00 EDT (1495433700)
>> May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:20:00 
>> EDT (1495434000) is stale (144873 > 60).
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:25:00 
>> EDT (1495434300) to database 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:25:00 
>> EDT (1495434300) to daily summary in 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:20:00 EDT (1495434000)
>> May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:25:00 
>> EDT (1495434300) is stale (144573 > 60).
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:30:00 
>> EDT (1495434600) to database 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:30:00 
>> EDT (1495434600) to daily summary in 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:25:00 EDT (1495434300)
>> May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:30:00 
>> EDT (1495434600) is stale (144273 > 60).
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:35:00 
>> EDT (1495434900) to database 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:30:00 EDT (1495434600)
>>
>

-- 
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.


Re: [weewx-user] Re: System has stopped reporting everywhere

2017-05-23 Thread Peter Dougherty
It's doesn't appear to be sending any of the missing data to Weather 
Underground, but it *is* sending current data. The station went back online 
around 18:29 today (23 May) and had been offline starting around 05:00 on 
17 May. Three hours after going back online I cannot find the missing data 
on the WU site.

This is a log excerpt. It appears as if it's trying to send the backlog 
(there are hundreds of these entries in the log).

.
May 23 18:34:32 wx weewx[1905]: manager: added record 2017-05-22 02:20:00 
EDT (1495434000) to database 'weewx.sdb'
May 23 18:34:32 wx weewx[1905]: manager: added record 2017-05-22 02:20:00 
EDT (1495434000) to daily summary in 'weewx.sdb'
May 23 18:34:32 wx weewx[1905]: restx: PWSWeather: Published record 
2017-05-22 02:15:00 EDT (1495433700)
May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:20:00 EDT 
(1495434000) is stale (144873 > 60).
May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:25:00 
EDT (1495434300) to database 'weewx.sdb'
May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:25:00 
EDT (1495434300) to daily summary in 'weewx.sdb'
May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
2017-05-22 02:20:00 EDT (1495434000)
May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:25:00 EDT 
(1495434300) is stale (144573 > 60).
May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:30:00 
EDT (1495434600) to database 'weewx.sdb'
May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:30:00 
EDT (1495434600) to daily summary in 'weewx.sdb'
May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
2017-05-22 02:25:00 EDT (1495434300)
May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:30:00 EDT 
(1495434600) is stale (144273 > 60).
May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:35:00 
EDT (1495434900) to database 'weewx.sdb'
May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
2017-05-22 02:30:00 EDT (1495434600)

-- 
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.


[weewx-user] Re: System has stopped reporting everywhere

2017-05-23 Thread Peter Dougherty
OK, done and that got things working again. I'm curious as to what broke. 
No changes were made since the end of February, and the system has been up 
and reporting continuously since then. My tech guru and I attempted to get 
the Twitter reporting function working (like I had with Cumulus software, 
under Windows) but it never would, and so we just ignored it.

Is there any way to determine if the last 5 days' data has been 
successfully downloaded from the data logger on the Vantage Pro 2? And if 
so, is there any way that you know if to retroactively upload it to Weather 
Underground's PWS feature. Thanks in advance.

On Tuesday, May 23, 2017 at 6:19:42 PM UTC-4, gjr80 wrote:
>
> Ok,disable Twitter in restful_services by commenting out:
>
> user.twitter.Twitter
>
> Save weewx.conf, stop then start weeWX and lets see what is in the 10 
> minute log then.
>
> Gary
>
>

-- 
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.


[weewx-user] Re: System has stopped reporting everywhere

2017-05-23 Thread Peter Dougherty
ypes of databases.

[DatabaseTypes]

# Defaults for SQLite databases
[[SQLite]]
driver = weedb.sqlite
# Directory in which the database files are located
SQLITE_ROOT = /var/lib/weewx

# Defaults for MySQL databases
[[MySQL]]
driver = weedb.mysql
# The host where the database is located
host = localhost
# The user name for logging in to the host
user = weewx
# The password for the user name
password = weewx

##

#   This section configures the internal weewx engine.

[Engine]

[[Services]]
# This section specifies the services that should be run. They are
# grouped by type, and the order of services within each group
# determines the order in which the services will be run.
prep_services = weewx.engine.StdTimeSynch
data_services = ,
process_services = weewx.engine.StdConvert, 
weewx.engine.StdCalibrate, weewx.engine.StdQC, 
weewx.wxservices.StdWXCalculate
archive_services = weewx.engine.StdArchive
restful_services = weewx.restx.StdStationRegistry, 
weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
user.twitter.Twitter
report_services = weewx.engine.StdPrint, weewx.engine.StdReport





On Monday, May 22, 2017 at 2:47:54 PM UTC-4, Peter Dougherty wrote:
>
> Weewx has developed a problem as described below. 
>
> I'm running it on a Raspberry Pi. It ran fine for 98 days and then stopped 
> cold. I pulled and restored power and can remote into the box using a VNC 
> client. The box is on the network, I can ping everything from it and I have 
> restarted weewx a dozen times using /etc/init.d/weewx restart. It appears 
> to be fine, but nothing is going out to Weather Underground, CWOP or 
> anybody else. The last update on the localhost interface was at 1pm today, 
> but the last update to WU and CWOP was on May 17th. The weather station is 
> a Davis Vantage Pro 2 using the USB dongle. I'm pretty sure it's sending 
> data from the logger to weewx but have no way or no understanding on how to 
> test communication with the Davis. According to the logs, it's functioning. 
> I have a huge log and I'm not sure how to post it, or how much of it I 
> should include here.
>
> I am an new user and extremely unfamiliar with Linux. The box was set up 
> by a friend and I myself am below kindergarten-level understanding of how 
> to fix it. I can follow a script but I have no natural sense of how to 
> proceed without being told explicitly. Any assistance tremendously 
> appreciated.
>

-- 
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.


[weewx-user] Re: System has stopped reporting everywhere

2017-05-23 Thread Peter Dougherty
Just bumping this up. Any ideas on where I should be looking, per the log 
excerpts? I'm thinking maybe the database has eaten itself somehow??

-- 
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.


[weewx-user] Re: System has stopped reporting everywhere

2017-05-22 Thread Peter Dougherty
OK, here's the point where the failures started to occur, on the afternoon 
of May 17th. I've included from the last good upload until about an hour 
later. There's roughly another hour of similar messages before it settles 
down into the handful of errors I stated in the above list. 

May 17 14:20:16 wx weewx[18242]: manager: added record 2017-05-17 14:20:00 
EDT (1495045200) to database 'weewx.sdb'
May 17 14:20:16 wx weewx[18242]: manager: added record 2017-05-17 14:20:00 
EDT (1495045200) to daily summary in 'weewx.sdb'
May 17 14:20:16 wx weewx[18242]: restx: PWSWeather: Published record 
2017-05-17 14:20:00 EDT (1495045200)
May 17 14:20:16 wx weewx[18242]: restx: CWOP: Published record 2017-05-17 
14:20:00 EDT (1495045200)
May 17 14:20:19 wx weewx[18242]: cheetahgenerator: Generated 14 files for 
report StandardReport in 3.04 seconds
May 17 14:20:20 wx weewx[18242]: genimages: Generated 12 images for 
StandardReport in 1.48 seconds
May 17 14:20:20 wx weewx[18242]: reportengine: copied 0 files to 
/var/www/html/weewx
May 17 15:12:16 wx weewx[18242]: manager: added record 2017-05-17 14:25:00 
EDT (1495045500) to database 'weewx.sdb'
May 17 15:12:16 wx weewx[18242]: manager: added record 2017-05-17 14:25:00 
EDT (1495045500) to daily summary in 'weewx.sdb'
May 17 15:12:25 wx weewx[18242]: manager: added record 2017-05-17 14:30:00 
EDT (1495045800) to database 'weewx.sdb'
May 17 15:12:25 wx weewx[18242]: manager: added record 2017-05-17 14:30:00 
EDT (1495045800) to daily summary in 'weewx.sdb'
May 17 15:12:34 wx weewx[18242]: manager: added record 2017-05-17 14:35:00 
EDT (1495046100) to database 'weewx.sdb'
May 17 15:12:34 wx weewx[18242]: manager: added record 2017-05-17 14:35:00 
EDT (1495046100) to daily summary in 'weewx.sdb'
May 17 15:12:41 wx weewx[18242]: restx: PWSWeather: Failed to publish 
record 2017-05-17 14:25:00 EDT (1495045500): Failed upload after 3 tries
May 17 15:12:44 wx weewx[18242]: manager: added record 2017-05-17 14:40:00 
EDT (1495046400) to database 'weewx.sdb'
May 17 15:12:44 wx weewx[18242]: manager: added record 2017-05-17 14:40:00 
EDT (1495046400) to daily summary in 'weewx.sdb'
May 17 15:12:56 wx weewx[18242]: vantage: DMPAFT try #1; error: Time out in 
get_data_with_crc16
May 17 15:13:00 wx weewx[18242]: restx: PWSWeather: Failed to publish 
record 2017-05-17 14:30:00 EDT (1495045800): Failed upload after 3 tries
May 17 15:13:00 wx weewx[18242]: manager: added record 2017-05-17 14:45:00 
EDT (1495046700) to database 'weewx.sdb'
May 17 15:13:00 wx weewx[18242]: manager: added record 2017-05-17 14:45:00 
EDT (1495046700) to daily summary in 'weewx.sdb'
May 17 15:13:09 wx weewx[18242]: manager: added record 2017-05-17 14:50:00 
EDT (1495047000) to database 'weewx.sdb'
May 17 15:13:09 wx weewx[18242]: manager: added record 2017-05-17 14:50:00 
EDT (1495047000) to daily summary in 'weewx.sdb'
May 17 15:13:18 wx weewx[18242]: manager: added record 2017-05-17 14:55:00 
EDT (1495047300) to database 'weewx.sdb'
May 17 15:13:18 wx weewx[18242]: manager: added record 2017-05-17 14:55:00 
EDT (1495047300) to daily summary in 'weewx.sdb'
May 17 15:13:24 wx weewx[18242]: restx: PWSWeather: Failed to publish 
record 2017-05-17 14:35:00 EDT (1495046100): Failed upload after 3 tries
May 17 15:13:27 wx weewx[18242]: manager: added record 2017-05-17 15:00:00 
EDT (1495047600) to database 'weewx.sdb'
May 17 15:13:27 wx weewx[18242]: manager: added record 2017-05-17 15:00:00 
EDT (1495047600) to daily summary in 'weewx.sdb'
May 17 15:13:35 wx weewx[18242]: manager: added record 2017-05-17 15:05:00 
EDT (1495047900) to database 'weewx.sdb'
May 17 15:13:35 wx weewx[18242]: manager: added record 2017-05-17 15:05:00 
EDT (1495047900) to daily summary in 'weewx.sdb'
May 17 15:13:43 wx weewx[18242]: restx: PWSWeather: Failed to publish 
record 2017-05-17 14:40:00 EDT (1495046400): Failed upload after 3 tries
May 17 15:13:44 wx weewx[18242]: vantage: DMPAFT try #1; error: Time out in 
get_data_with_crc16
May 17 15:13:47 wx weewx[18242]: manager: added record 2017-05-17 15:10:00 
EDT (1495048200) to database 'weewx.sdb'
May 17 15:13:47 wx weewx[18242]: manager: added record 2017-05-17 15:10:00 
EDT (1495048200) to daily summary in 'weewx.sdb'
May 17 15:14:03 wx weewx[18242]: restx: PWSWeather: Failed to publish 
record 2017-05-17 14:45:00 EDT (1495046700): Failed upload after 3 tries
May 17 15:14:17 wx weewx[18242]: cheetahgenerator: Generate failed with 
exception ''
May 17 15:14:17 wx weewx[18242]: cheetahgenerator:  Ignoring template 
/etc/weewx/skins/Standard/NOAA/NOAA-.txt.tmpl
May 17 15:14:17 wx weewx[18242]: cheetahgenerator:  Reason: database is 
locked
May 17 15:14:20 wx weewx[18242]:   Traceback (most recent call last):
May 17 15:14:20 wx weewx[18242]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 315, in generate
May 17 15:14:20 wx weewx[18242]:   print >> _file, text
May 17 15:14:20 wx weewx[18242]: File 

[weewx-user] Re: System has stopped reporting everywhere

2017-05-22 Thread Peter Dougherty
Hi Gary,
The log was where you first said it would be (in /var/log) Every 5 minutes 
the following errors appear, beginning yesterday at 06:25. So it would 
appear that WeeWX is alive, at least.

May 21 06:30:14 wx weewx[18242]: manager: added record 2017-05-21 06:30:00 
EDT (1495362600) to database 'weewx.sdb'
May 21 06:30:15 wx weewx[18242]: manager: added record 2017-05-21 06:30:00 
EDT (1495362600) to daily summary in 'weewx.sdb'
May 21 06:30:15 wx weewx[18242]: restx: CWOP: Failed to publish record 2017-
05-21 06:30:00 EDT (1495362600): Tried 4 servers 3 times each
May 21 06:30:19 wx weewx[18242]: cheetahgenerator: Generated 14 files for 
report StandardReport in 4.23 seconds
May 21 06:30:21 wx weewx[18242]: genimages: Generated 12 images for 
StandardReport in 1.65 seconds
May 21 06:30:21 wx weewx[18242]: reportengine: copied 0 files to /var/www/
html/weewx
May 21 06:30:30 wx weewx[18242]: restx: PWSWeather: Failed to publish 
record 2017-05-21 06:30:00 EDT (1495362600): Failed upload after 3 tries


-- 
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.


[weewx-user] System has stopped reporting everywhere

2017-05-22 Thread Peter Dougherty
Weewx has developed a problem as described below. 

I'm running it on a Raspberry Pi. It ran fine for 98 days and then stopped 
cold. I pulled and restored power and can remote into the box using a VNC 
client. The box is on the network, I can ping everything from it and I have 
restarted weewx a dozen times using /etc/init.d/weewx restart. It appears 
to be fine, but nothing is going out to Weather Underground, CWOP or 
anybody else. The last update on the localhost interface was at 1pm today, 
but the last update to WU and CWOP was on May 17th. The weather station is 
a Davis Vantage Pro 2 using the USB dongle. I'm pretty sure it's sending 
data from the logger to weewx but have no way or no understanding on how to 
test communication with the Davis. According to the logs, it's functioning. 
I have a huge log and I'm not sure how to post it, or how much of it I 
should include here.

I am an new user and extremely unfamiliar with Linux. The box was set up by 
a friend and I myself am below kindergarten-level understanding of how to 
fix it. I can follow a script but I have no natural sense of how to proceed 
without being told explicitly. Any assistance tremendously appreciated.

-- 
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.


[weewx-user] Re: Live console and uploading to a Website

2017-02-13 Thread Peter Dougherty
I don't even know what questions to start asking about this. I don't run 
servers here or know anything about them whatsoever (I'm a very, very 
inexperienced user and that's a gross understatement). Is there a "for 
utter morons" guide to setting it up? About all I can do is type in 
commands as written. I have exactly zero understanding of what any of them 
do. I would be more than happy to have commercial software and hosting for 
this!

On Monday, February 13, 2017 at 12:52:49 PM UTC-5, Andrew Milner wrote:
>
> mesowx extension should do the trick
>

-- 
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.


Re: [weewx-user] NEW USER Problems posting to CWOP and PWStation

2017-02-12 Thread Peter Dougherty
Awesome. Are there any other services that are actually used and useful? I 
think Wunderground is probably the most accurate, but I do take pride in 
being able to provide weather data as widely as I can to anybody who finds 
it useful.

On Sunday, February 12, 2017 at 3:44:51 PM UTC-5, Dave Webb wrote:
>
> If I remember correctly when I set mine up it took a good day or so before 
> it finally showed up then after that it was real-time. 
>
> Dave-KB1PVH
>
>
> Sent from my Galaxy S7
>
> On Feb 12, 2017 3:42 PM, "Peter Dougherty" <pjdou...@gmail.com 
> > wrote:
>
>> Oh, that makes sense; I thought it would be within a few minutes and then 
>> near-live after that.
>>
>> On Sunday, February 12, 2017 at 3:42:04 PM UTC-5, Dave Webb wrote:
>>>
>>> Peter,
>>>
>>> I think the PWS stuff takes a day or so before it shows your data if I 
>>> remember correctly. 
>>>
>>> Dave-KB1PVH
>>>
>>>
>>> Sent from my Galaxy S7
>>>
>>> On Feb 12, 2017 3:40 PM, "Peter Dougherty" <pjdou...@gmail.com> wrote:
>>>
>>>> Looking good now, and post_interval worked like a champ. I also got a 
>>>> passcode from Dave and I'm using that, plus logging post success & 
>>>> failure, 
>>>> so definitely a lot of thanks!
>>>>
>>>> Now there's still the issue of PWStation. That seems very 
>>>> straightforward, and weewx is not throwing error messages (says posting 
>>>> success), yet the website isn't receiving data. Thoughts? I just signed up 
>>>> for this yesterday and it's not particularly important--wunderground and 
>>>> CWOP are the only two I've used since 2012--but if it can be made to work, 
>>>> then great. If not, I'll leave this alone then worry about finding a way 
>>>> to 
>>>> output a live display somehow; my next big project!
>>>>
>>>> Thanks to all.
>>>>
>>>> -- 
>>>> 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+...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.


Re: [weewx-user] NEW USER Problems posting to CWOP and PWStation

2017-02-12 Thread Peter Dougherty
Looking good now, and post_interval worked like a champ. I also got a 
passcode from Dave and I'm using that, plus logging post success & failure, 
so definitely a lot of thanks!

Now there's still the issue of PWStation. That seems very straightforward, 
and weewx is not throwing error messages (says posting success), yet the 
website isn't receiving data. Thoughts? I just signed up for this yesterday 
and it's not particularly important--wunderground and CWOP are the only two 
I've used since 2012--but if it can be made to work, then great. If not, 
I'll leave this alone then worry about finding a way to output a live 
display somehow; my next big project!

Thanks to all.

-- 
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.


[weewx-user] NEW USER Problems posting to CWOP and PWStation

2017-02-12 Thread Peter Dougherty
Hello all,

I'm extremely new to weewx and the rawest Linux newbie with absolutely no 
experience in the OS. 

I've been running my Davis Vantage Pro 2 since 2012 on Windows, using 
Cumulus, and have had no uploading to any service when it's running. Due to 
Windows stability and other hardware issues I decided to run the station on 
a Raspberry Pi 3 using Raspian, which was powered up and configured for 
weewx for the first time yesterday. I'm running version 3.6.2 at the moment.

I upload to CWOP, Weather Underground and PWStation. Wunderground is 
working fine but the other two are not.

Troubleshooting log snippets follow:
my config:

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).

enable = true
station = w2irt
server = cwop.aprs.net:14580, cwop.aprs.net:23
interval = 180
protocol = CWOP

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = -1
Although I am a ham, I am *not* using the APRS network to generate posts. 
In Cumulus, I was told initially to use -1 as the passcode and it has 
worked since 2012. Different errors are occurring depending on whether I 
have "passcode" commented out or not. See below.

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = true
station = w2irt
password = (my PWSweather website password)


>From the log

Without "passcode = -1" enabled, the log returns this error:

11:29:35 wx weewx[15542]: APRS station W2IRT requires passcode


With "passcode = -1" this exception happens

11:29:10 wx weewx[15498]: engine: Caught unrecoverable exception in engine:
Feb 12 11:29:10 wx weewx[15498]:   __init__() got an unexpected 
keyword argument 'protocol'
Feb 12 11:29:10 wx weewx[15498]:   Traceback (most recent call 
last):
Feb 12 11:29:10 wx weewx[15498]: File 
"/usr/share/weewx/weewx/engine.py", line 841, in main
Feb 12 11:29:10 wx weewx[15498]:   engine = 
engine_class(config_dict)
Feb 12 11:29:10 wx weewx[15498]: File 
"/usr/share/weewx/weewx/engine.py", line 76, in __init__
Feb 12 11:29:10 wx weewx[15498]:   
self.loadServices(config_dict)
Feb 12 11:29:10 wx weewx[15498]: File 
"/usr/share/weewx/weewx/engine.py", line 140, in loadServices
Feb 12 11:29:10 wx weewx[15498]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
Feb 12 11:29:10 wx weewx[15498]: File 
"/usr/share/weewx/weewx/restx.py", line 880, in __init__
Feb 12 11:29:10 wx weewx[15498]:   **_cwop_dict)
Feb 12 11:29:10 wx weewx[15498]:   TypeError: __init__() got an 
unexpected keyword argument 'protocol'
Feb 12 11:29:10 wx weewx[15498]:   Exiting.
Feb 12 11:29:33 wx weewx[15513]: Stopping weewx weather system: weewx not 
running
---end log snippet

I am getting no errors for PWStation, but it's just not posting to the site.

Thanks in advance for any assistance.


-- 
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.