There was a subtle difference in how I was creating the next day accumulator 
vs. how WeeWX proper is doing it.  I’ve changed that.  Please install 1.3.15 
and let me know how it goes at midnight.

> On Jul 6, 2020, at 10:44 PM, geni08...@gmail.com <geni0815.0...@gmail.com> 
> wrote:
> 
> Jul  7 00:00:01 Wetter-Raspi rsyslogd:  [origin software="rsyslogd" 
> swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com";] rsyslogd 
> was HUPed
> Jul  7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded.
> Jul  7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files.
> Jul  7 00:00:02 Wetter-Raspi systemd[1]: man-db.service: Succeeded.
> Jul  7 00:00:02 Wetter-Raspi systemd[1]: Started Daily man-db regeneration.
> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
> 2020-07-07 00:00:00 CEST (1594072800) to database 'weewx'
> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
> 2020-07-07 00:00:00 CEST (1594072800) to daily summary in 'weewx'
> 
> 
> geni08...@gmail.com schrieb am Dienstag, 7. Juli 2020 um 07:39:52 UTC+2:
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> Traceback (most recent call last):
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>  File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>    self.day_accum.addRecord(pkt)
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>  File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>    % (record['dateTime'], self.timespan))
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> weewx.accum.OutOfSpan: Attempt to add out-of-interval record (1594072801) to 
>> timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 2020-07-07 00:00:00 CEST 
>> (1594072800)])
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> During handling of the above exception, another exception occurred:
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> Traceback (most recent call last):
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>  File "/usr/share/weewx/user/loopdata.py", line 370, in process_queue
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>    self.day_accum.addRecord(pkt)
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>  File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****   
>>    % (record['dateTime'], self.timespan))
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:     ****  
>> weewx.accum.OutOfSpan: Attempt to add out-of-interval record (1594072801) to 
>> timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 2020-07-07 00:00:00 CEST 
>> (1594072800)])
>> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Rotate log files...
>> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Daily man-db 
>> regeneration...
>> 
>> 
>> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 07:09:28 UTC+2:
>>> It looks like loopdata stopped again at midnight (I looked at your sight).
>>> 
>>> I think it likely that something in the packet at midnight is causing this. 
>>>  Loopdata does print a stack trace on an unexpected exception before 
>>> exiting.  Would you have a look in the log and send it?
>>> 
>>> If the stack trace doesn’t give me the info I need, I will send you an 
>>> instrumented version of loopdata.py that will, among other things, log loop 
>>> packets around midnight.
>>> 
>>>>> On Jul 6, 2020, at 10:26 AM, John Kline <jo...@johnkline.com> wrote:
>>>>> 
>>>> 
>>> 
>>>> BTW, I should probably make dewpoint position on the weatherboard 
>>>> configurable between dewpoint and appTemp.  That would save you from 
>>>> having to hack on the javaascript.
>>>> 
>>>> Also, I could make the legend configurable for translation.
>>>> 
>>>> I’ll try to do that today or tomorrow.
>>>> 
>>>>>> On Jul 6, 2020, at 10:19 AM, John Kline <jo...@johnkline.com> wrote:
>>>>>> 
>>>>> 
>>>>> Yep, you’ll need to make your changes to switch to appTemp.  That’s both 
>>>>> a change in index.html.tmpl and in the realtime_updater.inc file.
>>>>> 
>>>>> A new day accumulator gets created at midnight, so I am very interested 
>>>>> in that loopdata crash.  Do you have a stacktrace in the log?  Please 
>>>>> send what you have.  If it’s not descriptive enough, I’ll update loopdata 
>>>>> to provide more info on that crash.
>>>>> 
>>>>>> On Jul 6, 2020, at 8:20 AM, geni08...@gmail.com <geni08...@gmail.com> 
>>>>>> wrote:
>>>>>> 
>>>>>> 
>>>>>> I have replaced the index.html.tmpl with an old version! However, the 
>>>>>> appTemp is not yet running. Loopdate also crashed at midnight, so watch 
>>>>>> that today.
>>>>>> 
>>>>>> jo...@johnkline.com schrieb am Montag, 6. Juli 2020 um 15:50:11 UTC+2:
>>>>>>> Now that I’m up for the morning, I went to look at your WeatherBoard 
>>>>>>> page to see what the JavaScript error was, but I see that it is up and 
>>>>>>> runnning!
>>>>>>> 
>>>>>>>>> On Jul 6, 2020, at 3:44 AM, John Kline <jo...@johnkline.com> wrote:
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>>> Send realtime_updater.inc and weewx.conf.
>>>>>>>> The JavaScript is broken. I’ll have a look.
>>>>>>>> 
>>>>>>>>>> On Jul 5, 2020, at 10:35 PM, geni08...@gmail.com 
>>>>>>>>>> <geni08...@gmail.com> wrote:
>>>>>>>>>> 
>>>>>>>>> I have weewx-loopdata 1.1.13, only the default km_per_hour 
>>>>>>>>> definition -> the loop-data.txt is OK.
>>>>>>>>> Why is my WeatherBoard not working? Only time is running.
>>>>>>>>> 
>>>>>>>>> -- 
>>>>>>>>> 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+...@googlegroups.com.
>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/b24a6c1c-9b40-4c1b-abde-cf1c40d127e2n%40googlegroups.com.
>>>>>>>>> <index.html.tmpl.txt>
>>>>>> 
>>>>>> -- 
>>>>>> 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+...@googlegroups.com.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/441af783-906b-4497-a023-733da7ec6cc3n%40googlegroups.com.
> 
> -- 
> 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 the web visit 
> https://groups.google.com/d/msgid/weewx-user/9583022e-a87f-4991-8b71-9704b18c9ecen%40googlegroups.com.

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/1357BB1A-6A73-4ABB-BC2A-7F0DBDB80C84%40johnkline.com.

Reply via email to