For now, no, but error messages did not necessarily arrive immediately, so I will wait a few days.
Currently, I have about 120 ping at the moment (on the gateway), but no Gladys updates yet.
Edit: 20 ping locally and between 100 and 140 on the gateway (version 4.0.7
)
Hi @pierre-gilles,
After a few days of trouble-free operation, I unfortunately have the error messages back on the 4 boxes of my dashboard as in my message from 01/28. The ping has not necessarily increased, but the loading of the boxes is slow again and ends with an error.
I remain available if you want to take a look at the logs.
Hi @Mastho!
Bummer. In my opinion, there must be an integration on your end that is causing issues. From what weâve seen, itâs clearly a « local » problem with the instance.
What integrations do you already have configured? And with what settings?
Could you possibly send me your local database in private so I can try running your config locally on my end? (If you donât mind and thereâs nothing sensitive in it)
If you donât mind, the database is located on the Pi at:
/var/lib/gladysassistant/
There are 3 files I need (gladys-production.db, gladys-production.db-shm, gladys-development.db-wal). If you can stop Gladys before copying the files, thatâs better ![]()
Otherwise, we can call tomorrow and investigate further whatâs not working on your instance.
I have OpenWeather, Telegram, two cameras, and Owntracks that we had deactivated together. I still havenât reactivated it since.
Yes, I can send you all that without any issues. Iâll retrieve it and transfer it to you as soon as possible.
Today Iâm not available, but we can schedule a session in DM whenever.
Top
Send me the DB first and Iâll see what I can find with it!
@Mastho Well, on your DB side I didnât find anything special.
The fact that it takes time to appear as a bug makes me think of an option: a memory leak. Maybe there is a memory leak (Iâm especially thinking about the cameras), which would cause the RAM usage to increase, increase, increase until your Piâs RAM is full..
The problem with this theory is that you should also see problems locally, but here itâs only remotelyâŠ
Have you already checked the RAM usage on your Pi when you had the bugs (Type htop in the command line)?
Otherwise, I would need all the logs from your containers to see if something special is happening on your side.
For this, you can do on your Pi:
docker logs gladys > logfile.log 2>&1
And send me the log file
(by email if you want)
We will find it!! ![]()
I monitored the RAM and it remains at 25% usage, whether Gladys processes a request or not.
I will check again when the dashboard error messages reappear. They disappeared after the last restart.
I just sent you the log. Happy searching ![]()
So the log you sent me is empty, since Gladys updated in between (to v4.1.0), which renewed the container and cleared the logs ^^
The best thing is that as soon as you have the problem again:
- You directly export the logs with the command I gave you
- You run
htopand take a screenshot of your console
You send me both, and Iâll take a look ![]()