Closed janstadt closed 1 month ago
I've disabled the snapcast server (and also had to reboot in order for it to chill out) in MASS and things have calmed down a bit. I think it has something to do with that provider.
As per the instructions please ATTACH the log. This is impossible to read.
Ive disabled the provider and dont want to mess up my server due to this issue. Can you attempt to copy the log i pasted (which really is just a bunch of the same errors repeated) to a text editor by any chance?
mass.log Here you go buddy. I gotta be honest, having been a software engineer for the past 20 years, what i've found is that the attitude of the community and the maintainers are what produce successful products. Its been a bit over 4 months since i submitted an issue with MASS and i've noticed that you've recently added the "attachment" requirement to issues within the last couple months. I'll try harder to abide by your rules.
Can you please test this on a recent version of the MA server ? We have had some issues with spawned processes not closing properly but that should have been fixed weeks (if not months) ago. Also the other snapcast related issues whould have been fixed by now.
So for example the 2.1.3 stable version or the 2.2.0b5 beta version.
I pinned to 2.1.0rc1 some time ago as it was running well for me until i realized this issue. I just updated to 2.1.4 and i'll let you know how it goes. Thanks.
@janstadt checking in again as to whether this is still an issue?
We will close this soon due to no followup
What version of Music Assistant has the issue?
2.1.0rc1
What version of the Home Assistant Integration have you got installed?
2024.7.3
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
I've been having issues with my server (unraid) which has been running great for a while and then within the last few weeks it has started to freeze up and requires a reboot. I noticed that
I posted on unraids forums: https://forums.unraid.net/topic/170781-monitor_nchan-fork-retry-resource-temporarily-unavailable/#comment-1445488 and a mod pointed me to this: https://forums.unraid.net/bug-reports/stable-releases/61210-cannot-fork-resource-temporarily-unavailable-r3020/?page=2&tab=comments which made me start looking into my containers and how they're using processes.
I noticed that MASS is using a very high level of PIDs and it grows exponentially.
c74fa0351c36 music-assistant 942.16% 5.43GiB / 23.32GiB 23.29% 0B / 0B 2.08GB / 0B 17877
How to reproduce
Run
docker stats
while mass is running and see if the the PIDs grow.Music Providers
Unsure if its provider specific.
Player Providers
I see an error pointing to snapcast but im unsure if its that or something else.
Full log output
Including more logs:
Additional information
No response
What version of Home Assistant Core are your running
2024.7.3
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Linux