31 minutes ago, CaptainTrap said:

Hi Ich. This is perplexing then as when i set to false the server crashes. When i set to true its stable and connects to steam. could there be bios settings that solve this?

Hi ich, I just checked the log files at the point of crash from the docker console and this is the line logged indicating a segmentation fault when FORCE_86 is set to false:

 

15:24:48 Host identity created.

/opt/scripts/start-server.sh: line 69:     66 Segmentation fault     ./arma3server_x64 ${GAME_PARAMS}

57 minutes ago, CaptainTrap said:

could there be bios settings that solve this?

Usually not.

 

24 minutes ago, CaptainTrap said:

segmentation fault when FORCE_86 is set to false

This happens on some systems don‘t worry too much about it, if it runs fine in x86 mode than it‘s fine too.

HI,

I have 3 minecraft basic server's up and running, every thing works game wise but i can't get the tcp web console to work on any of them chrome or edge.

 

cheers

1 hour ago, turnipisum said:

I have 3 minecraft basic server's up and running, every thing works game wise but i can't get the tcp web console to work on any of them chrome or edge.

A bit more information please, what ports have you changed or what did you do exactly?

Do you have by any chance a screenshot from your Docker template?

 

I think you are talking about that correct:

On 9/11/2023 at 10:16 PM, ich777 said:

What version conflict do you get?

When I start the Game and got to Server Manager to start a session from my Server, i get the following Screen:

 

 

On 9/11/2023 at 10:16 PM, ich777 said:

What version do you use on your PC and what on your Server?

Do you maybe use another branch on your PC?

I'm not completly sure how to view the Version. I attach some screenshot from the game and the Docker page, maybe you can see whats mismatching.

 

 

This config worked for quite a long time, but since I updatet the game some weeks ago, I always get the message of the mismatch.

1 minute ago, b_tob said:

This config worked for quite a long time, but since I updatet the game some weeks ago, I always get the message of the mismatch.

