Server not starting - 0.2.34

Question

Server not starting - 0.2.34

freakyfreaky opened this issue a year ago · 6 comments

freakyfreaky commented a year ago

[10:57:13] [Server thread/INFO] [sh.co.ShetiPhianCore/]: Loading Teams Data
[10:57:13] [Server thread/INFO] [sh.co.ShetiPhianCore/]: Finished Loading Teams Data
[10:57:14] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class net.minecraft.world.entity.TamableAnimal from interface com.hollingsworth.arsnouveau.common.entity.IFollowingSummon
[10:57:15] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class cy.jdkdigital.everythingcopper.common.entity.CopperGolem from interface cy.jdkdigital.everythingcopper.common.entity.IWeatheringEntity
[10:57:15] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class cy.jdkdigital.everythingcopper.common.entity.CopperGolem from interface cy.jdkdigital.everythingcopper.common.entity.IWeatheringEntity

Finalizing energy block registration
Finalizing fluid block registration
[10:57:18] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class dev.murad.shipping.entity.custom.vessel.tug.AbstractTugEntity from class dev.murad.shipping.entity.custom.vessel.barge.FluidTankBargeEntity
[10:57:18] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class dev.murad.shipping.entity.custom.vessel.tug.AbstractTugEntity from class dev.murad.shipping.entity.custom.vessel.barge.FluidTankBargeEntity
[10:57:18] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class dev.murad.shipping.entity.custom.vessel.tug.AbstractTugEntity from class dev.murad.shipping.entity.custom.train.wagon.FluidTankCarEntity
[10:57:18] [Server thread/WARN] [minecraft/SynchedEntityData]: defineId called for: class dev.murad.shipping.entity.custom.vessel.tug.AbstractTugEntity from class dev.murad.shipping.entity.custom.train.wagon.FluidTankCarEntity
[10:57:20] [Worker-Main-2/WARN] [minecraft/JigsawPlacement]: Empty or non-existent pool: minecraft:
[10:57:20] [Worker-Main-2/WARN] [minecraft/JigsawPlacement]: Empty or non-existent pool: minecraft:
[10:57:32] [Server thread/INFO] [minecraft/MinecraftServer]: Preparing start region for dimension minecraft:overworld
[10:57:32] [Server thread/INFO] [KubeJS Server/]: Server resource reload complete!
[10:57:32] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 0%
[10:57:32] [Worker-Main-3/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 0%
[10:57:33] [Worker-Main-2/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 0%
[10:57:33] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 1%
[10:57:34] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 2%
[10:57:34] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 2%
[10:57:35] [Worker-Main-2/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 3%
[10:57:35] [Worker-Main-3/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 4%
[10:57:36] [Worker-Main-2/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 4%
[10:57:36] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 5%
[10:57:37] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 6%
[10:57:37] [Worker-Main-3/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 6%
[10:57:38] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 7%
[10:57:38] [Worker-Main-2/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 9%
[10:57:39] [Worker-Main-1/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 9%
[10:57:39] [Worker-Main-3/INFO] [minecraft/LoggerChunkProgressListener]: Preparing spawn area: 10%
Killed

josevictoremiliano · Answer 1 · 2023-12-27T14:00:32.000Z

I'm experiencing the error, I've already readjusted my server to 8GB of RAM but nothing works

Joshi425 · Answer 2 · 2023-12-28T14:56:02.000Z

if you run dmesg -T do you see java out of memory killed messages?

freakyfreaky · Answer 3 · 2023-12-28T19:49:47.000Z

journalctl -r is giving me an error which look like your idea
"A process of this unit has been killed by the OOM killer."

Server is running with 8GB

Even if I give him 10GB he will completely use it

Schildos · Answer 4 · 2023-12-30T18:07:29.000Z

what are your jvm args looking like for the server? Are you running minecraft from within the linux server directly or behind docker or such?

freakyfreaky · Answer 5 · 2023-12-30T19:28:38.000Z

It is a VM hosted on a proxmox server. Java and the ATM is running directly on the VM per ./startserver.sh

the args aren’t modified and normally used of that what the modpack is asking for. Is there a config file to look into?

Schildos · Answer 6 · 2023-12-30T23:42:05.000Z

well the oom killer kills a process if the OS happens to not have enough memory available..
the default jvm_args expect the server to have 8G of RAM available on the Operating system for the gameserver only.
Depending on what else might be occupying RAM on the system and some overhead for the JVM you might have to either lower the RAM assigned to the server or increase the OS RAM.
You could also try removing the -XX:+AlwaysPreTouch JVM Argument, however that will probably end up with the server getting killed at some stage of you playing causing a slight rollback in the world and/or the player inventories.

Share to