Re: [weewx-user] Re: Second crash after 11 days

Gary..yes..I believe you are correct, but there is something kind of nagging at me, so I am going to do a controlled test (ie writing down what I do) rather than trying to remember the steps I go through. On Thu, Jul 18, 2019, 11:40 AM gjr80 wrote: > Hi Steve, > > Haven’t we been round this

Re: [weewx-user] Re: Second crash after 11 days

Hi Steve, Haven’t we been round this buoy before? I thought you had previously disabled all things SteelSeries and it had more or less no effect on the problem. I thought the issue/leak had been nailed down to the driver(can’t link to a post on this device but on 6 Feb Tom said): Well, that's

Re: [weewx-user] Re: Second crash after 11 days

Peter..yes, Weewx is running when I backup. I have it scheduled to run on an odd minute once/day. Archiving runs on the even minute. -- 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: Second crash after 11 days

Do you back up your database with Weewx still running? I ask because I also use Steelseries on a Raspi and I've never had a problem. I have a script that stops Weewx momentarily at 3am, makes a copy of the database, and then restarts it. -- You received this message because you are subscribed to

Re: [weewx-user] Re: Second crash after 11 days

A follow-up to the memory problem. At present, Weewx will run for 45 days before my script restarts the program at 80% memory usage (approx 1.8% increase/day). I am not home, but when I get back I will shut down SteelSeries gauges and see what effect that has. The gauges are the only extension

Re: [weewx-user] Re: Second crash after 11 days

Thanks Gary...as usual, your fix was spot on! Steve On Mon, May 27, 2019 at 11:19 PM gjr80 wrote: > Steve, > > When I look at your gauges just now they are not working, the clue is in > the scroller message - 'error: Not Found'. This means the gauges.js > script cannot find gauge-data.txt. I

Re: [weewx-user] Re: Second crash after 11 days

Steve, When I look at your gauges just now they are not working, the clue is in the scroller message - 'error: Not Found'. This means the gauges.js script cannot find gauge-data.txt. I suppose it is possible that when we uncommented the SteelSeries skin a few days ago to get your plots back

Re: [weewx-user] Re: Second crash after 11 days

Do you have gauge-data.txt in the directory with your gauges? It looks like you might not. By the way, I got the same results with desktop chrome and on my android phone. Could you be seeing different results because of a browser cache? On Mon, May 27, 2019 at 5:25 PM Steve2Q wrote: > Gary...I

Re: [weewx-user] Re: Second crash after 11 days

Gary...I was away for the weekend, so when I checked in using the Chrome browser on my phone, the Steel Gauges were, and still are, working. However, if I pull up the guages on my desktop or tablet, they are frozen and "offline". Please take a look at photokinetics.org/Weather and click on

Re: [weewx-user] Re: Second crash after 11 days

Gary..thank you! that did the trick! -- 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

Re: [weewx-user] Re: Second crash after 11 days

Steve Ok, looks like you disabled the SteelSeries skin completely (not sure but this could be due to some instructions from me in the past, my apologies if I did say to to that). To fix you need to: 1. Uncommment the entire [[SteelSeries]] Stanza in weewx.conf (note you have a couple of

Re: [weewx-user] Re: Second crash after 11 days

Gary, thanks for answering. My regular weewx charts update, and the steel gauges themselves are operating correctly on my 2 second update. Only the graphs on the steel gauges are "stuck" on the installation date. He is the [StdReport] stanza from weewx.conf, followed by skin.conf for

Re: [weewx-user] Re: Second crash after 11 days

Steve, Regards the SteelSeries Gauges plots, when you installed rtgd and disabled the SteelSeries skin from producing gauge-data.txt you didn't happen to disable the whole SteelSeries skin did you? To use rtgd with the SteelSeries skin you need to disable the SteelSeries skin generation of

Re: [weewx-user] Re: Second crash after 11 days

Leon and Vince; first thanks for your help and advice. My only experience in programming was a LONG time ago, so anything I learn is either from helpful people like you or what I can figure out by searching the web. I did come to the conclusion that the nesting order of the expressions is most

Re: [weewx-user] Re: Second crash after 11 days

Your script has a lot of errors in it from a quick look-see, did you have a cut+paste massacre perhaps ? - if weewxd is not running at all, it'll blow up in your 'if' statement - you have braces and parens all messed up in your usage calculation line - do you really mean '3' and '4'

Re: [weewx-user] Re: Second crash after 11 days

Leon: thank you very much for your reply...lots of interesting things there. I like the top command rather than free as top would give me the % of memory used by weewxd. I took the command ps -C weewxd -o comm,size,rss,vsize,%mem (which I never saw before, thank you!) and shortened it to ps -C

Re: [weewx-user] Re: Second crash after 11 days

Leon: thank you very much for your reply...lots of interesting things there. I like the top command rather than free as top would give me the % of memory used by weewxd. I took the command ps -C weewxd -o comm,size,rss,vsize,%mem (which I never saw before, thank you!) and shortened it to ps -C

Re: [weewx-user] Re: Second crash after 11 days

Leon: thank you very much for your reply...lots of interesting things there. I like the top command rather than free as top would show me the % of memory used by weewxd. I took the command ps -C weewxd -o comm,size,rss,vsize,%mem (which I never saw before, thank you!) and shortened it to ps

Re: [weewx-user] Re: Second crash after 11 days

Hey, Steve, I must have missed the context, but if you are looking at overall system memory growth, well, it's a normal / healthy thing for a Linux kernel to try to use as much memory as possible at all times, to keep from having to go back to disk for code pages as different processes context

Re: [weewx-user] Re: Second crash after 11 days

A little follow up. As the memory growth is still happening, I implemented a script which runs the program free -m and does a little calculation to determine if memory use is over 80% (or any % I want to use). If mem >80% weewx is restarted. So at least it now will run unattended. A new

Re: [weewx-user] Re: Second crash after 11 days

Seems like I may not be upgrading. I have to point out that even after switching back to 11rc3 the memory growth is still there albeit slower. I guess I did not notice it before as the failure occurred over a longer period of time than what happened when a different driver was installed after

Re: [weewx-user] Re: Second crash after 11 days

Looks like memory growth is a problem using Python 3, under Debian 9.8. Sigh. http://www.threefools.org/weewx/ -tk On Mon, Mar 4, 2019 at 5:31 AM Thomas Keffer wrote: > Both the 0.11rc3 and 0.25 drivers are compatible with the current version > of WeeWX. > > I guess we'll include the v0.25

Re: [weewx-user] Re: Second crash after 11 days

Both the 0.11rc3 and 0.25 drivers are compatible with the current version of WeeWX. I guess we'll include the v0.25 driver in the distribution, but it sure is ugly and inefficient! -tk On Sun, Mar 3, 2019 at 10:06 AM Steve2Q wrote: > Hello; as of today, Weewx has been running for 96 hours

Re: [weewx-user] Re: Second crash after 11 days

Hello; as of today, Weewx has been running for 96 hours and Top shows memory to be 9.9% which is a big improvement. I don't know if you want to do any more tweaking, Tom. If not, I can always set a cron to stop and restart Weewx once a month. This would be a restart when Mem = 54% I would

Re: [weewx-user] Re: Second crash after 11 days

Here are today's numbers: 48 hours at 6.6%. While it is still going up, at the present rate I estimate that it should hit 90% in 55 days, which is much better than the 11 days it started at. Maybe it will level off. I will continue my updates. And thank you Tom and Matt for continuing to help.

Re: [weewx-user] Re: Second crash after 11 days

Tom: I will let it run as is, and report back tomorrow with 48 hour stats. -- 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

Re: [weewx-user] Re: Second crash after 11 days

5% is way better than before, no? I would expect occasional buffer errors with this version. The serial port is constantly getting opened and closed. If a new packet comes in at the wrong time, parts of it could get missed. On Thu, Feb 28, 2019 at 10:22 AM Steve2Q wrote: > Tom; at 25 hours top

Re: [weewx-user] Re: Second crash after 11 days

Tom; at 25 hours top shows 5.0% v 4.4% at 24 hours for 11rc3 and is still going up. Also 0.25 is throwing off sporadic buffer errors as follows. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving

Re: [weewx-user] Re: Second crash after 11 days

Steve, progress report? Is version 0.25 holding steady? On Wed, Feb 27, 2019 at 9:33 AM Thomas Keffer wrote: > Well, that's the current kernel version. Let's see how it goes with the > new Ultimeter driver. > > -tk > > On Wed, Feb 27, 2019 at 8:58 AM Steve2Q wrote: > >> I am going to try .25

Re: [weewx-user] Re: Second crash after 11 days

Well, that's the current kernel version. Let's see how it goes with the new Ultimeter driver. -tk On Wed, Feb 27, 2019 at 8:58 AM Steve2Q wrote: > I am going to try .25 now. Here is the result of uname -a > > -- > You received this message because you are subscribed to the Google Groups >

Re: [weewx-user] Re: Second crash after 11 days

I am going to try .25 now. Here is the result of uname -a -- 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

Re: [weewx-user] Re: Second crash after 11 days

The pl2303 is certainly a well known module. Which kernel? *uname -a* Here's yet another version, 0.25. This one opens and closes the port with every read. Incredibly inefficient, but if it gets the job done... -tk On Wed, Feb 27, 2019 at 7:50 AM Steve2Q wrote: > Tom: The memory usage

Re: [weewx-user] Re: Second crash after 11 days

Follow up: I did not stop Weewx before unplugging/replugging the USB/serial adapter from the Pi. I got the following, so I had to reboot to restart Weewx. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop

Re: [weewx-user] Re: Second crash after 11 days

Tom: The memory usage started at 3.4% on startup of Weewx. Then 6.8% at 14 hours and now 7.3% at 16 hours. Here is the result of dmesg | tail -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving

Re: [weewx-user] Re: Second crash after 11 days

It started at about 4.4%, right? You know, I just noticed another difference: 0.11 closed the serial port after every read, whereas 0.2x opens it only once, then leaves it open for all reads. That makes me think there might be an issue with the hardware device driver. Can you check and see what

Re: [weewx-user] Re: Second crash after 11 days

Tom: here are the results as of now: the new driver (v .24) is 6.8% after 14 hours v 4.0% after 16 hours with 11rc3. Looks like something else is still using increasing memory. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe

Re: [weewx-user] Re: Second crash after 11 days

We will solve the problem with the newer drivers!  Try this version. It reads data byte-by-byte, just like 0.11rc3. -tk On Tue, Feb 26, 2019 at 1:40 PM Steve2Q wrote: > Weewx has been running for 24 hours now with the 11rc3 driver. Top shows > 4.4% memory usage v 7.5% for the 0.22 driver. A

Re: [weewx-user] Re: Second crash after 11 days

Weewx has been running for 24 hours now with the 11rc3 driver. Top shows 4.4% memory usage v 7.5% for the 0.22 driver. A previous run of 11rc3 resulted in 4.8% after 31 hours v 9.0% for v 0.22 So obviously there is something going on with the newer drivers, but I cannot hazard a guess as to

Re: [weewx-user] Re: Second crash after 11 days

I meant 11rc3. -- 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

Re: [weewx-user] Re: Second crash after 11 days

Tom..I will put 11rc2 back and let it run for at least 24 hours. Then, we will know for sure if there is an increase in memory usage. I will post the results. Steve -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group

Re: [weewx-user] Re: Second crash after 11 days

I haven't been using TOP to monitor memory usage - I have cmon running and note the total memory use is creeping up. I restarted this station a couple of times yesterday. I had a request to show the freezing level on some charts - ended up setting soilTemp4 to 32 degrees and including it on

Re: [weewx-user] Re: Second crash after 11 days

My experience so far: With driver v 0.22, I first did a run of 44 hours with the DISABLE_ removed from the set time and get time portions of the driver. TOP showed 3.3% memory usage at startup, which climbed to 10.4% at 44 hours. I then replaced the DISABLE_ in both lines which put the driver

Re: [weewx-user] Re: Second crash after 11 days

I saw no errors during the run of over 30 minutes. I edited out the DISABLED_ under the get_time and set_time portion of the driver and restarted with debugs commented out. TOP show weexd at 3.3% -- You received this message because you are subscribed to the Google Groups "weewx-user" group.

Re: [weewx-user] Re: Second crash after 11 days

I guess so. Are you worried about the log size? I just want to make sure we capture any data gaps. -tk On Thu, Feb 21, 2019 at 9:28 AM Steve2Q wrote: > Tom..is 30 minutes enough time with debug and debug_serial both set to 1 ? > > -- > You received this message because you are subscribed to

Re: [weewx-user] Re: Second crash after 11 days

Tom..is 30 minutes enough time with debug and debug_serial both set to 1 ? -- 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

Re: [weewx-user] Re: Second crash after 11 days

Be sure to run with debug=1 and debug_serial=1 as per my earlier email . On Thu, Feb 21, 2019 at 9:18 AM Ralph Underwood wrote: > I have v0.22 running now and it appears to work - no buffer errors. > > Ralph > > -- > You

Re: [weewx-user] Re: Second crash after 11 days

I will test v0.22. Thanks!! On Thursday, February 21, 2019 at 9:04:04 AM UTC-8, Ralph Underwood wrote: > > The URL for the development station is http://www.mapleleaf.ruresearch.com. > This station is in my basement lab area - the wind and rain stuff is > sitting on a counter so that's why

Re: [weewx-user] Re: Second crash after 11 days

The URL for the development station is http://www.mapleleaf.ruresearch.com. This station is in my basement lab area - the wind and rain stuff is sitting on a counter so that's why there are no readings for them. The "Temperature 1" reading is from a DS18B20 sensor connected to an Adafruit

Re: [weewx-user] Re: Second crash after 11 days

OK, thanks, Ralph. Let's try this version of the driver, v0.22. This one is a little more sophisticated. It reads in buffer fulls (and, thus, is more efficient), but parcels them out byte-by-byte. It has the ability to throw away anything leading up to the buffer header (b'!!'). This is v0.22.

Re: [weewx-user] Re: Second crash after 11 days

Ralph. Thanks for joining this discussion. A few questions: 1. What is your station URL? There are not too many of us Ultimeter users, but I think it is great that Tom, Matt, Andrew, Vince and so many other help out our small population as best they can. Having another 2100 user may make

Re: [weewx-user] Re: Second crash after 11 days

I have a couple of stations with Ultimeter 2100 and usb-serial connections to RPi 3 B+. Both appear to have increasing memory usage. I just copied the "new" ultimeter.py driver to the driver directory and restarted - this was my result. I went back to "old" version of driver and restarted

Re: [weewx-user] Re: Second crash after 11 days

Oops. The set of valid buffer lengths was wrong. Try this one. On Thu, Feb 21, 2019 at 5:49 AM Thomas Keffer wrote: > Possibly, but I don't think so. The way I read the documents, a given > instrument has a given buffer length. Yours seems to be 52 bytes, which is > what the driver is

Re: [weewx-user] Re: Second crash after 11 days

Possibly, but I don't think so. The way I read the documents, a given instrument has a given buffer length. Yours seems to be 52 bytes, which is what the driver is expecting. The trouble is there is a communications glitch. Then the number of bytes may be unknown. It would help if you could

Re: [weewx-user] Re: Second crash after 11 days

A follow up: According to Peet Bros web site the Ultimeter 2100 (and several other models) emit data in 48 byte chunks in Data Logger Mode, while ultimeter.py (version .20) apparently expects 52 bytes. Could this be the problem?. Here is a snip from their web site: - *Data Logger Mode**:

Re: [weewx-user] Re: Second crash after 11 days

Hello: I have been out of town for several days. The good news is top shows weexd using only 4.6% of memory. The bad news is there are now many gaps in the charts (see example), which apparently are caused by the "unexpected error byte messages" I have been getting. So the question remains

Re: [weewx-user] Re: Second crash after 11 days

Matt...I have the model 2100, and it was manufactured in 2006 (I just got off the phone with Peet Bros.). Just FYI, you probably know this information, but here is the link to their page which shows the serial output for the different modes: http://www.peetbros.com/shop/custom.aspx?recid=29

Re: [weewx-user] Re: Second crash after 11 days

On Thursday, February 14, 2019 at 2:06:48 PM UTC-5, Steve2Q wrote: > > I set debug = 1, and rebooted. I then left the Pi running and then stopped > and restarted Weewx. Attached is syslog. It appears that there is an > "unexpected header bytes" error, which sometimes continues and at other >

Re: [weewx-user] Re: Second crash after 11 days

On Thursday, February 14, 2019 at 10:59:35 AM UTC-5, Thomas Keffer wrote: > > Matthew, do you recall why the time-related functions were disabled? > not enough testing. as i recall, the only feedback i got about them was from steve, and that was confounded by other issues he was having at the

Re: [weewx-user] Re: Second crash after 11 days

Matthew, do you recall why the time-related functions were disabled? -tk On Thu, Feb 14, 2019 at 7:55 AM mwall wrote: > > > On Thursday, February 14, 2019 at 10:12:37 AM UTC-5, Steve2Q wrote: >> >> The only difference now is the console clock is no longer being corrected >> as it was with

Re: [weewx-user] Re: Second crash after 11 days

On Thursday, February 14, 2019 at 10:12:37 AM UTC-5, Steve2Q wrote: > > The only difference now is the console clock is no longer being corrected > as it was with version 11rc3. > that is because setting the time is disabled in v0.20 of the ultimeter driver. you can enable it by changing

Re: [weewx-user] Re: Second crash after 11 days

Here is an update. After running for 16 hours 40 minutes memory usage is 5.0%, and Weewx itself is running normally. The only difference now is the console clock is no longer being corrected as it was with version 11rc3. -- You received this message because you are subscribed to the Google

Re: [weewx-user] Re: Second crash after 11 days

Here is an update. After running for 16 hours 40 minutes memory usage is 5.0%, and Weewx itself is running normally. The only difference now is the console clock is no longer being corrected as it was with version 11rc3. -- You received this message because you are subscribed to the Google

Re: [weewx-user] Re: Second crash after 11 days

Here is an update. After running for 16 hours 40 minutes memory usage is 5.0%, and Weewx itself is running normally. The only difference now is the console clock is no longer being corrected as it was with version 11rc3. Steve > -- You received this message because you are subscribed to the

Re: [weewx-user] Re: Second crash after 11 days

The one thing that gives me pause with my version is that it reads the lines in fixed length chunks: 52 bytes. Unfortunately, not all Ultimeters support the full buffer. Some emit 48 bytes, other 44. The amount is changeable via a [Ultimeter] setting, but earlier versions could handle all 3 buffer

Re: [weewx-user] Re: Second crash after 11 days

On Wednesday, February 13, 2019 at 12:15:22 PM UTC-5, Steve2Q wrote: > > A general question; if it turns out that both 11rc3 and 0.20 work, is > there any other advantage to changing to 0.20? Is it more compatible with > future changes in Weewx or perhaps with Python 3? > it may not affect

Re: [weewx-user] Re: Second crash after 11 days

It is slightly less resource intensive (it reads in 52 byte chunks instead of 1 byte chunks) and, yes, it has been ported to Python 3. -tk On Wed, Feb 13, 2019 at 9:15 AM Steve2Q wrote: > Tom. I am going to let Weewx run for another 12 hours before making the > change. That way I can be sure

Re: [weewx-user] Re: Second crash after 11 days

Tom. I am going to let Weewx run for another 12 hours before making the change. That way I can be sure memory usage has leveled off. A general question; if it turns out that both 11rc3 and 0.20 work, is there any other advantage to changing to 0.20? Is it more compatible with future changes

Re: [weewx-user] Re: Second crash after 11 days

I think we're getting closer. The biggest difference I see is that the current version uses the function serial.readline(), which reads to a newline, while the old version uses repeated calls to serial.read(), requesting a single byte each time, until it gets a full line. It's entirely possible

Re: [weewx-user] Re: Second crash after 11 days

Hi Tom: Attached is the 11rc3 version of ultimeter.py Steve -- 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

Re: [weewx-user] Re: Second crash after 11 days

Steve: could you send me the exact copy of ultimeter.py that you are using, so I can diff it? I can't find a version 11rc3 in git. Only version 11, and it is about 4 years old. On Wed, Feb 13, 2019 at 6:38 AM Steve2Q wrote: > Possible success??!! > > Yesterday I changed only one item, the

Re: [weewx-user] Re: Second crash after 11 days

Possible success??!! Yesterday I changed only one item, the driver. I rolled back to 11rc3 which has had two effects. First, after running for 24 hours the memory usage is up to only 4.4% where before it would be around 9+%. Second, Weewx has reset the time on my console to within 2 seconds

Re: [weewx-user] Re: Second crash after 11 days

I will try substituting an older version of the driver to see if that makes any difference. -- 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

Re: [weewx-user] Re: Second crash after 11 days

On Monday, February 11, 2019 at 6:43:06 PM UTC-8, Steve2Q wrote: > > Is there any possibility that substituting an older driver may work? The > newest version (0.18) is quite different than the older ones. > > > Still think you need to find a weewx user with the same driver+version and

Re: [weewx-user] Re: Second crash after 11 days

Tom: Thanks for checking in..I was going to get back to you after a few more days of running. At at this point, it still appears to be acting the same way. It is so regular that I derived a formula for % of memory v time: % = .253 (time in hours) + 3.24 For 2 Days 6 hours 50 minutes, % =

Re: [weewx-user] Re: Second crash after 11 days

Steve, how is it going with this? On Wed, Feb 6, 2019 at 9:16 AM Steve2Q wrote: > Tom: I upgraded pyserial and have rebooted. I will run just the regular > instance of weewx without the simulator, and will see how that goes. Weewxd > started at 3.4% mem usage. > > -- > You received this message

Re: [weewx-user] Re: Second crash after 11 days

Tom: I upgraded pyserial and have rebooted. I will run just the regular instance of weewx without the simulator, and will see how that goes. Weewxd started at 3.4% mem usage. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from

Re: [weewx-user] Re: Second crash after 11 days

That's the version that's included in the debian package python-serial. Looking through the pyserial change log , I don't see any obvious patches for memory leaks between v3.2.1 and v3.4. The only major difference (besides API

Re: [weewx-user] Re: Second crash after 11 days

My version is 3.2.1 -- 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

Re: [weewx-user] Re: Second crash after 11 days

Well, that's pretty definitive: the problem is in the driver, or its underlying libraries. Can you check what version of pyserial you are using: *python -c "import serial; print serial.VERSION"* I get "3.4" -tk On Wed, Feb 6, 2019 at 6:56 AM Steve2Q wrote: > Here is this mornings results.

Re: [weewx-user] Re: Second crash after 11 days

Here is this mornings results. No change in the simulator, but weewx itself is going up. I was wondering if it would help with diagnosis if I tried running an older driver version. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe

Re: [weewx-user] Re: Second crash after 11 days

Tom: Here is the screenshot of Top showing both instances running. Obviously, the simulator is using far less memory. I will check tomorrow AM and send an updated screen capture. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe

Re: [weewx-user] Re: Second crash after 11 days

On Tuesday, February 5, 2019 at 10:38:36 AM UTC-5, Thomas Keffer wrote: > > I really only need the 'top' results for the instance running the > simulator: is it growing in its memory use? > > On Tue, Feb 5, 2019 at 7:11 AM Steve2Q > > wrote: > >> Tom: After I run my system for a few more days,

Re: [weewx-user] Re: Second crash after 11 days

I really only need the 'top' results for the instance running the simulator: is it growing in its memory use? On Tue, Feb 5, 2019 at 7:11 AM Steve2Q wrote: > Tom: After I run my system for a few more days, let me know which file(s) > you would like to see. > > -- > You received this message

Re: [weewx-user] Re: Second crash after 11 days

Tom: After I run my system for a few more days, let me know which file(s) you would like to see. -- 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

Re: [weewx-user] Re: Second crash after 11 days

Another data point: I installed the stretch 4.14.94 kernel that Steve is using, then ran weewxd using my VPro2. No memory growth. I'll be interested to see the results of running the simulator. -tk On Mon, Feb 4, 2019 at 12:12 PM Thomas Keffer wrote: > It is helpful for figuring out which

Re: [weewx-user] Re: Second crash after 11 days

It is helpful for figuring out which services WeeWX is loading. Not essential, but useful for when you post a log. -tk On Mon, Feb 4, 2019 at 11:04 AM Steve2Q wrote: > Tom..now that I have a better understanding of the process, I will > implement the change. Before I do that, I note that you

Re: [weewx-user] Re: Second crash after 11 days

Tom..now that I have a better understanding of the process, I will implement the change. Before I do that, I note that you have debug = 1 in weewx_mem.conf, while in my weewx.conf debug is not set. Should I set it to 1 in my weewx.conf? -- You received this message because you are subscribed

Re: [weewx-user] Re: Second crash after 11 days

Yes, the memory would increase for the WeeWX instance running the Ultimeter. Nothing changes there. What we are trying to see is if the same thing happens with the simulator. That would point to whether or not it has anything to do with the hardware, driver, and serial interface. You can, of

Re: [weewx-user] Re: Second crash after 11 days

Tom: I am not sure how this would work. If I am running both the Ultimeter and the Simulator simultaneously, wouldn't I get the same memory increase as data from the Ultimeter would still be coming in? Steve -- You received this message because you are subscribed to the Google Groups

Re: [weewx-user] Re: Second crash after 11 days

Good idea. You don't even need to shut down your Ultimeter. Just run a second instance of weewx, using the attached configuration file weewx_mem.conf. It will put the database in subdirectory /home/weewx/archive2, and the generated reports in /home/weewx/public_html2. Put it in /home/weewx, then

Re: [weewx-user] Re: Second crash after 11 days

Tom and Vince. It appears that using the serial connections on the Pi is a relatively easy thing to do. I just need the proper adapter and then have to make a few changes in the software for the pi and Weewx. I am going to order one, do the change and see what happens. Steve -- You received

Re: [weewx-user] Re: Second crash after 11 days

Kevin..thats what I am doing now until a resolution is found. On Sun, Feb 3, 2019 at 9:01 AM Kevin Hedgepeth wrote: > I ran into a problem with my pi randomly shutting down. I set CRON to > restart my pi every night and have not had a problem since. The only > adverse effect is that the

Re: [weewx-user] Re: Second crash after 11 days

On Monday, February 4, 2019 at 6:37:14 AM UTC-8, Thomas Keffer wrote: > Steve, I'm at a loss. You are running a simple system, on a well-known > platform, yet experiencing memory growth. > > Tom - the only thing I can think of is to take the driver and usb stuff out of the equation temporarily

Re: [weewx-user] Re: Second crash after 11 days

I've been running WeeWX on an RPi with stretch for a day now. I don't have an Ultimeter, so I used a VPro2 console, which also has a serial interface. Memory use is VIRT=48416, RES=33500 and seems to be steady. I'm using kernel Linux-4.14.79-v7+-armv7l-with-debian-9.6, which is a slightly older

Re: [weewx-user] Re: Second crash after 11 days

Tom..thank you for taking the time to help. For now I will reboot the system when the % gets up to around 80. It will be interesting if this is a problem with Stretch. I wonder if any other Pi users have similar problems with Stretch or they are using an older Raspian distro. -- You received

Re: [weewx-user] Re: Second crash after 11 days

Well, that's no good. I've been doing some of my own tests here, and think that the weakrefs are an artifact of using pympler. I am running some experiments on my end with stretch. Unfortunately, I don't have a lot of time at the moment, so it may take a while. -tk On Sat, Feb 2, 2019 at 1:18

Re: [weewx-user] Re: Second crash after 11 days

Now up to 15% :( -- 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

Re: [weewx-user] Re: Second crash after 11 days

Rats. It should have leveled off by now. On Fri, Feb 1, 2019 at 1:13 PM Steve2Q wrote: > Tom, so far it is climbing. Started at 3.4, this AM it was 7.7, and now 9.1 > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from

Re: [weewx-user] Re: Second crash after 11 days

Tom, so far it is climbing. Started at 3.4, this AM it was 7.7, and now 9.1 -- 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

Re: [weewx-user] Re: Second crash after 11 days

... and climbing? Or, has it been stable? On Fri, Feb 1, 2019 at 1:01 PM Steve2Q wrote: > Weewxd using 9.1% of memory as of now. > > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails

  1   2   >