After updating and playing a little on my private server I was unable to log in as the server was stuck in a crash loop. I did nothing in the nether other than deleted the old dim file and ensure a new nether was generated.

https://gist.github.com/SpeedSlider/c64d99746294299d426d9d7d796a9bea

Expected Behavior

Server should run continuously as it has before the latest update.

Current Behavior

Server stuck in a crash loop.

Possible Solution

I will be deleting the nether dim and restarting the server. The only thing I can think is that I am not currently playing on the server much and I had a nether portal within 100 blocks of spawn.

Steps to Reproduce

N/A

Log

https://gist.github.com/SpeedSlider/c64d99746294299d426d9d7d796a9bea

Detailed Description

Mostly I am posting this for the crash report. I have done no troubleshooting at this point. Prior to updating to 1.5.0. the server ran fine and I had limited issues. After updating which including deleting the nether files the server got stuck in a crash loop. I manually stopped the server and restarted it and it crashed. At this point I can only assume that I left the nether portal active within 500 blocks of spawn which had the nether constantly loaded. Previously, I had deactivated the portal and used waystones to get to the nether.

Your RAM is set too low to even run remix.

I have been playing it fine for several months with that RAM which is one higher than what Akliz's recommends :P. Also, it ran and played fine after the update. The crash occurred after it ran all night with no-one on.

Bug from NetherEX apparently.
https://github.com/LogicTechCorp/NetherEx/issues/192

Hmmm... Not sure what to do with that info at the moment. I am restarting after deleting the nether. If that works then I will be trying it without an active portal to see what happens.

Well... that didn't work and I went into the config files. I found an Netherex_old, netherex, and Netherex folders. I will do some poking but may just revert to 1.4.9 as I backed up the world and skip this update.

@Yamza @SpeedSlider
Since you referenced my crash report I would have thought you would have also read the crash report in its entirety. Two things here 1) that crash report is very straightforward as it tells you what caused the crash, a json file is missing the first character required in a json file, and 2) The most recent version of NetherEx is now 2.0.14 which was published last night shortly after they became aware of this issue, as stated here in my report: https://github.com/LogicTechCorp/NetherEx/issues/192#issuecomment-530591553

Because your crash was on an outdated version, this invalidates your bug report at this time. @SpeedSlider Additionally, to resolve this issue, you simply need to delete the netherex folder that is in the ./config/ folder and replace it with one that has good and valid json files. Depending on which modpack this is for, one way to accomplish this is to download the server files and extract the required folder and copy it over to your client. This again was addressed in this comment in my bug report, however at the time I did not post my solution: https://github.com/LogicTechCorp/NetherEx/issues/192#issuecomment-530377577

I suggest that if you are going to reference a bug report that you actually read the report. My report is over 14 hours old, and with the issue potentially resolved already (I say potentially as I have not had a chance to personally verify the issue is resolved in 2.0.14).

Also just an FYI, this crash has been an issue in netherex since before the 2.0.13 update. The reason for the json files becoming blank is as of yet unknown. It seems to happen at random, with no clear cause. The fact it happened after you updated to 2.0.13 is purely a coincidence, and not a result of.

@Gunner76th As you can see, this is not a report to netherex about the issue, thus I referenced the relevant issue so that it can be fixed. No need for the condescending remarks really..
The fact that it is 14 hours old doesn't help anyone here. Pack is now using this version of netherex and this is clearly going to be an issue until the pack is updated again.

@Gunner76th I apologize for the inconvenience. Although I can read a crash report I have limited understanding of them. I generally can determine what mod is causing the issue but beyond that it has been way too long since I have done any programming and never in Java. I mostly posted this as I do helping/testing for ATM3 and just wanted to document that the latest update produced something different. Again, sorry for the inconvenience.

As this is a private server, he can easily update the NetherEx file on both his private server and his client manually and resolve his issue. Additionally, players who are only playing in single player, or on servers that they manage can also do the same. Sorry if I was overly aggressive in my initial reply. I had literally just woken up, saw I had updates and was still operating with sleep/brain fog.
And SpeedSlider, Yamza is correct, your memory needs to be set to a minimum of 4096m otherwise you will eventually have an OutofMemory heap crash. All modpacks after Minecraft 1.10 require a minimum of 4096m (Or 4G) of memory in order to load and run without a memory issue. The fact that it is working with 4000m at the moment is purely luck.

I am also testing version 2.0.14 now to confirm that the json issue is resolved.

Memory is fine for an Akliz server. Thanks for the clarification.

Well... perhaps both of you may want to talk with Akliz and find out what they do that is different. I purchased the server through them and they recommended a minimum of 3Gig for ATM3:Remix which ran fine for me. I only updated to 4Gig as I have a son and a friend that now play with me and when we were exploring in different dims we started to get block lag. Other then generating new chunks I have had no issues running ATM3:Remix while only purchasing their 4Gig package. Since it is not my physical server I have not altered any of the hardware specs/configs in the files.

Ok bad news, 2.0.14 has not fixed the problem. At this point in time the only way to resolve this problem is to download valid json files and replace the empty ones with them.

This is why I am a self proclaimed Noob. Only a Noob can throw a wrench in things and make this kind of mess. I have errands to run and will try to get my server restored with previous files before updating since I still have the old NetherEx folder.

OK so update 2.whatever, Seems I was hasty in my initial assessment of 2.0.14 The fix technically fixes the problem, in so long as the .json file is completely empty. However, if the json file is only missing the first character as the crash log technically states, the mod still crashes. I am updating my initial report to include as such, so that hopefully they can refine their json validation and detection calls.

Fixed in 1.5.1.