Help! 0.8.2 server error after trying to convert world in previous version

The next update will be available on Wednesday, December 18, in the early evening (GMT+1).

This update will not yet replace the Java version, instead it is the actual content update. We'll provide more information about the transition together with the update.

    Hi @red51,


    After updating (ie copying the new 0.8.2 files over the old ones), the server will try to convert the world to the new version and fail.


    Happy to share my files.


    This is the log:


    Rising World - 0.8.2 - Dedicated Server
    Linux 4.9.0-2-amd64 Java 1.8.0_121 (amd64) Memory: 1908 MB
    2017/04/21 10:11 AM


    [...]
    Initializing world (sqlite)
    LOAD WORLD Marcolandia3
    DATABASE TYPE: SQLite
    /home/marcos/rising-world_server/Worlds/Marcolandia3:::Marcolandia3
    CREATE WORLD STRUCTURE - DONE!
    2017/04/21 10:11 AM x.a
    INFO: DatabaseTaskManager started with ThreadPoolSize 1
    WORLDINFO Gamemode: Survival
    Gametype set to Survival
    WORLDINFO Seed: -51773781607014
    WORLDINFO Caves: true
    WORLDINFO Vegetations: true
    WORLDINFO OreAmount: 3
    WORLDINFO DisabledNPCs:
    WORLDINFO DisabledDungeons:
    WORLDINFO DisabledWaterSources:
    WORLDINFO Worldtype: Normal
    WORLDINFOS seed: -51773781607014 type: Normal caves: true vegetations: true oreamount: 3 disablednpc: [] disableddungeons: [] disabledwatersources: []
    WORLDINFO Time: 27.9.0 22:24:1.6864659
    set game time from string: 27.9.0 22:24:1.6864659
    WORLDINFO Creationdate: 1487073467036
    WORLDINFO Version: 0.8.1.2_32
    TRIGGER UPDATE
    Worldconverter: Updating (32) to version (33) 0.8.2 ...
    Creating world backup...Copied directory from /home/marcos/rising-world_server/Worlds/Marcolandia3/worldParts to /home/marcos/rising-world_server/Worlds/.backup/Marcolandia3_1492740714/worldParts
    [...]
    DONE!
    Worldpart generating...
    Biomepart generating...
    biomepart offset 0 0 -> 4 1 (-1754662916, -438665729)
    Biomepart (0) generated: 0 - 0 (438ms)
    CavePoints: 386862
    DungeonPoints: 717
    clear dungeon map
    -> NO GENERATION POSSIBLE AT 66 -28 19


    - neighbour is still null for BigHallExit
    -> NO GENERATION POSSIBLE AT 37 -57 7


    - neighbour is still null for BigHallEntrance
    - neighbour is null(2) for Singledoor_Arc
    - neighbour is still null for BigHallEntrance
    - neighbour is null(2) for Singledoor_Arc
    - neighbour is still null for StairwayF
    - neighbour is null(2) for Singledoor_Arc
    - neighbour is still null for StairwayF
    - neighbour is null(2) for Singledoor_Arc
    - neighbour is still null for BigHallExit
    - neighbour is null(2) for StairwayL
    - neighbour is null(2) for Singledoor_Arc
    -> NO GENERATION POSSIBLE AT 4 -75 107


    - neighbour is still null for StairwayB
    - neighbour is null(2) for Singledoor_Arc
    - neighbour is still null for BigHallEntrance
    -> NO GENERATION POSSIBLE AT 5 -40 19


    - neighbour is still null for BigHallEntrance
    - neighbour is null(2) for Singledoor_Arc
    0 0 total underground dungeons: 319
    java.lang.NullPointerException
    at commons.world.p.a(SourceFile:489)
    at commons.world.p.a(SourceFile:406)
    at commons.world.i.a(SourceFile:535)
    at commons.world.i.a(SourceFile:693)
    at commons.world.i.a(SourceFile:233)
    at server.util.a.a(SourceFile:146)
    at server.e.a(SourceFile:1327)
    at server.e.a(SourceFile:1212)
    at server.e.a(SourceFile:1039)
    at server.Main.d(SourceFile:427)
    at server.Main.initApplication(SourceFile:251)
    at commons.JIWApplication.initialize(SourceFile:231)
    at com.jme3.system.NullContext.initInThread(NullContext.java:87)
    at com.jme3.system.NullContext.run(NullContext.java:130)
    at java.lang.Thread.run(Thread.java:745)
    2017/04/21 10:12 AM server.Main
    SEVERE: Fatal error occurred!
    java.lang.NullPointerException
    at commons.world.p.a(SourceFile:489)
    at commons.world.p.a(SourceFile:406)
    at commons.world.i.a(SourceFile:535)
    at commons.world.i.a(SourceFile:693)
    at commons.world.i.a(SourceFile:233)
    at server.util.a.a(SourceFile:146)
    at server.e.a(SourceFile:1327)
    at server.e.a(SourceFile:1212)
    at server.e.a(SourceFile:1039)
    at server.Main.d(SourceFile:427)
    at server.Main.initApplication(SourceFile:251)
    at commons.JIWApplication.initialize(SourceFile:231)
    at com.jme3.system.NullContext.initInThread(NullContext.java:87)
    at com.jme3.system.NullContext.run(NullContext.java:130)
    at java.lang.Thread.run(Thread.java:745)


    Shutdown 1 database threads...
    2017/04/21 10:12 AM x.a
    INFO: DatabaseTaskManager stopped!

    Ok, looks like the error happens even when starting from scratch a new world:


    2017/04/21 11:40 AM server.Main


    SEVERE: Fatal error occurred!


    java.lang.NullPointerException


    at commons.world.p.a(SourceFile:489)


    at commons.world.p.a(SourceFile:406)


    at commons.world.i.a(SourceFile:535)


    at commons.world.i.a(SourceFile:693)


    at commons.world.i.a(SourceFile:233)


    at server.e.b(SourceFile:1073)


    at server.e.a(SourceFile:1043)


    at server.Main.d(SourceFile:427)


    at server.Main.initApplication(SourceFile:251)


    at commons.JIWApplication.initialize(SourceFile:231)


    at com.jme3.system.NullContext.initInThread(NullContext.java:87)


    at com.jme3.system.NullContext.run(NullContext.java:130)


    at java.lang.Thread.run(Thread.java:745)

    By the way, I copied the world to the Rising World steam client folder, and opening it as single player it converts and loads fine, I can even Open to LAN fine, so it is something with the server software only that is giving the error...


    0.8.1 is still fine if I start it instead of the new one (but can connect from the 0.8.2 client).


    Cheers,
    Marcos

    Sorry for my late response! It looks like some server files are outdated, at least it can't find the new definitions (or more precisely, it's using the old world definitions). Make sure you replace all files in your server directory, especially those files in the "lib" subfolder (or it's better to delete the lib folder and put the new lib folder from the new server version there).
    In some cases a file access restriction can cause some weird behaviour of SQLite (or more precisely, the JDBC driver). So if updating the server does not help, try to move the server to a new directory and see if the issue persists. Also make sure to delete the "cache" folder in your server directory.

Participate now!

Don’t have an account yet? Create a new account now and be part of our community!

Create Account Login