Re: [weewx-user] davis vantage not outputing data to either WU or mqtt

[Daniel Smith]

thank-you thank-you thank-you, I feel sane again.

Kind regards
Daniel Smith

dan...@greenembrace.net

Think Green be Green - Think about the environment don't print e-mails -
Think Green be Seen
This email contains confidential information intended only for the
person(s) named above and may be subject to legal privilege. If you are
not the intended recipient, any disclosure, copying, printing or use in
anyway of this information is prohibited, and it must be deleted from
your system immediately. Please send return mail advising of its
reception. We also cannot provide any guarantees that this communication
is free of viruses or any other malicious agents although it was scanned
before transmission. If you have received this email in error or have
any other concerns regarding its transmission, please notify:
postmas...@greenembrace.net

On Sun, 2 Dec 2018, at 12:58 PM, Thomas Keffer wrote:
> The memory of the logger has been corrupted.
> 
> To fix, see the section *WeeWX generates HTML pages, but it does not
> update them[1]* in the User's Guide.> 
> -tk
> 
> On Sat, Dec 1, 2018 at 5:52 PM Daniel Smith
>  wrote:>> Hi 
>> I've been running for a while with no issues publishing to both weather-
>> underground and through MQTT to other parts of my system.>> two (2) days ago 
>> output stopped.__
>> I'm using Rpi 3. with a USB connection to davis console. I've
>> reinstalled weewx with no output success.>> weewx seems to be running ok.
>> Can't find anything wrong with hardware, iv'e also tries different
>> usb port, new RPi, different USB cable. I've connected minicom to
>> /dev/ttyUSB0 port activity happening on it.>> My MQTT stopped at the same 
>> time.
>> 
>> I can't see any issues in syslog. but I also don't know what to look
>> for>> 
>> below out from syslog:
>> 
>> Dec  2 11:46:53 automation systemd[1]: Starting LSB: weewx weather
>> system...>> Dec  2 11:46:53 automation weewx[9259]: engine: Initializing 
>> weewx
>> version 3.8.2>> Dec  2 11:46:53 automation weewx[9259]: engine: Using Python 
>> 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]>> Dec  2 11:46:53 
>> automation weewx[9259]: engine: Platform 
>> Linux-4.14.79-v7+-armv7l-with-debian-
>> 9.6>> Dec  2 11:46:53 automation weewx[9259]: engine: Locale is 'en_GB.UTF-
>> 8'>> Dec  2 11:46:53 automation weewx[9259]: engine: pid file is
>> /var/run/weewx.pid>> Dec  2 11:46:53 automation weewx[9263]: engine: Using 
>> configuration
>> file /etc/weewx/weewx.conf>> Dec  2 11:46:53 automation weewx[9263]: engine: 
>> Debug is 1
>> Dec  2 11:46:53 automation weewx[9263]: engine: Initializing engine
>> Dec  2 11:46:53 automation weewx[9263]: engine: Loading station type
>> Vantage (weewx.drivers.vantage)>> Dec  2 11:46:53 automation weewx[9242]: 
>> Starting weewx weather
>> system: weewx.>> Dec  2 11:46:53 automation systemd[1]: Started LSB: weewx 
>> weather
>> system.>> Dec  2 11:46:53 automation weewx[9263]: vantage: Driver version
>> is 3.0.11>> Dec  2 11:46:53 automation weewx[9263]: vantage: Opened up serial
>> port /dev/ttyUSB0; baud 19200; timeout 4.00>> Dec  2 11:46:53 automation 
>> weewx[9263]: vantage: Gentle wake up of
>> console successful>> Dec  2 11:46:53 automation weewx[9263]: vantage: 
>> Hardware type is 16>> Dec  2 11:46:53 automation weewx[9263]: vantage: ISS 
>> ID is 1
>> Dec  2 11:46:53 automation weewx[9263]: vantage: Hardware name:
>> Vantage Pro2>> Dec  2 11:46:53 automation weewx[9263]: engine: Loading 
>> service
>> weewx.engine.StdTimeSynch>> Dec  2 11:46:53 automation weewx[9263]: engine: 
>> Finished loading
>> service weewx.engine.StdTimeSynch>> Dec  2 11:46:53 automation weewx[9263]: 
>> engine: Loading service
>> weewx.engine.StdConvert>> Dec  2 11:46:53 automation weewx[9263]: engine: 
>> StdConvert target
>> unit is 0x1>> Dec  2 11:46:53 automation weewx[9263]: engine: Finished 
>> loading
>> service weewx.engine.StdConvert>> Dec  2 11:46:53 automation weewx[9263]: 
>> engine: Loading service
>> weewx.engine.StdCalibrate>> Dec  2 11:46:53 automation weewx[9263]: engine: 
>> Finished loading
>> service weewx.engine.StdCalibrate>> Dec  2 11:46:53 automation weewx[9263]: 
>> engine: Loading service
>> weewx.engine.StdQC>> Dec  2 11:46:53 automation weewx[9263]: engine: 
>> Finished loading
>> service weewx.engine.StdQC>> Dec  2 11:46:53 automation weewx[9263]: engine: 
>> Loading service
>> weewx.wxservices.StdWXCalculate>> Dec  2 11:46:53 automation weewx[9263]: 
>> 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>> Dec  2 11:46:53 automation weewx[9263]: 
>> wxcalculate: The following
>> algorithms 

[weewx-user] Re: davis vantage not outputing data to either WU or mqtt

[Daniel Smith]

Thanks Thomas, I do remember reading about that but did not make the 
connection. I will give it a go.
kind regards

>

-- 
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] davis vantage not outputing data to either WU or mqtt

[Thomas Keffer]

The memory of the logger has been corrupted.

To fix, see the section *WeeWX generates HTML pages, but it does not update
them * in
the User's Guide.

-tk

On Sat, Dec 1, 2018 at 5:52 PM Daniel Smith  wrote:

> Hi
> I've been running for a while with no issues publishing to both
> weather-underground and through MQTT to other parts of my system.
> two (2) days ago output stopped.
> I'm using Rpi 3. with a USB connection to davis console. I've reinstalled
> weewx with no output success.
> weewx seems to be running ok.
> Can't find anything wrong with hardware, iv'e also tries different usb
> port, new RPi, different USB cable. I've connected minicom to /dev/ttyUSB0
> port activity happening on it.
> My MQTT stopped at the same time.
>
> I can't see any issues in syslog. but I also don't know what to look
> for
>
> below out from syslog:
>
> Dec  2 11:46:53 automation systemd[1]: Starting LSB: weewx weather
> system...
> Dec  2 11:46:53 automation weewx[9259]: engine: Initializing weewx version
> 3.8.2
> Dec  2 11:46:53 automation weewx[9259]: engine: Using Python 2.7.13
> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> Dec  2 11:46:53 automation weewx[9259]: engine: Platform
> Linux-4.14.79-v7+-armv7l-with-debian-9.6
> Dec  2 11:46:53 automation weewx[9259]: engine: Locale is 'en_GB.UTF-8'
> Dec  2 11:46:53 automation weewx[9259]: engine: pid file is
> /var/run/weewx.pid
> Dec  2 11:46:53 automation weewx[9263]: engine: Using configuration file
> /etc/weewx/weewx.conf
> Dec  2 11:46:53 automation weewx[9263]: engine: Debug is 1
> Dec  2 11:46:53 automation weewx[9263]: engine: Initializing engine
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading station type
> Vantage (weewx.drivers.vantage)
> Dec  2 11:46:53 automation weewx[9242]: Starting weewx weather system:
> weewx.
> Dec  2 11:46:53 automation systemd[1]: Started LSB: weewx weather system.
> Dec  2 11:46:53 automation weewx[9263]: vantage: Driver version is 3.0.11
> Dec  2 11:46:53 automation weewx[9263]: vantage: Opened up serial port
> /dev/ttyUSB0; baud 19200; timeout 4.00
> Dec  2 11:46:53 automation weewx[9263]: vantage: Gentle wake up of console
> successful
> Dec  2 11:46:53 automation weewx[9263]: vantage: Hardware type is 16
> Dec  2 11:46:53 automation weewx[9263]: vantage: ISS ID is 1
> Dec  2 11:46:53 automation weewx[9263]: vantage: Hardware name: Vantage
> Pro2
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading service
> weewx.engine.StdTimeSynch
> Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service
> weewx.engine.StdTimeSynch
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading service
> weewx.engine.StdConvert
> Dec  2 11:46:53 automation weewx[9263]: engine: StdConvert target unit is
> 0x1
> Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service
> weewx.engine.StdConvert
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading service
> weewx.engine.StdCalibrate
> Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service
> weewx.engine.StdCalibrate
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading service
> weewx.engine.StdQC
> Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service
> weewx.engine.StdQC
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading service
> weewx.wxservices.StdWXCalculate
> Dec  2 11:46:53 automation weewx[9263]: 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
> Dec  2 11:46:53 automation weewx[9263]: wxcalculate: The following
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service
> weewx.wxservices.StdWXCalculate
> Dec  2 11:46:53 automation weewx[9263]: engine: Loading service
> weewx.engine.StdArchive
> Dec  2 11:46:53 automation weewx[9263]: engine: Archive will use data
> binding wx_binding
> Dec  2 11:46:53 automation weewx[9263]: engine: Record generation will be
> attempted in 'hardware'
> Dec  2 11:46:53 automation weewx[9263]: engine: Using archive interval of
> 300 seconds (specified by hardware)
> Dec  2 11:46:53 automation weewx[9263]: engine: Use LOOP data in hi/low
> calculations: 1
> Dec  2 11:46:53 automation weewx[9263]: manager: Daily summary version is
> 2.0
> Dec  2 11:46:53 automation weewx[9263]: engine: Using binding 'wx_binding'
> to database 'weewx.sdb'
> Dec  2 11:46:53 automation weewx[9263]: manager: Starting backfill of
> daily summaries
> Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service
> 

