Mmmm - I'll have a look to see if there is an issue with the delay setting.

I've had a look at the log file and I can't see any reason why it should 
just stop like that. I fact, how do you know that it *has* stopped? Can you 
do a 'ps' or 'top' to se if the process is still running, or if you are 
using systemd, then do a status on weewx to see what has happened.

As far as I know (and in like with the original title of this thread) if 
there was an error then it should have displayed that and then continued. 
In my (limited) experience, Python code only stops when the program exits 
normally.

Susan

On Saturday, April 7, 2018 at 6:44:11 PM UTC+10, Graham Seward wrote:
>
> Hi Susan
> Your last comment got me to thinking about the loop delay so I reset 
> weewx.conf to a loop delay of 15 secs. It has now been running for 14 hours 
> without a glitch so it looks like I had caused the problem but I’m not sure 
> how. I will leave it as is.
> Thanks 
> Graham 
>
> Sent from my iPad
>
> On 5 Apr 2018, at 03:37, vk3...@gmail.com <javascript:> wrote:
>
> You are not being a nuisance at all, but it is a bit hard to do 'remote 
> diagnostics'.
>
> The log file would be useful but not the whole thing: just the part a bit 
> before you start weewx until just after it has stopped will be enough.
>
> Where are you setting the loop delay value and can you show us the 
> file/line in question?
>
> Susan
>
> On Thursday, April 5, 2018 at 2:20:53 AM UTC+10, Graham Seward wrote:
>>
>> Hi Susan
>>
>> Regret to say that weewx stopped running again without writing anything 
>> to syslog, messages or user.log. Syslog shows that when weewx starts it is 
>> using the correct version of the driver, so I’m puzzled as to what is going 
>> on. Would you like a copy of the syslog file in it’s entirety to see if 
>> that throws up any clues?
>>
>>  
>>
>> I’m going to run weewx again but with your original driver to see what 
>> happens this time. Incidentally if I set the loop-delay to 60 secs the 
>> program doesn’t run at all – currently set at 30secs. 
>>
>>  
>>
>> Sorry to be a nuisance!
>>
>> Graham
>>
>>  
>>
>> *From:* weewx...@googlegroups.com <weewx...@googlegroups.com> *On Behalf 
>> Of *vk3...@gmail.com
>> *Sent:* 04 April 2018 03:50
>> *To:* weewx-user <weewx...@googlegroups.com>
>> *Subject:* Re: [weewx-user] Re: weewx crashes with error: unpack 
>> requires a string of len 104
>>
>>  
>>
>> Grrrr - too long since I wrote the code and I made a stupid mistake. The 
>> two 'loginf' lines should read
>>
>>  
>>
>> loginf('Bad data: length = {0}'.format(len(rxData)))
>>
>> loginf('Bad data: "{0}"'.format(rxData))
>>
>>  
>>
>> I've attached your file with the correction in it.
>>
>>  
>>
>> Sorry about that.
>>
>>  
>>
>> Susan
>>
>>  
>>
>> -- 
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> 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 <javascript:>.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to