Re: [weewx-user] Re: launch of report thread aborted: existing report thread still running.

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

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

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

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

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

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

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:

Re: [weewx-user] To many data :-)

Hi Hajo, On 12 October 2017 at 08:06, Hajo Harms wrote: > Hi Glenn > > so I use weewx 3.7.1 and meso 0.4.0 with raw_0.4.1-lh.py. > > But my section of def newLoop Packet looks different [...] Okay, use the attached version of Luc's ( raw_0.4.3-lh.py ) with that change

Re: [weewx-user] launch of report thread aborted: existing report thread still running.

Weewx does not launch a new reporting thread if an old one is active. This keeps them from queuing up. As for why your old thread failed to finish... well, it's impossible to say without seeing the log. -tk On Wed, Oct 11, 2017 at 2:05 PM, Oscar wrote: > Lost power

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

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

Re: [weewx-user] To many data :-)

Hi Glenn so I use weewx 3.7.1 and meso 0.4.0 with raw_0.4.1-lh.py. But my section of def newLoop Packet looks different def newLoopPacket(self, event): packet = event.packet prune_period = 300 # It's possible for records with duplicate dateTimes - this occurs when an

[weewx-user] launch of report thread aborted: existing report thread still running.

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 issue was resolved. As a test, I disconnected power and the same issue

[weewx-user] Re: weewx interceptor with acurite and raspberry not working.

On Thursday, August 31, 2017 at 12:28:44 PM UTC-6, Eddie Lent wrote: > > I my set up is an acurite smarthub, a raspberry pi 1 running weewx and > weewx-interceptor in sniff mode, port mirroring using netgear GS105Ev2. > > I can't seem to get data into weewx. > I can run tcpdump on my router

Re: [weewx-user] Wunderground reporting "missing wind data"

It stays in the direction of the last wind. If the wind was from the North, it will stay pointing North, but when the station reports no wind it sends that it's zero from the East (even though it's physically pointing North. On Monday, September 25, 2017 at 9:30:16 AM UTC-5, Andrew Milner

[weewx-user] Re: Weewx and WH4000 with PI3

Yeah it works nowso thank you all for your help. I´m very happy. I know it is not easy to talk with an newbie ;-). Greetings Holm -- 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

Re: [weewx-user] Re: NOAA Dropdown not populating

Well, perhaps the error was caused by copying from the RPi to Windows. In any case, we still have not seen a log file. Set debug=1, restart weewx, then post the log from startup to the first report generation. -tk On Wed, Oct 11, 2017 at 5:52 AM, Mauro De Lauretis < mauro.delaure...@gmail.com>

Re: [weewx-user] Re: NOAA Dropdown not populating

Thanks for your reply Tom, I will have a look at it as soon as I can, but It seems strange because I didn't get the error you posted me, Il giorno martedì 10 ottobre 2017 14:19:35 UTC+2, Tom Keffer ha scritto: > > When I try your template (renamed as index.html.tmpl) and your skin >

[weewx-user] Re: Reports not generating

Thanks for the advice. I just needed to wait a while to get some logs entries of use. My assumption was that when I ran wee_reports (which was completing in a few milliseconds), that logs would be generated that would help, but that’s not the case for me. The root of the problem was