Problem Server Stalls Upon Startup

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

chaseoes

New Member
Jul 29, 2019
3
0
0
I can not figure this out. Using the Mindcrack pack, the server starts, prints the "Can't keep up!" message, and stalls. It does not appear to be online via the server list and is un-reponsive to any commands. Possibly an issue with NEI or PortalGun? It seems to happen right as both are loading.

ForgeModLoader Log

I'm happy to provide any additional information.
 

Dingham

New Member
Jul 29, 2019
294
0
0
I didn't really read the FML log 4000 line!

When a server says can't keep up its because its overloaded(processing too much information).

Whats your system spec like.?

If you thinks is NEI have you tried removing it.
 

chaseoes

New Member
Jul 29, 2019
3
0
0
I didn't really read the FML log 4000 line!

When a server says can't keep up its because its overloaded(processing too much information).

Whats your system spec like.?

If you thinks is NEI have you tried removing it.

It was running fine previously. I removed NEI and PortalGun with no results.

It appears to be something with the world - creating a brand new world worked, however, that's not really an option.
 

Dingham

New Member
Jul 29, 2019
294
0
0
I see now. Sorry. I don't know what to suggest, not come across anything like this with my server. Whats the server been installed on?

My usual approach to this sort of thing is to rebuild the server. Compile the pack(my case build as custom) or just download the mod pack* your using, if you have custom config for the server, save. Make a back up of the world(s). Then delete everything. Installed a fresh build and put your back up on. (It's a bit like turning it off and on again).

If your using a customized mod pack, ie with a few extra added. Install the basic mod pack first, check its working then add your additions in one by one.

edit: just thought, if your using a custom config file, don't install on first load, to make sure the issue isn't there.