[weewx-user] Re: Crash with log info

[Ron]

No need to apologize! If it weren't for your hard work we wouldn't have this 
driver at all. I'm happy to contribute even if small.

-- 
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: Crash with log info

[vk3anz]

AAGGHH - this is what happens when you try to refactor your code and forget 
about variable scoping.
The 'network_retry_count' variable IS set (with the line you added) in line 
493 which is right at the start of the 'getLoopPackets' function.
The next part of the process is to use the 'self.connectToWeatherStation()' 
function which originally only existed where the function call is located. 
However when I added the functionality to read the history data, I needed 
to connect to the weather station from several places and so I moved the 
code into a separate function. Of course that is when I forgot about the 
scope of the variable!
It also shows that my network is fairly reliable as I've obviously never 
triggered that error condition in my testing.
My apologies for the bugs and my thanks for helping me find them.
I'll update my repository tonight (hopefully).
Susan

-- 
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: Crash with log info

[Ron]

I had another crash of the HP1000 driver yesterday. I made a change which 
will hopefully fix it in the future which was to add
>
> network_retry_count = self.max_retry
>
before the try enclosing line 324. I guess my setup is good for testing 
error conditions! I committed to my HP1000 repo. I still need to remove the 
superfluous login() calls from my copy though.

The exception details were

> HP1000: Timed out too many times

Apr 22 16:36:07 AllenWeather weewx[6000]: engine: Main loop exiting. 
> Shutting engine down.

Apr 22 16:36:07 AllenWeather weewx[6000]: engine: Shutting down StdReport 
> thread

Apr 22 16:36:07 AllenWeather weewx[6000]: engine: StdReport thread has been 
> terminated

Apr 22 16:36:07 AllenWeather weewx[6000]: restx: Shut down CWOP thread.

Apr 22 16:36:07 AllenWeather weewx[6000]: restx: Shut down StationRegistry 
> thread.

Apr 22 16:36:07 AllenWeather weewx[6000]: engine: Caught unrecoverable 
> exception in engine:

Apr 22 16:36:07 AllenWeather weewx[6000]:   local variable 
> 'network_retry_count' referenced before assignment

Apr 22 16:36:07 AllenWeather weewx[6000]:   Traceback (most recent 
> call last):

Apr 22 16:36:07 AllenWeather weewx[6000]: File 
> "/usr/share/weewx/weewx/engine.py", line 890, in main

Apr 22 16:36:07 AllenWeather weewx[6000]:   engine.run()

Apr 22 16:36:07 AllenWeather weewx[6000]: File 
> "/usr/share/weewx/weewx/engine.py", line 188, in run

Apr 22 16:36:07 AllenWeather weewx[6000]:   for packet in 
> self.console.genLoopPackets():

Apr 22 16:36:07 AllenWeather weewx[6000]: File 
> "/usr/share/weewx/user/HP1000.py", line 497, in genLoopPackets

Apr 22 16:36:07 AllenWeather weewx[6000]:  
>  self.connectToWeatherStation()

Apr 22 16:36:07 AllenWeather weewx[6000]: File 
> "/usr/share/weewx/user/HP1000.py", line 324, in connectToWeatherStation

Apr 22 16:36:07 AllenWeather weewx[6000]:   network_retry_count 
> -= 1

Apr 22 16:36:07 AllenWeather weewx[6000]:   UnboundLocalError: 
> local variable 'network_retry_count' referenced before assignment

Apr 22 16:36:07 AllenWeather weewx[6000]:   Exiting.

 

-- 
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: Crash with log info

[Ron]

FWIW the changes have been running on my install and there have been no further 
crashes. 

-- 
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: Crash with log info

[vk3anz]

I've updated the files in github with the error fix(es) that Ron suggested.
I have *NOT* tested this with the latest version of Weewx nor with the 
Python 3 version - that work is yet to come.
Susan

-- 
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: Crash with log info

[Ron]

Re: the added loginf, I wanted to let this version run for several days. If 
it is stable up to then I plan to remove the unnecessary loginf. Congrats 
on the new grandkid! And thanks again for creating the HP1000 driver. 