[weewx-user] davis vantage not outputing data to either WU or mqtt

[Daniel Smith]

Hi 
I've been running for a while with no issues publishing to both 
weather-underground and through MQTT to other parts of my system.
two (2) days ago output stopped.
I'm using Rpi 3. with a USB connection to davis console. I've reinstalled 
weewx with no output success.
weewx seems to be running ok.
Can't find anything wrong with hardware, iv'e also tries different usb 
port, new RPi, different USB cable. I've connected minicom to /dev/ttyUSB0 
port activity happening on it.
My MQTT stopped at the same time.

I can't see any issues in syslog. but I also don't know what to look for

below out from syslog:

Dec  2 11:46:53 automation systemd[1]: Starting LSB: weewx weather system...
Dec  2 11:46:53 automation weewx[9259]: engine: Initializing weewx version 
3.8.2
Dec  2 11:46:53 automation weewx[9259]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Dec  2 11:46:53 automation weewx[9259]: engine: Platform 
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Dec  2 11:46:53 automation weewx[9259]: engine: Locale is 'en_GB.UTF-8'
Dec  2 11:46:53 automation weewx[9259]: engine: pid file is 
/var/run/weewx.pid
Dec  2 11:46:53 automation weewx[9263]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec  2 11:46:53 automation weewx[9263]: engine: Debug is 1
Dec  2 11:46:53 automation weewx[9263]: engine: Initializing engine
Dec  2 11:46:53 automation weewx[9263]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Dec  2 11:46:53 automation weewx[9242]: Starting weewx weather system: 
weewx.
Dec  2 11:46:53 automation systemd[1]: Started LSB: weewx weather system.
Dec  2 11:46:53 automation weewx[9263]: vantage: Driver version is 3.0.11
Dec  2 11:46:53 automation weewx[9263]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
Dec  2 11:46:53 automation weewx[9263]: vantage: Gentle wake up of console 
successful
Dec  2 11:46:53 automation weewx[9263]: vantage: Hardware type is 16
Dec  2 11:46:53 automation weewx[9263]: vantage: ISS ID is 1
Dec  2 11:46:53 automation weewx[9263]: vantage: Hardware name: Vantage Pro2
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.engine.StdTimeSynch
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.engine.StdConvert
Dec  2 11:46:53 automation weewx[9263]: engine: StdConvert target unit is 
0x1
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.engine.StdConvert
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.engine.StdCalibrate
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.engine.StdCalibrate
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.engine.StdQC
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.engine.StdQC
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Dec  2 11:46:53 automation weewx[9263]: 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
Dec  2 11:46:53 automation weewx[9263]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.engine.StdArchive
Dec  2 11:46:53 automation weewx[9263]: engine: Archive will use data 
binding wx_binding
Dec  2 11:46:53 automation weewx[9263]: engine: Record generation will be 
attempted in 'hardware'
Dec  2 11:46:53 automation weewx[9263]: engine: Using archive interval of 
300 seconds (specified by hardware)
Dec  2 11:46:53 automation weewx[9263]: engine: Use LOOP data in hi/low 
calculations: 1
Dec  2 11:46:53 automation weewx[9263]: manager: Daily summary version is 
2.0
Dec  2 11:46:53 automation weewx[9263]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Dec  2 11:46:53 automation weewx[9263]: manager: Starting backfill of daily 
summaries
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.engine.StdArchive
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.restx.StdStationRegistry
Dec  2 11:46:53 automation weewx[9263]: restx: StationRegistry: 
Registration not requested.
Dec  2 11:46:53 automation weewx[9263]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Dec  2 11:46:53 automation weewx[9263]: engine: Loading service 
weewx.restx.StdWunderground
Dec  2 11:46:53 

[weewx-user] Re: WMR200-driver shutdown directly after startup

[Per Edström]

I don't seem to have that file..

-- 
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: Belchertown skin for weewx now available!

[Pat]

Attached is what I'm seeing when I try to access 
http://weather.w0avq.org/json/day.json directly. 

