Vince,

As I stated earlier, I have no knowledge how to get program modbusenergy 
stable. 
I only can monitor the difference in memory leak with different settings.
Restarting a program doesn't change the used memory.

Luc

On Friday, 27 March 2020 16:32:56 UTC-3, Vince Skahan wrote:
>
> On Friday, March 27, 2020 at 11:47:34 AM UTC-7, Lucas Heijst wrote
>
>> Program modbusenergy has a memory leak of 80 KB per 24 h (nothing new), 
>> so the memory will be full after 7.5 days.
>> It looks like the program starts and stops a program twice per second, 
>> because each time I perform 'ps aux' the count is higher (2 counts per 
>> second).
>> Currently the counter has reach a maximum of 32316 and does't increase 
>> anymore.
>>
>> I have too little knowledge of linux and python to debug the memory leak, 
>> so as a work-around my system is rebooted each 5th day.
>>
>>
>>
> I'd reiterate my earlier suggestion......
>
> - disable everything except one thing
> - run it and get that stable
> - add one thing at a time
> - get 'that' stable
> - then add the next thing
> - and so on
>
> Alternately.....
>
> - start with your as-is
> - disable one thing at a time
> - see if that fixes things for a few days
> - if not, disable the next thing
> - and so on (ie, same as above, just by subtracting services)
>
> From your skeletal description it certainly sounds like modbusenergy might 
> be your problem.  Can you disable that first for a few days and see if 
> things stabilize ?
>
> You should never have to reboot a Linux system for stability reasons.   My 
> ancient 128 MB RAM Seagate dockstar running my primary weewx has been up 
> for 3.3 years, although I reset weewx occasionally when I update versions 
> that of course.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" 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-development/6c485b26-a93f-4c88-b5d0-b188a28c1206%40googlegroups.com.

Reply via email to