TunkDesign / NeMa

NeManager | The true real-time multi-server Minecraft control panel.
http://nemanager.com/
12 stars 0 forks source link

Spigot MaxPermGen Error (Arg no fix) #12

Closed Zendrex closed 10 years ago

Zendrex commented 10 years ago

Well I messed with the wrapper with spigot, and by default spigot needs a permgen size of 128, as the spigot option with the brand does not fix it and the extra args that can be set wont fix it, I shall report this as a bug.

This is what spigot gives by default when using setup parameters.

java -Xms512M -Xmx1536M -XX:MaxPermSize=128M -jar spigot.jar pause

What I have set in my ini file:

[Wrapper] FirstStart=False Port=REMOVED SecretKey=REMOVED Debug=False AutoUpdate=True

[Minecraft] JVM=server RestartOnCrash=True MaxMemory=1024 MinMemory=256 Args=-XX:MaxPermSize=128M

[Server] Brand=spigot JarName=spigot

Console response: http://prntscr.com/4khagi

A simple addition do your startup script for spigot will fix this easy.

Suggested: java -Xms()()()m -Xmx()()()m -XX:MaxPermSize=128M -jar JAR.jar nogui --nojline

()()() for the parameters in the ini files under ram.

JAR for jar name in the ini file.

I confirmed this when I did a simple shell file and ran it from ssh. Seems to be the wrapper not understanding the X command for java args.

-Brandon

Zendrex commented 10 years ago

In addition, for future note,

For things like Cauldron and such that use forge, use -XX:MaxPermSize=256M or the server will crash. Its required for forge.

TunkDesign commented 10 years ago

This bug has been fixed in the latest release of the wrapper (1.4.3a | Changelog)