On Saturday, December 1, 2018 at 2:21:07 PM UTC-5, Pat wrote:
>
> Having your site URL is helpful and this is an interesting one. When I try 
> to access your chart data directly via 
> http://weather.w0avq.org/json/day.json I'm seeing in the Chrome Console a 
> blocked page to sedoparking. Do you know what this is? Is this your web 
> hosting provider?
>
> The other directories look good, so maybe the /json/ folder is missing and 
> your provider is trying to send a 404 in a weird way? Try putting an 
> index.html with a "hello world" inside of it to see *something* work in 
> http://weather.w0avq.org/json/...
>
> Admittedly, I don't have any experience with the ftpuploader - so there 
> very well could be a fault with that extension but I'm not familiar with. 
> Your NOAA reports aren't working either - so it could be something with the 
> ftpuploader. Can you set debug = 1 in weewx.conf and see if it gives any 
> clues?
>
> On Saturday, December 1, 2018 at 8:40:51 AM UTC-5, John Clark wrote:
>>
>> Did as directed and so far all is wonderfully functional except the 
>> graphs which are not available either through localhost or remotely, and 
>> the monthly reports only show the current month no matter which one I 
>> choose. I am convinced that I have one (or more) directories looking at the 
>> wrong place, just haven't tracked it down yet. All info at CWOP,  PWS, 
>> WUnderground, and weathercloud seem to be correctly updated which (to me) 
>> further states it is a local problem, something pointing the wrong 
>> direction. For instance, year.json is locally generated just fine 
>> (apparently) and uploaded just fine, but I cannot read it either locally or 
>> on the website. This is particularly disquieting as I decided to quit 
>> shaving my head and it is getting long enough to pull out. Just in case it 
>> will help the website is weather.w0avq.org
>>
>> Dec  1 06:20:22 Optiplex weewx[22287]: manager: Added record 2018-12-01 
>> 06:20:00 CST (1543666800) to database 'weewx.sdb'
>> Dec  1 06:20:22 Optiplex weewx[22287]: manager: Added record 2018-12-01 
>> 06:20:00 CST (1543666800) to daily summary in 'weewx.sdb'
>> Dec  1 06:20:22 Optiplex weewx[22287]: restx: StationRegistry: wait 
>> interval (2400 < 604800) has not passed for record 2018-12-01 06:20:00 CST 
>> (1543666800)
>> Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Running reports for 
>> latest time in the database.
>> Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Running report 
>> StandardReport
>> Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Found configuration 
>> file /etc/weewx/skins/Belchertown/skin.conf for report StandardReport
>> Dec  1 06:20:22 Optiplex weewx[22287]: cheetahgenerator: using search 
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
>> 'user.belchertown.getData']
>> Dec  1 06:20:22 Optiplex weewx[22287]: acurite: Found station at bus= 
>> device=
>> Dec  1 06:20:22 Optiplex weewx[22287]: manager: Daily summary version is 
>> 2.0
>> Dec  1 06:20:22 Optiplex upowerd[1092]: unhandled action 'bind' on 
>> /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0
>> Dec  1 06:20:22 Optiplex weewx[22287]: acurite: next read in 18 seconds
>> Dec  1 06:20:22 Optiplex upowerd[1092]: unhandled action 'unbind' on 
>> /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0
>> Dec  1 06:20:22 Optiplex weewx[22287]: restx: CWOP: Connected to server 
>> cwop.aprs.net:14580
>> Dec  1 06:20:23 Optiplex weewx[22287]: cheetahgenerator: Generated 13 
>> files for report StandardReport in 0.27 seconds
>> Dec  1 06:20:23 Optiplex weewx[22287]: copygenerator: copied 1 files to 
>> /var/www/html/weewx
>> Dec  1 06:20:23 Optiplex weewx[22287]: reportengine: Running report 
>> Highcharts_Belchertown
>> Dec  1 06:20:23 Optiplex weewx[22287]: reportengine: Found configuration 
>> file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report 
>> Highcharts_Belchertown
>> Dec  1 06:20:23 Optiplex weewx[22287]: cheetahgenerator: using search 
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
>> 'user.belchertown_highchartsSearchX.highchartsDay', 
>> 'user.belchertown_highchartsSearchX.highchartsWeek', 
>> 'user.belchertown_highchartsSearchX.highchartsMonth', 
>> 'user.belchertown_highchartsSearchX.highchartsYear']
>> Dec  1 06:20:23 Optiplex weewx[22287]: manager: Daily summary version is 
>> 2.0
>> Dec  1 06:20:23 Optiplex weewx[22287]: restx: CWOP: Published record 
>> 2018-12-01 06:20:00 CST (1543666800)
>> Dec  1 06:20:23 Optiplex weewx[22287]: restx: AWEKAS: Published 

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Having your site URL is helpful and this is an interesting one. When I try 
to access your chart data directly 
via http://weather.w0avq.org/json/day.json I'm seeing in the Chrome Console 
a blocked page to sedoparking. Do you know what this is? Is this your web 
hosting provider?

The other directories look good, so maybe the /json/ folder is missing and 
your provider is trying to send a 404 in a weird way? Try putting an 
index.html with a "hello world" inside of it to see *something* work 
in http://weather.w0avq.org/json/...

Admittedly, I don't have any experience with the ftpuploader - so there 
very well could be a fault with that extension but I'm not familiar with. 
Your NOAA reports aren't working either - so it could be something with the 
ftpuploader. Can you set debug = 1 in weewx.conf and see if it gives any 
clues?

On Saturday, December 1, 2018 at 8:40:51 AM UTC-5, John Clark wrote:
>
> Did as directed and so far all is wonderfully functional except the graphs 
> which are not available either through localhost or remotely, and the 
> monthly reports only show the current month no matter which one I choose. I 
> am convinced that I have one (or more) directories looking at the wrong 
> place, just haven't tracked it down yet. All info at CWOP,  PWS, 
> WUnderground, and weathercloud seem to be correctly updated which (to me) 
> further states it is a local problem, something pointing the wrong 
> direction. For instance, year.json is locally generated just fine 
> (apparently) and uploaded just fine, but I cannot read it either locally or 
> on the website. This is particularly disquieting as I decided to quit 
> shaving my head and it is getting long enough to pull out. Just in case it 
> will help the website is weather.w0avq.org
>
> Dec  1 06:20:22 Optiplex weewx[22287]: manager: Added record 2018-12-01 
> 06:20:00 CST (1543666800) to database 'weewx.sdb'
> Dec  1 06:20:22 Optiplex weewx[22287]: manager: Added record 2018-12-01 
> 06:20:00 CST (1543666800) to daily summary in 'weewx.sdb'
> Dec  1 06:20:22 Optiplex weewx[22287]: restx: StationRegistry: wait 
> interval (2400 < 604800) has not passed for record 2018-12-01 06:20:00 CST 
> (1543666800)
> Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Running reports for 
> latest time in the database.
> Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Running report 
> StandardReport
> Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Found configuration 
> file /etc/weewx/skins/Belchertown/skin.conf for report StandardReport
> Dec  1 06:20:22 Optiplex weewx[22287]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown.getData']
> Dec  1 06:20:22 Optiplex weewx[22287]: acurite: Found station at bus= 
> device=
> Dec  1 06:20:22 Optiplex weewx[22287]: manager: Daily summary version is 
> 2.0
> Dec  1 06:20:22 Optiplex upowerd[1092]: unhandled action 'bind' on 
> /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0
> Dec  1 06:20:22 Optiplex weewx[22287]: acurite: next read in 18 seconds
> Dec  1 06:20:22 Optiplex upowerd[1092]: unhandled action 'unbind' on 
> /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0
> Dec  1 06:20:22 Optiplex weewx[22287]: restx: CWOP: Connected to server 
> cwop.aprs.net:14580
> Dec  1 06:20:23 Optiplex weewx[22287]: cheetahgenerator: Generated 13 
> files for report StandardReport in 0.27 seconds
> Dec  1 06:20:23 Optiplex weewx[22287]: copygenerator: copied 1 files to 
> /var/www/html/weewx
> Dec  1 06:20:23 Optiplex weewx[22287]: reportengine: Running report 
> Highcharts_Belchertown
> Dec  1 06:20:23 Optiplex weewx[22287]: reportengine: Found configuration 
> file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report 
> Highcharts_Belchertown
> Dec  1 06:20:23 Optiplex weewx[22287]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown_highchartsSearchX.highchartsDay', 
> 'user.belchertown_highchartsSearchX.highchartsWeek', 
> 'user.belchertown_highchartsSearchX.highchartsMonth', 
> 'user.belchertown_highchartsSearchX.highchartsYear']
> Dec  1 06:20:23 Optiplex weewx[22287]: manager: Daily summary version is 
> 2.0
> Dec  1 06:20:23 Optiplex weewx[22287]: restx: CWOP: Published record 
> 2018-12-01 06:20:00 CST (1543666800)
> Dec  1 06:20:23 Optiplex weewx[22287]: restx: AWEKAS: Published record 
> 2018-12-01 06:20:00 CST (1543666800)
> Dec  1 06:20:24 Optiplex weewx[22287]: cheetahgenerator: Generated 4 files 
> for report Highcharts_Belchertown in 1.84 seconds
> Dec  1 06:20:24 Optiplex weewx[22287]: copygenerator: copied 0 files to 
> 

[weewx-user] Weewx on OSX High Sierra (10.13.6), newbie

[Tom Buckler]

Hello

Attempting to run a new installation of Weewx 3.8.2 on OSX 10.13.6 High 
Sierra. Python 2.7.10. Weather station is an Acurite 5-in-1.


*administrator on server6: /users/shared/weewx$* ./bin/weewxd weewx.conf

Traceback (most recent call last):

  File "./bin/weewxd", line 64, in 

weewx.engine.main(options, args)

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 877, in main

engine.run()

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 188, in run

for packet in self.console.genLoopPackets():

  File "/Users/Shared/weewx/bin/weewx/drivers/acurite.py", line 477, in 
genLoopPackets

