What is in the backups doesn’t matter really,  Lets see the output of 
‘weectl extension list’ and if it isn’t there, post your weewx.conf file 
with any usernames and passwords obfuscated,

On Wednesday, November 19, 2025 at 4:15:22 PM UTC-8 Peter Fletcher wrote:

> I have never (as far as I can remember) used any skin other than a couple 
> of modified versions of the old (early V 4.x, or possibly even V 3.x) 
> Seasons skin, nor have I installed anything within Weewx to track memory 
> usage. The references to the mem system are present in a backup copy of my 
> conf file from 2023, but, as I noted, I don't recall seeing the mem.db file 
> before the last few days. I will look at a few backup images to see if I 
> can confirm this. It is a puzzler!
>
> On Wednesday, November 19, 2025 at 12:07:39 PM UTC-5 vince wrote:
>
>> It is not referenced in the weewx.conf put into place on a new 
>> installation (link 
>> <https://raw.githubusercontent.com/weewx/weewx/refs/heads/master/src/weewx_data/weewx.conf>
>> ).
>>
>> I wrote a memory usage skin/extension that uses a db of that name,  so if 
>> your extensions include that one, that might be it.  
>>
>> On Wednesday, November 19, 2025 at 7:15:41 AM UTC-8 Peter Fletcher wrote:
>>
>>> There have been a few references to mem_binding in weewx.conf for a long 
>>> time and mem.db is referenced in the stanza for MySQL, but I don't recall 
>>> previously seeing a file of that name in my data directory. One has now 
>>> appeared and appears to be being actively updated. I would note that this 
>>> is not the system referred to in another recent message on which I am 
>>> experimenting with MySQL - it should just be using Sqlite. Have I just been 
>>> blind before, or has something changed?
>>
>>

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/ec9fc234-cf8b-49c8-bcb2-d75e467b189fn%40googlegroups.com.

Reply via email to