On Monday, April 8, 2019 at 10:48:19 PM UTC-5, vk3...@gmail.com wrote:
>
> I'm not sure what this means but if it works then great.
>
> On Monday, April 8, 2019 at 8:59:13 PM UTC+10, Ron wrote:
>>
>> Oh, in my repo I also changed the formatting of the installation steps in 
>> the README file. Githubs markdown was smushing them all onto a single line 
>> and eating the portions of the commands saying to insert the HP1000 
>> directory.
>
>
> You have uncovered a bug in my code that has been there all along with 
> regard to the 'sleep' command. As I mentioned above, there is a 
> 'sleep'command in the genLoopPackates function that stops the weather 
> station being accessed too frequently. in *that* call to 'sleep' I *do* 
> prefix it with 'time.' but in all other cases I don't. I guess it shows 
> that I hadn't checked all of the error code paths well enough!!!
>
> The only word of warning I'd make is that anyone using your code will get 
> the additional 'loginf' messages as it is reading in the history 
> packets.(BTW, in line 785 of your file, the 'loginf' is after the 'raise' 
> so probably won;t get actioned.)
>
> Thanks for the assistance on this - I'll update my repository over the 
> next few days as time permits (my daughter is about to make me a 'Grannie' 
> again).
>
> Susan
>

-- 
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: Crash with log info

[vk3anz]

I'm not sure what this means but if it works then great.

On Monday, April 8, 2019 at 8:59:13 PM UTC+10, Ron wrote:
>
> Oh, in my repo I also changed the formatting of the installation steps in 
> the README file. Githubs markdown was smushing them all onto a single line 
> and eating the portions of the commands saying to insert the HP1000 
> directory.


You have uncovered a bug in my code that has been there all along with 
regard to the 'sleep' command. As I mentioned above, there is a 
'sleep'command in the genLoopPackates function that stops the weather 
station being accessed too frequently. in *that* call to 'sleep' I *do* 
prefix it with 'time.' but in all other cases I don't. I guess it shows 
that I hadn't checked all of the error code paths well enough!!!

The only word of warning I'd make is that anyone using your code will get 
the additional 'loginf' messages as it is reading in the history 
packets.(BTW, in line 785 of your file, the 'loginf' is after the 'raise' 
so probably won;t get actioned.)

Thanks for the assistance on this - I'll update my repository over the next 
few days as time permits (my daughter is about to make me a 'Grannie' 
again).

Susan

-- 
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: Crash with log info

[Ron]

Oh, in my repo I also changed the formatting of the installation steps in the 
README file. Githubs markdown was smushing them all onto a single line and 
eating the portions of the commands saying to insert the HP1000 directory.

-- 
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: Crash with log info

[Ron]

Hello Susan! 

I've had weewx running about 3 weeks. I am running the current weewx using 
python2.7. It's running on a Raspberry Pi Zero W (so wireless connection). The 
weather station is a WS-1001. After the first week I haven't made changes to 
the setup until I made the changes last week to address the exceptions.

FYI I forked your repo to https://github.com/ronguest/HP1000. The changes 
roughly speaking were to unpack the tar file, add the above change to address 
the unpack exception, and change all the sleep() calls to be time.sleep(). 
There are also some loginf() calls added in getHistoryData. I need to remove 
those as I added them in an effort to understand how that was working.

I imagined, without any data to support it, a transient network issue caused 
the unpack errors. The sleep() exception I posted was in HP1000 code that 
catches an exception on a a socket call. It occurred about the time I took the 
WS-1001 offline to move some cabling around so it might be a complete one-off 
where the driver was talking to the WS just as I disconnected it.

The HP1000.py in my repo has been running with the change for the unpack 
exception since the 27th. I just made the change to the sleep() calls 
yesterday. 

-- 
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: Crash with log info

[vk3anz]

Also which version of weewx are you running?

I've not tested the HP1000 driver with the latest version (I know, I know).

Susan

-- 
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: Crash with log info

[vk3anz]

Sorry everyone but I've only just seen this thread (it would have helped if 
the title referenced the HP1000 driver).

As for the unpacking error - that would indicate that the packet from the 
HP1000 itself has altered, especially if it was working and then stopped.
Has something been updated - if so what?

Regarding the 'sleep' error, the 'time' namespace should be added to the 
global namespace. As Ron mentions, 'sleep' is used in several places, 
including the main packet generation loop (to stop it trying to access the 
weather station multiple times a second). Therefore if it has worked at all 
then it also indicates that something else has changed.

