Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Crashed after issues with untagged
16-03-2021, 11:34
Post: #1
Crashed after issues with untagged
Yesterday I noticed a massive list of tracks in untagged

previously I had none in untagged - and I checked a few individual files that were listed in untagged and they had a full set of tags and where also listed in the folder section and composer section

I then did a full rescan and saw a crash so I did another full scan with debug on and include the relevant part of the report

I am running the latest version on a Synology

10:10:00.781 main: Deleting file Music1-2.mcache
10:10:00.850 main: Renaming Music1-temp.mcache to Music1-2.mcache
10:10:00.851 main: Forcing sync for renamed file Music1-2.mcache
java.lang.NullPointerException
at java.nio.file.Files.provider(Files.java:97)
at java.nio.file.Files.readAttributes(Files.java:1737)
at java.nio.file.Files.isRegularFile(Files.java:2229)
at com.minimserver.Server.readFiles(Server.java:7220)
at com.minimserver.Server.doStart(Server.java:3500)
at com.minimserver.Server.start(Server.java:1113)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:228)
at org.jminim.core.ContextImpl.start(ContextImpl.java:116)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:2652)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1302)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav​a:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jminim.mlaunch.MinimLaunch.doLaunch(MinimLaunch.java:525)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:150)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav​a:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jminim.launch.Launcher.launch(Launcher.java:88)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:38)
10:10:01.093 main: exception while starting component minimserver in context context0
10:10:01.093 main: >>> EVENT >>> componentError: minimserver
10:10:01.093 main: ServerControl: componentError event for minimserver
10:10:01.093 main: Monitor: componentError event for minimserver in context context0
10:10:01.127 main: stopping component minimserver in context context0
10:10:01.127 main: >>> EVENT >>> componentStopping: minimserver
10:10:01.127 main: ServerControl: componentStopping event for minimserver
10:10:01.128 main: Monitor: componentStopping event for minimserver in context context0
10:10:01.128 main: stopping MinimServer
10:10:01.128 main: disposing http service
10:10:01.128 main: disposing HTTPContext
10:10:01.128 main: removing contextRoot minimserver
10:10:01.128 main: HTTPService: removing path minimserver
10:10:01.129 main: HTTPService: found handler for minimserver
10:10:01.129 main: http service disposed
10:10:01.129 main: stopped MinimServer
10:10:01.129 main: stopped component minimserver in context context0
10:10:01.129 main: >>> EVENT >>> componentStopped: minimserver
10:10:01.129 main: ServerControl: componentStopped event for minimserver
10:10:01.129 main: Monitor: componentStopped event for minimserver in context context0
10:10:01.130 main: error while starting context context0
10:10:01.131 main: stopping context context0
10:10:01.131 main: >>> EVENT >>> contextStopping: context0
10:10:01.131 main: ServerControl: contextStopping event for context0
10:10:01.131 main: Monitor: contextStopping event for context0
10:10:01.132 Thread-11: Monitor action: GetErrorInfo
10:10:01.132 Thread-11: version=2, adapter=192.168.1.109, uriPrefix=http://192.168.1.109:9791/1ff2bc3a-9ad3-48f0-a4e0-600a335a5735/Upnp/resource/, clientEndpoint=192.168.1.141:61715
10:10:01.133 Thread-11: Monitor response: GetErrorInfo
10:10:01.133 Thread-11: ErrorInfo=MinimServer: unexpected exception java.lang.NullPointerException
10:10:01.134 main: stopping component minimserver in context context0
10:10:01.134 main: >>> EVENT >>> componentStopping: minimserver
10:10:01.134 main: ServerControl: componentStopping event for minimserver
10:10:01.134 main: Monitor: componentStopping event for minimserver in context context0
10:10:01.135 main: stopping MinimServer
10:10:01.135 main: stopped MinimServer
Find all posts by this user
Quote this message in a reply
16-03-2021, 13:03
Post: #2
RE: Crashed after issues with untagged
Thanks for letting me know about this. This problem is caused by a recent change to how MinimServer cache files are handled. If you select Rescan again after this error message, the rescan will complete successfully. The problem will be fixed in the next MinimServer update.

I don't think the "untagged" problem is related to this. Can you provide a couple of examples of files that show in "untagged" but are actually tagged? It is expected that untagged files would be in the folder section but not in the Composer section.
Find all posts by this user
Quote this message in a reply
16-03-2021, 13:59
Post: #3
RE: Crashed after issues with untagged
I have a green light but see loads of files in untagged (also did a full rescan and still loads there) -
How do I send the file ?
Find all posts by this user
Quote this message in a reply
16-03-2021, 15:05
Post: #4
RE: Crashed after issues with untagged
What setting do you have for the indexTags property?
Find all posts by this user
Quote this message in a reply
16-03-2021, 15:22
Post: #5
RE: Crashed after issues with untagged
Artist, Date, Genre, All Artists, Composer, -DateAdded, -Grouping, Century, Rating
Find all posts by this user
Quote this message in a reply
16-03-2021, 15:24
Post: #6
RE: Crashed after issues with untagged
DateAdded and Grouping and Century and Rating and I use the aliastags below

MUSICBRAINZ_ARTISTID:Century,ASIN:DateAdded,DESCRIPTION:Rating
Find all posts by this user
Quote this message in a reply
16-03-2021, 18:28
Post: #7
RE: Crashed after issues with untagged
(16-03-2021 13:03)simoncn Wrote:  Thanks for letting me know about this. This problem is caused by a recent change to how MinimServer cache files are handled. If you select Rescan again after this error message, the rescan will complete successfully. The problem will be fixed in the next MinimServer update.

I don't think the "untagged" problem is related to this. Can you provide a couple of examples of files that show in "untagged" but are actually tagged? It is expected that untagged files would be in the folder section but not in the Composer section.

I also have problems with untagged albums.
My first impression is that all albums that have no picture in IndexArtist seem to be untagged.
In what way can I help to solve this problem?
Find all posts by this user
Quote this message in a reply
16-03-2021, 20:55
Post: #8
RE: Crashed after issues with untagged
I have found the cause of the "untagged" problem. It will be fixed in the next update. Many thanks to those who have reported this.
Find all posts by this user
Quote this message in a reply
16-03-2021, 21:00
Post: #9
RE: Crashed after issues with untagged
Excellent news and thanks for the super quick fix

BTW I love the new enhancements to images for composers etc

Best wishes

Mike
Find all posts by this user
Quote this message in a reply
18-03-2021, 09:49
Post: #10
RE: Crashed after issues with untagged
The NullPointerException and the [untagged] problem are both fixed now in MinimServer update 190.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)