Have you yet tried to force a update with the Validation Installation (please don't forget to unset it again after it finished verifying)?

 

You can also try to set up a second instance if that is working.

Yes, I set the Validate Installation to true, updatet the container and removet the variable, still doesn't work. Just set up a new container, also don't work.

 

Could there be a problem with steamcmd?

6 minutes ago, b_tob said:

Could there be a problem with steamcmd?

No.

 

22 minutes ago, b_tob said:

Ah, now I saw it... You are using the experimental client. You have to add that to the GAME_ID:

-beta experimental

 

You are on the experimental branch and therefore you have to also use the experimental branch on the server (please note that switching branches needs validation the installation once).

 

 

 

See also here: Click

Thanks, this was the solution!

I installed Wreckfest today. (for testing for a lan party) unfortunately I can't find the server in the game under LAN. I didn't change anything after the installation.

38 minutes ago, front-line-hearthstone1374 said:

I can't find the server in the game under LAN

Did you make sure that it is also reachable from outside?

 

The log is also looking good to me.

What do you mean?  The server comes onto the Internet.  Or should I set port forward.  (I'll have to see how it works first).

12 minutes ago, front-line-hearthstone1374 said:

Or should I set port forward.

Yes, you should definitely do the port forwarding.

 

My server is only visible on the LAN after I do a proper port forwading.

 

Just to be sure you changed nothing in terms of port forwarding in the template correct?

Ok thx. Is that necessary for all servers that are from STEAM.

13 minutes ago, front-line-hearthstone1374 said:

Ok thx. Is that necessary for all servers that are from STEAM.

Nope, only for a few of them. V-Rising back then was such a game but they've implemented LAN mode but you have to pass over an argument to start it in LAN mode for example. AssettoCorsa and AssettoCorsaCompetitione is online only and a few more but I don't remember all of them.

 

However most of them work fine in LAN too and sometimes need a special argument to be passed over <- but that is only necessary for a few games.

Running Project Zomboid with mods. Was having an issue when it tries to update mods:

 

Workshop: onItemNotDownloaded itemID=<workshop_id> result=2.
Workshop: item state DownloadPending -> Fail ID=<workshop_id>.

 

After some research, I figured out I needed to delete the 'appmanifest' files in the 'steamapps' folder. Instead of manually doing this every time mods update, I decided to add some code to the 'start-server.sh' script (between setting the 'INSTDIR' variable and the if-else block that starts the server) to do it automatically before the server starts:

 

# enable ** globbing in bash
shopt -s globstar

# did the last restart get borked on updates?
borked=[ $(tail -1 $INSTDIR/Zomboid/server-console.txt) =~ 'Fail ID=' ]

if [[ $borked ]]; then
  # remove/delete workshop manifest files to fix borked updates
  rm $INSTDIR/steamapps/**/appmanifest_*.acf
fi

 

Hope this helps someone with the same issue

1 hour ago, irreparable-civilization6266 said:

Hope this helps someone with the same issue

Would that maybe also work with a user.sh that is executed early in the start from the container?

Just asking because I'm not a big fan of modifying the start script because this will be discarded if you update the container or change anything in the template.

1 hour ago, ich777 said:

Would that maybe also work with a user.sh that is executed early in the start from the container?

I believe so, yes. It just needs to be ran before it tries to download workshop updates

On 9/11/2023 at 4:37 PM, SlyFox said:

Well I upgraded to 6.12.4, deleted the container and removed the folder. Fired it back up and after a long download process it does seem to do something similar and just crashes before the sever progress actually starts up. I wish there was more in the log for me to track it down but i'm not sure what is doing this? 

 

It doesn't have anything to do with the Steam API warning line does it?

"Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory"

 

Regarding the Privileged Permissions it's been removed; I was just pulling levers and agreed that Privileged permission would not be on typically but for debugging I was throwing everything at it. 

 

For CPU, i'm running: 

Intel® Xeon® CPU E5-2697 v2 @ 2.70GHz 24 Core (2 sockets but only 24C sent to this VM)

Running on a VRTX Blade Server (1 of 2) and then VMWare virtualized to UNRAID. Not running any VM's within UNRAID due to the virtualization. No GPU on this server chassis. 

I could also show my VMWare VM settings for UNRAID if anything would help allow more compatibilty?

I have all RAM Reserved for the VM (50GB)

 

Do you think it has something to do with the compatibilty of the CPU? I've had other (sparatic) Dockers not work properly/install but ~80% work fine. 

Having the same problem with Icarus. Yesterday everthing was working fine but since today it stops everytime. We change nothing. I have removed everything in appdata and the steam folder went to CA and grabbed a fresh template but with the same result. The log of the docker is the same as @SlyFox

Edited September 25, 20232 yr by Pepreal

3 minutes ago, Pepreal said:

We change nothing.

Was maybe the dedicated server updated through SteamCMD?

 

I'll just update my container real quick and let you know how my container is doing.

5 minutes ago, ich777 said:

Was maybe the dedicated server updated through SteamCMD?

 

I'll just update my container real quick and let you know how my container is doing.

Just tried it on a different Unraid server which is on a different location with a clean Icarus docker but it does exactly the same.

Edited September 25, 20232 yr by Pepreal

5 minutes ago, Pepreal said:

Just tried it on a different Unraid server which is on a different location with a clean Icarus docker but it does exactly the same.

Just working fine here:

 

What CPU/type of system are you using? Does you system support AVX?

7 minutes ago, ich777 said:

Just working fine here:

 

What CPU/type of system are you using? Does you system support AVX?

CPU is AMD R5 5600G and yes it supports AVX. We played yesterday with no problems. When start to play we start the docker and when we are done we are stopping the docker thats it. Both server doing the same thing.

 

Edited September 25, 20232 yr by Pepreal

Just now, Pepreal said:

CPU is AMD R5 5600G and yes it supports AVX. We played yesterday with no problems. When start to play we start the docker and when we are done we are stopping the docker thats it. And it both server doing the same thing.

Since when have you set up this container?

 

Have you maybe restarted the container when it still was doing stuff for the second time? The container can take a really long time (about 3-5 minutes on my i5-10600 after the initial download finished).

I assume you have enough free RAM correct?

It seems like that WINE can't start the game which most of the time happens when it is not set up correctly.

Please do the following:

1. Stop the container
2. Go into the directory for Icarus (usually in your appdata)
3. Remove the directory "WINE64" and the file "runtimes"
4. Start the container again and wait <- this could as said take some time and the log probably won't move

 

Hope that will make it work.

12 minutes ago, ich777 said:

Since when have you set up this container?

 

Have you maybe restarted the container when it still was doing stuff for the second time? The container can take a really long time (about 3-5 minutes on my i5-10600 after the initial download finished).

I assume you have enough free RAM correct?

It seems like that WINE can't start the game which most of the time happens when it is not set up correctly.

Please do the following:

1. Stop the container
2. Go into the directory for Icarus (usually in your appdata)
3. Remove the directory "WINE64" and the file "runtimes"
4. Start the container again and wait <- this could as said take some time and the log probably won't move

 

Hope that will make it work.

When the docker did not work i removed everything, the Icarus folder in the appdata folder, the steamcmd folder and the docker image, went to the appstore downloaded the latest Icarus template, started the docker waited for long time and when it was finished it started to restart constantly. and my screenshot from above is al what its doing. So this is a clean docker, appdata folder and steamcmd folder. Sorry English is not my main language.

Edited September 25, 20232 yr by Pepreal