BTW - are these systems running under the weewx Python 3 version? If so 
then I have not made any attempt (yet!) to have the code run under that 
version. (When I wrote this, the answer about Python 3 as generally 'too 
hard at this time' so I wrote it for Python 2.7; the same as weewx itself.)

I'll try to have a look at these issues tonight (no promises).

Susan

-- 
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: Crash with log info

[Ron]

I got a different exception from the HP1000 driver today. I am adding it to 
this thread since I had sent Susan a link to this post. I believe the call 
should be to time.sleep() rather than just sleep() but I’m not up to enough to 
really know (there appear to be several places lacking “time.” In the code).

Apr  6 09:06:06 AllenWeather weewx[2377]:   global name 'sleep' is not 
defined
Apr  6 09:06:06 AllenWeather weewx[2377]:   Traceback (most recent call 
last):
Apr  6 09:06:06 AllenWeather weewx[2377]: File 
"/usr/share/weewx/weewx/engine.py", line 890, in main
Apr  6 09:06:06 AllenWeather weewx[2377]:   engine.run()
Apr  6 09:06:06 AllenWeather weewx[2377]: File 
"/usr/share/weewx/weewx/engine.py", line 188, in run
Apr  6 09:06:06 AllenWeather weewx[2377]:   for packet in 
self.console.genLoopPackets():
Apr  6 09:06:06 AllenWeather weewx[2377]: File 
"/usr/share/weewx/user/HP1000.py", line 511, in genLoopPackets
Apr  6 09:06:06 AllenWeather weewx[2377]:   sleep(self.retry_wait)
Apr  6 09:06:06 AllenWeather weewx[2377]:   NameError: global name 
'sleep' is not defined
Apr  6 09:06:06 AllenWeather weewx[2377]:   Exiting.

-- 
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: Crash with log info

[mwall]

On Friday, April 5, 2019 at 3:13:06 PM UTC-4, Ron wrote:
>
> Is it considered "expected" that the driver error would take out weewx 
> itself?
>

weewx will continue to collect data even if there are failures in the 
reporting system

but failures in the data collection will typically cause weewx to stop, and 
will spit out an exception stack such as the one you got

that makes it pretty easy for the driver author to figure out what is 
happening, then design logic to handle it

the more mature the driver, the less likely that there will be any 
situations that will take it down

-- 
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: Crash with log info

[Ron]

Thanks very much for your tip. I'll try that change to the driver. I had 
filed a different issue on the Github for HP1000 but didn't get a response. 
I found an email address for her recently so I'll try dropping her a note.

Is it considered "expected" that the driver error would take out weewx 
itself?

Thanks again!

On Friday, April 5, 2019 at 11:29:15 AM UTC-5, mwall wrote:
>
>
>
> On Wednesday, March 27, 2019 at 4:35:44 PM UTC-4, Ron wrote:
>>
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: File 
 "/usr/share/weewx/user/HP1000.py", line 524, in genLoopPackets
>>>
>>> Mar 26 20:02:17 AllenWeather weewx[7839]:   interp_data = 
 struct.unpack("8s8s16s8shbb14fbbh", rxData)
>>>
>>> Mar 26 20:02:17 AllenWeather weewx[7839]:   error: unpack 
 requires a string argument of length 104
>>>
>>> Mar 26 20:02:17 AllenWeather weewx[7839]:   Exiting.

>>>
> this is a bug in the HP1000.py driver.  the driver received some data, but 
> it was not the type/structure that it expected, and the code does not know 
> how to deal with what it actually received.
>
> as a workaround, you could change line 524 of HP1000.py from this:
>
> interp_data = struct.unpack("8s8s16s8shbb14fbbh", rxData)
>
> to this:
>
> try:
> interp_data = struct.unpack("8s8s16s8shbb14fbbh", 
> rxData)
> except struct.error as e:
> network_retry_count -= 1
> if network_retry_count > 0:
> sleep(self.retry_wait)
> self.ws_socket.close()
> self.ws_socket = None
> continue
> else:
> raise weewx.RetriesExceeded
>
> but for a proper fix the driver auther (susan mackay) should look at it in 
> more detail.
>
> 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: Crash with log info

[mwall]

On Wednesday, March 27, 2019 at 4:35:44 PM UTC-4, Ron wrote:
>
>
> Mar 26 20:02:17 AllenWeather weewx[7839]: File 
>>> "/usr/share/weewx/user/HP1000.py", line 524, in genLoopPackets
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   interp_data = 
>>> struct.unpack("8s8s16s8shbb14fbbh", rxData)
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   error: unpack 
>>> requires a string argument of length 104
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   Exiting.
>>>
>>
this is a bug in the HP1000.py driver.  the driver received some data, but 
it was not the type/structure that it expected, and the code does not know 
how to deal with what it actually received.

as a workaround, you could change line 524 of HP1000.py from this:

interp_data = struct.unpack("8s8s16s8shbb14fbbh", rxData)

to this:

try:
interp_data = struct.unpack("8s8s16s8shbb14fbbh", 
rxData)
except struct.error as e:
network_retry_count -= 1
if network_retry_count > 0:
sleep(self.retry_wait)
self.ws_socket.close()
self.ws_socket = None
continue
else:
raise weewx.RetriesExceeded

but for a proper fix the driver auther (susan mackay) should look at it in 
more detail.

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: Crash with log info

[mwall]

On Thursday, March 28, 2019 at 2:50:24 AM UTC-4, AsgeirK wrote:
>
> I have a similar issue since I upgraded to the latest version:
>
> Mar 27 18:07:48 PI-W4 weewx[507]: wmr200: MainThread: W Exiting with 
> packets still in live queue cnt:2
> Mar 27 18:07:48 PI-W4 weewx[507]: wmr200: MainThread: I Driver gracefully 
> exiting
> Mar 27 18:07:48 PI-W4 weewx[507]: engine: Caught unrecoverable exception 
> in engine:
> Mar 27 18:07:48 PI-W4 weewx[507]:   Non-positive value for record 
> field 'interval': 0
> ...
> Mar 27 18:07:48 PI-W4 weewx[507]:   ValueError: Non-positive value 
> for record field 'interval': 0
> Mar 27 18:07:48 PI-W4 weewx[507]:   Exiting.
>

this is not at all related to the original posting  of this thread.  this 
was a bug in the wmr200, fixed at commit 
7ccb1345cc0831bae7df46266ee79f7b0b8c3b59 on 15feb2019.
 

-- 
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: Crash with log info

[Ron]

This same exception occurred again last night, and once again weewx did not 
restart and I could not start it manually until after I rebooted the Pi. 

There were no suggestions on my original post. Hoping someone can give me 
some advice now that it is a repeating issue. Thanks.

-- 
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: Crash with log info

[AsgeirK]

I have a similar issue since I upgraded to the latest version:

Mar 27 18:07:48 PI-W4 weewx[507]: wmr200: MainThread: W Exiting with 
packets still in live queue cnt:2
Mar 27 18:07:48 PI-W4 weewx[507]: wmr200: MainThread: I Driver gracefully 
exiting
Mar 27 18:07:48 PI-W4 weewx[507]: engine: Caught unrecoverable exception in 
engine:
Mar 27 18:07:48 PI-W4 weewx[507]:   Non-positive value for record 
field 'interval': 0
Mar 27 18:07:48 PI-W4 weewx[507]:   Traceback (most recent call 
last):
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 890, in main
Mar 27 18:07:48 PI-W4 weewx[507]:   engine.run()
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 160, in run
Mar 27 18:07:48 PI-W4 weewx[507]:   
self.dispatchEvent(weewx.Event(weewx.STARTUP))
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Mar 27 18:07:48 PI-W4 weewx[507]:   callback(event)
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 520, in startup
Mar 27 18:07:48 PI-W4 weewx[507]:   
self._catchup(self.engine.console.genStartupRecords)
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 635, in _catchup
Mar 27 18:07:48 PI-W4 weewx[507]:   origin='hardware'))
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Mar 27 18:07:48 PI-W4 weewx[507]:   callback(event)
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record
Mar 27 18:07:48 PI-W4 weewx[507]:   
dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/manager.py", line 246, in addRecord
Mar 27 18:07:48 PI-W4 weewx[507]:   
self._addSingleRecord(record, cursor, log_level)
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord
Mar 27 18:07:48 PI-W4 weewx[507]:   _weight = 
self._calc_weight(record)
Mar 27 18:07:48 PI-W4 weewx[507]: File 
"/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight
Mar 27 18:07:48 PI-W4 weewx[507]:   raise 
ValueError("Non-positive value for record field 'interval': %s" % 
(record['interval'], ))
Mar 27 18:07:48 PI-W4 weewx[507]:   ValueError: Non-positive value 
for record field 'interval': 0
Mar 27 18:07:48 PI-W4 weewx[507]:   Exiting.
Mar 27 18:08:45 PI-W4 systemd[1]: Started Session c427 of user pi.
Mar 27 18:09:45 PI-W4 systemd[1]: Started Session c428 of user pi.

 