with Station() as station:

  File "/Users/Shared/weewx/bin/weewx/drivers/acurite.py", line 598, in 
__enter__

self.open()

  File "/Users/Shared/weewx/bin/weewx/drivers/acurite.py", line 623, in open

self.handle.detachKernelDriver(interface)

  File "/Library/Python/2.7/site-packages/usb/legacy.py", line 307, in 
detachKernelDriver

self.dev.detach_kernel_driver(interface)

  File "/Library/Python/2.7/site-packages/usb/core.py", line 1077, in 
detach_kernel_driver

interface)

  File "/Library/Python/2.7/site-packages/usb/backend/libusb1.py", line 
902, in detach_kernel_driver

_check(self.lib.libusb_detach_kernel_driver(dev_handle.handle, intf))

  File "/Library/Python/2.7/site-packages/usb/backend/libusb1.py", line 
593, in _check

raise NotImplementedError(_strerror(ret))

NotImplementedError: Operation not supported or unimplemented on this 
platform


I can find some old references to libusb issues, but I did install libusb 
1.0.9. If the legacy version of libusb is still required I've not been able 
to find a package for it.

Installation followed was from weewx-3.8.2/docs/macos.htm where I had to 
make 2 modifications:

1) install pysqlite with the --user option

2) install Pillow instead of PIL 


Any insight is appreciated,
Thanks
Tom

-- 
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: weewx abends with no reason

[Gary Hopkins]

Will do my best and see what I can do.

Thanks

Gary

On Saturday, 1 December 2018 15:34:36 UTC, Thomas Keffer wrote:
>
> It could also be a kernel problem. It would be most helpful if the other 
> RPi is running a different kernel.
>
> -tk
>
> On Sat, Dec 1, 2018 at 7:30 AM Gary Hopkins  > wrote:
>
>> Hi,
>>
>> Thanks for the info. I have a new Pi 3+ coming this afternoon as I was 
>> worried the one I have was busted in some way. I will post back once that's 
>> arrived and I've had a chance to try it out. I've also been given a Pi 
>> image from someone who already has this up and running and working so all 
>> else fails I can give that a go.
>>
>> I could run it in a VM too I guess but I'd rather crack it on the Pi 
>> first.
>>
>> Cheers
>>
>> Gary
>>
>> On Saturday, 1 December 2018 15:04:13 UTC, Thomas Keffer wrote:
>>>
>>> They don't happen very often, but usually these abrupt crashes without 
>>> anything in the log is due to a low-level driver or hardware failure. 
>>> Something on the USB bus. 
>>>
>>> Do you have another RPi or, even better, a x86-based PC you can try it 
>>> on?
>>>
>>> -tk
>>>
>>> On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins  wrote:
>>>
 Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1

 Line 6 of the capture you're replying to.
 weewx in not running
 Disabled the cron

 Thanks for the help.

 G

 On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:
>
>
>
> On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:
>>
>>
>> sudo weewxd /etc/weewx/weewx.conf
>>
>> From the command line itself it doesn't show anything until it starts 
>> taking in data and then I get
>>
>> REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 
>> 30.4319672166, appTemp: 52.5740750576, barometer: 30.28595518, 
>> cloudbase: 
>> 2734.00530669, dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 
>> 44.0235577061, ET: 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, 
>> inDewpoint: 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, 
>> maxSolarRad: None, outHumidity: 69, outTemp: 53.96, pressure: 
>> 29.9227363337, radiation: 3.38595106551, rain: 0.0, rainRate: 0, 
>> usUnits: 
>> 1, UV: 0, windchill: 53.96, windDir: None, windGust: 0.0, windGustDir: 
>> None, windrun: 0.0, windSpeed: 0.0
>>
>> Which repeats (I can post them all but they really are just more of 
>> the same) and then stops and returns me a to a command prompt with no 
>> massages.
>>
>
> you should try setting debug=1
>
> be sure that weewx is not already running, and be sure that your cron 
> task is disabled while you are running weewx directly.
>
> @aussisusan (or some enterprising python sleuth) will probably have to 
> help you at this point.  you'll have to check the code for cases where a 
> try-except block is catching all exceptions, not just the intended 
> exception.  a generic catch block like that will hide the exception trace 
> that would otherwise tell you where the failure is coming from.
>
> it is also possible that your system is shutting down the weewxd 
> process, but that is typically accompanied by some kind of output from 
> the 
> system, even if it is simply 'Killed'.
>
> m
>
 -- 
 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] Re: weewx abends with no reason

[Gary Hopkins]

Hi,

Hahaha yeh it's not as bad as it seems! Theres a 12+ month or so gap in the 
middle at some point where it wasn't connected as I was redecorating. At 
some point it's going to skip almost a year and catch up.

Thing is, it's only collecting for about 1 min before it falls over so it's 
only incrementing the sql file about 40k a time. I've also tested the 
throughput of the cards and they manage 5MB/s write and 15MB/s read so I 
don't think it's anything to do with volume or throughput.

Cheers

G

On Saturday, 1 December 2018 15:17:31 UTC, Andrew Milner wrote:
>
> I have just noticed that the records being retrieved at startup are at one 
> minute intervals from April 2017.  How much data can be stored in the HP at 
> one minute intervals??  Could just be a data overload possibly!!
>
>
> On Saturday, 1 December 2018 17:04:13 UTC+2, Thomas Keffer wrote:
>>
>> They don't happen very often, but usually these abrupt crashes without 
>> anything in the log is due to a low-level driver or hardware failure. 
>> Something on the USB bus. 
>>
>> Do you have another RPi or, even better, a x86-based PC you can try it on?
>>
>> -tk
>>
>> On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins  wrote:
>>
>>> Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1
>>>
>>> Line 6 of the capture you're replying to.
>>> weewx in not running
>>> Disabled the cron
>>>
>>> Thanks for the help.
>>>
>>> G
>>>
>>> On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:



 On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:
>
>
> sudo weewxd /etc/weewx/weewx.conf
>
> From the command line itself it doesn't show anything until it starts 
> taking in data and then I get
>
> REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166, 
> appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669, 
> dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET: 
> 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint: 
> 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad: 
> None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, 
> radiation: 
> 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 
> 53.96, 
> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 
> 0.0
>
> Which repeats (I can post them all but they really are just more of 
> the same) and then stops and returns me a to a command prompt with no 
> massages.
>

 you should try setting debug=1

 be sure that weewx is not already running, and be sure that your cron 
 task is disabled while you are running weewx directly.

 @aussisusan (or some enterprising python sleuth) will probably have to 
 help you at this point.  you'll have to check the code for cases where a 
 try-except block is catching all exceptions, not just the intended 
 exception.  a generic catch block like that will hide the exception trace 
 that would otherwise tell you where the failure is coming from.

 it is also possible that your system is shutting down the weewxd 
 process, but that is typically accompanied by some kind of output from the 
 system, even if it is simply 'Killed'.

 m

>>> -- 
>>> 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] Re: weewx abends with no reason

[Thomas Keffer]

It could also be a kernel problem. It would be most helpful if the other
RPi is running a different kernel.

-tk

On Sat, Dec 1, 2018 at 7:30 AM Gary Hopkins  wrote:

> Hi,
>
> Thanks for the info. I have a new Pi 3+ coming this afternoon as I was
> worried the one I have was busted in some way. I will post back once that's
> arrived and I've had a chance to try it out. I've also been given a Pi
> image from someone who already has this up and running and working so all
> else fails I can give that a go.
>
> I could run it in a VM too I guess but I'd rather crack it on the Pi first.
>
> Cheers
>
> Gary
>
> On Saturday, 1 December 2018 15:04:13 UTC, Thomas Keffer wrote:
>>
>> They don't happen very often, but usually these abrupt crashes without
>> anything in the log is due to a low-level driver or hardware failure.
>> Something on the USB bus.
>>
>> Do you have another RPi or, even better, a x86-based PC you can try it on?
>>
>> -tk
>>
>> On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins  wrote:
>>
>>> Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1
>>>
>>> Line 6 of the capture you're replying to.
>>> weewx in not running
>>> Disabled the cron
>>>
>>> Thanks for the help.
>>>
>>> G
>>>
>>> On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:



 On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:
>
>
> sudo weewxd /etc/weewx/weewx.conf
>
> From the command line itself it doesn't show anything until it starts
> taking in data and then I get
>
> REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166,
> appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669,
> dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET:
> 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint:
> 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad:
> None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation:
> 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 
> 53.96,
> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed:
> 0.0
>
> Which repeats (I can post them all but they really are just more of
> the same) and then stops and returns me a to a command prompt with no
> massages.
>

 you should try setting debug=1

 be sure that weewx is not already running, and be sure that your cron
 task is disabled while you are running weewx directly.

 @aussisusan (or some enterprising python sleuth) will probably have to
 help you at this point.  you'll have to check the code for cases where a
 try-except block is catching all exceptions, not just the intended
 exception.  a generic catch block like that will hide the exception trace
 that would otherwise tell you where the failure is coming from.

 it is also possible that your system is shutting down the weewxd
 process, but that is typically accompanied by some kind of output from the
 system, even if it is simply 'Killed'.

 m

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

-- 
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: weewx abends with no reason

[Gary Hopkins]

Hi,

Thanks for the info. I have a new Pi 3+ coming this afternoon as I was 
worried the one I have was busted in some way. I will post back once that's 
arrived and I've had a chance to try it out. I've also been given a Pi 
image from someone who already has this up and running and working so all 
else fails I can give that a go.

I could run it in a VM too I guess but I'd rather crack it on the Pi first.

Cheers

Gary

On Saturday, 1 December 2018 15:04:13 UTC, Thomas Keffer wrote:
>
> They don't happen very often, but usually these abrupt crashes without 
> anything in the log is due to a low-level driver or hardware failure. 
> Something on the USB bus. 
>
> Do you have another RPi or, even better, a x86-based PC you can try it on?
>
> -tk
>
> On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins  > wrote:
>
>> Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1
>>
>> Line 6 of the capture you're replying to.
>> weewx in not running
>> Disabled the cron
>>
>> Thanks for the help.
>>
>> G
>>
>> On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:
>>>
>>>
>>>
>>> On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:


 sudo weewxd /etc/weewx/weewx.conf

 From the command line itself it doesn't show anything until it starts 
 taking in data and then I get

 REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166, 
 appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669, 
 dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET: 
 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint: 
 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad: 
 None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation: 
 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 
 53.96, 
 windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 
 0.0

 Which repeats (I can post them all but they really are just more of the 
 same) and then stops and returns me a to a command prompt with no massages.

>>>
>>> you should try setting debug=1
>>>
>>> be sure that weewx is not already running, and be sure that your cron 
>>> task is disabled while you are running weewx directly.
>>>
>>> @aussisusan (or some enterprising python sleuth) will probably have to 
>>> help you at this point.  you'll have to check the code for cases where a 
>>> try-except block is catching all exceptions, not just the intended 
>>> exception.  a generic catch block like that will hide the exception trace 
>>> that would otherwise tell you where the failure is coming from.
>>>
>>> it is also possible that your system is shutting down the weewxd 
>>> process, but that is typically accompanied by some kind of output from the 
>>> system, even if it is simply 'Killed'.
>>>
>>> m
>>>
>> -- 
>> 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] Re: weewx abends with no reason

[Andrew Milner]

I have just noticed that the records being retrieved at startup are at one 
minute intervals from April 2017.  How much data can be stored in the HP at 
one minute intervals??  Could just be a data overload possibly!!


On Saturday, 1 December 2018 17:04:13 UTC+2, Thomas Keffer wrote:
>
> They don't happen very often, but usually these abrupt crashes without 
> anything in the log is due to a low-level driver or hardware failure. 
> Something on the USB bus. 
>
> Do you have another RPi or, even better, a x86-based PC you can try it on?
>
> -tk
>
> On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins  > wrote:
>
>> Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1
>>
>> Line 6 of the capture you're replying to.
>> weewx in not running
>> Disabled the cron
>>
>> Thanks for the help.
>>
>> G
>>
>> On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:
>>>
>>>
>>>
>>> On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:


 sudo weewxd /etc/weewx/weewx.conf

 From the command line itself it doesn't show anything until it starts 
 taking in data and then I get

 REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166, 
 appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669, 
 dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET: 
 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint: 
 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad: 
 None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation: 
 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 
 53.96, 
 windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 
 0.0

 Which repeats (I can post them all but they really are just more of the 
 same) and then stops and returns me a to a command prompt with no massages.

>>>
>>> you should try setting debug=1
>>>
>>> be sure that weewx is not already running, and be sure that your cron 
>>> task is disabled while you are running weewx directly.
>>>
>>> @aussisusan (or some enterprising python sleuth) will probably have to 
>>> help you at this point.  you'll have to check the code for cases where a 
>>> try-except block is catching all exceptions, not just the intended 
>>> exception.  a generic catch block like that will hide the exception trace 
>>> that would otherwise tell you where the failure is coming from.
>>>
>>> it is also possible that your system is shutting down the weewxd 
>>> process, but that is typically accompanied by some kind of output from the 
>>> system, even if it is simply 'Killed'.
>>>
>>> m
>>>
>> -- 
>> 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] Re: weewx abends with no reason

[Thomas Keffer]

They don't happen very often, but usually these abrupt crashes without
anything in the log is due to a low-level driver or hardware failure.
Something on the USB bus.

Do you have another RPi or, even better, a x86-based PC you can try it on?

-tk

On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins  wrote:

> Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1
>
> Line 6 of the capture you're replying to.
> weewx in not running
> Disabled the cron
>
> Thanks for the help.
>
> G
>
> On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:
>>
>>
>>
>> On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:
>>>
>>>
>>> sudo weewxd /etc/weewx/weewx.conf
>>>
>>> From the command line itself it doesn't show anything until it starts
>>> taking in data and then I get
>>>
>>> REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166,
>>> appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669,
>>> dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET:
>>> 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint:
>>> 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad:
>>> None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation:
>>> 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 53.96,
>>> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed:
>>> 0.0
>>>
>>> Which repeats (I can post them all but they really are just more of the
>>> same) and then stops and returns me a to a command prompt with no massages.
>>>
>>
>> you should try setting debug=1
>>
>> be sure that weewx is not already running, and be sure that your cron
>> task is disabled while you are running weewx directly.
>>
>> @aussisusan (or some enterprising python sleuth) will probably have to
>> help you at this point.  you'll have to check the code for cases where a
>> try-except block is catching all exceptions, not just the intended
>> exception.  a generic catch block like that will hide the exception trace
>> that would otherwise tell you where the failure is coming from.
>>
>> it is also possible that your system is shutting down the weewxd process,
>> but that is typically accompanied by some kind of output from the system,
>> even if it is simply 'Killed'.
>>
>> m
>>
> --
> 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.
>

-- 
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: weewx abends with no reason

[Gary Hopkins]

Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1

Line 6 of the capture you're replying to.
weewx in not running
Disabled the cron

Thanks for the help.

G

On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote:
>
>
>
> On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:
>>
>>
>> sudo weewxd /etc/weewx/weewx.conf
>>
>> From the command line itself it doesn't show anything until it starts 
>> taking in data and then I get
>>
>> REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166, 
>> appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669, 
>> dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET: 
>> 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint: 
>> 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad: 
>> None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation: 
>> 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 53.96, 
>> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 
>> 0.0
>>
>> Which repeats (I can post them all but they really are just more of the 
>> same) and then stops and returns me a to a command prompt with no massages.
>>
>
> you should try setting debug=1
>
> be sure that weewx is not already running, and be sure that your cron task 
> is disabled while you are running weewx directly.
>
> @aussisusan (or some enterprising python sleuth) will probably have to 
> help you at this point.  you'll have to check the code for cases where a 
> try-except block is catching all exceptions, not just the intended 
> exception.  a generic catch block like that will hide the exception trace 
> that would otherwise tell you where the failure is coming from.
>
> it is also possible that your system is shutting down the weewxd process, 
> but that is typically accompanied by some kind of output from the system, 
> even if it is simply 'Killed'.
>
> m
>

