[weewx-user] Re: Belchertown skin 0.9 now available

[rich T]

But I get an "TypeError: format() got an unexpected keyword argument 
'None_string''  error.



On Thursday, February 28, 2019 at 10:15:31 PM UTC-5, rich T wrote:
>
> Pat
>
> Installed without any issues.
>
> Rich
>
> On Thursday, February 28, 2019 at 7:50:34 PM UTC-5, Pat wrote:
>
>> I've just released Belchertown skin 0.9. You can read the updates and 
>> download it here: https://github.com/poblabs/weewx-belchertown/releases
>>
>> A lot of work went into this release. I've learned a lot through feedback 
>> on the skin. 
>>
>> This release fixes a major bug with the rain charts which were taking a 
>> very long time to generate. This release also brings a lot of updates to 
>> locale formats. 
>>
>> *There's 1 breaking change if you are upgrading*. Please take special 
>> note to a few MQTT variable names which have changed to mqtt_websockets_. 
>> This is to reduce confusion and offer clarity on new user installations. 
>>
>> Please let me know if you've upgraded and share your site. I'd love to 
>> see it out there!
>>
>>

-- 
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.
Feb 28 22:39:06 raspberrypi systemd[1]: Started Clean php session files.
Feb 28 22:39:28 raspberrypi systemd[1]: Time has been changed
Feb 28 22:39:28 raspberrypi systemd-timesyncd[279]: Synchronized to time server 
194.177.210.54:123 (2.debian.pool.ntp.org).
Feb 28 22:39:28 raspberrypi systemd[587]: Time has been changed
Feb 28 22:39:28 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 6min 
58.014370s random time.
Feb 28 22:39:28 raspberrypi systemd[1]: apt-daily.timer: Adding 9h 52min 
8.415715s random time.
Feb 28 22:39:40 raspberrypi weewx[523]: acurite: Found station at bus= device=
Feb 28 22:39:40 raspberrypi weewx[523]: acurite: next read in 6 seconds
Feb 28 22:39:46 raspberrypi weewx[523]: acurite: Found station at bus= device=
Feb 28 22:39:46 raspberrypi weewx[523]: acurite: next read in 12 seconds
Feb 28 22:39:58 raspberrypi weewx[523]: acurite: Found station at bus= device=
Feb 28 22:39:58 raspberrypi weewx[523]: acurite: next read in 18 seconds
Feb 28 22:40:16 raspberrypi weewx[523]: acurite: Found station at bus= device=
Feb 28 22:40:16 raspberrypi weewx[523]: manager: Added record 2019-02-28 
22:40:00 EST (1551411600) to database 'weewx.sdb'
Feb 28 22:40:16 raspberrypi weewx[523]: manager: Added record 2019-02-28 
22:40:00 EST (1551411600) to daily summary in 'weewx.sdb'
Feb 28 22:40:17 raspberrypi weewx[523]: reportengine: Running reports for 
latest time in the database.
Feb 28 22:40:17 raspberrypi weewx[523]: reportengine: Running report 
StandardReport
Feb 28 22:40:18 raspberrypi weewx[523]: reportengine: Found configuration file 
/home/weewx/skins/Belchertown/skin.conf for report StandardReport
Feb 28 22:40:18 raspberrypi weewx[523]: 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']
Feb 28 22:40:18 raspberrypi weewx[523]: acurite: Found station at bus= device=
Feb 28 22:40:18 raspberrypi weewx[523]: acurite: next read in 17 seconds
Feb 28 22:40:18 raspberrypi weewx[523]: manager: Daily summary version is 2.0
Feb 28 22:40:18 raspberrypi weewx[523]: Belchertown Extension: version 0.9
Feb 28 22:40:22 raspberrypi CRON[934]: (root) CMD (python 
/home/pi/Desktop/test.py >/dev/null 2>&1)
Feb 28 22:40:25 raspberrypi weewx[523]: cheetahgenerator: Generate failed with 
exception ''
Feb 28 22:40:25 raspberrypi weewx[523]: cheetahgenerator:  Ignoring 
template /home/weewx/skins/Belchertown/index.html.tmpl
Feb 28 22:40:25 raspberrypi weewx[523]: cheetahgenerator:  Reason: format() 
got an unexpected keyword argument 'None_string'
Feb 28 22:40:25 raspberrypi weewx[523]:   Traceback (most recent call last):
Feb 28 22:40:25 raspberrypi weewx[523]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 330, in generate
Feb 28 22:40:25 raspberrypi weewx[523]:   print >> _file, 
compiled_template
Feb 28 22:40:25 raspberrypi weewx[523]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in __str__
Feb 28 22:40:25 raspberrypi weewx[523]:   rc = getattr(self, 
mainMethName)()
Feb 28 22:40:25 raspberrypi weewx[523]: File 
"_home_weewx_skins_Belchertown_index_html_tmpl.py", line 1531, in respond
Feb 28 22:40:25 raspberrypi weewx[523]: File 
"_home_weewx_skins_Belchertown_index_html_tmpl.py", line 287, in 
__errorCatcher32
Feb 28 22:40:25 raspberrypi weewx[523]: File "", line 1, in 

