+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Minim Server 'in the red' (/showthread.php?tid=663)
Minim Server 'in the red' - jolivetj - 16-06-2013 22:14
Simon,
Minim Server will inexplicably not start today (red symbol). It worked fine until yesterday. I also updated Kinsky on my iPad yesterday.
Here is a copy of the log:
17:11:09.218 main: exception while starting component minimserver in context context0
17:11:09.218 main: >>> EVENT >>> componentError: minimserver
17:11:09.229 main: ServerControl: componentError event for minimserver
17:11:09.229 main: Monitor: componentError event for minimserver in context context0
17:11:09.230 main: Monitor: setting property AllComponentStatus
17:11:09.230 main: previous value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.minimserver.Server,context0,Starting,watch,com.minimserver.WatchService,watchContext,Running,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,monitor,org.jminim.lib.MonitorService,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService,httpContext,Running
17:11:09.231 main: new value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.minimserver.Server,context0,Error,watch,com.minimserver.WatchService,watchContext,Running,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,monitor,org.jminim.lib.MonitorService,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService,httpContext,Running
17:11:09.252 main: stopping component minimserver in context context0
17:11:09.253 main: >>> EVENT >>> componentStopping: minimserver
17:11:09.253 main: ServerControl: componentStopping event for minimserver
17:11:09.253 main: Monitor: componentStopping event for minimserver in context context0
17:11:09.254 main: Monitor: setting property AllComponentStatus
17:11:09.254 main: previous value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.minimserver.Server,context0,Error,watch,com.minimserver.WatchService,watchContext,Running,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,monitor,org.jminim.lib.MonitorService,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService,httpContext,Running
17:11:09.254 main: new value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.minimserver.Server,context0,Error,watch,com.minimserver.WatchService,watchContext,Running,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,monitor,org.jminim.lib.MonitorService,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService,httpContext,Running
17:11:09.255 main: stopping MinimServer
17:11:09.255 main: ComponentClassLoader: using parent class loader for class java.nio.channels.FileLock
17:11:09.301 main: disposing http service
17:11:09.301 main: disposing HTTPContext
17:11:09.302 main: removing contextRoot minimserver
17:11:09.302 main: HTTPService: removing path minimserver
17:11:09.302 main: HTTPService: found handler for minimserver
17:11:09.304 main: HTTPService: closing server socket
17:11:09.341 main: http service disposed
17:11:09.342 main: closing cacheData[0]
RE: Minim Server 'in the red' - simoncn - 16-06-2013 22:52
(16-06-2013 22:14)jolivetj Wrote: Simon,
Minim Server will inexplicably not start today (red symbol). It worked fine until yesterday. I also updated Kinsky on my iPad yesterday.
Here is a copy of the log:
17:11:09.218 main: exception while starting component minimserver in context context0
17:11:09.218 main: >>> EVENT >>> componentError: minimserver
17:11:09.229 main: ServerControl: componentError event for minimserver
17:11:09.229 main: Monitor: componentError event for minimserver in context context0
........
This log data appears to be incomplete. Please post the complete log as a forum attachment (not inline text). To understand what's causing the problem, I need to see details of the exception that occurred while the minimserver component was being started.
RE: Minim Server 'in the red' - jolivetj - 17-06-2013 01:45
(16-06-2013 22:52)simoncn Wrote:(16-06-2013 22:14)jolivetj Wrote: Simon,
Minim Server will inexplicably not start today (red symbol). It worked fine until yesterday. I also updated Kinsky on my iPad yesterday.
Here is a copy of the log:
17:11:09.218 main: exception while starting component minimserver in context context0
17:11:09.218 main: >>> EVENT >>> componentError: minimserver
17:11:09.229 main: ServerControl: componentError event for minimserver
17:11:09.229 main: Monitor: componentError event for minimserver in context context0
........
This log data appears to be incomplete. Please post the complete log as a forum attachment (not inline text). To understand what's causing the problem, I need to see details of the exception that occurred while the minimserver component was being started.
The file is too large (493 Ko) to be attached. Almost all lines refer to conflicting items or truncanting incorrect values except for this last bit:
at com.minimserver.Server.constructAlbum(Server.java:3911)
at com.minimserver.Server.constructMergedAlbums(Server.java:2734)
at com.minimserver.Server.doStart(Server.java:1539)
at com.minimserver.Server.start(Server.java:382)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:156)
at org.jminim.core.ContextImpl.start(ContextImpl.java:84)
at org.jminim.core.RootContextImpl.startComponent(RootContextImpl.java:36)
at org.jminim.core.ContextImpl.start(ContextImpl.java:84)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:398)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:681)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jminim.launch.Launcher.launch(Launcher.java:64)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:24)
RE: Minim Server 'in the red' - simoncn - 17-06-2013 08:54
(17-06-2013 01:45)jolivetj Wrote: The file is too large (493 Ko) to be attached. Almost all lines refer to conflicting items or truncanting incorrect values except for this last bit:
at com.minimserver.Server.constructAlbum(Server.java:3911)
at com.minimserver.Server.constructMergedAlbums(Server.java:2734)
at com.minimserver.Server.doStart(Server.java:1539)
at com.minimserver.Server.start(Server.java:382)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:156)
at org.jminim.core.ContextImpl.start(ContextImpl.java:84)
at org.jminim.core.RootContextImpl.startComponent(RootContextImpl.java:36)
at org.jminim.core.ContextImpl.start(ContextImpl.java:84)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:398)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:681)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jminim.launch.Launcher.launch(Launcher.java:64)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:24)
I have increased the forum attachment size limit for .log files to 550 KB. Please attach the complete log file. Many thanks!
RE: Minim Server 'in the red' - jolivetj - 17-06-2013 12:59
I still get the following error message:
'Please correct the following errors before continuing:
•The file you attached is too large. The maximum size for that type of file is 200 kilobytes'
RE: Minim Server 'in the red' - simoncn - 17-06-2013 15:28
(17-06-2013 12:59)jolivetj Wrote: I still get the following error message:
'Please correct the following errors before continuing:
•The file you attached is too large. The maximum size for that type of file is 200 kilobytes'
As I said in my previous post, I have changed the attachment size limit for the .log extension to 550 KB. Does the file you are trying to attach have a .log extension?
Alternatively, you can zip the log file. The limit for the .zip extension is 1 MB. The zipped file will be much smaller, which is helpful for forum manintenance.
RE: Minim Server 'in the red' - jolivetj - 17-06-2013 22:21
(17-06-2013 15:28)simoncn Wrote:(17-06-2013 12:59)jolivetj Wrote: I still get the following error message:
'Please correct the following errors before continuing:
•The file you attached is too large. The maximum size for that type of file is 200 kilobytes'
As I said in my previous post, I have changed the attachment size limit for the .log extension to 550 KB. Does the file you are trying to attach have a .log extension?
Alternatively, you can zip the log file. The limit for the .zip extension is 1 MB. The zipped file will be much smaller, which is helpful for forum manintenance.
Here it is
RE: Minim Server 'in the red' - simoncn - 18-06-2013 06:54
(17-06-2013 22:21)jolivetj Wrote: Here it is
The startup error is caused by a bug in MinimServer that can cause a NullPointerException when a group contains tracks that aren't consecutive.
The log contains the lines:
Error: group contains tracks that aren't consecutive: Cuatro madrigales amatorios
Error: group contains tracks that aren't consecutive: Piano Concerto No. 1
If you fix these two problems, MinimServer will start normally.
This bug will be fixed in the next release of MinimServer. Thanks for letting me know about this.
RE: Minim Server 'in the red' - jolivetj - 19-06-2013 02:43
[attachment=225]
(18-06-2013 06:54)simoncn Wrote:(17-06-2013 22:21)jolivetj Wrote: Here it is
The startup error is caused by a bug in MinimServer that can cause a NullPointerException when a group contains tracks that aren't consecutive.
The log contains the lines:
Error: group contains tracks that aren't consecutive: Cuatro madrigales amatorios
Error: group contains tracks that aren't consecutive: Piano Concerto No. 1
If you fix these two problems, MinimServer will start normally.
This bug will be fixed in the next release of MinimServer. Thanks for letting me know about this.
Minim Server appears to be findings new errors as I restart after fixing the previous 2 bugs
RE: Minim Server 'in the red' - simoncn - 19-06-2013 08:48
(19-06-2013 02:43)jolivetj Wrote: Minim Server appears to be findings new errors as I restart after fixing the previous 2 bugs
The latest log contains the following messages:
Error: group spans multiple discs: Concertos Brandebourgeois
Error: group contains tracks that aren't consecutive: Piano Concerto No. 1
Error: group contains tracks that aren't consecutive: Alceste
Error: group contains tracks that aren't consecutive: Piano Concerto No. 4
As you fix one error, MinimServer is able to get further through processing your groups and may then find further group errors. You need to fix all the group errors and MinimServer will then be able to start.