[weewx-user] Re: weewx stopped for no apparent reason

Yes, everything has been working fine since the changes. No, there isn't anything else talking to the WLL, except that the WLL posts to the Davis WLL website - but those are all outbound. Since I changed the check on the counter from 1 to 2 I have seen none of those warning messages. I wait

[weewx-user] Re: weewx stopped for no apparent reason

OK, I've just taken a look into the 5 minutes thing. Forget my point from above, the 5 minutes correspond to the 300 second archive interval. I was able to confirm this by changing the interval. Michael Schantl schrieb am Freitag, 18. Juni 2021 um 15:41:57 UTC+2: > OK, will push a new release

[weewx-user] Re: weewx stopped for no apparent reason

OK, will push a new release shortly with the change you suggested. Did everything work in the last few days? On the topic of the regular messages, is there any other device or process talking to the WLL. I've noticed that the WLL's HTTP server can act weird when there are too many connections

[weewx-user] Re: weewx stopped for no apparent reason

FYI, now that I am monitoring for the WARNING messages, I am seeing them like clockwork every 5 minutes - in the SAME SECOND for which I see weewx "Added record" messages. Doubt it is a coincidence - correlation is nearly 99% (once in a while there is no WARNING. Suggest only issuing the

[weewx-user] Re: weewx stopped for no apparent reason

FYI, just had my first case under the new code - worked fine. Suggestion: The message logged is the same for both start_broadcast and request_current - spotted that when I saw the message and I couldn't tell which had failed without looking at the debug log to see the DEBUG entry - and even

[weewx-user] Re: weewx stopped for no apparent reason

FYI, I did have an instance of the issue late yesterday, and the patch I put did allow it to recover. I just installed the dev release snapshot and will keep you posted if/when I see the recoveries. THANKS! JRJ On Saturday, June 12, 2021 at 1:50:39 PM UTC-5 michael.s...@gmail.com wrote: >

[weewx-user] Re: weewx stopped for no apparent reason

FYI, since I made the change (using my own code, and only on the WllPollHost related call, it has stayed up. HOWEVER, it also has not issued any error message, and it has not yet been, say, 3 days, so that might be a coincidence. After, say, Tuesday, I'll give your new dev release a whirl

[weewx-user] Re: weewx stopped for no apparent reason

Hi JRJ, thank you for the extensive debugging. I've just pushed a new dev release . Yeah, you're right with the missing timeout. I had assumed the requests library honors the socket timeout configured

[weewx-user] Re: weewx stopped for no apparent reason

I noticed that there is no timeout keyword on the request call davis_http.request_current. I will add one to see if it helps. (I also note that there is no timeout on the call in start_broadcast either. JRJ On Friday, June 11, 2021 at 10:58:48 AM UTC-5 Jay Jaeger wrote: > I just noticed

[weewx-user] Re: weewx stopped for no apparent reason

I just noticed that the call to _poll_callback() [to WllPollHost.poll] is indeed apparently not returning - noticed in the above logs that there is NO message "Polled current conditions". Working theory: if it receives a UDP (broadcast) packet while it is doing the HTTP poll request, the

[weewx-user] Re: weewx stopped for no apparent reason

Happened again while I was looking at logs. Just for grins, I fired off an HTTP request from my PC, and it woke back up. So: for some reason the WLL driver scheduler _do_tick method call to _poll_callback() never returns, so that _do_tick never returns to _scheduler_tick and thus it goes

[weewx-user] Re: weewx stopped for no apparent reason

Here are some more datapoints from the log that confirm that the needed HTTP request to the WLL box is not occurring: Jun 10 22:37:01 mythtv2 weewx[239040] DEBUG user.weatherlink_live.scheduler: 13scheduler ticks until next push refresh Jun 10 22:37:01 mythtv2 weewx[239040] DEBUG

[weewx-user] Re: weewx stopped for no apparent reason

This time it lasted only a couple of hours before Jun 10 22:37:44 mythtv2 weewx[239040] DEBUG urllib3.connectionpool: Starting new HTTP connection (1): vantagevieww.lan:80 [Last HTTP request] Jun 10 22:37:45 mythtv2 weewx[239040] DEBUG urllib3.connectionpool: http://vantagevieww.lan:80 "GET

[weewx-user] Re: weewx stopped for no apparent reason

So, it happened again. Here is how the events seem to have unfolded, based on the logs: *** The last HTTP request seems to have gone out at 16:26 (so, before data stopped flowing) - there were no more HTTP requests after that - it was the last appearnce of http or HTTP from the weewx process

[weewx-user] Re: weewx stopped for no apparent reason

@eric thread population is up to you, if you want to post on this one, that is fine with me. FYI, I have now been running a little over 1 full day with debug with the newer WeatherLinkLive driver with no untoward events - but note that the first one took over two days to occur. On Thursday,

[weewx-user] Re: weewx stopped for no apparent reason

@JRJ, it appears this (or something similar) has just happened on my weewx 4.5.1 installation. I suppose I should start a new thread on it. I'll be watching yours to see if you find out whats going wrong! On Wednesday, June 9, 2021 at 2:29:39 PM UTC-5 cub...@gmail.com wrote: > @michael: No,

[weewx-user] Re: weewx stopped for no apparent reason

@michael: No, that is not what I am saying. In fact, the converse is likely true: that it ALSO stopped recording data in the database, as there are no more messages of the sort "Added record ... to database" INFO level messages in my logs once this occurred, as can be seen in my original post

[weewx-user] Re: weewx stopped for no apparent reason

@JRJ: So, you're saying that WeeWX stopped generating reports but data still was recorded in the database, correct? If yes, it seems unlikely that it's a driver issue and more on the weewx engine's side. cub...@gmail.com schrieb am Mittwoch, 9. Juni 2021 um 20:22:01 UTC+2: > @chris: yes,

Re: [weewx-user] Re: weewx stopped for no apparent reason

Jay: I tried 'sudo service weewx restart', and it did NOT fix the problem. I rebooted the machine, and it worked great. Hopefully, now that I've got debug enabled, if it happens again, I can debug it. Thank you for sharing your WMII driver for Python 3! Chris Shaker On 6/9/2021 11:20 AM,

[weewx-user] Re: weewx stopped for no apparent reason

@chris: yes, indeed, the issue on my system was that weewx stopped producing reports (and also there were no reporting-related messages in the log. I do am now running with debug set to 1 in the config. JRJ On Wednesday, June 9, 2021 at 12:09:08 PM UTC-5 cjsh...@gmail.com wrote: > JRJ: > >

[weewx-user] Re: weewx stopped for no apparent reason

@Chris: Version 3 weewx with my wmII was rock solid. I didn't run the wmII more than a day under version 4, so I can't speak to that. I had no issues restarting weewx - didn't need a reboot. NOTE: systemd behavior, being what it is, if a service crashes, it still is not STOPPED, and it

[weewx-user] Re: weewx stopped for no apparent reason

I have set debug to 1, and disabled the crontab reboot, to see if I can collect some debug data. Chris Shaker On Wednesday, June 9, 2021 at 10:09:08 AM UTC-7 Christopher Shaker wrote: > JRJ: > > Are you saying that weewx stopped generating reports? My weewx stopped > generating reports, with

[weewx-user] Re: weewx stopped for no apparent reason

JRJ: Are you saying that weewx stopped generating reports? My weewx stopped generating reports, with no error messages, at 4:00 AM. Restarting service weewx did not fix it. Rebooting my raspberry pi DID fix it. So, I added a crontab entry to reboot my raspberry pi each morning: 5 4 * * *

[weewx-user] Re: weewx stopped for no apparent reason

@michael: It should not be related to the SCP upload, which continues even after weewx has gone "night night". It is running from a cron, not under weewx. It merely copies the generated HTML/graphics up to another machine. It runs every 17 minutes. If it were, say, locking up a file and

[weewx-user] Re: weewx stopped for no apparent reason

@vince: I worked in IT for over 36 years, and with UNIX and "C" since 1976. I know what I am doing. There can be lots of reasons why an issue appears on one machine vs. another, often related to the timing relationship between events. Yes, it occurred to me that logging at the DEBUG level

[weewx-user] Re: weewx stopped for no apparent reason

Nah, the logging level change doesn't matter, I've published a dev release a few days ago making exactly that change. I'd suggest you to try the new driver version anyway since I also made some changes regarding the HTTP interaction with the WLL. You should also enable debug logging so we get

[weewx-user] Re: weewx stopped for no apparent reason

On Tuesday, June 8, 2021 at 12:43:44 PM UTC-7 cub...@gmail.com wrote: > (Note: I did "tweaked" the WLL driver code to suppress the "Emitting > poll/(broadcast) messages by changing those two log calls to "log.debug"). I'd suggest running the unaltered driver and especially in this case so

[weewx-user] Re: weewx stopped for no apparent reason

FYI, it has happened again, at about 18:00 today. Any suggestions on instrumentation? JRJ On Tuesday, June 8, 2021 at 2:43:44 PM UTC-5 Jay Jaeger wrote: > I knew the log looked "normal" aside from messages from weewx stopping - > had there been some error or other, I would have tracked it

[weewx-user] Re: weewx stopped for no apparent reason

I knew the log looked "normal" aside from messages from weewx stopping - had there been some error or other, I would have tracked it down on my own. The log extract was done using "grep weewx /var/log/syslog" [my logs rotate at midnight]. (Note: I ded "tweaked" the WLL driver code to

[weewx-user] Re: weewx stopped for no apparent reason

Hi, I'm the author of that WLL driver. Yes, the UDP broadcasts come from the WeatherLink Live. The driver should continue to 'tickle' the WLL even if any packets should have been missed, so that shouldn't be an issue. Were there no errors in the log? Your log dump looks absolutely normal. -

[weewx-user] Re: weewx stopped for no apparent reason

Oh it is worse than unwise. I know better (I worked in network security for years) - incredibly STUPID is more like it. Fortunately, a sandboxed, unpriviledged user - and fixed now. ;) [I tried to edit the post post facto to take it out, but it wouldn't let me edit the post. 8(] That

[weewx-user] Re: weewx stopped for no apparent reason

First thing, it's unwise to post your password for the world to see, so go change that now. :^) Next, if weewx is stopped, try that scp command from the command line. It's way easier to debug that way. As for your firewall entries, it looks like something is talking directly to your gateway