Single grid crash on startup [ LoadFromFile ] [5x5]

[duxck 1]

I have a 5x5 that is running just fine for 24 of my 25 servers. grid D2 (3,1) is having issues with starting up. Haven't been able to find any issues with the json files or the game config files that are unique to this grid and I don't really know where to continue my search. 

I have built the grid in ServerGridEditor and haven't edited much manually. Been going through the forums for a solution but sadly I have only seen people with similar issues but no solutions, those threads just went silent. 

Help me Atlas Dedicated server forum, you're my only hope!
Any pointers on where I should continue my search for a solution is highly appreciated.

 

[2019.02.21-11.10.13:898][  0]Log file open, 02/21/19 12:10:13
[2019.02.21-11.10.13:898][  0]LogMemory: Platform Memory Stats for WindowsServer
[2019.02.21-11.10.13:898][  0]LogMemory: Process Physical Memory: 59.32 MB used, 59.32 MB peak
[2019.02.21-11.10.13:898][  0]LogMemory: Process Virtual Memory: 51.89 MB used, 52.02 MB peak
[2019.02.21-11.10.13:899][  0]LogMemory: Physical Memory: 3557.78 MB used, 135167.48 MB total
[2019.02.21-11.10.13:899][  0]LogMemory: Virtual Memory: 281.26 MB used, 134217728.00 MB total
[2019.02.21-11.10.14:437][  0]ATLAS Version: 18.95 (Rev. 107965)
[2019.02.21-11.10.14:437][  0]PID: 2628
[2019.02.21-11.10.45:147][  0]Primal Game Data Took 29.92 seconds
[2019.02.21-11.10.49:615][  0]SteamSocketsOpenSource: gethostname failed ()
[2019.02.21-11.10.49:616][  0]gethostbyname failed ()
[2019.02.21-11.10.55:473][  0]Server Initializing with BattlEye Anti-Cheat Protection. If you do not wish to use BattlEye, please launch with -NoBattlEye
[2019.02.21-11.10.55:475][  0]BattlEye successfully started.
[2019.02.21-11.10.55:477][  0]Network range scales set to: 48 start, 77 end, 0.440000 endscale
[2019.02.21-11.15.01:696][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItemArmor_YarkAoDShield_C_488 [C35C28D841F784F7CBB82F90A567D7AC vs 7CFD89A14EE038AD4C4825B46092040A]
[2019.02.21-11.15.01:698][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItemArmor_YarkAoDShield_C_485 [CE3693A54B04D20DD861C28EC98E1DAB vs EAB84B9D4DEA04C0E66BAC8E7791291B]
[2019.02.21-11.15.01:699][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItemArmor_YarkAoDShield_C_482 [04E10132405A29207673578FACF04A46 vs 121BCEB84E59AE189AA958988181CCB3]
[2019.02.21-11.15.01:700][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItemArmor_YarkAoDShield_C_479 [AF4588464E10743DC5A2A4B970A7EA7D vs 0E0E396941B34D1E8D5D0AAECB972DEB]
...
...
...
A lot of these messages, about 20.000 lines of LoadFromFile, Ignored blah blah blah
...
...
...
[2019.02.21-11.15.21:923][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItem_WeaponCrossbow_AoD_C_1243 [51B4605D49F6D8139A5C7D95A08E9036 vs 729E34094A5E17F8DABE7AB821B25A3E]
[2019.02.21-11.15.21:924][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItemArmor_YarkAoDShield_C_917 [A39B8EEC49E3E485C6961FBDDB130E2E vs 02E79E3F4258C71B398FFEAF07E30608]
[2019.02.21-11.15.21:925][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItem_YarkWeaponSword_AoD_C_1263 [23FDC178419986EBCDC3F693D8C35D6F vs CD704B204B47D90679266DB7365269E7]
[2019.02.21-11.15.21:926][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItem_WeaponCrossbow_AoD_C_1245 [D4DC546A4B5FA7BBC273BCA459FA8B2A vs 4F3B50D34C98857247D434A587A8FEA6]
[2019.02.21-11.15.21:926][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItemArmor_AoDHelmet_C_3169 [F6A931E446827B8A84CECEA92C4C3347 vs 132B6FAB49D03404F9885FB016CB13F4]
[2019.02.21-11.15.21:927][  0]UWorld::LoadFromFile: Ignored second entry for PrimalItem_WeaponCrossbow_AoD_C_1247 [76765B414228EC2787BBD7BFD2087E1F vs E339F2674DBD3E782FB8179E63365DB0]
[2019.02.21-11.17.37:618][  0]LogMemory: Platform Memory Stats for WindowsServer
[2019.02.21-11.17.37:620][  0]LogMemory: Process Physical Memory: 3702.15 MB used, 3702.15 MB peak
[2019.02.21-11.17.37:622][  0]LogMemory: Process Virtual Memory: 3807.91 MB used, 3891.91 MB peak
[2019.02.21-11.17.37:623][  0]LogMemory: Physical Memory: 7851.54 MB used, 135167.48 MB total
[2019.02.21-11.17.37:624][  0]LogMemory: Virtual Memory: 4260.84 MB used, 134217728.00 MB total
[2019.02.21-11.18.01:171][  0] - FPlatformMisc::RequestExit(1)
[2019.02.21-11.18.01:173][  0]Log file closed, 02/21/19 12:18:01

 

Attached dmp and crashstack. Honestly they didn't make me any smarter.

02.21-12.18.00.crashstack

Dump797865504.dmp

[duxck 1]

When I renamed C:\Atlas\steamapps\common\ATLAS Dedicated Server\ShooterGame\Saved\31 to \Saved\31_OLD and let it generate a new folder for the server it looked like it solved the problem. At this stage I only started this specific grid and it seemed to be working. 

I then renamed Saved to Saved_OLD to force it to create new save files. I am aware that this solution only works if you're willing to loose all saved data. 
Either way, all servers now started up without a hitch. Validated the install and everything works fine. 

[MaLioSherGaming 5]

I think I see what our issue was.  I saw someone say that each server needs its own save folder.  That may be our problem!  Try changing your startup commands for each server to save to a different folder. so for instance:

 

start ShooterGameServer.exe Ocean?ServerX=0?ServerY=0?AltSaveDirectoryName=00.....

start ShooterGameServer.exe Ocean?ServerX=0?ServerY=1?AltSaveDirectoryName=01.....

start ShooterGameServer.exe Ocean?ServerX=1?ServerY=1?AltSaveDirectoryName=02.....

 

 

I know all mine were saving to the same directory, I bet that's why they crash on restart.  If only one of yours is failing, see if the save folder is being reused.