-- 
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: Crash with log info

[Ron]

I should add that I tried to start weewx manually after I discovered it 
wasn't running using

> sudo /etc/init.d/weewx start
>

It didn't start and I didn't see anything coming syslog. I rebooted the Pi 
and it started normally, including HP1000 loading the records it had 
missed. 

On Wednesday, March 27, 2019 at 3:35:44 PM UTC-5, Ron wrote:
>
> I discovered today that weewx was no longer running. It had been running 
> fine for several days. I installed it late last week using the Debian 
> instructions  and used these 
> instructions 
>  
> regarding installation of the HP1000 driver. At the bottom of this post I 
> included the crash related entries +/- a few lines as well as what I see in 
> systemctl. I'm not sure but possibly the HP1000 driver got a malformed 
> packet from my AW WS-1001 (?). As far as I can tell there was no effort by 
> the system to restart weewx. I did confirm there was no weewx process 
> running.
>
> Do you have any advice on how to have it better cope with this error? If 
> it happened once after a few days I imagine it will happen again. There 
> were no known networking issues yesterday. Thanks!
>
> I did a systemctl status command and weewx was listed there as expected:
>
>> system.slice
>>
>>  ├─weewx.service
>>
>>  │ └─428 python /usr/bin/weewxd --daemon 
>>> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>>
>>
>
> Mar 26 20:00:28 AllenWeather weewx[7839]: reportengine: Found 
>>> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
>>> 'SeasonsReport'
>>
>> Mar 26 20:00:28 AllenWeather weewx[7839]: cheetahgenerator: using search 
>>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
>>
>> Mar 26 20:00:28 AllenWeather weewx[7839]: manager: Daily summary version 
>>> is 2.0
>>
>> Mar 26 20:00:37 AllenWeather weewx[7839]: cheetahgenerator: Generated 8 
>>> files for report SeasonsReport in 8.54 seconds
>>
>> Mar 26 20:00:37 AllenWeather weewx[7839]: manager: Daily summary version 
>>> is 2.0
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: imagegenerator: Generated 28 
>>> images for SeasonsReport in 15.84 seconds
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: copygenerator: copied 0 files 
>>> to /var/www/html/weewx
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: reportengine: Report 
>>> 'SmartphoneReport' not enabled. Skipping.
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: reportengine: Report 
>>> 'MobileReport' not enabled. Skipping.
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: reportengine: Report 
>>> 'StandardReport' not enabled. Skipping.
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: reportengine: Report 'FTP' not 
>>> enabled. Skipping.
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: reportengine: Running report 
>>> 'RSYNC'
>>
>> Mar 26 20:00:52 AllenWeather weewx[7839]: reportengine: Found 
>>> configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC'
>>
>> Mar 26 20:00:55 AllenWeather weewx[7839]: rsyncupload: rsync'd 1 files 
>>> (41,762,816 bytes) in 2.69 seconds
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: engine: Main loop exiting. 
>>> Shutting engine down.
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: engine: Shutting down StdReport 
>>> thread
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: engine: StdReport thread has 
>>> been terminated
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: restx: Shut down CWOP thread.
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: restx: Shut down 
>>> StationRegistry thread.
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: engine: Caught unrecoverable 
>>> exception in engine:
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   unpack requires a 
>>> string argument of length 104
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   Traceback (most 
>>> recent call last):
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 890, in main
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   engine.run()
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 188, in run
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   for packet in 
>>> self.console.genLoopPackets():
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]: File 
>>> "/usr/share/weewx/user/HP1000.py", line 524, in genLoopPackets
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   interp_data = 
>>> struct.unpack("8s8s16s8shbb14fbbh", rxData)
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   error: unpack 
>>> requires a string argument of length 104
>>
>> Mar 26 20:02:17 AllenWeather weewx[7839]:   Exiting.
>>
>> Mar 26 20:09:01 AllenWeather systemd[1]: