MinimServer Forum
Minim server crashed in Diskstation DS214se after firmware update - Printable Version

+- MinimServer Forum (http://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Minim server crashed in Diskstation DS214se after firmware update (/showthread.php?tid=4265)

Pages: 1 2


Minim server crashed in Diskstation DS214se after firmware update - jolivetj - 04-12-2017 23:33

The following is the error message in the Log:

MinimServer internal error: Item oldKey=570 newKey=571


RE: Minim server crashed in Diskstation DS214se after firmware update - simoncn - 05-12-2017 08:41

Please attach the complete log file to a post here. What were you doing when this happened?


RE: Minim server crashed in Diskstation DS214se after firmware update - jolivetj - 05-12-2017 14:03

MinimServer 0.8.4, Copyright © 2012-2016 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot™ Client VM (build 24.60-b09, mixed mode)
Platform default charset is UTF-8
autoUpdate: installed package 'minimserver-0.8-update-110'
autoUpdate: relaunching runtime
MinimServer 0.8.4 update 110, Copyright © 2012-2017 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot™ Client VM (build 24.60-b09, mixed mode)
Platform default charset is UTF-8
Language setting is 'fre'
Current time is Sun Dec 03 13:47:32 PST 2017 in time zone Canada/Pacific
starting MinimServer[DiskStation]
MinimServer internal error: Item oldKey=570 newKey=571
MinimServer error: now stopped, use 'restart' or 'exit'

Same thing on MinimServer on my other server:

stopping MinimServer[NASC66EA1]
MinimServer[NASC66EA1] is stopped
Language setting is 'auto'
Current time is Mon Dec 04 17:44:09 EST 2017 in time zone US/Eastern
starting MinimServer[NASC66EA1]
MinimServer internal error: Item oldKey=798 newKey=799

Both messages appeared after Rescans.


RE: Minim server crashed in Diskstation DS214se after firmware update - simoncn - 05-12-2017 16:23

Thanks for providing this information.

On the DiskStation, there should be a minimserver-crash log file in the MinimServer/appData folder. Please attach this file to a post here. If there is more than one minimserver-crash file, please attach the most recent. Many thanks.


RE: Minim server crashed in Diskstation DS214se after firmware update - jolivetj - 05-12-2017 22:29

MinimServer 0.8.4, Copyright © 2012-2016 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot™ Client VM (build 24.60-b09, mixed mode)
Platform default charset is UTF-8
autoUpdate: installed package 'minimserver-0.8-update-110'
autoUpdate: relaunching runtime
MinimServer 0.8.4 update 110, Copyright © 2012-2017 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot™ Client VM (build 24.60-b09, mixed mode)
Platform default charset is UTF-8
Language setting is 'fre'
Current time is Sun Dec 03 13:47:32 PST 2017 in time zone Canada/Pacific
starting MinimServer[DiskStation]
MinimServer internal error: Item oldKey=570 newKey=571
MinimServer error: now stopped, use 'restart' or 'exit'


RE: Minim server crashed in Diskstation DS214se after firmware update - simoncn - 06-12-2017 07:37

This isn't the minimserver-crash log file. The crash log file would have a name like minimserver-crash-20171112-192136.log.


RE: Minim server crashed in Diskstation DS214se after firmware update - jolivetj - 06-12-2017 14:18

Cannot find the minimserver crash log in file station. I have asked Synology for help....


RE: Minim server crashed in Diskstation DS214se after firmware update - simoncn - 06-12-2017 16:58

Perhaps a crash log was not created for this error. Thanks for checking. I will investigate further.


RE: Minim server crashed in Diskstation DS214se after firmware update - simoncn - 06-12-2017 23:17

PM sent.


RE: Minim server crashed in Diskstation DS214se after firmware update - simoncn - 08-12-2017 10:25

Did you have a chance to try the test build that I sent you? It should produce additional diagnostic information that will help me find and fix the problem.