-- 
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: weewx abends with no reason

[mwall]

On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote:
>
>
> sudo weewxd /etc/weewx/weewx.conf
>
> From the command line itself it doesn't show anything until it starts 
> taking in data and then I get
>
> REC:2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166, 
> appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669, 
> dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET: 
> 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint: 
> 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad: 
> None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation: 
> 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: 53.96, 
> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 
> 0.0
>
> Which repeats (I can post them all but they really are just more of the 
> same) and then stops and returns me a to a command prompt with no massages.
>

you should try setting debug=1

be sure that weewx is not already running, and be sure that your cron task 
is disabled while you are running weewx directly.

@aussisusan (or some enterprising python sleuth) will probably have to help 
you at this point.  you'll have to check the code for cases where a 
try-except block is catching all exceptions, not just the intended 
exception.  a generic catch block like that will hide the exception trace 
that would otherwise tell you where the failure is coming from.

it is also possible that your system is shutting down the weewxd process, 
but that is typically accompanied by some kind of output from the system, 
even if it is simply 'Killed'.

m

-- 
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: weewx abends with no reason

[Gary Hopkins]

Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Initializing weewx version 
3.8.2
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Platform 
Linux-4.14.79+-armv6l-with-debian-9.6
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Locale is 'en_GB.UTF-8'
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Initializing engine
Dec  1 14:18:16 raspberrypi weewx[2088]: engine: Loading station type 
HP1000 (user.HP1000)
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: HP1000 Starting
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Using user-defined 
broadcast mask - 172.17.10.255
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Address Mask = 
172.17.10.255
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Retry count = 5.00
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Socket timeout = 5.00
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Loop delay = 10.00
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Retry Wait = 10.00
Dec  1 14:18:16 raspberrypi weewx[2088]: HP1000: Max Retry = 3.00
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.engine.StdTimeSynch
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.engine.StdConvert
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: StdConvert target unit is 
0x1
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.engine.StdConvert
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.engine.StdCalibrate
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.engine.StdCalibrate
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.engine.StdQC
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.engine.StdQC
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Dec  1 14:18:17 raspberrypi weewx[2088]: 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
Dec  1 14:18:17 raspberrypi weewx[2088]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.engine.StdArchive
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Archive will use data 
binding wx_binding
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Record generation will be 
attempted in 'software'
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Use LOOP data in hi/low 
calculations: 1
Dec  1 14:18:17 raspberrypi weewx[2088]: manager: Daily summary version is 
2.0
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Dec  1 14:18:17 raspberrypi weewx[2088]: manager: Starting backfill of 
daily summaries
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.engine.StdArchive
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.restx.StdStationRegistry
Dec  1 14:18:17 raspberrypi weewx[2088]: restx: StationRegistry: 
Registration not requested.
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.restx.StdWunderground
Dec  1 14:18:17 raspberrypi weewx[2088]: restx: Wunderground: Posting not 
enabled.
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.restx.StdWunderground
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.restx.StdPWSweather
Dec  1 14:18:17 raspberrypi weewx[2088]: restx: PWSweather: Posting not 
enabled.
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.restx.StdPWSweather
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 
weewx.restx.StdCWOP
Dec  1 14:18:17 raspberrypi weewx[2088]: restx: CWOP: Posting not enabled.
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Finished loading service 
weewx.restx.StdCWOP
Dec  1 14:18:17 raspberrypi weewx[2088]: engine: Loading service 

[weewx-user] Re: weewx abends with no reason

[mwall]

On Saturday, December 1, 2018 at 5:27:09 AM UTC-5, Gary Hopkins wrote:
>
> Original Rasperry Pi Model B
> 8GB Class 4 SD Card
> Latest Raspian installed through Noobs 3
> Latest weewx installed following online guide through apt
> Aercus WeatherRanger (WS1000 clone)
> Used https://github.com/AussieSusan/HP1000 custom driver to grab events 
> over WiFi
>
>
gary,

please run weewx directly (e.g., `weewxd /etc/weewx.conf`) instead of as a 
daemon.

there might be an exception that is being hidden when you run as daemon.

m 

-- 
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: weewx abends with no reason

[Gary Hopkins]

On Saturday, 1 December 2018 10:51:28 UTC, Andrew Milner wrote:
>
> First of all get rid of the HUP in Cron - that does not help at all
>
> Both log sections seem to show more than pne occurrence of weewx to be 
> running - look at the PIDs.  You can only have one.
>
>
> Hi,

Actually heres a snippet from further in the log where the cron fires one 
second after the minute mid download when weewx is actually working. As you 
can see it does nothing

Dec  1 13:52:00 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:54:40 BST (1491404080) to daily summary in 'weewx.sdb'
Dec  1 13:52:00 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:55:40 BST (1491404140) to database 'weewx.sdb'
Dec  1 13:52:01 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:55:40 BST (1491404140) to daily summary in 'weewx.sdb'
Dec  1 13:52:01 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:56:40 BST (1491404200) to database 'weewx.sdb'
Dec  1 13:52:01 raspberrypi CRON[1243]: (pi) CMD (/home/pi/restart_weewx)
Dec  1 13:52:01 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:56:40 BST (1491404200) to daily summary in 'weewx.sdb'
Dec  1 13:52:01 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:57:40 BST (1491404260) to database 'weewx.sdb'
Dec  1 13:52:02 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:57:40 BST (1491404260) to daily summary in 'weewx.sdb'
Dec  1 13:52:02 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
15:58:40 BST (1491404320) to database 'weewx.sdb'

Then after it hangs you get this

Dec  1 13:52:17 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
16:27:40 BST (1491406060) to database 'weewx.sdb'
Dec  1 13:52:17 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
16:27:40 BST (1491406060) to daily summary in 'weewx.sdb'
Dec  1 13:52:17 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
16:28:40 BST (1491406120) to database 'weewx.sdb'
Dec  1 13:52:17 raspberrypi weewx[1230]: manager: Added record 2017-04-05 
16:28:40 BST (1491406120) to daily summary in 'weewx.sdb'
Dec  1 13:53:01 raspberrypi CRON[1257]: (pi) CMD (/home/pi/restart_weewx)
Dec  1 13:53:02 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...
Dec  1 13:53:02 raspberrypi weewx[1268]: Stopping weewx weather system: 
weewx not running
Dec  1 13:53:02 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
Dec  1 13:53:02 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...

Again the cron fires one second past the minute but this time, as weewx has 
already crashed, it gets restarted.

Hope that better explains what's going on.

Thanks

G

-- 
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: Belchertown skin for weewx now available!

[John Clark]

Did as directed and so far all is wonderfully functional except the 
graphs which are not available either through localhost or remotely, and 
the monthly reports only show the current month no matter which one I 
choose. I am convinced that I have one (or more) directories looking at 
the wrong place, just haven't tracked it down yet. All info at CWOP,  
PWS, WUnderground, and weathercloud seem to be correctly updated which 
(to me) further states it is a local problem, something pointing the 
wrong direction. For instance, year.json is locally generated just fine 
(apparently) and uploaded just fine, but I cannot read it either locally 
or on the website. This is particularly disquieting as I decided to quit 
shaving my head and it is getting long enough to pull out. Just in case 
it will help the website is weather.w0avq.org


