INTERACT FORUM
More => Old Versions => JRiver Media Center 21 for Linux => Topic started by: Afrosheen on June 20, 2016, 02:57:37 pm
-
I'm currently experiencing frequent crashes after updating to 21.0.83. Is there an appropriate place to submit my crashlogs?
-
This current version is unstable. After playing a track or two I get an audio streaming error upon trying to play the next track in JRemote and when I VNC into my QNAP NAS, I see that MC is no longer running.
I've linked the "previous log" and "log" files below. I'm hoping someone from JRiver's development team will review this thread.
Log (https://www.dropbox.com/s/x66193sqhj2dggx/Log.txt?dl=0)
Previous Log (https://www.dropbox.com/s/4tgjokshf3084st/Previous%20Log.txt?dl=0)
-
Is it related to the file type being played and / or converted?
-
Would you try removing auto-import watch folders and see if the crash goes away?
-
Would you try removing auto-import watch folders and see if the crash goes away?
Yes, and confirming that this is the culprit after having unchecked "run auto-import in the background."
Thanks bob, and thanks JimH for the consideration!
-
Yes, and confirming that this is the culprit after having unchecked "run auto-import in the background."
Thanks bob, and thanks JimH for the consideration!
It possible the JRWorker for importing is crashing on a particular file
OR
The watch folders for autoimport are so many that the QNAP is running out of resources
A log might help. If there is a specific file that gets processed to cause the crash you might try importing that folder manually and see if it works.
-
It possible the JRWorker for importing is crashing on a particular file
OR
The watch folders for autoimport are so many that the QNAP is running out of resources
A log might help. If there is a specific file that gets processed to cause the crash you might try importing that folder manually and see if it works.
I'm not sure I'm locating the right logs. Are the ones that I posted above correct? If not could you please remind me where they would be located on a QNAP install?
-
Yes those logs are correct.
I dont' see anything catastrophic in them.
It could be that you are simply running out of resources (memory for watch handles?).
You could try setting ths auto import to a smaller directory tree to see if the the issue is the number of watch handles...
-
I appreciate the consideration bob! I've only got two main folders that MC is watching, (one main, one new but untagged) but both combined led to a 1 TB of space. I've decided to keep the auto import off and just use VNC to run the import function when I have fresh music that I wish to see in my library. Since turning off auto-import I no longer need to first use a VNC app to launch MC and then connect via JRemote.
Before the recent update, it would be infrequent, but I would have had to launch MC every couple of days first before connecting via JRemote. But since turning off auto-import, I've yet to experience a crash or having to manually launch MC except for instances where I've restarted the QNAP OS. So I'm just going to keep it off and just run the import once a week and relaunch the app when it finishes with the import if/when there is a crash.
-
I appreciate the consideration bob! I've only got two main folders that MC is watching, (one main, one new but untagged) but both combined led to a 1 TB of space. I've decided to keep the auto import off and just use VNC to run the import function when I have fresh music that I wish to see in my library. Since turning off auto-import I no longer need to first use a VNC app to launch MC and then connect via JRemote.
Before the recent update, it would be infrequent, but I would have had to launch MC every couple of days first before connecting via JRemote. But since turning off auto-import, I've yet to experience a crash or having to manually launch MC except for instances where I've restarted the QNAP OS. So I'm just going to keep it off and just run the import once a week and relaunch the app when it finishes with the import if/when there is a crash.
I assume that you don't get a crash when you run the import manually?
It would be interesting to know how many folders there are underneath your 2 autoimport folders (the watch on linux uses one handle for each directory in the hierarchy).
-
I've been testing it out and wanted to be sure before affirming that it doesn't crash when running auto import via JRemote and, yes, your assumption is correct it does not crash when running the import manually.
As for the folders, they get pretty deep.
My main one is as follows:
Library -> Genre -> Style -> Country -> Artist -> Albums
The other one doesn't go as deep, but it's my dump directories over the years and they've yet to be fully organized into the above schematic, i.e.
Main Dump Directory -> Previous Dump Directory 1…, 2…, 3…, etc. -> list of albums.
Not sure if that helps…
-
I've been testing it out and wanted to be sure before affirming that it doesn't crash when running auto import via JRemote and, yes, your assumption is correct it does not crash when running the import manually.
As for the folders, they get pretty deep.
My main one is as follows:
Library -> Genre -> Style -> Country -> Artist -> Albums
The other one doesn't go as deep, but it's my dump directories over the years and they've yet to be fully organized into the above schematic, i.e.
Main Dump Directory -> Previous Dump Directory 1…, 2…, 3…, etc. -> list of albums.
Not sure if that helps…
If you log into the QNAP at the base of where your auto-import folder is you could do this:
find . -type d | wc -l
Which will return the number of directories that need watch handles.
-
Thanks bob for the command!
Here are the numbers I got from running it:
2760 - Main Library
7596 - Dump directories
10,356 - Total
-
From stack overflow:
You can find the system limits by reading /proc/sys/fs/inotify/max_user_instances (maximum number of inotify "objects") and /proc/sys/fs/inotify/max_user_watches (maximum number of files watched).
Each watch takes about 1k of memory. In your case about 10 megs I'd think. Doesn't seem significant to me.
-
Ok thanks bob, I'll turn auto-import back on and run those commands to see if it picks up anything abnormal. My QNAP NAS has 16 gigs of ram so I'm not sure why it would run out of memory even in the worst case.
-
Ok thanks bob, I'll turn auto-import back on and run those commands to see if it picks up anything abnormal. My QNAP NAS has 16 gigs of ram so I'm not sure why it would run out of memory even in the worst case.
Thanks, I don't see how it could run out of ram either, it's got more than my desktop!