AllTheMods / Server-Scripts

Server Startup Scripts
Other
68 stars 37 forks source link

error with max ram? #6

Open xiXNiNjaDuDEXix opened 7 years ago

xiXNiNjaDuDEXix commented 7 years ago

;Details/Help Found here: https://github.com/AllTheMods/Server-Scripts

MAX_RAM=5G; JAVA_ARGS=-server -d64 -Xms1G -XX:+ExplicitGCInvokesConcurrent -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=50 -XX:UseSSE=3; CRASH_COUNT=10; CRASH_TIMER=600; RUN_FROM_BAD_FOLDER=0; IGNORE_OFFLINE=0; IGNORE_JAVA_CHECK=0; USE_SPONGE=0;

MODPACK_NAME=All The Mods 1; MCVER=1.10.2; FORGEVER=12.18.3.2316; FORGEURL=DISABLE;

ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=6/01 DEBUG: MC_SERVER_CRASH_HHMMSS=161434 DEBUG: Current directory file listing: Volume in drive C has no label. Volume Serial Number is 3E86-6CC5

OrdinatorStouff commented 7 years ago

Something is funky here with the script's ability to see files. The log line DEBUG: Current directory file listing: is supposed to dump the dir contents to the log too but it's fully blank. MAX_RAM is the first variable the script "checks" for so if it can't see the config file or can't "open" it this error would come up.

I partially suspect an antivirus software could be interfering, if it has built in batch/script "protection"

Can you give more details about your system, what folder you have this extracted to, has it worked for you in the past or is this your first time setting up?

xiXNiNjaDuDEXix commented 7 years ago

I dont have any Anti-virus programs or anything similar other than the built in windows defender which i turned off and the issue still occured. i have a 64 bit windows 10, 16gb ram, gtx960 graphics, i5 intel core (3.20Ghz) and a 1TB disk drive with 350GB spare space. i have the server files v2.7 folder on my desktop extracted with winrar and this is my first time running it and have never used it in the past.


INFO: Starting batch at 6/01:133334


DEBUG: Current Dir is C:\Users\jwint\Desktop\Server Files v2.57 -- trying to change to C:\Users\jwint\Desktop\Server Files v2.57\ INFO: Checking that settings.cfg exists DEBUG: settings.cfg Found. Logging full contents below: ;Details/Help Found here: https://github.com/AllTheMods/Server-Scripts

MAX_RAM=5G; JAVA_ARGS=-server -d64 -Xms1G -XX:+ExplicitGCInvokesConcurrent -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=50 -XX:UseSSE=3; CRASH_COUNT=10; CRASH_TIMER=600; RUN_FROM_BAD_FOLDER=0; IGNORE_OFFLINE=0; IGNORE_JAVA_CHECK=0; USE_SPONGE=0;

MODPACK_NAME=All The Mods 1; MCVER=1.10.2; FORGEVER=12.18.3.2316; FORGEURL=DISABLE;

ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=6/01 DEBUG: MC_SERVER_CRASH_HHMMSS=133334 DEBUG: Current directory file listing: Volume in drive C has no label. Volume Serial Number is 3E86-6CC5

Directory of C:\Users\jwint\Desktop\Server Files v2.57

17/06/2017 13:33

. 17/06/2017 13:33 .. 09/06/2017 00:15 config 09/06/2017 00:15 mods 09/06/2017 00:17 resources 09/06/2017 00:15 scripts 08/06/2017 23:01 39,954 ServerStart.bat 17/06/2017 13:33 1,895 serverstart.log 08/06/2017 23:01 9,751 ServerStart.sh 08/06/2017 23:02 537 settings.cfg 09/06/2017 00:15 woot 4 File(s) 52,137 bytes 7 Dir(s) 366,279,712,768 bytes free DEBUG: JAVA version output (java -d64 -version): java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) 'bitsadmin' is not recognized as an internal or external command, operable program or batch file.

OrdinatorStouff commented 7 years ago

This is a bit confusing, nothing is jumping out as an obvious reason why it's giving that error.

I'm wondering if your system is defaulting to something like powershell to open .bat files instead of the normal command prompt. Although I just tested it in powershell and it did work for me. Another concern is the line saying 'bitsadmin' is not recognized

Can you try opening the command prompt (Win+R, type "cmd") and then manually navigate to the folder and run the batch file by typing it's name? If you need more help with how to do that let me know and I'll be more specific.

