MinimServer Forum

Full Version: ServerBundle_xxx.properties issues after reinstalling minimserver
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi community,

everything worked out well in my post: https://forum.minimserver.com/showthread.php?tid=6050

And then i asked for the limitations and firewall! By reinstalling minim the firewall problem got solved! Thanks again Smile

But now after reinstalling minim my CP shows everything in english and the lines in the ServerBundle_de.properties file are not working anymore.
And in the beginning the folder was called "Ordneransicht" and now its displayed as "folder view" in my CP. And numbers are still infront of albums although i changed everything in the file as before and the properties from minimwatch are the same...

Any solutions?

Greetings Smile
MinimServer selects its default user interface language from the Synology language setting. In the DSM Control Panel, select Regional Options and Language. If Display Language in set to 'Browser Default' or 'English', set it to 'Deutsch'. After doing this, restart MinimServer (no need to reinstall).
(07-02-2021 11:19)simoncn Wrote: [ -> ]MinimServer selects its default user interface language from the Synology language setting. In the DSM Control Panel, select Regional Options and Language. If Display Language in set to 'Browser Default' or 'English', set it to 'Deutsch'. After doing this, restart MinimServer (no need to reinstall).

The language settings in DSM are everywhere set to german. It worked in the beginning. MinimServer was in german (in my CP) before reinstalling it. Just afterwards in english even with my german DSM settings. And the CP looks like this (even with my ServerBundle_de.properties file and the configured details):

[Image: IMG-2252.png]
What do you see in the MinimServer log? It should be something like this:

MinimServer 2.0.18 update 182, Copyright © 2012-2020 Simon Nash. All rights reserved.
OpenJDK Runtime Environment (build 14.0.1+7)
OpenJDK 64-Bit Server VM (build 14.0.1+7, mixed mode)
Platform default charset is UTF-8
System platform is linux-arm64
Setting language to German (de)
Current time is Sun Feb 07 12:26:57 GMT 2021 in time zone Europe/Dublin
starting MinimServer[DS118]
MinimServer[DS118] is running
(07-02-2021 13:28)simoncn Wrote: [ -> ]What do you see in the MinimServer log? It should be something like this:

MinimServer 2.0.18 update 182, Copyright © 2012-2020 Simon Nash. All rights reserved.
OpenJDK Runtime Environment (build 14.0.1+7)
OpenJDK 64-Bit Server VM (build 14.0.1+7, mixed mode)
Platform default charset is UTF-8
System platform is linux-arm64
Setting language to German (de)
Current time is Sun Feb 07 12:26:57 GMT 2021 in time zone Europe/Dublin
starting MinimServer[DS118]
MinimServer[DS118] is running

MinimWatch 2.0.8 update 90, Copyright © 2012-2020 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_281-b09)
Java HotSpot™ 64-Bit Server VM (build 25.281-b09, mixed mode)
Platform default charset is windows-1252
System platform is windows-x64
Active subnet is "my IP-Adress"
Startup complete
MinimServer [DS920+] is running
14:17:35.120 Thread-20: saveProperty: compName=null propName=logLevel propValue=debug
14:17:35.121 Thread-20: getSaveValue: compName= propName=logLevel propValue=debug saveValue=debug
14:17:35.121 Thread-20: writeConfigProperty: propFullName=.logLevel propValue=debug
14:17:35.128 Thread-20: updateActiveProfile: propFullName=.logLevel
14:17:35.128 Thread-20: RootContextImpl: called writeActiveProfile
14:17:35.128 Thread-20: writeActiveProfile: activeProfile=null
14:17:35.128 Thread-20: writeActiveProfile: activeProfile=null
14:17:35.128 Thread-20: writeActiveProfile: activeProfile=null
14:17:35.128 Thread-20: writeActiveProfile: activeProfile=null
14:17:35.128 Thread-20: writeActiveProfile: activeProfile=null
14:17:35.128 Thread-20: writeActiveProfile: activeProfile=null
14:17:35.129 Thread-20: writeActiveProfile: activeProfile=null
14:17:42.594 AWT-EventQueue-0: User changed log level: trace
14:17:42.595 Thread-21: saveProperty: compName=null propName=logLevel propValue=trace
14:17:42.595 Thread-21: getSaveValue: compName= propName=logLevel propValue=trace saveValue=trace
14:17:42.596 Thread-21: writeConfigProperty: propFullName=.logLevel propValue=trace
14:17:42.602 Thread-21: updateActiveProfile: propFullName=.logLevel
14:17:42.602 Thread-21: RootContextImpl: called writeActiveProfile
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: writeActiveProfile: activeProfile=null
14:17:42.602 Thread-21: TrayView.updateLogLevel: remote runtime log level: trace
14:17:42.602 AWT-EventQueue-0: User changed log level: trace
14:17:42.603 Thread-22: saveProperty: compName=null propName=logLevel propValue=trace
14:17:42.603 Thread-22: getSaveValue: compName= propName=logLevel propValue=trace saveValue=trace
14:17:42.603 Thread-22: writeConfigProperty: propFullName=.logLevel propValue=trace
14:17:42.608 Thread-22: updateActiveProfile: propFullName=.logLevel
14:17:42.608 Thread-22: RootContextImpl: called writeActiveProfile
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:42.608 Thread-22: writeActiveProfile: activeProfile=null
14:17:53.927 AWT-EventQueue-0: User changed log level: info
14:17:53.927 Thread-23: saveProperty: compName=null propName=logLevel propValue=info
14:17:53.927 Thread-23: getSaveValue: compName= propName=logLevel propValue=info saveValue=
14:17:53.928 Thread-23: writeConfigProperty: propFullName=.logLevel propValue=
14:17:53.935 Thread-23: updateActiveProfile: propFullName=.logLevel
14:17:53.935 Thread-23: RootContextImpl: called writeActiveProfile
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
14:17:53.935 Thread-23: writeActiveProfile: activeProfile=null
This is a MinimWatch log, not a MinimServer log. Please post a MinimServer log ('Show log' from the MinimWatch menu) with the logging level set to Info. Only the first few lines are needed.
(07-02-2021 14:35)simoncn Wrote: [ -> ]This is a MinimWatch log, not a MinimServer log. Please post a MinimServer log ('Show log' from the MinimWatch menu) with the logging level set to Info. Only the first few lines are needed.