Dec  1 06:20:22 Optiplex weewx[22287]: manager: Added record 2018-12-01 
06:20:00 CST (1543666800) to database 'weewx.sdb'
Dec  1 06:20:22 Optiplex weewx[22287]: manager: Added record 2018-12-01 
06:20:00 CST (1543666800) to daily summary in 'weewx.sdb'
Dec  1 06:20:22 Optiplex weewx[22287]: restx: StationRegistry: wait 
interval (2400 < 604800) has not passed for record 2018-12-01 06:20:00 
CST (1543666800)
Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Running reports for 
latest time in the database.
Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Running report 
StandardReport
Dec  1 06:20:22 Optiplex weewx[22287]: reportengine: Found configuration 
file /etc/weewx/skins/Belchertown/skin.conf for report StandardReport
Dec  1 06:20:22 Optiplex weewx[22287]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getData']
Dec  1 06:20:22 Optiplex weewx[22287]: acurite: Found station at bus= 
device=

Dec  1 06:20:22 Optiplex weewx[22287]: manager: Daily summary version is 2.0
Dec  1 06:20:22 Optiplex upowerd[1092]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0

Dec  1 06:20:22 Optiplex weewx[22287]: acurite: next read in 18 seconds
Dec  1 06:20:22 Optiplex upowerd[1092]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0
Dec  1 06:20:22 Optiplex weewx[22287]: restx: CWOP: Connected to server 
cwop.aprs.net:14580
Dec  1 06:20:23 Optiplex weewx[22287]: cheetahgenerator: Generated 13 
files for report StandardReport in 0.27 seconds
Dec  1 06:20:23 Optiplex weewx[22287]: copygenerator: copied 1 files to 
/var/www/html/weewx
Dec  1 06:20:23 Optiplex weewx[22287]: reportengine: Running report 
Highcharts_Belchertown
Dec  1 06:20:23 Optiplex weewx[22287]: reportengine: Found configuration 
file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report 
Highcharts_Belchertown
Dec  1 06:20:23 Optiplex weewx[22287]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']

Dec  1 06:20:23 Optiplex weewx[22287]: manager: Daily summary version is 2.0
Dec  1 06:20:23 Optiplex weewx[22287]: restx: CWOP: Published record 
2018-12-01 06:20:00 CST (1543666800)
Dec  1 06:20:23 Optiplex weewx[22287]: restx: AWEKAS: Published record 
2018-12-01 06:20:00 CST (1543666800)
Dec  1 06:20:24 Optiplex weewx[22287]: cheetahgenerator: Generated 4 
files for report Highcharts_Belchertown in 1.84 seconds
Dec  1 06:20:24 Optiplex weewx[22287]: copygenerator: copied 0 files to 
/var/www/html/weewx/belchertown/Highcharts_Belchertown
Dec  1 06:20:24 Optiplex weewx[22287]: reportengine: Running report 
Belchertown
Dec  1 06:20:24 Optiplex weewx[22287]: reportengine: Found configuration 
file /etc/weewx/skins/Belchertown/skin.conf for report Belchertown
Dec  1 06:20:24 Optiplex weewx[22287]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getData']

Dec  1 06:20:24 Optiplex weewx[22287]: manager: Daily summary version is 2.0
Dec  1 06:20:25 Optiplex weewx[22287]: cheetahgenerator: Generated 13 
files for report Belchertown in 0.24 seconds
Dec  1 06:20:25 Optiplex weewx[22287]: copygenerator: copied 1 files to 
/var/www/html/weewx/belchertown

Dec  1 06:20:25 Optiplex weewx[22287]: reportengine: Running report FTP
Dec  1 06:20:25 Optiplex weewx[22287]: reportengine: Found configuration 
file 

[weewx-user] Re: weewx abends with no reason

[Gary Hopkins]

Hi,

I can 100% assure you that weewx isn't running when the HUP happens. The 
cron for that is a standard tiny script that checks first to make sure it's 
not running before it restarts it.


#!/bin/bash

ps auxw | grep weewxd | grep -v grep > /dev/null

if [ $? != 0 ]
then
sudo systemctl restart weewx
fi

If you look at the first log, it's pulling down 3 or 4 entries a second, it 
then hangs and weewx abends. You then see the cron realising it's stopped 
and restarting it. If I don't have the cron restarting weewx then it will 
literally just stop after the last entry (like this one in the second 
paste) and I get nothing after it because weewx is literally not running. 

Dec  1 10:33:26 raspberrypi weewx[21612]: manager: Added record 2017-03-15 
11:43:43 GMT (1489578223) to daily summary in 'weewx.sdb'

So I can stop the cron, sure, but all it means is that it starts as show, 
it takes down a few hours of the backlog and then weewx literally exits 
with no info.

Does that better explain?

Thanks

G


On Saturday, 1 December 2018 10:51:28 UTC, Andrew Milner wrote:
>
> First of all get rid of the HUP in Cron - that does not help at all
>
> Both log sections seem to show more than pne occurrence of weewx to be 
> running - look at the PIDs.  You can only have one.
>
>
>

-- 
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: weewx abends with no reason

[Andrew Milner]

First of all get rid of the HUP in Cron - that does not help at all

Both log sections seem to show more than pne occurrence of weewx to be 
running - look at the PIDs.  You can only have one.



On Saturday, 1 December 2018 12:27:09 UTC+2, Gary Hopkins wrote:
>
> Original Rasperry Pi Model B
> 8GB Class 4 SD Card
> Latest Raspian installed through Noobs 3
> Latest weewx installed following online guide through apt
> Aercus WeatherRanger (WS1000 clone)
> Used https://github.com/AussieSusan/HP1000 custom driver to grab events 
> over WiFi
>
> weewx connects to the WS with no problems and starts to catchup with my 
> archived data. After approximately 40 seconds the feed stops coming and 
> weewx just stops.
>
> I've turned on debug=1, I've added a HUP to cron running every minuite to 
> re-start weewx so it's very very slowly working its way through the 
> backlog. I've fiddled with the retry/timeouts etc. available in weewx.conf.
>
> Heres the syslog from the abend of the previous feed, the start up then 
> starting the next feed.
>
> Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
> 13:51:43 GMT (1489499503) to database 'weewx.sdb'
> Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
> 13:51:43 GMT (1489499503) to daily summary in 'weewx.sdb'
> Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
> 13:52:43 GMT (1489499563) to database 'weewx.sdb'
> Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
> 13:52:43 GMT (1489499563) to daily summary in 'weewx.sdb'
> Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
> 13:53:43 GMT (1489499623) to database 'weewx.sdb'
> Dec  1 10:06:18 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
> 13:53:43 GMT (1489499623) to daily summary in 'weewx.sdb'
> Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Initializing weewx 
> version 3.8.2
> Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Using Python 2.7.13 
> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Platform 
> Linux-4.14.79+-armv6l-with-debian-9.6
> Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Locale is 'en_GB.UTF-8'
> Dec  1 10:07:04 raspberrypi weewx[20698]: engine: pid file is 
> /var/run/weewx.pid
> Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Loading station type 
> HP1000 (user.HP1000)
> Dec  1 10:07:04 raspberrypi weewx[20702]: engine: StdConvert target unit 
> is 0x1
> Dec  1 10:07:04 raspberrypi weewx[20702]: 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
> Dec  1 10:07:04 raspberrypi weewx[20702]: wxcalculate: The following 
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Archive will use data 
> binding wx_binding
> Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Record generation will 
> be attempted in 'software'
> Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Using archive interval 
> of 300 seconds (specified in weewx configuration)
> Dec  1 10:07:05 raspberrypi weewx[20702]: engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Dec  1 10:07:05 raspberrypi weewx[20702]: manager: Starting backfill of 
> daily summaries
> Dec  1 10:07:05 raspberrypi weewx[20702]: restx: StationRegistry: 
> Registration not requested.
> Dec  1 10:07:05 raspberrypi weewx[20702]: restx: Wunderground: Posting not 
> enabled.
> Dec  1 10:07:05 raspberrypi weewx[20702]: restx: PWSweather: Posting not 
> enabled.
> Dec  1 10:07:05 raspberrypi weewx[20702]: restx: CWOP: Posting not enabled.
> Dec  1 10:07:05 raspberrypi weewx[20702]: restx: WOW: Posting not enabled.
> Dec  1 10:07:05 raspberrypi weewx[20702]: restx: AWEKAS: Posting not 
> enabled.
> Dec  1 10:07:05 raspberrypi weewx[20702]: engine: Starting up weewx 
> version 3.8.2
> Dec  1 10:07:27 raspberrypi weewx[20702]: manager: Added record 2017-03-14 
> 13:54:43 GMT (1489499683) to database 'weewx.sdb'
> Dec  1 10:07:28 raspberrypi weewx[20702]: manager: Added record 2017-03-14 
> 13:54:43 GMT (1489499683) to daily summary in 'weewx.sdb'
>
> Here's my weewx.conf (as mentioned above I understand the retry timings 
> etc. are changed but I was experimenting and desperate but it did exactly 
> the same thing with the default values). I also removed the location and 
> long/lat values.
>
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 Tom Keffer >
> # See the file 