Feb 28 22:40:25 raspberrypi weewx[523]:   TypeError: format() got an 
unexpected keyword argument 

Re: [weewx-user] Belchertown skin 0.9 now available

[Colin Larsen]

Thanks Pat appreciate all the hard work you do. I'll upgrade either tonight
or first thing tomorrow.

Cheers
Colin

On Fri, 1 Mar 2019, 13:50 Pat,  wrote:

> I've just released Belchertown skin 0.9. You can read the updates and
> download it here: https://github.com/poblabs/weewx-belchertown/releases
>
> A lot of work went into this release. I've learned a lot through feedback
> on the skin.
>
> This release fixes a major bug with the rain charts which were taking a
> very long time to generate. This release also brings a lot of updates to
> locale formats.
>
> *There's 1 breaking change if you are upgrading*. Please take special
> note to a few MQTT variable names which have changed to mqtt_websockets_.
> This is to reduce confusion and offer clarity on new user installations.
>
> Please let me know if you've upgraded and share your site. I'd love to see
> it out there!
>
> --
> 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] Belchertown skin 0.9 now available

[Pat]

I've just released Belchertown skin 0.9. You can read the updates and 
download it here: https://github.com/poblabs/weewx-belchertown/releases

A lot of work went into this release. I've learned a lot through feedback 
on the skin. 

This release fixes a major bug with the rain charts which were taking a 
very long time to generate. This release also brings a lot of updates to 
locale formats. 

*There's 1 breaking change if you are upgrading*. Please take special note 
to a few MQTT variable names which have changed to mqtt_websockets_. This 
is to reduce confusion and offer clarity on new user installations. 

Please let me know if you've upgraded and share your site. I'd love to see 
it out there!

-- 
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] Moon phase & pyephem question

[kutzenco]

So the visible % is now 26% for both the new and old versions of 
almanac.py/Moon.py and the new version now lists the phase as Waning 
Crescent (as does the old version and WU). 

Phil

On Thursday, February 28, 2019 at 11:29:28 AM UTC-5, kutz...@gmail.com 
wrote:
>
> Here's an interesting piece of data. I'm using Tom's new almanac.py and 
> Moon.py on a testbed version of WeeWX. On my "production" instance of 
> WeeWX, I have the versions of those files originally installed with WeeWX 
> 3.9.1.
>
> On my production instance the moon is listed as 29% visible and is 
> described as "Waning Crescent" (which matches what WU says). On my testbed 
> instance, the moon is listed at 29% visible but is described as "Last 
> Quarter". 
>
> So it looks like the version that Tom updated hasn't yet updated the 
> description from Last Quarter to Waning Crescent. That should have occurred 
> as the visible amount decreased to 40%. I'm not sure if that's due to the 
> variability Tom mentioned or something in the new version that should be 
> changed.
>
> Phil
>
>
> On Wednesday, February 27, 2019 at 9:53:10 PM UTC-5, kutz...@gmail.com 
> wrote:
>>
>> Ah. Right you are. I had put it in the right place, but somehow, I ended 
>> up saving it as moon.py instead of Moon.py. I'm not sure how I did that, 
>> since I thought I copied it, name and all, from the GitHub repository. I 
>> renamed it (after removing the old Moon.py, which was still there) and all 
>> works fine now.
>>
>> Thanks for helping me out.
>>
>> Phil
>>
>> On Wednesday, February 27, 2019 at 8:13:23 PM UTC-5, Thomas Keffer wrote:
>>>
>>> You probably still have the old copy of weeutil/Moon.py. You need this 
>>> one 
>>> . 
>>> Or, you accidentally put it in the weewx directory, instead of the weeutil 
>>> directory.
>>>
>>> -tk
>>>
>>> On Wed, Feb 27, 2019 at 1:31 PM  wrote:
>>>
 Understood. In the meantime, I did try copying your new version of 
 almanac.py into the bin/weewx directory on my testbed weewx (I copied 
 moon.py into the bin/weeutil directory also, though I don't think that 
 matters). I got the attached errors complaining about moon_phase_ts. Did I 
 miss a file updated in an earlier commit?

 Phil



-- 
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: Second crash after 11 days

[Steve2Q]

Tom: I will let it run as is, and report back tomorrow with 48 hour stats.

-- 
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: Second crash after 11 days

[Thomas Keffer]

5% is way better than before, no?

I would expect occasional buffer errors with this version. The serial port
is constantly getting opened and closed. If a new packet comes in at the
wrong time, parts of it could get missed.

On Thu, Feb 28, 2019 at 10:22 AM Steve2Q  wrote:

> Tom; at 25 hours top shows 5.0% v  4.4% at 24 hours for 11rc3 and is still
> going up.
>
> Also 0.25 is throwing off sporadic buffer errors as follows.
>
> --
> 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: Second crash after 11 days

[Steve2Q]

Tom; at 25 hours top shows 5.0% v  4.4% at 24 hours for 11rc3 and is still 
going up.

Also 0.25 is throwing off sporadic buffer errors as follows.

-- 
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: Second crash after 11 days

[Thomas Keffer]

Steve, progress report? Is version 0.25 holding steady?

On Wed, Feb 27, 2019 at 9:33 AM Thomas Keffer  wrote:

> Well, that's the current kernel version. Let's see how it goes with the
> new Ultimeter driver.
>
> -tk
>
> On Wed, Feb 27, 2019 at 8:58 AM Steve2Q  wrote:
>
>> I am going to try .25 now. Here is the result of uname -a
>>
>> --
>> 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] Moon phase & pyephem question

[kutzenco]

Here's an interesting piece of data. I'm using Tom's new almanac.py and 
Moon.py on a testbed version of WeeWX. On my "production" instance of 
WeeWX, I have the versions of those files originally installed with WeeWX 
3.9.1.

On my production instance the moon is listed as 29% visible and is 
described as "Waning Crescent" (which matches what WU says). On my testbed 
instance, the moon is listed at 29% visible but is described as "Last 
Quarter". 

So it looks like the version that Tom updated hasn't yet updated the 
description from Last Quarter to Waning Crescent. That should have occurred 
as the visible amount decreased to 40%. I'm not sure if that's due to the 
variability Tom mentioned or something in the new version that should be 
changed.

Phil


On Wednesday, February 27, 2019 at 9:53:10 PM UTC-5, kutz...@gmail.com 
wrote:
>
> Ah. Right you are. I had put it in the right place, but somehow, I ended 
> up saving it as moon.py instead of Moon.py. I'm not sure how I did that, 
> since I thought I copied it, name and all, from the GitHub repository. I 
> renamed it (after removing the old Moon.py, which was still there) and all 
> works fine now.
>
> Thanks for helping me out.
>
> Phil
>
> On Wednesday, February 27, 2019 at 8:13:23 PM UTC-5, Thomas Keffer wrote:
>>
>> You probably still have the old copy of weeutil/Moon.py. You need this 
>> one 
>> . 
>> Or, you accidentally put it in the weewx directory, instead of the weeutil 
>> directory.
>>
>> -tk
>>
>> On Wed, Feb 27, 2019 at 1:31 PM  wrote:
>>
>>> Understood. In the meantime, I did try copying your new version of 
>>> almanac.py into the bin/weewx directory on my testbed weewx (I copied 
>>> moon.py into the bin/weeutil directory also, though I don't think that 
>>> matters). I got the attached errors complaining about moon_phase_ts. Did I 
>>> miss a file updated in an earlier commit?
>>>
>>> Phil
>>>
>>>

-- 
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: Showing message to weather website users when stopped working

[Thomas Keffer]

Pull its power supply,  then plug it back in. That's as good a test as any.

On Thu, Feb 28, 2019 at 6:40 AM David Hindley  wrote:

> Thanks for your reply, Tom - much appreciated.
>
> I have removed the fake clock (pending purchase of a RTC) and made the
> change to the file in init.d and restarted weewx with a working network and
> all seems OK, but I guess I won't know fully until the Pi crashes again.
>
> David.
>
> On Thu, 28 Feb 2019 at 13:32, Thomas Keffer  wrote:
>
>> 1. It looks like you're using the WeatherLinkIP logger in your Vantage.
>> These are generally not as reliable as the serial and USB versions and, as
>> you discovered, depend on the network being up before the Vantage is useful.
>>
>> I am not a boot expert, but try this: go into /etc/init.d/weewx and
>> change this
>>
>> ### BEGIN INIT INFO
>> # Provides:  weewx
>> # Required-Start:$local_fs $remote_fs $syslog $time
>> # Required-Stop: $local_fs $remote_fs $syslog
>> # Default-Start: 2 3 4 5
>> # Default-Stop:  0 1 6
>> # Short-Description: weewx weather system
>> # Description:   Manages the weewx weather system
>> ### END INIT INFO
>>
>>
>> to this
>>
>> ### BEGIN INIT INFO
>> # Provides:  weewx
>> # Required-Start:$local_fs $remote_fs $syslog $networking $time
>> # Required-Stop: $local_fs $remote_fs $syslog
>> # Default-Start: 2 3 4 5
>> # Default-Stop:  0 1 6
>> # Short-Description: weewx weather system
>> # Description:   Manages the weewx weather system
>> ### END INIT INFO
>>
>> This says that the system should not run WeeWX until the network is up.
>> What I'm not sure of is how Debian defines "up." Worth a try.
>>
>> 2. The clock must also be set. Either use a hardware real time clock
>> (RTC), or remove the "fake clock" by following these directions
>> 
>> .
>>
>> On Thu, Feb 28, 2019 at 3:57 AM David Hindley 
>> wrote:
>>
>>> Many Thanks.
>>>
>>> 1.  I will do as you suggest re separate log files.
>>>
>>> 3. The cron task was something I had to add after installing the
>>> belchertown skin, just to copy some files from one directory to another, on
>>> the Rpi, before then using sftp to upload to my website. It seems to work
>>> most of the time, but, as you say, this seemed to be when the corruption
>>> occurred.  The CRON job works every five minutes at 1,6,11... minutes past
>>> each hour - on the basis that weewx should have updated the archive etc by
>>> then - maybe that is something to do with it.
>>>
>>> 4. Further down the log file, I see:
>>>
>>> Feb 27 15:17:04 raspberrypi weewx[379]: Starting weewx weather system:
>>> weewxerror: unexpectedly disconnected from boot status daemon
>>>
>>> and then...
>>>
>>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Initializing weewx
>>> version 3.9.1
>>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Using Python 2.7.13
>>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Platform
>>> Linux-4.14.79-v7+-armv7l-with-debian-9.6
>>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Locale is 'en_GB.UTF-8'
>>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: pid file is
>>> /var/run/weewx.pid
>>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Using configuration file
>>> /etc/weewx/weewx.conf
>>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Debug is 1
>>> Feb 27 15:17:05 raspberrypi weewx[379]: .
>>> Feb 27 15:17:05 raspberrypi systemd[1]: Started LSB: weewx weather
>>> system.
>>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Initializing engine
>>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Loading station type
>>> Vantage (weewx.drivers.vantage)
>>> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Driver version is 3.1.1
>>> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Socket error while
>>> opening port 2 to ethernet host 10.0.1.83.
>>> Feb 27 15:17:06 raspberrypi weewx[467]: import of driver failed: [Errno
>>> 101] Network is unreachable ()
>>> Feb 27 15:17:06 raspberrypi weewx[467]: engine: Unable to load driver:
>>> [Errno 101] Network is unreachable
>>> Feb 27 15:17:06 raspberrypi weewx[467]:   Exiting...
>>>
>>> So, looks like the internet connection went down perhaps? (I was away
>>> when all this happened yesterday, so not sure)
>>>
>>> Good point re making sure weewx doesn't restart until it has a sensible
>>> time via valid NTP connection - any idea how I do that?  I will order an
>>> RTC anyway I think.
>>>
>>> Thanks
>>>
>>> David.
>>>
>>> On Thu, 28 Feb 2019 at 11:25, Andrew Milner 
>>> wrote:
>>>
 1.  I recommend you put weewx log messages in their own log file - see
 wiki for a) separate logfile and also logrotation.
 2.  The ^@ rubbish looks like possible corruption whilst executing a
 cron task
 3.  What cron task was it trying to execute
 4.  I see the clock has gone backwards around the rubbish point -
 implying 

[weewx-user] Re: crash with Non-positive value for record field 'interval'

[vince]

Do a google search of this group for "non-positive" and you'll find a 
number of *very* recent threads for other folks with this message..



-- 
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: Showing message to weather website users when stopped working

[David Hindley]

Thanks for your reply, Tom - much appreciated.

I have removed the fake clock (pending purchase of a RTC) and made the
change to the file in init.d and restarted weewx with a working network and
all seems OK, but I guess I won't know fully until the Pi crashes again.

David.

On Thu, 28 Feb 2019 at 13:32, Thomas Keffer  wrote:

> 1. It looks like you're using the WeatherLinkIP logger in your Vantage.
> These are generally not as reliable as the serial and USB versions and, as
> you discovered, depend on the network being up before the Vantage is useful.
>
> I am not a boot expert, but try this: go into /etc/init.d/weewx and
> change this
>
> ### BEGIN INIT INFO
> # Provides:  weewx
> # Required-Start:$local_fs $remote_fs $syslog $time
> # Required-Stop: $local_fs $remote_fs $syslog
> # Default-Start: 2 3 4 5
> # Default-Stop:  0 1 6
> # Short-Description: weewx weather system
> # Description:   Manages the weewx weather system
> ### END INIT INFO
>
>
> to this
>
> ### BEGIN INIT INFO
> # Provides:  weewx
> # Required-Start:$local_fs $remote_fs $syslog $networking $time
> # Required-Stop: $local_fs $remote_fs $syslog
> # Default-Start: 2 3 4 5
> # Default-Stop:  0 1 6
> # Short-Description: weewx weather system
> # Description:   Manages the weewx weather system
> ### END INIT INFO
>
> This says that the system should not run WeeWX until the network is up.
> What I'm not sure of is how Debian defines "up." Worth a try.
>
> 2. The clock must also be set. Either use a hardware real time clock
> (RTC), or remove the "fake clock" by following these directions
> 
> .
>
> On Thu, Feb 28, 2019 at 3:57 AM David Hindley  wrote:
>
>> Many Thanks.
>>
>> 1.  I will do as you suggest re separate log files.
>>
>> 3. The cron task was something I had to add after installing the
>> belchertown skin, just to copy some files from one directory to another, on
>> the Rpi, before then using sftp to upload to my website. It seems to work
>> most of the time, but, as you say, this seemed to be when the corruption
>> occurred.  The CRON job works every five minutes at 1,6,11... minutes past
>> each hour - on the basis that weewx should have updated the archive etc by
>> then - maybe that is something to do with it.
>>
>> 4. Further down the log file, I see:
>>
>> Feb 27 15:17:04 raspberrypi weewx[379]: Starting weewx weather system:
>> weewxerror: unexpectedly disconnected from boot status daemon
>>
>> and then...
>>
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Initializing weewx
>> version 3.9.1
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Platform
>> Linux-4.14.79-v7+-armv7l-with-debian-9.6
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Locale is 'en_GB.UTF-8'
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: pid file is
>> /var/run/weewx.pid
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Using configuration file
>> /etc/weewx/weewx.conf
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Debug is 1
>> Feb 27 15:17:05 raspberrypi weewx[379]: .
>> Feb 27 15:17:05 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Initializing engine
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Loading station type
>> Vantage (weewx.drivers.vantage)
>> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Driver version is 3.1.1
>> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Socket error while
>> opening port 2 to ethernet host 10.0.1.83.
>> Feb 27 15:17:06 raspberrypi weewx[467]: import of driver failed: [Errno
>> 101] Network is unreachable ()
>> Feb 27 15:17:06 raspberrypi weewx[467]: engine: Unable to load driver:
>> [Errno 101] Network is unreachable
>> Feb 27 15:17:06 raspberrypi weewx[467]:   Exiting...
>>
>> So, looks like the internet connection went down perhaps? (I was away
>> when all this happened yesterday, so not sure)
>>
>> Good point re making sure weewx doesn't restart until it has a sensible
>> time via valid NTP connection - any idea how I do that?  I will order an
>> RTC anyway I think.
>>
>> Thanks
>>
>> David.
>>
>> On Thu, 28 Feb 2019 at 11:25, Andrew Milner 
>> wrote:
>>
>>> 1.  I recommend you put weewx log messages in their own log file - see
>>> wiki for a) separate logfile and also logrotation.
>>> 2.  The ^@ rubbish looks like possible corruption whilst executing a
>>> cron task
>>> 3.  What cron task was it trying to execute
>>> 4.  I see the clock has gone backwards around the rubbish point -
>>> implying the rpi has rebooted itself.  If that is the case you need to
>>> ensure that weewx does not restart again until it has a sensible time - or
>>> fit an RTC to your rpi
>>>
>>> All looks like some form of corruption - power supply perhaps or memory
>>> card 

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[Thomas Keffer]

1. It looks like you're using the WeatherLinkIP logger in your Vantage.
These are generally not as reliable as the serial and USB versions and, as
you discovered, depend on the network being up before the Vantage is useful.

I am not a boot expert, but try this: go into /etc/init.d/weewx and change
this

### BEGIN INIT INFO
# Provides:  weewx
# Required-Start:$local_fs $remote_fs $syslog $time
# Required-Stop: $local_fs $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
# Short-Description: weewx weather system
# Description:   Manages the weewx weather system
### END INIT INFO


to this

### BEGIN INIT INFO
# Provides:  weewx
# Required-Start:$local_fs $remote_fs $syslog $networking $time
# Required-Stop: $local_fs $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
# Short-Description: weewx weather system
# Description:   Manages the weewx weather system
### END INIT INFO

This says that the system should not run WeeWX until the network is up.
What I'm not sure of is how Debian defines "up." Worth a try.

2. The clock must also be set. Either use a hardware real time clock (RTC),
or remove the "fake clock" by following these directions
.

On Thu, Feb 28, 2019 at 3:57 AM David Hindley  wrote:

> Many Thanks.
>
> 1.  I will do as you suggest re separate log files.
>
> 3. The cron task was something I had to add after installing the
> belchertown skin, just to copy some files from one directory to another, on
> the Rpi, before then using sftp to upload to my website. It seems to work
> most of the time, but, as you say, this seemed to be when the corruption
> occurred.  The CRON job works every five minutes at 1,6,11... minutes past
> each hour - on the basis that weewx should have updated the archive etc by
> then - maybe that is something to do with it.
>
> 4. Further down the log file, I see:
>
> Feb 27 15:17:04 raspberrypi weewx[379]: Starting weewx weather system:
> weewxerror: unexpectedly disconnected from boot status daemon
>
> and then...
>
> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Initializing weewx version
> 3.9.1
> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Using Python 2.7.13
> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Platform
> Linux-4.14.79-v7+-armv7l-with-debian-9.6
> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Locale is 'en_GB.UTF-8'
> Feb 27 15:17:05 raspberrypi weewx[423]: engine: pid file is
> /var/run/weewx.pid
> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Using configuration file
> /etc/weewx/weewx.conf
> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Debug is 1
> Feb 27 15:17:05 raspberrypi weewx[379]: .
> Feb 27 15:17:05 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Initializing engine
> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Loading station type
> Vantage (weewx.drivers.vantage)
> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Driver version is 3.1.1
> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Socket error while
> opening port 2 to ethernet host 10.0.1.83.
> Feb 27 15:17:06 raspberrypi weewx[467]: import of driver failed: [Errno
> 101] Network is unreachable ()
> Feb 27 15:17:06 raspberrypi weewx[467]: engine: Unable to load driver:
> [Errno 101] Network is unreachable
> Feb 27 15:17:06 raspberrypi weewx[467]:   Exiting...
>
> So, looks like the internet connection went down perhaps? (I was away when
> all this happened yesterday, so not sure)
>
> Good point re making sure weewx doesn't restart until it has a sensible
> time via valid NTP connection - any idea how I do that?  I will order an
> RTC anyway I think.
>
> Thanks
>
> David.
>
> On Thu, 28 Feb 2019 at 11:25, Andrew Milner 
> wrote:
>
>> 1.  I recommend you put weewx log messages in their own log file - see
>> wiki for a) separate logfile and also logrotation.
>> 2.  The ^@ rubbish looks like possible corruption whilst executing a cron
>> task
>> 3.  What cron task was it trying to execute
>> 4.  I see the clock has gone backwards around the rubbish point -
>> implying the rpi has rebooted itself.  If that is the case you need to
>> ensure that weewx does not restart again until it has a sensible time - or
>> fit an RTC to your rpi
>>
>> All looks like some form of corruption - power supply perhaps or memory
>> card problem which is then causing a pi reboot and should cause a weewx
>> restart - but the log portion you posted does not run long enough to give
>> weewx restart details and ensure it held off until it had a valid time and
>> ntp connection.
>>
>>
>>
>> On Thursday, 28 February 2019 13:10:57 UTC+2, David Hindley wrote:
>>>
>>> Thanks.  I agree that it is probably the Raspberry Pi, rather than
>>> weewx.  My syslog file around the relevant time that it stopped working
>>> 

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[David Hindley]

Many Thanks.

1.  I will do as you suggest re separate log files.

3. The cron task was something I had to add after installing the
belchertown skin, just to copy some files from one directory to another, on
the Rpi, before then using sftp to upload to my website. It seems to work
most of the time, but, as you say, this seemed to be when the corruption
occurred.  The CRON job works every five minutes at 1,6,11... minutes past
each hour - on the basis that weewx should have updated the archive etc by
then - maybe that is something to do with it.

4. Further down the log file, I see:

Feb 27 15:17:04 raspberrypi weewx[379]: Starting weewx weather system:
weewxerror: unexpectedly disconnected from boot status daemon

and then...

Feb 27 15:17:05 raspberrypi weewx[423]: engine: Initializing weewx version
3.9.1
Feb 27 15:17:05 raspberrypi weewx[423]: engine: Using Python 2.7.13
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Feb 27 15:17:05 raspberrypi weewx[423]: engine: Platform
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Feb 27 15:17:05 raspberrypi weewx[423]: engine: Locale is 'en_GB.UTF-8'
Feb 27 15:17:05 raspberrypi weewx[423]: engine: pid file is
/var/run/weewx.pid
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Using configuration file
/etc/weewx/weewx.conf
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Debug is 1
Feb 27 15:17:05 raspberrypi weewx[379]: .
Feb 27 15:17:05 raspberrypi systemd[1]: Started LSB: weewx weather system.
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Initializing engine
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Loading station type
Vantage (weewx.drivers.vantage)
Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Driver version is 3.1.1
Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Socket error while opening
port 2 to ethernet host 10.0.1.83.
Feb 27 15:17:06 raspberrypi weewx[467]: import of driver failed: [Errno
101] Network is unreachable ()
Feb 27 15:17:06 raspberrypi weewx[467]: engine: Unable to load driver:
[Errno 101] Network is unreachable
Feb 27 15:17:06 raspberrypi weewx[467]:   Exiting...

So, looks like the internet connection went down perhaps? (I was away when
all this happened yesterday, so not sure)

Good point re making sure weewx doesn't restart until it has a sensible
time via valid NTP connection - any idea how I do that?  I will order an
RTC anyway I think.

Thanks

David.

On Thu, 28 Feb 2019 at 11:25, Andrew Milner 
wrote:

> 1.  I recommend you put weewx log messages in their own log file - see
> wiki for a) separate logfile and also logrotation.
> 2.  The ^@ rubbish looks like possible corruption whilst executing a cron
> task
> 3.  What cron task was it trying to execute
> 4.  I see the clock has gone backwards around the rubbish point - implying
> the rpi has rebooted itself.  If that is the case you need to ensure that
> weewx does not restart again until it has a sensible time - or fit an RTC
> to your rpi
>
> All looks like some form of corruption - power supply perhaps or memory
> card problem which is then causing a pi reboot and should cause a weewx
> restart - but the log portion you posted does not run long enough to give
> weewx restart details and ensure it held off until it had a valid time and
> ntp connection.
>
>
>
> On Thursday, 28 February 2019 13:10:57 UTC+2, David Hindley wrote:
>>
>> Thanks.  I agree that it is probably the Raspberry Pi, rather than
>> weewx.  My syslog file around the relevant time that it stopped working
>> yesterday is as follows.  Does anyone have any idea how to interpret this?
>> The "^@" is very puzzling to a linux novice such as me!
>>
>> David.
>>
>> Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/graphs/index.html
>> Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/records
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/records/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/reports
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/reports/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/about
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/about/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/images
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /reports
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /reports/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /about
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /about/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /images
>> Feb 27 15:30:30 raspberrypi weewx[9312]: sftpgenerator: transferred 34
>> files in 7.72 seconds
>> Feb 27 15:30:30 raspberrypi weewx[9312]: 

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[Andrew Milner]

1.  I recommend you put weewx log messages in their own log file - see wiki 
for a) separate logfile and also logrotation.
2.  The ^@ rubbish looks like possible corruption whilst executing a cron 
task
3.  What cron task was it trying to execute
4.  I see the clock has gone backwards around the rubbish point - implying 
the rpi has rebooted itself.  If that is the case you need to ensure that 
weewx does not restart again until it has a sensible time - or fit an RTC 
to your rpi

All looks like some form of corruption - power supply perhaps or memory 
card problem which is then causing a pi reboot and should cause a weewx 
restart - but the log portion you posted does not run long enough to give 
weewx restart details and ensure it held off until it had a valid time and 
ntp connection.



On Thursday, 28 February 2019 13:10:57 UTC+2, David Hindley wrote:
>
> Thanks.  I agree that it is probably the Raspberry Pi, rather than weewx.  
> My syslog file around the relevant time that it stopped working yesterday 
> is as follows.  Does anyone have any idea how to interpret this? The "^@" 
> is very puzzling to a linux novice such as me!
>
> David.
>
> Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: uploaded file 
> /belchertown/graphs/index.html
> Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: create remote directory 
> /belchertown/records
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file 
> /belchertown/records/index.html
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory 
> /belchertown/reports
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file 
> /belchertown/reports/index.html
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory 
> /belchertown/about
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file 
> /belchertown/about/index.html
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory 
> /belchertown/images
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory 
> /reports
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file 
> /reports/index.html
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory 
> /about
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file 
> /about/index.html
> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory 
> /images
> Feb 27 15:30:30 raspberrypi weewx[9312]: sftpgenerator: transferred 34 
> files in 7.72 seconds
> Feb 27 15:30:30 raspberrypi weewx[9312]: reportengine: Running report 
> 'Highcharts_Belchertown'
> Feb 27 15:30:30 raspberrypi weewx[9312]: reportengine: Found configuration 
> file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report 
> 'Highcharts_Belchertown'
> Feb 27 15:30:30 raspberrypi weewx[9312]: 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.$
> Feb 27 15:30:30 raspberrypi weewx[9312]: manager: Daily summary version is 
> 2.0
> Feb 27 15:30:44 raspberrypi weewx[9312]: cheetahgenerator: Generated 4 
> files for report Highcharts_Belchertown in 14.36 seconds
> Feb 27 15:30:44 raspberrypi weewx[9312]: copygenerator: copied 0 files to 
> /var/www/html/weewx/belchertown
> Feb 27 15:30:44 raspberrypi weewx[9312]: reportengine: Running report 
> 'Belchertown'
> Feb 27 15:30:44 raspberrypi weewx[9312]: reportengine: Found configuration 
> file /etc/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
> Feb 27 15:30:44 raspberrypi weewx[9312]: 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']
> Feb 27 15:30:44 raspberrypi weewx[9312]: manager: Daily summary version is 
> 2.0
> Feb 27 15:30:47 raspberrypi weewx[9312]: cheetahgenerator: Generated 12 
> files for report Belchertown in 3.13 seconds
> Feb 27 15:30:47 raspberrypi weewx[9312]: copygenerator: copied 1 files to 
> /var/www/html/weewx/belchertown
> Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Running report 'FTP'
> Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Found configuration 
> file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
> Feb 27 15:30:47 raspberrypi weewx[9312]: ftpgenerator: FTP upload not 
> requested. Skipped.
> Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Running report 
> 'RSYNC'
> Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Found configuration 
> file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC'
> Feb 27 15:30:47 raspberrypi weewx[9312]: rsyncgenerator: rsync upload not 
> requested. Skipped.
> Feb 27 15:31:01 raspberrypi CRON[12528]: (pi) CMD (sudo cp -f 
> 

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[David Hindley]

Thanks.  I agree that it is probably the Raspberry Pi, rather than weewx.
My syslog file around the relevant time that it stopped working yesterday
is as follows.  Does anyone have any idea how to interpret this? The "^@"
is very puzzling to a linux novice such as me!

David.

Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/graphs/index.html
Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/records
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/records/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/reports
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/reports/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/about
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/about/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/images
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/reports
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/reports/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/about
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/about/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/images
Feb 27 15:30:30 raspberrypi weewx[9312]: sftpgenerator: transferred 34
files in 7.72 seconds
Feb 27 15:30:30 raspberrypi weewx[9312]: reportengine: Running report
'Highcharts_Belchertown'
Feb 27 15:30:30 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report
'Highcharts_Belchertown'
Feb 27 15:30:30 raspberrypi weewx[9312]: 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.$
Feb 27 15:30:30 raspberrypi weewx[9312]: manager: Daily summary version is
2.0
Feb 27 15:30:44 raspberrypi weewx[9312]: cheetahgenerator: Generated 4
files for report Highcharts_Belchertown in 14.36 seconds
Feb 27 15:30:44 raspberrypi weewx[9312]: copygenerator: copied 0 files to
/var/www/html/weewx/belchertown
Feb 27 15:30:44 raspberrypi weewx[9312]: reportengine: Running report
'Belchertown'
Feb 27 15:30:44 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
Feb 27 15:30:44 raspberrypi weewx[9312]: 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']
Feb 27 15:30:44 raspberrypi weewx[9312]: manager: Daily summary version is
2.0
Feb 27 15:30:47 raspberrypi weewx[9312]: cheetahgenerator: Generated 12
files for report Belchertown in 3.13 seconds
Feb 27 15:30:47 raspberrypi weewx[9312]: copygenerator: copied 1 files to
/var/www/html/weewx/belchertown
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Running report 'FTP'
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
Feb 27 15:30:47 raspberrypi weewx[9312]: ftpgenerator: FTP upload not
requested. Skipped.
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Running report
'RSYNC'
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC'
Feb 27 15:30:47 raspberrypi weewx[9312]: rsyncgenerator: rsync upload not
requested. Skipped.
Feb 27 15:31:01 raspberrypi CRON[12528]: (pi) CMD (sudo cp -f
/var/www/html/weewx/belchertown/json/day.json
/var/www/html/weewx/belchertown/json/week.json
/var/www/html/weewx/belchertown/json/month.json
/var/www/html/weewx/belchertown/json/year.json /var/www/html/weewx/json)
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$
Feb 27 15:17:04 raspberrypi kernel: [0.00] Booting Linux on
physical CPU 0x0
Feb 27 15:17:04 raspberrypi kernel: [0.00] Linux version
4.14.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG
crosstool-ng-1.22.0-88-g8460611)) #1159 SMP Sun Nov 4 17:50:20 GMT 2018
Feb 27 15:17:04 raspberrypi kernel: [0.00] CPU: ARMv7 Processor
[410fd034] revision 4 (ARMv7), cr=10c5383d
Feb 27 15:17:04 raspberrypi kernel: [0.00] CPU: div instructions
available: patching division code
Feb 27 15:17:04 raspberrypi kernel: [0.00] CPU: PIPT / 