Also can you get a screenshot of your "winver" -- (Win+R, type "winver") and submit that as well?

xiXNiNjaDuDEXix commented 7 years ago

rgergerg Winver ^ wefrhbrth CMD^: The outcome of running through cmd gave me the same issue only it didn't automatically close after showing the error like it did when i just ran it normally Ill paste the log below just incase there was a change made after i did this:


INFO: Starting batch at 6/01:135114


DEBUG: Current Dir is C:\Users\jwint\Desktop\Server Files v2.57 -- trying to change to C:\Users\jwint\Desktop\Server Files v2.57\ INFO: Checking that settings.cfg exists DEBUG: settings.cfg Found. Logging full contents below: ;Details/Help Found here: https://github.com/AllTheMods/Server-Scripts

MAX_RAM=5G; JAVA_ARGS=-server -d64 -Xms1G -XX:+ExplicitGCInvokesConcurrent -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=50 -XX:UseSSE=3; CRASH_COUNT=10; CRASH_TIMER=600; RUN_FROM_BAD_FOLDER=0; IGNORE_OFFLINE=0; IGNORE_JAVA_CHECK=0; USE_SPONGE=0;

MODPACK_NAME=All The Mods 1; MCVER=1.10.2; FORGEVER=12.18.3.2316; FORGEURL=DISABLE;

ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=6/01 DEBUG: MC_SERVER_CRASH_HHMMSS=135114 DEBUG: Current directory file listing: Volume in drive C has no label. Volume Serial Number is 3E86-6CC5

Directory of C:\Users\jwint\Desktop\Server Files v2.57

18/06/2017 13:51

. 18/06/2017 13:51 .. 09/06/2017 00:15 config 09/06/2017 00:15 mods 09/06/2017 00:17 resources 09/06/2017 00:15 scripts 08/06/2017 23:01 39,954 ServerStart.bat 18/06/2017 13:51 1,825 serverstart.log 08/06/2017 23:01 9,751 ServerStart.sh 08/06/2017 23:02 537 settings.cfg 09/06/2017 00:15 woot 4 File(s) 52,067 bytes 7 Dir(s) 363,957,977,088 bytes free DEBUG: JAVA version output (java -d64 -version): java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) 'bitsadmin' is not recognized as an internal or external command, operable program or batch file.

OrdinatorStouff commented 7 years ago

You have the "Creator" update and seems that it does make some changes to the command prompt. I haven't tested this yet (and didn't even know they touched the command prompt...)

Try this please: Open a cmd windows, right click on the title bar to select "properties https://www.top-password.com/blog/wp-content/uploads/2016/03/cmd.png cmd

Then check "Use legacy console" legacy-cmd-console

Then click okay, exit the command window and try the ServerStart.bat again

xiXNiNjaDuDEXix commented 7 years ago

1

Same issue Copy of the log:


INFO: Starting batch at 6/01:182605


DEBUG: Current Dir is C:\Users\jwint\Desktop\Server Files v2.57 -- trying to change to C:\Users\jwint\Desktop\Server Files v2.57\ INFO: Checking that settings.cfg exists DEBUG: settings.cfg Found. Logging full contents below: ;Details/Help Found here: https://github.com/AllTheMods/Server-Scripts

MAX_RAM=5G; JAVA_ARGS=-server -d64 -Xms1G -XX:+ExplicitGCInvokesConcurrent -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=50 -XX:UseSSE=3; CRASH_COUNT=10; CRASH_TIMER=600; RUN_FROM_BAD_FOLDER=0; IGNORE_OFFLINE=0; IGNORE_JAVA_CHECK=0; USE_SPONGE=0;

MODPACK_NAME=All The Mods 1; MCVER=1.10.2; FORGEVER=12.18.3.2316; FORGEURL=DISABLE;

ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=6/01 DEBUG: MC_SERVER_CRASH_HHMMSS=182605 DEBUG: Current directory file listing: Volume in drive C has no label. Volume Serial Number is 3E86-6CC5

Directory of C:\Users\jwint\Desktop\Server Files v2.57

18/06/2017 18:26