[weewx-user] Re: weewx abends with no reason

[Gary Hopkins]

Hi,

Here's a better capture of the restart process. Not sure why it didn't have 
all the extra info in the previous capture as it's from the exact same 
process. I also modified some the parameters back to near their defaults 
for clarity. Many thanks again.

G

Dec  1 10:33:26 raspberrypi weewx[21612]: manager: Added record 2017-03-15 
11:43:43 GMT (1489578223) to database 'weewx.sdb'
Dec  1 10:33:26 raspberrypi weewx[21612]: manager: Added record 2017-03-15 
11:43:43 GMT (1489578223) to daily summary in 'weewx.sdb'
Dec  1 10:34:01 raspberrypi CRON[21636]: (pi) CMD (/home/pi/restart_weewx)
Dec  1 10:34:01 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...
Dec  1 10:34:02 raspberrypi weewx[21646]: Stopping weewx weather system: 
weewx not running
Dec  1 10:34:02 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
Dec  1 10:34:02 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Dec  1 10:34:04 raspberrypi weewx[21670]: engine: Initializing weewx 
version 3.8.2
Dec  1 10:34:04 raspberrypi weewx[21670]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Dec  1 10:34:04 raspberrypi weewx[21670]: engine: Platform 
Linux-4.14.79+-armv6l-with-debian-9.6
Dec  1 10:34:04 raspberrypi weewx[21670]: engine: Locale is 'en_GB.UTF-8'
Dec  1 10:34:04 raspberrypi weewx[21670]: engine: pid file is 
/var/run/weewx.pid
Dec  1 10:34:04 raspberrypi weewx[21659]: Starting weewx weather system: 
weewx.
Dec  1 10:34:04 raspberrypi systemd[1]: Started LSB: weewx weather system.
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Debug is 1
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Initializing engine
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading station type 
HP1000 (user.HP1000)
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: HP1000 Starting
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Using user-defined 
broadcast mask - 172.17.10.255
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Address Mask = 
172.17.10.255
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Retry count = 5.00
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Socket timeout = 5.00
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Loop delay = 10.00
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Retry Wait = 10.00
Dec  1 10:34:04 raspberrypi weewx[21674]: HP1000: Max Retry = 3.00
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading service 
weewx.engine.StdTimeSynch
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading service 
weewx.engine.StdConvert
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: StdConvert target unit is 
0x1
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Finished loading service 
weewx.engine.StdConvert
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading service 
weewx.engine.StdCalibrate
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Finished loading service 
weewx.engine.StdCalibrate
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading service 
weewx.engine.StdQC
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Finished loading service 
weewx.engine.StdQC
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Dec  1 10:34:04 raspberrypi weewx[21674]: 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
Dec  1 10:34:04 raspberrypi weewx[21674]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Loading service 
weewx.engine.StdArchive
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Archive will use data 
binding wx_binding
Dec  1 10:34:04 raspberrypi weewx[21674]: engine: Record generation will be 
attempted in 'software'
Dec  1 10:34:05 raspberrypi weewx[21674]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
Dec  1 10:34:05 raspberrypi weewx[21674]: engine: Use LOOP data in hi/low 
calculations: 1
Dec  1 10:34:05 raspberrypi weewx[21674]: manager: Daily summary version is 
2.0
Dec  1 10:34:05 raspberrypi weewx[21674]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec  1 10:34:05 raspberrypi weewx[21674]: manager: Starting backfill of 
daily summaries
Dec  1 10:34:05 raspberrypi weewx[21674]: engine: Finished loading service 

[weewx-user] weewx abends with no reason

[Gary Hopkins]

Original Rasperry Pi Model B
8GB Class 4 SD Card
Latest Raspian installed through Noobs 3
Latest weewx installed following online guide through apt
Aercus WeatherRanger (WS1000 clone)
Used https://github.com/AussieSusan/HP1000 custom driver to grab events 
over WiFi

weewx connects to the WS with no problems and starts to catchup with my 
archived data. After approximately 40 seconds the feed stops coming and 
weewx just stops.

I've turned on debug=1, I've added a HUP to cron running every minuite to 
re-start weewx so it's very very slowly working its way through the 
backlog. I've fiddled with the retry/timeouts etc. available in weewx.conf.

Heres the syslog from the abend of the previous feed, the start up then 
starting the next feed.

Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
13:51:43 GMT (1489499503) to database 'weewx.sdb'
Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
13:51:43 GMT (1489499503) to daily summary in 'weewx.sdb'
Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
13:52:43 GMT (1489499563) to database 'weewx.sdb'
Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
13:52:43 GMT (1489499563) to daily summary in 'weewx.sdb'
Dec  1 10:06:17 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
13:53:43 GMT (1489499623) to database 'weewx.sdb'
Dec  1 10:06:18 raspberrypi weewx[20638]: manager: Added record 2017-03-14 
13:53:43 GMT (1489499623) to daily summary in 'weewx.sdb'
Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Initializing weewx 
version 3.8.2
Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Platform 
Linux-4.14.79+-armv6l-with-debian-9.6
Dec  1 10:07:04 raspberrypi weewx[20698]: engine: Locale is 'en_GB.UTF-8'
Dec  1 10:07:04 raspberrypi weewx[20698]: engine: pid file is 
/var/run/weewx.pid
Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Loading station type 
HP1000 (user.HP1000)
Dec  1 10:07:04 raspberrypi weewx[20702]: engine: StdConvert target unit is 
0x1
Dec  1 10:07:04 raspberrypi weewx[20702]: 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
Dec  1 10:07:04 raspberrypi weewx[20702]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Archive will use data 
binding wx_binding
Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Record generation will be 
attempted in 'software'
Dec  1 10:07:04 raspberrypi weewx[20702]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
Dec  1 10:07:05 raspberrypi weewx[20702]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec  1 10:07:05 raspberrypi weewx[20702]: manager: Starting backfill of 
daily summaries
Dec  1 10:07:05 raspberrypi weewx[20702]: restx: StationRegistry: 
Registration not requested.
Dec  1 10:07:05 raspberrypi weewx[20702]: restx: Wunderground: Posting not 
enabled.
Dec  1 10:07:05 raspberrypi weewx[20702]: restx: PWSweather: Posting not 
enabled.
Dec  1 10:07:05 raspberrypi weewx[20702]: restx: CWOP: Posting not enabled.
Dec  1 10:07:05 raspberrypi weewx[20702]: restx: WOW: Posting not enabled.
Dec  1 10:07:05 raspberrypi weewx[20702]: restx: AWEKAS: Posting not 
enabled.
Dec  1 10:07:05 raspberrypi weewx[20702]: engine: Starting up weewx version 
3.8.2
Dec  1 10:07:27 raspberrypi weewx[20702]: manager: Added record 2017-03-14 
13:54:43 GMT (1489499683) to database 'weewx.sdb'
Dec  1 10:07:28 raspberrypi weewx[20702]: manager: Added record 2017-03-14 
13:54:43 GMT (1489499683) to daily summary in 'weewx.sdb'

Here's my weewx.conf (as mentioned above I understand the retry timings 
etc. are changed but I was experimenting and desperate but it did exactly 
the same thing with the default values). I also removed the location and 
long/lat values.

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