rustymyers

I ran without Home Assistant for a few days and things seem to be ok. When starting it again, I got an update for the Alexa Media Player integration to fix an infinite loop and memory exhaustion: https://github.com/alandtse/alexa_media_player/pull/2589 After updating and running Home Assistant for another day I have not received any out of memory errors. I'm going to continue to bring containers online one by one to see if the issue returns, but for now I'm going to blame the issue above as the main culprit. I'll continue to post as I check things to ensure I have isolated the issue and share my results. Thanks again! rusty

6ba7fd76579f9d0638ab122feba7c103e977ac04b07fe58fcfaeab655fe0b13f is a swag container (https://github.com/linuxserver/docker-swag). It has fail2ban and spans many nginx processes. 1d1c308d88054708609009b1a4ab5c02180e54ad530e239c4f418fff5e8138fd is grocy (https://github.com/grocy/grocy). Redis is used for Manyfold, but I think that's it. I got another OOM error last night and Home Assistant was the only container not running, so I wonder if that's what's causing the errors. HomeAssistant is constantly dying on me, so I'm wondering if something there is being reaped? Searching for the python3 process that's causing this is certainly a difficult task! Thanks rusty

Thanks! I'm curious as to what you're looking for to diagnose which containers might be taking over memory?

Still getting the Out of Memory Error. Additional diagnostics attached. rustymyers-diagnostics-20241004-1056 2.zip

Thank you Michael_P! I removed my credentials and changed them. I've started by disabling mosquitto and openeats, hoping to not see the error again. Looks like mosquitto was updated a day ago, so perhaps an issue is happening there. Much appreciated! rusty

Howdy, I'm getting the `Out of memory errors detected on your server` every 30-60 minutes. I have been rebooting and disabling Docker containers to isolate the issue. I'm unsure what is going on, however I did get a diagnostics export (attached). Any ideas on the "Out of memory errors detected on your server" message? rustymyers-diagnostics-20241004-0904 2.zip

I'm running the Jupyter docker and it's working well, but I'm unable to get a password authentication configured instead of using a token. It seems the config files are not being written or are being reset after updating/restarting the container. I have /root/.jupyter forwarded to /mnt/user/appdata/jupyterlab/config; which seems to work to load a config file: Loaded config files: /root/.jupyter/jupyter_server_config.json The contents of the file are { "IdentityProvider": { "hashed_password": 'argon2:XXXXXXXXXXXXXXXXXXXXXXXXX', "allow_password_change": false } } Is there another way to prevent the token/password change screen and set a password for the server? Thanks rusty

I WAS able to provision a certificate today. It worked as expected. Thanks!

Having the same issue, ProvisionCert.php returns no results in logs. Attached diagnostics. spidercache-diagnostics-20220718-1316.zip