Update: PROBLEM IDENTIFIED AND SOLVED! After following the above routine
for several days and re-reading the Davis Vantqge Pro 2 Console manual I
noted it recommends the console not be located outside. Though my mine is
located in my upstairs bedroom, away from the elements, it does get a bit
Update: Since my last post, I tried making a wireless connection to my
WeatherLinkLive unit but could not get it to work.
I have recently started running weewx again via the console and the
(faulty?) data logger. All works well for a while (about 12 hrs) then it
stops and I get a message sayin
At this point after installing weewx on different Rpis on several occasions
with the same results, like Vince I am fairly convinced the problem is with
the logger and for now I'm going wait till I can swap it out and see if it
makes a difference. If I'm lucky my friend will loan me an extra log
Timothy Bryan writes:
> Addendum to last message. This just happened when I Stopped weewx then
> started it again.
I see a lot of starting and stopping and it's really hard to separate
what happened before you did that, or if systemd did that by itself.
I am suggesting that you change things
If you changed out the pi, sd card, and pi power supply then you've
probably proven your logger is ill.
--
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
Addendum to last message. This just happened when I Stopped weewx then
started it again.
On Sat, Jan 15, 2022 at 10:13 AM Timothy Bryan wrote:
> Hi Greg(and all), just read up on systemd though don't really understand
> it. I will study more and try to figure out how to run without it. In
> th
Timothy Bryan writes:
> I installed ntp. I also disabled timesyncd.
>
> I also switched out the computer to a pi4, using the same sd card.
>
> The system came back and worked fine until 12 midnite, then, wait for
> it...it crashed.
>
> Next I plan to change the card and reinstall weewx. More a
I installed ntp. I also disabled timesyncd.
I also switched out the computer to a pi4, using the same sd card.
The system came back and worked fine until 12 midnite, then, wait for
it...it crashed.
Next I plan to change the card and reinstall weewx. More and more I am
suspecting the logger as
On Thursday, January 13, 2022 at 3:57:17 PM UTC-8 jo...@johnkline.com wrote:
> It’s not the greatest for stable time, but it’s good enough for most.
> I’ve ripped this out on my machines.
>
Me too. Just install ntp on all your systems which just plain works. You
don't even need to disable t
I should have known you'd have the answer, John!
On Thu, Jan 13, 2022 at 3:57 PM 'John Kline' via weewx-user <
weewx-user@googlegroups.com> wrote:
> I don’t the time syncs are an issue. I believe the time syncs after DHCP
> adverts are because of the following file:
>
> /etc/dhcp/dhclient-exit-h
I don’t the time syncs are an issue. I believe the time syncs after DHCP
adverts are because of the following file:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd
On each DHCP renewal, this script is called which causes a restart with the NTP
servers passed by DHCP (which probably haven’t changed).
Change one thing at a time please.
On Thursday, January 13, 2022 at 1:37:21 PM UTC-8 timot...@gmail.com wrote:
>
> Sorry Tom, didn't see your question. The logger is a USB logger not a
> serial with a USB adaptor.
>
> I'll try the pi4 and see if we can maybe eliminate the pi(s) as being the
>
Sorry Tom, didn't see your question. The logger is a USB logger not a
serial with a USB adaptor.
I'll try the pi4 and see if we can maybe eliminate the pi(s) as being the
culprits. I am also trying to locate another logger.
Don't know what to say about the network time synchronizations.
Tha
All I can suggest is that if you can swap in a different pi/SD/power-supply
and it goes away, that would point to the pi3 being the problem. If the
problem continues with a different computer, that would point to your
datalogger probably.
Your logger will save a week of readings, so there's li
The only things I have plugged in besides the logger is the keyboard. The
mouse is Bluetooth. I have on occasion shared the keyboard with another
computer, but not very often. I thought about the power supply and it was a
2.4 amp cube but to be safe I changed it to a 3 amp cube and that is wha
In addition to Vince's questions, here's one more: are you using a
serial-to-usb converter? If so, do you have another one you can try? They
are notoriously flaky.
You also have a *lot* of network time synchronizations, which always follow
a DHCP router advertisement. I have no idea what that mean
Are you plugging stuff in and unplugging it a lot ?
Do you have 'just' the usb keyboard plugged in ?
Is there anything else plugged into the USB slots ?
How are you powering your pi ?
Most issues on a pi are from a slow SD card, or an overburdened USB
subsystem or the pi is being powered with a w
This is the output from "dmesg --ctime"
On Thursday, January 13, 2022 at 8:16:16 AM UTC-10 vince wrote:
> Please run:
> dmesg --ctime
>
> I see it went whacko at 00:44 or so but I sure don't see anything saying
> why.
>
>
>
--
You received this message because you are subscribed to the G
Please run:
dmesg --ctime
I see it went whacko at 00:44 or so but I sure don't see anything saying
why.
--
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 wee
It looks like an instance of weewx was running, but, for some reason,
systemd stopped it. Can we see earlier in the log? It may give us a clue as
to why.
On Thu, Jan 13, 2022 at 7:00 AM Timothy Bryan wrote:
> It happening again at at around 1am. I woke and noticed it at 4am.
> Though I am creat
It happening again at at around 1am. I woke and noticed it at 4am. Though
I am creating a log as described in "Help! Posting To Weewx Users," I don't
know how to attach "/var/log/messages" log.
Sorry for the ignorance but I am learning, all-be it slowly,
Tim
On Wednesday, January 12, 2022 a
On Wednesday, January 12, 2022 at 5:26:22 PM UTC-8 timot...@gmail.com wrote:
> It seems the crashes only occur roughly between 10pm and 2am either side
> of midnight.
>
>
Well when it happens again, we need to see /var/log/messages and
/var/log/syslog for the period before+after it fails, and a
I guess I'm not following. The log excerpt you posted had a crash around
0830. Was this atypical? If so, you should post the log for your "late
night" crashes.
On Wed, Jan 12, 2022 at 5:26 PM Timothy Bryan wrote:
> No. Nothing else is running on the pi except weewx. It seems the crashes
> only
No. Nothing else is running on the pi except weewx. It seems the crashes only
occur roughly between 10pm and 2am either side of midnight.
> On Jan 12, 2022, at 2:53 PM, vince wrote:
>
> "right on time" What time ?
>
> Do you have some cron job running at a particular time of day that
24 matches
Mail list logo