. 18/06/2017 18:26 .. 09/06/2017 00:15 config 09/06/2017 00:15 mods 09/06/2017 00:17 resources 09/06/2017 00:15 scripts 08/06/2017 23:01 39,954 ServerStart.bat 18/06/2017 18:26 1,825 serverstart.log 08/06/2017 23:01 9,751 ServerStart.sh 08/06/2017 23:02 537 settings.cfg 09/06/2017 00:15 woot 4 File(s) 52,067 bytes 7 Dir(s) 360,252,231,680 bytes free DEBUG: JAVA version output (java -d64 -version): java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) 'bitsadmin' is not recognized as an internal or external command, operable program or batch file.

xiXNiNjaDuDEXix commented 7 years ago

just for proof aswell: 2

OrdinatorStouff commented 7 years ago

I am legitimately running out of ideas on what's even happening, let alone how to fix it. This is an odd one for sure.

Please try running the script in PowerShell. General steps to do so would be:

  1. Open PowerShell from start menu
  2. Browse to the drive/folder where the server files are by using cd to change directories (cd \Users\jwint\Desktop\Server Files v2.57 might work) or might need to go one directory at a time, cd .. to go "up one level" for example
  3. Once you're PowerShell is in the correct directory, type .\ServerStart.sh (the .\ is needed or else it won't start.)

Then please share the screen output and serverstart.log after that

xiXNiNjaDuDEXix commented 7 years ago

1 2 3 4

Image no. 1: This image shows what happens after i navigate to the folder and then do the .\ServerStart.sh command Image no. 2: This image shows what is happening behind the choose app program where i ran it a second time to get the screenshot Image no. 3: This image shows what i did next because i thought that maybe you meant for me to run the .bat version and not the .sh version Image no. 3: This image shows what happens when i run that command from image 3 where it closes powershell and opens a window with a cmd ui but if you look in the top left it says powershell still and gives the same error

And heres the newest version of the log:


INFO: Starting batch at 6/01:233834


DEBUG: Current Dir is C:\users\jwint\desktop\Server Files v2.57 -- trying to change to C:\Users\jwint\Desktop\Server Files v2.57\ INFO: Checking that settings.cfg exists DEBUG: settings.cfg Found. Logging full contents below: ;Details/Help Found here: https://github.com/AllTheMods/Server-Scripts

MAX_RAM=5G; JAVA_ARGS=-server -d64 -Xms1G -XX:+ExplicitGCInvokesConcurrent -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=50 -XX:UseSSE=3; CRASH_COUNT=10; CRASH_TIMER=600; RUN_FROM_BAD_FOLDER=0; IGNORE_OFFLINE=0; IGNORE_JAVA_CHECK=0; USE_SPONGE=0;

MODPACK_NAME=All The Mods 1; MCVER=1.10.2; FORGEVER=12.18.3.2316; FORGEURL=DISABLE;

ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=6/01 DEBUG: MC_SERVER_CRASH_HHMMSS=233834 DEBUG: Current directory file listing: Volume in drive C has no label. Volume Serial Number is 3E86-6CC5

Directory of C:\users\jwint\desktop\Server Files v2.57

21/06/2017 23:38

. 21/06/2017 23:38 .. 09/06/2017 00:15 config 09/06/2017 00:15 mods 09/06/2017 00:17 resources 09/06/2017 00:15 scripts 08/06/2017 23:01 39,954 ServerStart.bat 21/06/2017 23:38 1,825 serverstart.log 08/06/2017 23:01 9,751 ServerStart.sh 08/06/2017 23:02 537 settings.cfg 09/06/2017 00:15 woot 4 File(s) 52,067 bytes 7 Dir(s) 356,764,549,120 bytes free DEBUG: JAVA version output (java -d64 -version): java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) 'bitsadmin' is not recognized as an internal or external command, operable program or batch file.

OrdinatorStouff commented 7 years ago

I want to check in again @xiXNiNjaDuDEXix if there has been any change? I have been unable to reproduce and I have not heard of anyone else with similar problems so I am out of ideas on why it's so different for you on your system only.

Zettac commented 7 years ago

I am having this exact same problem.

xiXNiNjaDuDEXix commented 7 years ago

Well there we go a second person with this issue and no i have no idea what is causing this with still no changes

OrdinatorStouff commented 7 years ago

Ok so @Zettac and @xiXNiNjaDuDEXix if only we could figure out now what you two have in common with eachother that is somehow different from myself and most every other Windows user. Do either of you have a second computer/laptop/whatever that you can try this on, not to actually RUN the server but just see if the script behaves differently on a different machine?

xiXNiNjaDuDEXix commented 7 years ago

i dont lets hope @Zettac does

Zettac commented 7 years ago

There is a Laptop I could try, but the opportunity to use it won't come until the evening. I will mention up front that My OS is Win 7 and the Laptop's OS is Win 10. Will update with the results afterward.

Zettac commented 7 years ago

The server installs and runs fine on the Laptop, but still no luck on my Desktop. Which really confuses me since I had an old version of the server running fine on my Desktop a few months ago.

Zettac commented 7 years ago

To be clear I had a server for ATM running on my computer a few months ago, but decided to delete it and install the latest version from scratch. Since then every attempt to do so has resulted with the Max Ram error.

OrdinatorStouff commented 6 years ago

@Zettac and @xiXNiNjaDuDEXix I think I finally figured this out. If you have any other type of "find" executable in your PATH or that your command prompt defaults to becasue of modifications (like MiniGW or Cygwin or anything that adds to or expands the functionality of the command prompt) or just some program that has a find exe that is added to your path variable, then the default system32 FIND will not be run.

MAX RAM is just the first time that "FIND" is attempted to be executed.

I have pushed a new commit that adds some checks to FIND and PING and a few others and forced the batch to use the SYSTEM32 version, not whatever other one might be getting called instead. If either of you were still having this problem with the old script version, can you try downloading the latest from this github and seeing if that fixes it for you?

xiXNiNjaDuDEXix commented 6 years ago

Yeah I have steam cmd so that would make sense i will try it when im back home. (The other one was my college account sorry forgot i was signed in as that)

kkbEumel commented 6 years ago

Same Problem


INFO: Starting batch at 4.01:184417


DEBUG: Current Dir is F:\ -- trying to change to F:\ATMServer\ServerFiles-AllTheModsExpertRemastered-1.1.1\ INFO: Checking that settings.cfg exists DEBUG: settings.cfg Found. Logging full contents below: ;Details/Help Found here: https://github.com/AllTheMods/Server-Scripts

MAX_RAM=4G; JAVA_ARGS=-server -d64 -Xms1G -XX:+ExplicitGCInvokesConcurrent -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=50 -XX:UseSSE=3 -Dfml.readTimeout=60; CRASH_COUNT=10; CRASH_TIMER=600; RUN_FROM_BAD_FOLDER=0; IGNORE_OFFLINE=0; IGNORE_JAVA_CHECK=0; USE_SPONGE=0;

MODPACK_NAME=All The Mods Expert Remastered; MCVER=1.10.2; FORGEVER=12.18.3.2511; FORGEURL=DISABLE;

ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=4.01 DEBUG: MC_SERVER_CRASH_HHMMSS=184417 DEBUG: Current directory file listing: Datentr„ger in Laufwerk F: ist SATA 800 GB Volumeseriennummer: 2A9C-A065

Verzeichnis von F:\ATMServer\ServerFiles-AllTheModsExpertRemastered-1.1.1

22.04.2018 18:44

. 22.04.2018 18:44 .. 22.04.2018 18:27 17 classCache.dat 22.04.2018 18:27 config 22.04.2018 18:29 184 eula.txt 22.04.2018 18:27 4.641.767 forge-1.10.2-12.18.3.2511-installer.jar 22.04.2018 18:26 4.317.031 forge-1.10.2-12.18.3.2511-universal.jar 22.04.2018 18:27 3.237 LICENSE.md 22.04.2018 18:27 local 22.04.2018 18:28 logs 22.04.2018 18:26 9.459.897 minecraft_server.1.10.2.jar 22.04.2018 18:28 mods 22.04.2018 18:27 11.782 README.md 22.04.2018 18:28 resources 22.04.2018 18:28 scripts 22.04.2018 18:28 62 server.properties 22.04.2018 18:27 39.949 ServerStart.bat 22.04.2018 18:44 1.840 serverstart.log 22.04.2018 18:27 9.751 ServerStart.sh 22.04.2018 18:36 574 settings.cfg 12 Datei(en), 18.486.091 Bytes 8 Verzeichnis(se), 340.444.094.464 Bytes frei DEBUG: JAVA version output (java -d64 -version): java version "9.0.1" Java(TM) SE Runtime Environment (build 9.0.1+11) Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode) Der Befehl "bitsadmin" ist entweder falsch geschrieben oder konnte nicht gefunden werden.