Results 1 to 6 of 6

Thread: Dedicated Linux Server A18 crashes during RWG at size 8192

  1. #1
    Scavenger
    Join Date
    Apr 2015
    Posts
    33
    Rep Power
    0

    Dedicated Linux Server A18 crashes during RWG at size 8192

    Can't seem to ever get past WorldGen. It inevitably has a NULL exception.

    https://pastebin.com/FxAkzLjR

    i7-4790K with 32GB of memory. It takes it about 32 minutes to eventually crash. World size is 8192. I am curious why generation is so slow though. The same size world on my desktop Windows PC with an i7-8700k, takes like 5-10 minutes? I'll have to time it, but I wouldn't expect it to be this much faster (plus it actually finishes).

    Just tried lowering world size to 6144 and this time generation completed, taking about 19 minutes. System should be more than capable of generating a larger world size. Also suggests that other settings, permissions, etc. is all good.

  2. #2
    Reconstructionist zootal's Avatar
    Join Date
    Dec 2015
    Posts
    748
    Rep Power
    1
    I get a different error when trying to generate 16K maps. Have you tried different seeds? A17 was sensitive to seeds and every now and then I would find a seed that would not generate.

    That almost looks like a memory allocation issue, how much memory is it using when it crashes?

  3. #3
    Survivor Skier's Avatar
    Join Date
    Jan 2015
    Posts
    87
    Rep Power
    0
    I've also tried generating 8192 sized maps on my Windows server, and I've waited anywhere from 10-30 minutes, and it never seemed to get past:

    ...
    2019-10-09T23:43:41 75.868 INF Started thread RWG
    2019-10-09T23:43:41 75.874 INF WorldGenerator:Generating New Asoha Valley
    2019-10-09T23:43:41 75.874 INF WorldGenerator:Generating Socket Data
    2019-10-09T23:43:41 76.263 INF WorldGenerator:Generating Detail Data

    When I look at procmon, it seems the only think the game is doing for this 20+ minutes is accessing serveradmin.xml 4 times per second, so I eventually kill it... I just set the map size to 2048 and after about 20 minute, it moved forward the server is up. Maybe it's actually doing something internally for this long period of time, but it doesn't seem to access any files, other than serveradmin.xml. Maybe I'll set the map size to 8192 and let it run over night to see if the server is up in the morning...

  4. #4
    Scavenger
    Join Date
    Apr 2015
    Posts
    33
    Rep Power
    0
    Quote Originally Posted by zootal View Post
    That almost looks like a memory allocation issue, how much memory is it using when it crashes?
    I haven't caught the exact memory usage when it fails, but it was using maybe 6GB at 20 minutes in, with 20GB free. System has 32GB physical. Was one of my first thoughts, but system has plenty and it is running the 64-bit version so it's not going to have address space fragmentation issues (or at least shouldn't).

    Disks are SSD and tons of free space there (over 400GB). It doesn't even get to point of writing it to disk though. And seen from the smaller size, no permissions issues with writing it to disk.

    Thanks for the seed suggestion, i'll try out some others if i decide to restart the world and want to try a larger size again.

    One theory I did have is that Alloc's scripts requesting a save might be causing it due to some timing issue so was thinking i'd turn off the auto saves/backups and try again as well.

  5. #5
    Survivor Skier's Avatar
    Join Date
    Jan 2015
    Posts
    87
    Rep Power
    0
    Update on my situation.... I guess I just wans't being patient enough, figuring 20-30 minutes was long enough to wait for a 8192 sized map. I tried a 2048 sized map and it actually worked, but took about 10 minutes (IIRC). So, before I went to get, I told it to make the map size 10240 (I went slightly larger than 8192, since I was letting it sit over night to see what happened), and by the morning, it was working... Per log file entries, It took almost exactly 2 hours to generate and for the server to come online... See below:

    Code:
    2019-10-10T00:40:28 65.266 INF Started thread RWG
    2019-10-10T00:40:28 65.270 INF WorldGenerator:Generating Borebo Valley
    2019-10-10T00:40:28 65.270 INF WorldGenerator:Generating Socket Data
    2019-10-10T00:40:29 66.849 INF WorldGenerator:Generating Detail Data
    
    [Here's where it seems to hang, and where I used to kill it after 20-30 minutes]
    
    2019-10-10T02:39:49 7226.300 INF WorldGenerator:Generating county 'Borebo Valley' took 119 minutes, 25 seconds
    2019-10-10T02:39:49 7226.302 INF WorldGenerator:Generation Finished
    Server is a VM running with about 6 cores assigned at 2.93GHz (Lynfield, Core-i7, K-series CPU, IIRC), with about 10GB RAM assigned, on a Server 2012 OS. Save Game Data is saved to an SSD.

    P.S. I normally run alloc's server mods, but currently have them disabled, but might try them later tonight, now that I actually have the world generated and server running.

  6. #6
    Scavenger
    Join Date
    Apr 2015
    Posts
    33
    Rep Power
    0
    Decided to experiment with creating a larger world again now that there was a new build, and to try a different seed. Tried 12288 and it also failed.

    Code:
    2019-10-13T17:23:55 13.632 INF Started thread RWG
    2019-10-13T17:23:55 13.634 INF WorldGenerator:Generating Vimasi Territory
    2019-10-13T17:23:55 13.634 INF WorldGenerator:Generating Socket Data
    2019-10-13T17:23:55 13.998 INF WorldGenerator:Generating Detail Data
    eac_server.so [x64] :: OnLoad()
    Receiving unhandled NULL exception
    #0  0x007fdadb36842a in (Unknown)
    #1  0x007fdad8ce9b3a in (Unknown)
    #2  0x007fdad8ce9ba7 in (Unknown)
    #3  0x007fdad8ceca9d in (Unknown)
    #4  0x007fdad8cecd06 in (Unknown)
    #5  0x007fdad8ced174 in (Unknown)
    #6  0x007fdad8cedfa6 in (Unknown)
    #7  0x007fdad8cf0e1e in (Unknown)
    #8  0x007fdad8cf1086 in (Unknown)
    #9  0x007fdad8cc4135 in (Unknown)
    #10 0x007fdad8c7a3de in (Unknown)
    #11 0x007fdad8c7a555 in (Unknown)
    #12 0x007fdad8c7a59d in (Unknown)
    #13 0x00000041372f37 in (wrapper managed-to-native) object:__icall_wrapper_ves_icall_object_new_specific (intptr)
    Trying another different seed now.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •