lving the cause, or minimising the
> chances of lock up occurring, rather than focussing on recovery methods.
>
>
>
> On Tuesday, 12 December 2017 14:31:42 UTC+2, Redanman wrote:
>
>> Yes, I did look at the Wiki on FineOffset lock-ups, but as I mentioned in
>>
and they
are immaculate. I changed the USB cable a little while back, but that had
no effect. I'll try a different power supply for the Pi as their
performance can drop off with time or maybe I'll try and find a powered hub
from somewhere.
On Monday, 11 December 2017 22:54:03 UTC, Redanman wrote:
>
&
I'll have a look inside the console, I must admit that I have a habit of
taking things to bits to see what's inside, but the weather station has sat
there for 5 years and I've never taken a screwdriver to it.
On Monday, 11 December 2017 22:54:03 UTC, Redanman wrote:
>
> My old WH1080 is g
For anyone else struggling with this problem, the behaviour pattern of USB
lock-ups has completely changed when I swapped the Pi power supply for a
different one. My system was locking up at 1 to 2 day intervals on the old
power supply; I am now at 10 days without a problem on the new power
Thank you. Problem solved (hopefully).
Mike
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on
OK, that's done and I've checked that the cmon parameters are being written
to the syslog. Let's see what happens.
Mike
--
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
My system configuration is :
Weewx version 3.9.1 running on a Raspberry Pi Zero
Aercus Weathersleuth weather station with Weewx using Interceptor driver
over local network
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
Weewx crashed again tonight with what seems to be the same root cause.
Here is the syslog just at the moment it crashed. Again, looking at the
data, I cannot see any spurious text/numbers. Out of interest, is accum.py
run every iteration of the engine or only on an interval?
May 6
I had Debug=1 when it crashed. I've gone back into the syslog archives and
pulled out the section starting roughly 5 minutes before the last crash.
At that point everything seems to be running fine. See attached.
Mike
On Sunday, 28 April 2019 04:28:14 UTC+1, mwall wrote:
>
> could you set
For me it's an Aercus WeatherSleuth. The section of my config pertaining
to this device is :
[Interceptor]
# This section is for the network traffic interceptor driver.
# The driver to use:
driver = user.interceptor
port = 55
device_type = observer
On Saturday, 27
not
clear the problem, it needed a sudo reboot to get back to normal.
Mike
On Sunday, 28 April 2019 12:26:02 UTC+1, mwall wrote:
>
> On Sunday, April 28, 2019 at 2:29:41 AM UTC-4, Redanman wrote:
>>
>> I had Debug=1 when it crashed. I've gone back into the syslog archives
Thank you for any possible insights into what might be causing Weewx to
occasionally crash. The relevant part of the syslog is :
Apr 26 08:20:32 raspberrypi weewx[7715]: File
"/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
Apr 26 08:20:32 raspberrypi
I've updated my Weewx to 4.0 and then 4.1 in the last few days and in doing
so I've noticed that on each archive cycle there are 174 consecutive log
messages of the type shown below :
Jun 1 17:40:55 raspberrypi weewx[9275] DEBUG user.forecast: ReportThread:
_get_stats: '>' not supported
Hi. I decided to upgrade to Weewx 5.0.2 this morning.The upgrade
itself seemingly ran without errors. My system is a virtual machine
running Debian 11 - Bullseye.
However, on checking Weewx status, the program has exited with this error
sequence in the syslog file
Feb 18 12:16:08 debian
it.
>
> -tk
>
> On Sun, Feb 18, 2024 at 4:34 AM Redanman wrote:
>
>> Hi. I decided to upgrade to Weewx 5.0.2 this morning.The upgrade
>> itself seemingly ran without errors. My system is a virtual machine
>> running Debian 11 - Bullseye.
>>
>&
15 matches
Mail list logo
