Thanks Glen!
Sorry for the delay. I thought I posted this yesterday.
I found the issue with multiple copies of weewx running. On another note,
I removed systemd (Thanks!). Time is set in rc.local. The pi has an old
time until rc.local runs. Here is the current log.
Dec 31 17:00:20 zk30
Hi Oscar,
A working hardware clock on the pi should kick in soon after bootup.
As I recall a systemd installation requires a few adjustments if
you're working from a wheezy HowTo.
If you have a look at the rorpi HowTo it gives some extra details for
the systemd changes
https://github.com/glennmck
Notice you have a date of Nov-3 and then it flips back to Oct-11 ?
That can really blow weewx's mind.
You need the clock right before weewx starts, or at a minimum you need the
clock to not go 'backward' while the daemon is running.
--
You received this message because you are subscribed to the
Here are portions of the startup file.
Here is portions of the startup file.
# set the hardware clock
wait_for_time_set() {
if [ ! -f /sys/class/i2c-adapter/i2c-1/new_device ]
then
echo "Setting Clock"
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
hwclock -s
I added a hardware clock to fix the not posting data problem. It appears I
may have a problem. Here is the log. I manually killed power at 18:40:41
Oct 11 18:40:22 zk30 weewx[1513]: copygenerator: copied 0 files to
/home/weewx/weewx/html
Oct 11 18:40:29 zk30 weewx[1513]: cheetahgenerator: Gen
On Wednesday, October 11, 2017 at 2:05:33 PM UTC-7, Oscar wrote:
>
> Lost power the other day. When power came back on, the error "launch of
> report thread aborted: existing report thread still running." was being
> written to the log file every couple of seconds. I restarted weewx and the
>
