search

ich777 / docker-steamcmd-server

Simple Dockerfile that installs steamcmd and a selected game server
119 stars 95 forks source link

Palworld Version 1.4+ #55

Closed SalazarElite closed 6 months ago

SalazarElite commented 6 months ago

We need to find a way to update the server more easily, currently the game is on version 1.4 and the server does not support this version

CurtHubb commented 6 months ago

The read me says "Update Notice: Simply restart the container if a newer version of the game is available." however this didn't work for me. I still get a incompatible error.

2024-02-01 13:16:10.711118-05:00---Ensuring UID: 568 matches user--- 2024-02-01 13:16:11.630015-05:00---Ensuring GID: 568 matches user--- 2024-02-01 13:16:11.876303-05:00usermod: no changes 2024-02-01 13:16:11.876397-05:00---Setting umask to 002--- 2024-02-01 13:16:11.876442-05:00---Checking for optional scripts--- 2024-02-01 13:16:11.878954-05:00---No optional script found, continuing--- 2024-02-01 13:16:11.878969-05:00---Taking ownership of data...--- 2024-02-01 13:16:12.243049-05:00---Starting...--- 2024-02-01 13:16:12.280931-05:00---Update SteamCMD--- 2024-02-01 13:16:13.618164-05:00tid(32) burning pthread_key_t == 0 so we never use it 2024-02-01 13:16:13.618186-05:00Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' 2024-02-01 13:16:13.618194-05:00Logging directory: '/serverdata/Steam/logs' 2024-02-01 13:16:13.618200-05:00[ 0%] Checking for available updates... 2024-02-01 13:16:13.618216-05:00[----] Verifying installation... 2024-02-01 13:16:13.618223-05:00Steam Console Client (c) Valve Corporation - version 1705108307 2024-02-01 13:16:13.618229-05:00-- type 'quit' to exit -- 2024-02-01 13:16:13.618235-05:00Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory 2024-02-01 13:16:13.618244-05:00OK 2024-02-01 13:16:13.618250-05:002024-02-01T13:16:13.618250817-05:00 2024-02-01 13:16:15.780761-05:00Connecting anonymously to Steam Public...OK 2024-02-01 13:16:15.780787-05:00Waiting for client config...OK 2024-02-01 13:16:19.202241-05:00Waiting for user info...OK 2024-02-01 13:16:19.365728-05:00---Update Server--- 2024-02-01 13:16:20.570904-05:00tid(55) burning pthread_key_t == 0 so we never use it 2024-02-01 13:16:20.570928-05:00Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' 2024-02-01 13:16:20.570943-05:00Logging directory: '/serverdata/Steam/logs' 2024-02-01 13:16:20.570960-05:00[ 0%] Checking for available updates... 2024-02-01 13:16:20.570968-05:00[----] Verifying installation... 2024-02-01 13:16:20.570975-05:00Steam Console Client (c) Valve Corporation - version 1705108307 2024-02-01 13:16:20.570981-05:00-- type 'quit' to exit -- 2024-02-01 13:16:20.570988-05:00Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory 2024-02-01 13:16:20.570999-05:00OK 2024-02-01 13:16:20.571006-05:002024-02-01T13:16:20.571006194-05:00 2024-02-01 13:16:22.425242-05:00Connecting anonymously to Steam Public...OK 2024-02-01 13:16:22.425327-05:00Waiting for client config...OK 2024-02-01 13:16:22.778629-05:00Waiting for user info...OK 2024-02-01 13:16:22.845247-05:00/serverdata/steamcmd/steamcmd.sh: line 39: 55 Segmentation fault $DEBUGGER "$STEAMEXE" "$@" 2024-02-01 13:16:22.845551-05:00---Checking if configuration is in place--- 2024-02-01 13:16:22.845592-05:00---Configuration found, continuing...--- 2024-02-01 13:16:22.845608-05:00---Checking if PublicIP is in place--- 2024-02-01 13:16:22.899529-05:00---Nothing to do, PublicIP: Removed still up-to-date!--- 2024-02-01 13:16:22.899646-05:00---Prepare Server--- 2024-02-01 13:16:22.976967-05:00---Server ready--- 2024-02-01 13:16:22.977019-05:00---Starting Backup daemon--- 2024-02-01 13:16:22.977150-05:00---Start Server--- 2024-02-01 13:16:23.663608-05:00Shutdown handler: initalize. 2024-02-01 13:16:23.663635-05:00Disabling core dumps. 2024-02-01 13:16:23.663608-05:00[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. 2024-02-01 13:16:23.771551-05:00CAppInfoCacheReadFromDiskThread took 2 milliseconds to initialize 2024-02-01 13:16:23.793991-05:00Setting breakpad minidump AppID = 2394010 2024-02-01 13:16:23.794545-05:00[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded. 2024-02-01 13:16:23.794570-05:00[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded. 2024-02-01 13:16:24.256335-05:00[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded. 2024-02-01 13:16:24.314496-05:00[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

ich777 commented 6 months ago

We need to find a way to update the server more easily, currently the game is on version 1.4 and the server does not support this version

Please read like @CurtHubb already pointed out, you simply have to restart the container. Sorry but I really don't know how to do it more easily...

however this didn't work for me. I still get a incompatible error.

Are you sure that you client is already on version 1.4.0.0? No issues over here, see this post.

What you could do is to force a complete repull from all the files is:

  1. Stop the container
  2. Delete everything in the palworld directory but NOT the Pal directory
  3. Start the container

Such errors that you are experiencing are caused because something prevents SteamCMD communicating properly with Steam Pipe because something is hold in the cache or simply blocked.

CurtHubb commented 6 months ago

What you could do is to force a complete repull from all the files is:

  1. Stop the container
  2. Delete everything in the palworld directory but NOT the Pal directory
  3. Start the container

This worked great, thank you! Also thank you for all the hard work you do!

ich777 commented 6 months ago

Also thank you for all the hard work you do!

Thanks really much appreciated! Really hard these days because nobody seems to read nowadays (except for a few people)... :D

ich777 commented 6 months ago

@SalazarElite can this be closed?

SalazarElite commented 6 months ago

yep, ir you want

From: Christoph Hummer @.> Sent: Thursday, February 1, 2024 5:34:29 PM To: ich777/docker-steamcmd-server @.> Cc: Natan Salazar @.>; Mention @.> Subject: Re: [ich777/docker-steamcmd-server] Palworld Version 1.4+ (Issue #55)

@SalazarElitehttps://github.com/SalazarElite can this be closed?

— Reply to this email directly, view it on GitHubhttps://github.com/ich777/docker-steamcmd-server/issues/55#issuecomment-1922198134, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEWZ46TB5DJHVZ2COAOEJFTYRP35LAVCNFSM6AAAAABCVH3OCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRSGE4TQMJTGQ. You are receiving this because you were mentioned.Message ID: @.***>

ich777 commented 6 months ago

yep, ir you want

Is this now also resolved for you?

SalazarElite commented 6 months ago

in fact I made my own workaround, I wasn't updating for anything so I made a workaround for steamCMD to use the updated version of the server

From: Christoph Hummer @.> Sent: Thursday, February 1, 2024 6:24:44 PM To: ich777/docker-steamcmd-server @.> Cc: Natan Salazar @.>; Mention @.> Subject: Re: [ich777/docker-steamcmd-server] Palworld Version 1.4+ (Issue #55)

yep, ir you want

Is this now also resolved for you?

— Reply to this email directly, view it on GitHubhttps://github.com/ich777/docker-steamcmd-server/issues/55#issuecomment-1922272170, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEWZ46UL2VFS2CGWDQ3BDK3YRQBZZAVCNFSM6AAAAABCVH3OCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRSGI3TEMJXGA. You are receiving this because you were mentioned.Message ID: @.***>

ich777 commented 6 months ago

in fact I made my own workaround

I don't quiet understand, if you restart the container it will check for updates and download them eventually.

SalazarElite commented 6 months ago

This update on restart function is not working as it should, I use a Truenas Scale server based on Linux and for some reason it does not update, but I made a workaround to download the files from Steam and manually send it to my server where the Palworld server is

From: Christoph Hummer @.> Sent: Thursday, February 1, 2024 6:41:04 PM To: ich777/docker-steamcmd-server @.> Cc: Natan Salazar @.>; Mention @.> Subject: Re: [ich777/docker-steamcmd-server] Palworld Version 1.4+ (Issue #55)

in fact I made my own workaround

I don't quiet understand, if you restart the container it will check for updates and download them eventually.

— Reply to this email directly, view it on GitHubhttps://github.com/ich777/docker-steamcmd-server/issues/55#issuecomment-1922294880, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEWZ46VXAJEKKQFFIA427BLYRQDXBAVCNFSM6AAAAABCVH3OCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRSGI4TIOBYGA. You are receiving this because you were mentioned.Message ID: @.***>

ich777 commented 6 months ago

This update on restart function is not working as it should, I use a Truenas Scale server based on Linux and for some reason it does not update

Ah, now I get it...

What is the error, this is the first time I hear of that problem. I also have a few users on TrueNAS who are using my container and the update on start is working for them, at least to my knowledge.

but I made a workaround to download the files from Steam and manually send it to my server where the Palworld server is

However that sounds pretty involved...