Hi,
When you start or restart weewx one of the first things it does is
Dec 4 12:15:48 raspberrypi weewx[13161]: HP1000: Retrieving startup records
Previously I had records going back to 2017. It would start to download
these "historc" values (i.e. because it was the first time I'd used weewx
I'm not sure what procedure you are talking about with the 'historic'
values.
As far as the HP1000 driver is concerned, it looks at the last date in the
weewx database and then queries the weather station for any records it has
for after that date. Therefore it typically only downloads historic
OK Update.
I did get the new Pi but I've not installed it with weewx.
I was "fiddling" with the historic values on the WS and I went to delete
all the 2017 ones. Instead I accidentally deleted the 2018 ones so by then
it was too late.
Once I'd gone back and deleted all the 2017 entries and the
>
>
> I must be missing something but I can't see any error messages in the logs
> posted so far. Without those it i shard to guess what is going on.
>
>
Exactly. That's why I suspect it's a kernel-level problem. If the problem
were in user's space, it should have generated an exception.
-tk
--
I must be missing something but I can't see any error messages in the logs
posted so far. Without those it i shard to guess what is going on.
As far as I am aware, I don't have any try-except blocks that capture and
ignore everything and if an error occurs in the HP1000 driver that I don't
catc
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,
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 in
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
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
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'
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 wro
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,
> a
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-de
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/Aussie
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 sni
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
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
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[2
19 matches
Mail list logo
