You are not logged in.
Since i upgraded mono, emby went completely unstable, with many "too many files open" errors, and a few more problems (crashes to sometimes).
I then made a thread to the emby forum : http://emby.media/community/index.php?/ … /?p=333376
Other people encountered problems with mono 4.4 : http://emby.media/community/index.php?/ … -starting/
A thing i dont understand is that the actual mono packaged is flagged out of date : https://www.archlinux.org/packages/extra/x86_64/mono/
Packaged version is 4.4.0.40-2 ATM, while http://www.mono-project.com/download/ says that stable version is 4.2.
Seems fedora, centos, gentoo also ships 4.4, but deb based distros ships 4.2.
My question is : Why are we shipping 4.4 ?
The commit message for mono 4.4 refers to https://bugs.archlinux.org/task/46608
So i do understand that going for 4.4 fixes binary building, but it seems to at least break one packaged app.
Any thoughts ?
I solved my problem by downgrading back to 4.2, but maybe some people would have to check if it also breaks other apps, or if it was a good idea to move to 4.4 that seems to be in beta state.
Offline
I also wanted to confirm that I was having this issue. I had to downgrade to 4.2 and place a restriction so pacman wouldn't update mono. I noticed that now the stable version is 4.4.0.182, which this package is older than. Thought I should let people know.
Offline
Thanks for reporting this. I've been scratching my head trying to understand why Emby suddenly started behaving strangly with lots of error messages like "too many files open" appearing in the logs. Downgrading mono to 4.2.2 has fix this problem for me for now.
Offline
Registered a new account to thank you!
I was experiencing the same problem, even after raising file limits it'd still have 100,000+ "files" open (most were pipes).
Downgrading to 4.2.3.4 fixed it right up.
Offline