More > JRiver Media Center 21 for Linux
Where to submit crashlogs for QNAP MC?
bob:
--- Quote from: Afrosheen on June 21, 2016, 01:49:40 pm ---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!
--- End quote ---
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.
Afrosheen:
--- Quote from: bob on June 23, 2016, 01:10:38 pm ---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.
--- End quote ---
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?
bob:
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...
Afrosheen:
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.
bob:
--- Quote from: Afrosheen on June 29, 2016, 12:08:34 am ---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.
--- End quote ---
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).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version