unable to reproduce error - driver too reliable! sending the debug==3 logs anyway (direct to gary rather than clog up the forum) in case they prove useful later. three logs, one with GW1000 disconnected a bit more than 30 secs, another with just a few secs disconnection and another much longer (about 15 mins) - with suffix .txt (sorry about previous .log). at that debug level there is a lot of noise from my Alarms service…
i must have hit a corner case on my first test. i don’t know weewx guts well enough but OSError exception (rather than IOError) coming from StdPrint sounds very strange, maybe a resource exhaustion Q: “Is there anything noteworthy about your GW1000/WeeWX machine network connections? Does the log cover two disconnections of the GW1000?" A: single disconnect, while moving GW1000 to its permanent position ready for cutover. no unusual config - both server (RPi 4) and GW1000 on wifi only, no service interruptions during tests, no weird interface-bending apps cheers > On 17 Aug 2020, at 3:10 pm, gjr80 <[email protected]> wrote: > > I've spent some time trying to work out what is going on here and I am still > not 100% sure. The exception that is causing the restart after the 10 second > wait is being raised in StdPrint. If that is the case the behaviour you are > seeing when the GW1000 is pulled is different to what I have seen. Is there > anything noteworthy about your GW1000/WeeWX machine network connections? Does > the log cover two disconnections of the GW1000? > > Can I get you to set debug = 3 in weewx.conf and then restart WeeWX. Let > WeeWX run so that at least two 'Augmented packet:' lines are displayed then > unplug the GW1000 from its power supply. Assuming that causes the same > OSError can you reconnect the GW1000 after at least 30 seconds. Assuming > again that WeeWX reconnects to the GW1000 let it run for another two > 'Augmented packets:' and then post the log from WeeWX startup. Could you also > post the log as a .txt file rather than a .log, .log gives me some real > headaches trying to open them on some mobile devices. > > Gary > > On Sunday, 16 August 2020 23:48:15 UTC+10, Graham Eddy wrote: > i pulled the power plug on the gw1000 to test the new recovery/rediscover and > it did not go well. > it is cycling through restart of the engine, with gw1000 service falling over > soon after starting (it does find a device first). > extract from log showing a couple of those cycles with weewx.debug==2 attached > > -- > 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 [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/4573f5aa-30b4-4fce-9a06-de9933fa208ao%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/4573f5aa-30b4-4fce-9a06-de9933fa208ao%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/D1FF9A3F-2895-4A81-AE51-13ECDFEB0C60%40gmail.com.