oh. I'm sorry. This should be the right one.

MinimServer 2.0.18 update 182, Copyright © 2012-2020 Simon Nash. All rights reserved.
OpenJDK Runtime Environment (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
Platform default charset is UTF-8
System platform is linux-x64
Using platform default language English (en-US)
Current time is Sat Feb 06 19:14:28 CET 2021 in time zone Europe/Amsterdam
starting MinimServer [DS920+]

There is the language in english. Even if the DSM is in german?!

There are another few errors beneath. But those are according to some albums. I think you don't need this information?!

And after solving the issues with the albums and clearing the log and restarting the server there ist just this:

restarting MinimServer [DS920+]
Current time is Sun Feb 07 15:28:53 CET 2021 in time zone Europe/Amsterdam
starting MinimServer [DS920+]
MinimServer [DS920+] is running
15:29:21.026 Thread-13: Monitor response: SaveProperty
15:29:21.026 Thread-13: ErrorMsg=
15:29:24.545 Thread-20: Monitor action: SaveProperty
15:29:24.545 Thread-20: version=2, adapter=<my IP>, uriPrefix=http://<my IP>:9791/d0b18838-6dfe-4d0d-8c9b-e1f6965c9881/Upnp/resource/, clientEndpoint=<my IP>:62271
15:29:24.545 Thread-20: ComponentName= PropertyName=logLevel PropertyValue=trace
15:29:24.545 Thread-20: saveProperty: compName=null propName=logLevel propValue=trace
15:29:24.545 Thread-20: getSaveValue: compName= propName=logLevel propValue=trace saveValue=trace
15:29:24.545 Thread-20: writeConfigProperty: propFullName=.logLevel propValue=trace
15:29:24.637 Thread-20: updateActiveProfile: propFullName=.logLevel
15:29:24.638 Thread-20: RootContextImpl: called writeActiveProfile
15:29:24.638 Thread-20: writeActiveProfile: activeProfile=Jan
15:29:24.638 Thread-20: writeProfile: Jan
15:29:24.715 Thread-20: writeActiveProfile: activeProfile=null
15:29:24.715 Thread-20: writeActiveProfile: activeProfile=null
15:29:24.715 Thread-20: writeActiveProfile: activeProfile=null
15:29:24.715 Thread-20: writeActiveProfile: activeProfile=null
15:29:24.716 Thread-20: writeActiveProfile: activeProfile=null
15:29:24.716 Thread-20: writeActiveProfile: activeProfile=null
15:29:24.716 Thread-20: Monitor response: SaveProperty
15:29:24.716 Thread-20: ErrorMsg=
The "platform default language" message is shown when the DSM language setting was not passed to MinimServer for some reason. Rebooting the NAS might solve this problem.
(07-02-2021 16:54)simoncn Wrote: [ -> ]The "platform default language" message is shown when the DSM language setting was not passed to MinimServer for some reason. Rebooting the NAS might solve this problem.

I just deinstalled MinimServer with my profiledata, restarted my NAS and reinstalled it completely new.

Now its working again back in german without any numbers!

Thumbs up! I apreciate your support!
(07-02-2021 16:54)simoncn Wrote: [ -> ]The "platform default language" message is shown when the DSM language setting was not passed to MinimServer for some reason. Rebooting the NAS might solve this problem.

Not working again! This seems like a bug. I rebooted my NAS again because of another thing and click - all the things are back in english and with the numbers infront. Rebooting the NAS again didn't bring any chance. So its everything back in english and "wrong" displayed not recognizing my ServerBundle file...
Pages: 1 2
Reference URL's