On Tuesday, 28 February 2017 07:50:50 UTC-8, vince wrote:
>
>
> I run weewx on a computer with 128MB RAM, if that helps any.
>
> One thing to watch for is the forecast extension, which can use a 'lot' of
> memory (or it did for me), but weewx plus a couple skins is very light
> typically.
>
On Monday, February 27, 2017 at 7:41:47 PM UTC-8, Francisco Puig wrote:
>
> @mwall,
>
> Thanks a lot for your analysis. I'm running an RPi B = 512 MB of RAM, if
> the issue show up again I can swap it for a RPi 3 that has 1GB of RAM and
> better CPU, maybe is overkill but I really like how weewx
@mwall,
Thanks a lot for your analysis. I'm running an RPi B = 512 MB of RAM, if
the issue show up again I can swap it for a RPi 3 that has 1GB of RAM and
better CPU, maybe is overkill but I really like how weewx works. I will do
some tests to see what happen.
On Monday, February 27, 2017 at
On Monday, February 27, 2017 at 6:01:46 PM UTC-5, mwall wrote:
>
> the memory use of weewx was 149066/90779 VSZ/RSS just before it was killed.
>
btw, typical memory use for weewx is 12000-5 for RSS and 12-25
for VSZ
so your 90779 is a bit high (probably due to the 5 uploaders?), but
On Monday, February 27, 2017 at 1:33:20 PM UTC-5, Francisco Puig wrote:
>
> I just sent the logs from the last 24hrs before and after the crash.
>
francisco,
how much memory is in the pi?
you are generating only the Standard report. your reports take 20 to 80
seconds to run. this is slow,
I just sent the logs from the last 24hrs before and after the crash.
Thanks in advance for the help.
On Monday, February 27, 2017 at 1:20:32 PM UTC-5, mwall wrote:
>
> On Monday, February 27, 2017 at 1:02:30 PM UTC-5, Francisco Puig wrote:
>>
>> @mwall , here is the logs. The last log is the
On Monday, February 27, 2017 at 1:02:30 PM UTC-5, Francisco Puig wrote:
>
> @mwall , here is the logs. The last log is the Before and after the memory
> crash issue. I hope to find the reason, could be a memory leak in some
> place. I manually restarted the service at Feb 27 11:07:43.
>
>
@mwall , here is the logs. The last log is the Before and after the memory
crash issue. I hope to find the reason, could be a memory leak in some
place. I manually restarted the service at Feb 27 11:07:43.
*root@weather_bridge:~# sudo grep oom /var/log/**
grep: /var/log/apache2: Is a
francesco,
it would also help if you could post more context about why the
out-of-memory killer was activated. see the answer to this posting:
http://unix.stackexchange.com/questions/128642/debug-out-of-memory-with-var-log-messages
and post any oom/total_vm results you find:
sudo grep oom
On Monday, February 27, 2017 at 11:18:00 AM UTC-5, Francisco Puig wrote:
>
> After 45 days running in a raspberry pi my weewx suddenly stopped. I
> found on the logs a *"**Out of memory: Kill process 472 (python) score
> 814 or sacrifice child"* error. I restarted the weewx service and
>
10 matches
Mail list logo
