Hardware: Raspberry Pi at home
YunoHost version: 184.108.40.206 (stable).
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
recently i have noticed my server being really slow, and xmpp messages not sending. when i look into htop on the server, metronome is using 100% of a CPU core and gradually swallowing all free memory.
i firstly restarted metronome visa
systemctl, it worked fine for the rest of the day. then next the same issue has come up again. now if i restart it only takes 5-10 minutes for metronome to use all available memory and stall the whole server.
i am running a modified metronome.cfg.lua file: i added modules and ports for a/v calls, turn/stun server. but that was long ago, and it has worked fine since.
i’m not sure if there have been any config updates that i should merge with my version?
i’m a bit surprised by this behaviour, as i have run prosody on other servers for years at a time without ever seeing this.
metronome’s error log file is empty, while its standard log file doesn’t show anything disastrous.
perhaps someone else has had a similar issue, or has a suggestion of where to start digging around?
sudo journalctl -u metronome.service also shows nothing other than my restarting it.
we only have a handful of users, and only connect to a handful of other servers.
one thing i noticed in
metronome.log is that metronome is trying to connect to the subdomain
jabber.my.beloved.ynh.server, about which is says this:
incoming s2s stream my.beloved.ynh->jabber.my.beloved.ynh closed: This host does not serve jabber.my.beloved.ynh
the only other error is a failed connected to a now defunct/offline server.