[weewx-user] Re: Showing message to weather website users when stopped working

[Andrew Milner]

The best tip I can give you is to identify why the site is crashing by 
looking at the weewx and webserver logs.

Weewx should never crash per se.  If it encounters an irrecpoverable 
situation it should restart.  If it is not restarting Tom would require, I 
am pretty sure, to see the log of the failure.  The log should also give 
you a clue as to the cause of the failure (if it is indeed weewx).

A more likely cause would be flakey RPi power supply or flakey SD card - 
both of which are pretty notorious issues when an RPi is running 24/7.  If 
you are also hosting the site on the RPi it is even possible that your site 
is being hacked from outside and brought down!!!

So there you have it, in a nutshell.  Find the cause first then try and 
find a solution!!!



On Thursday, 28 February 2019 11:36:14 UTC+2, hind...@gmail.com wrote:
>
> I use weewx on a Raspberry pi and post my results to my own public weather 
> station website (www.ashteadweather.com) with the excellent belchertown 
> skin.  It all works very nicely most of the time, but now and again, 
> something goes wrong and the Raspberry pi crashes and weewx stops working - 
> then my weather website shows out of date results until I notice this and 
> restart the pi and weewx - then all fine again.  Has anyone got any tips 
> for tracking these problems proactively so as to minimise the downtime 
> (rather than waiting until I happen to notice the problem) and perhaps 
> getting weewx to show a holding message on the website until the problem is 
> corrected?
>
> Thanks
>
> David.
>

-- 
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] Showing message to weather website users when stopped working

[hindleydj]

I use weewx on a Raspberry pi and post my results to my own public weather 
station website (www.ashteadweather.com) with the excellent belchertown 
skin.  It all works very nicely most of the time, but now and again, 
something goes wrong and the Raspberry pi crashes and weewx stops working - 
then my weather website shows out of date results until I notice this and 
restart the pi and weewx - then all fine again.  Has anyone got any tips 
for tracking these problems proactively so as to minimise the downtime 
(rather than waiting until I happen to notice the problem) and perhaps 
getting weewx to show a holding message on the website until the problem is 
corrected?

Thanks

David.

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