More > JRiver Media Center 21 for Linux
JRiver Media Center 21.0.85 for Debian
mwillems:
--- Quote from: bob on June 02, 2016, 06:39:00 pm ---I connect to windows current version using authentication from debian and it works fine.
Also just tried one from ubuntu to debian and it worked fine.
Not sure what's going on. Are they both on the same lan?
--- End quote ---
All machines are on the same LAN, and all work perfectly with .83. To be clear, the problem I'm seeing is only Linux client to Linux server (if either endpoint runs windows there's no issue), only when both are on .85, and only when authentication is enabled. I'm seeing it on all four of my Linux clients, two of which are raspberry's running Debian, and two of which are regular computers running Arch. My server is on Debian. It's 100% reproducible here, and rolling back to .83 fixes it in every case.
If it helps to describe more clearly: if I try to connect to a library server with authentication enabled for the first time, it asks me for credentials; then after entering them I get a long hand, and the "failed to load library" dialog pops up. I never see the prompt for credentials after that first failed connection, and rolling back to .83 and connecting with the same install connects successfully without prompting for the credentials, so it's clear they're the correct credentials.
Also potentially of note: auto-import has completely stopped working on my server. I can add new items to watched folders and days will pass with no imports. Nothing is imported until I manually do it. The watched folders are all on local filesystems which, to my knowledge, support inotify. Auto-import worked correctly in .83 as well.
bob:
--- Quote from: mwillems on June 02, 2016, 06:51:35 pm ---All machines are on the same LAN, and all work perfectly with .83. To be clear, the problem I'm seeing is only Linux client to Linux server (if either endpoint runs windows there's no issue), only when both are on .85, and only when authentication is enabled. I'm seeing it on all four of my Linux clients, two of which are running Debian, and two of which are running Arch. My server is on Debian. It's 100% reproducible here, and rolling back to .83 fixes it in every case.
Also potentially of note: auto-import has completely stopped working on my server. I can add new items to watched folders and days will pass with no imports. Nothing is imported until I manually do it. The watched folders are all on local filesystems which, to my knowledge, support inotify. This all worked correctly in .83 as well.
--- End quote ---
Very odd.
Can you turn on logging and check the logs for import issues?
As for the auth, I really don't get that. The big change was a fix for a null buffer pointer that was causing an occasional segfault. I might throw a printf in there for testing.
mwillems:
--- Quote from: bob on June 02, 2016, 06:56:32 pm ---Very odd.
Can you turn on logging and check the logs for import issues?
--- End quote ---
Will do, but manual import works fine with no issues.
--- Quote ---As for the auth, I really don't get that. The big change was a fix for a null buffer pointer that was causing an occasional segfault. I might throw a printf in there for testing.
--- End quote ---
Happy to test anything that might help; right now it's a hard blocker for upgrading for me so I'm motivated ;D
mwillems:
I did some logging on the auto-import issue and saw no evidence that MC was ever even receiving the notifications from inotify. That made me suspicious. Turns out I had a much too low inotify watch limit, it's a wonder it was working correctly before (but would explain inconsistent activity). After raising the limit, auto-import appears to be working correctly now. Sorry for the false alarm on that point.
The library server issue is still live though, I still can't login to an authenticated library server on .85. Some other folks are seeing it too, see : https://yabb.jriver.com/interact/index.php?topic=105283.0
aoqw76:
Hi, I think I'm also getting an issue with autoimport not working.
I ran "cat /proc/sys/fs/inotify/max_user_watches" and the resukt was 8192.
Is this too low?
Didnt get this issue with v83.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version