Issue while updateing to Palworld 0.1.5.0

[adamburns525]

Hello,

I'm not able to start my server/ update my server after the most recent update to Palworld 0.1.5.0

Log: 2024-02-27 09:20:53.048704-06:00---Ensuring UID: 568 matches user--- 2024-02-27 09:20:54.462949-06:00---Ensuring GID: 568 matches user--- 2024-02-27 09:20:54.994045-06:00usermod: no changes 2024-02-27 09:20:54.994337-06:00---Setting umask to 0022--- 2024-02-27 09:20:54.994369-06:00---Checking for optional scripts--- 2024-02-27 09:20:54.998266-06:00---No optional script found, continuing--- 2024-02-27 09:20:54.998308-06:00---Taking ownership of data...--- 2024-02-27 09:20:55.669846-06:00---Starting...--- 2024-02-27 09:20:55.679323-06:00---Update SteamCMD--- 2024-02-27 09:20:57.019577-06:00tid(32) burning pthread_key_t == 0 so we never use it 2024-02-27 09:20:57.019617-06:00Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' 2024-02-27 09:20:57.019627-06:00Logging directory: '/serverdata/Steam/logs' 2024-02-27 09:20:57.019637-06:00[ 0%] Checking for available updates... 2024-02-27 09:20:57.019658-06:00[----] Verifying installation... 2024-02-27 09:20:57.019668-06:00Steam Console Client (c) Valve Corporation - version 1705108307 2024-02-27 09:20:57.019677-06:00-- type 'quit' to exit -- 2024-02-27 09:20:57.283265-06:00Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory 2024-02-27 09:20:57.283304-06:00OK 2024-02-27 09:20:57.283314-06:002024-02-27T09:20:57.283314961-06:00 2024-02-27 09:20:58.798623-06:00Connecting anonymously to Steam Public...OK 2024-02-27 09:20:58.798675-06:00Waiting for client config...OK 2024-02-27 09:21:01.580064-06:00Waiting for user info...OK 2024-02-27 09:21:01.660860-06:00---Update Server--- 2024-02-27 09:21:01.660910-06:00---Validating installation--- 2024-02-27 09:21:02.679273-06:00tid(56) burning pthread_key_t == 0 so we never use it 2024-02-27 09:21:02.679324-06:00Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' 2024-02-27 09:21:02.679335-06:00Logging directory: '/serverdata/Steam/logs' 2024-02-27 09:21:02.679343-06:00[ 0%] Checking for available updates... 2024-02-27 09:21:02.679352-06:00[----] Verifying installation... 2024-02-27 09:21:02.679360-06:00Steam Console Client (c) Valve Corporation - version 1705108307 2024-02-27 09:21:02.679369-06:00-- type 'quit' to exit -- 2024-02-27 09:21:02.810612-06:00Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory 2024-02-27 09:21:02.810646-06:00OK 2024-02-27 09:21:02.810657-06:002024-02-27T09:21:02.810657004-06:00 2024-02-27 09:21:04.167444-06:00Connecting anonymously to Steam Public...OK 2024-02-27 09:21:04.167507-06:00Waiting for client config...OK 2024-02-27 09:21:14.056770-06:00Waiting for user info...OK 2024-02-27 09:21:14.056835-06:00Update state (0x3) reconfiguring, progress: 0.00 (0 / 0) 2024-02-27 09:21:14.056847-06:00Update state (0x5) verifying install, progress: 6.90 (156071881 / 2260984531) 2024-02-27 09:21:14.056856-06:00Update state (0x5) verifying install, progress: 31.16 (704435491 / 2260984531) 2024-02-27 09:21:14.056864-06:00Update state (0x5) verifying install, progress: 55.83 (1262308120 / 2260984531) 2024-02-27 09:21:14.056872-06:00Update state (0x5) verifying install, progress: 80.18 (1812906151 / 2260984531) 2024-02-27 09:21:14.056885-06:00Success! App '2394010' fully installed. 2024-02-27 09:21:14.188582-06:00---Checking if configuration is in place--- 2024-02-27 09:21:14.188638-06:00---Configuration found, continuing...--- 2024-02-27 09:21:14.188661-06:00---Checking if PublicIP is in place--- 2024-02-27 09:21:14.215501-06:00---Nothing to do, PublicIP: 47. still up-to-date!--- 2024-02-27 09:21:14.215568-06:00---Prepare Server--- 2024-02-27 09:21:14.265736-06:00---Server ready--- 2024-02-27 09:21:14.265796-06:00---Starting Backup daemon--- 2024-02-27 09:21:14.265997-06:00---Start Server--- 2024-02-27 09:21:15.285371-06:00[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. 2024-02-27 09:21:15.401412-06:00CAppInfoCacheReadFromDiskThread took 6 milliseconds to initialize 2024-02-27 09:21:15.422164-06:00Setting breakpad minidump AppID = 2394010 2024-02-27 09:21:15.423446-06:00[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded. 2024-02-27 09:21:15.423487-06:00[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded. 2024-02-27 09:21:16.147178-06:00[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded. 2024-02-27 09:21:16.265752-06:00[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded. 2024-02-27 09:26:00.664272-06:002024-02-27T09:26:00.664272678-06:00 2024-02-27 09:26:00.664343-06:00Session terminated, killing shell.../opt/scripts/start.sh: line 29: kill: (84) - Operation not permitted 2024-02-27 09:26:02.660023-06:00...killed.

[ich777]

I don't see an error, what is your error? If the container won't properly update then you can try to:

1. Stop the container
2. Delete everything except for the Pal directory
3. Start the container

BTW please check your permissions and if your Docker service is actually able to us UID 568 and GID 568

[DearMusic903]

The same thing happened to my setup.

Before the deployment failed, this message came up:

FUnixPlatformMisc::RequestExitWithStatus FUnixPlatformMisc::RequestExit Shutdown handler: initialize Disabling core dumps. Session terminated, killing shell... ...killed. Exiting abnormally (error code: 143) Shutdown handler: cleanup.

The deployment worked perfectly fine before the Palworld V0.1.5.0 update.

[ich777]

@DearMusic903 this is really too less information, this is the shutdown handler and this is the normal behaviour... other than that where do you see that message in the log above?

I can only tell you that my server is running fine with the newest update:

However what is working not fine is RCON since it seems it is broken after the newest update but that is nothing I can change since this is a game issue.

Have you yet tried what I've posted above your comment?

[DearMusic903]

other than that where do you see that message in the log above?

If you look at adamburns525's log and replace the last 2 lines with the error I posted, that's where I see the message.

However what is working not fine is RCON since it seems it is broken after the newest update but that is nothing I can change since this is a game issue.

Have you tried adding -rconport=xxxx as a parameter? It's one of the new changes made in v0.1.5.0 -publiclobby is also one of the new arguments that replace EpicApp=PalServer

Have you yet tried what I've posted above your comment?

~I am too afraid to lose my world that was working perfectly fine before v0.1.5.0 update... I'll try that later~

I figured out the issue, it was RCON.

[adamburns525]

I was able to correct the issue with the RCON fix as well.

[xstar97]

truecharts uses RCON as a healthcheck for UDP game servers; so sorry for the invalid issue request; wanted to be sure it wasnt a container issue with the latest version.

[ich777]

Have you tried adding -rconport=xxxx as a parameter?

This is a stupid change, why would the make that now a requirement when they already had it in the config and it was working... Is that documented somewhere, as time of writing it is not mentioned here.

I am too afraid to lose my world that was working perfectly fine before v0.1.5.0 update... I'll try that later

Nothing to worry about since the Pal directory contains your savegame.

[ich777]

I was able to correct the issue with the RCON fix as well.

So is it now working? Can this issue be closed?

[DearMusic903]

Is that documented somewhere, as time of writing it is not mentioned here.

It's not documented anywhere yet I don't think, but a lot of people asked in the official Palworld discord server and the solution came up.

[ich777]

@adamburns525 is your container now up and running again?

[adamburns525]

Yes thank you for your help!