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 from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit
On Friday, February 1, 2019 at 7:29:27 AM UTC-8, Thomas Keffer wrote:
>
> Still, if you've got any early results...
>
>
>
yeah - this one is pretty interesting.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
Still, if you've got any early results...
On Fri, Feb 1, 2019 at 6:57 AM Steve2Q wrote:
> Vince..good idea. I will let it keep running and chart the results as I
> did last time. Hopefully it will level off.
>
>>
>> Steve - give it 2-3 days since you've previously seen it grow quickly.
>> What
Vince..good idea. I will let it keep running and chart the results as I did
last time. Hopefully it will level off.
>
> Steve - give it 2-3 days since you've previously seen it grow quickly.
> What the heck...have a weekend maybe and see what it looks like Sunday or
> Monday. It should stay
On Thursday, January 31, 2019 at 4:48:43 PM UTC-8, Thomas Keffer wrote:
>
> It should go up, but stabilize within a couple hours. If you let it run
> overnight, you should have a pretty good indication by morning.
>
> -tk
>
> On Thu, Jan 31, 2019 at 4:36 PM Steve2Q >
> wrote:
>
>> Tom: will the
It should go up, but stabilize within a couple hours. If you let it run
overnight, you should have a pretty good indication by morning.
-tk
On Thu, Jan 31, 2019 at 4:36 PM Steve2Q wrote:
> Tom: will the memory usage stay fairly flat if things are working
> properly? I seem to remember some
Tom: will the memory usage stay fairly flat if things are working properly?
I seem to remember some comments that it can go up, but then levels off. Is
there some average % of usage that is considered "normal"?
Steve
--
You received this message because you are subscribed to the Google Groups
Several things:
- The climb in the number of weakrefs, which are not used by WeeWX, so
must be used indirectly in a library or driver;
- Of the libraries used by WeeWX, only the usb drivers use weakrefs (I
checked);
- User Kurt has an Ultimeter, but with a serial connection
I substituted another cable. This is the result of lsusb for this one:
With the reboot, top shows 3.4%, will watch it over the next 24 hours. Just
for info; what makes you suspect the cable?
Steve
--
You received this message because you are subscribed to the Google Groups
"weewx-user"
You can comment out the debug_memory option.
I'm suspecting your serial-to-usb cable. Do you have another one you can
try?
-tk
On Thu, Jan 31, 2019 at 10:45 AM Steve2Q wrote:
> Tom and Vince:
>
> Should I leave Weewx running as is or should I comment out the
> debug_memory = True line, and
Tom and Vince:
Should I leave Weewx running as is or should I comment out the debug_memory
= True line, and switch back to the original engine.py?
I have cut and pasted the information you asked for, Tom. If it ends up
being the driver, I could always use an old version I have (11rc3) and see
Good idea. I've sent a note to a couple of them.
-tk
On Thu, Jan 31, 2019 at 9:27 AM vince wrote:
> On Thursday, January 31, 2019 at 8:00:11 AM UTC-8, Thomas Keffer wrote:
>>
>> It appears that "weakref" references are steadily climbing over time.
>> Weak references are used to aid garbage
On Thursday, January 31, 2019 at 8:00:11 AM UTC-8, Thomas Keffer wrote:
>
> It appears that "weakref" references are steadily climbing over time.
> Weak references are used to aid garbage collection in Python. They are not
> used in WeeWX, so they are probably being used by an underlying
It appears that "weakref" references are steadily climbing over time. Weak
references are used to aid garbage collection in Python. They are not used
in WeeWX, so they are probably being used by an underlying library. My
candidate is the driver for your Ultimeter.
Could you please do two things?
Tom and Glenn..thanks..it is running now. I will let it run for a full 24
hours and post the results tomorrow. At this moment (weewx running for 5
minutes), top shows 4.6% memory usage by weewxd.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
Glenn..it did say that it installed, but i will try your suggestion tomorrow.
Thanks
--
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
Hi Steve,
The error is "No module named pympler"
Looks like you've either missed step 1. of Toms instructions, or it's
failed to install.
Try installing it with sudo
sudo pip install pympler
On 30/01/2019, Steve2Q wrote:
> Tom; the previous is what I got just by stopping weewx and then
Tom; the previous is what I got just by stopping weewx and then restarting
after the mods (no reboot of the pi).
> If I reboot the pi, it hangs here:
I reverted back to the original setting so the station will keep running
until I hear back from you.
Steve
--
You received this message
Tom: I followed the instruction I received the following:
--
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
OK, Steve, I think we're ready. This is going to take a little preparation
on your part.
1. Install the tool pympler. This is a memory profiler.
*pip install pympler*
2. Replace your version of engine.py with the attached version. You should
find it in /home/weewx/bin/weewx/engine.py.
3.
Steve
I'm running with desktop.
On Tuesday, January 29, 2019 at 8:05:08 AM UTC-5, Steve2Q wrote:
> Andrew and Rich...are you running the version of Stretch with the desktop,
> of just the Lite version?
>
> My system did crash last evening as I thought it would.
>
> Steve
>
--
You received
I am not concerned about any crontab extensions. It's weewx.conf extensions
that we care about. Can you please run
*cd /home/weewx*
*./bin/wee_debug --info --output*
then email me (tkef...@gmail.com) the file /var/tmp/weewx.debug.
On Tue, Jan 29, 2019 at 6:40 AM Steve2Q wrote:
> Tom: I am
Tom: I am running Stretch on a RPi 3 + (most recent Raspian from
raspberrypi.org; the version that includes desktop however I have the pi
set to boot into the cli, not the GUI). I have run the necessary commands
to update, upgrade, and update the firmware. I used setup.py with the
Ultimeter
If I understand the situation correctly, you
- Are running plain-vanilla wheezy on a stock RPi;
- Installed weewx using setup.py;
- Are using an Ultimeter station;
- Have absolutely no extensions installed (in particular, rtg has been
disabled);
yet are experiencing memory growth.
Here is syslog from shortly before the crash.. Is there any other files
that may be useful for analysis?
Jan 28 23:44:15 raspberrypi weewx[9770]: manager: Added record 2019-01-28
23:44:00 EST (1548737040) to database 'weewx.sdb'
Jan 28 23:44:16 raspberrypi weewx[9770]: manager: Added record
Andrew and Rich...are you running the version of Stretch with the desktop,
of just the Lite version?
My system did crash last evening as I thought it would.
Steve
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
I'm running the same as you and not having any memory issues.
pi@stormRPI3:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
Looks the same as mine!!
pi@RPi3:~/perl $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
Vince, I am running Raspian with the "image with Desktop base on Debian
Stretch" (this is from the download section of raspberrypi.org). Wonder if
it is possible that the image I used has some elements for running the
Desktop that may be causing the problem. I am just speculating and it would
On Monday, January 28, 2019 at 6:42:30 PM UTC-8, Steve2Q wrote:
>
> Vince; I used setup.py for installation. Additional info: Running Debian
> 9.6 (Stretch) on a pi3 B+ . I do not have the "lite" version as I was
> using the pi for other things. Do you think not having Stretch Lite could
> be
Vince; I used setup.py for installation. Additional info: Running Debian
9.6 (Stretch) on a pi3 B+ . I do not have the "lite" version as I was
using the pi for other things. Do you think not having Stretch Lite could
be part of the problem?
Steve
--
You received this message because you
Gary..Yes, RTG is not enabled. At the time I am writing this, top yields
weewxd using 92.5% of memory. Putty is now very slow when trying to access
the pi, so I think it is very close to going down. The current up time is
21D 23H 31M. I am going to let it run till it goes down.
--
You
Steve, so just to be absolutely 100% clear, rtgd has not been running at
any time while the attached graph was compiled? If that is the case there
must be something fundamental causing the leak, I don't see a daily cron
such as you describe causing this. I have not seen a plain vanilla WeeWX
Ok..here is what has been happening so far. I am running 3.8.2 which is
"plain vanilla" with the exception of a cron which zips weewx.sdb once/day,
uploads the zip file to my website for storage, and send me an email that
the cron finished successfully. I thought the memory problem was gone
101 - 134 of 134 matches
Mail list logo
