dlchamp

Yes. VALIDATE is empty. I restart after making any changes. To reiterate my findings: If I leave password, admin password, and do not pass maxplayers param, then the container is rebuilt (after changing config) or restarted, the password, adminpassword, and maxplayers values in GameUserSettings.ini are defaulted to blank and 70 respectively. So, what I have opted to do is set the passwords in the container config, and pass the MaxPlayers param in the container config, then leave server name and the rest of my configurations in GameUserSettings.ini and Game.ini and they do not appear to be overwritten on container restart. So, it's working now. Leaving the passwords values empty seemed to be the culprit. Set those in the container config and my .ini files are untouched.

I'm talking about survival evolved. Setting the password and admin password via the container variables seems to prevent the overwrite. Adding the `?MaxPlayers` param under GAME PARAMS seems to prevent that from overwriting as well. SERVER_NAME is never touched, so I was able to leave that configured only in the .ini and the rest of the configuration appears to persist through restarts.

Having the same issues as this user: And tried with validate set to true and left empty, per here: It seems that all [ServerSettings] are defaulted any time the container is restarted. Also, defaults MaxPlayers=70 under [/Script/Engine.GameSession] unless I specify the `?MaxPlayers=X` parameter. [MessageOfTheDay] and [SessionSettings], and the other sections appear untouched as my session name, duration, and message persist through container restarts. I've left the variables blank as I wanted to configure them in GameUserSettings.ini On Unraid 6.12.6 and using the latest from `ich777/steamcmd:arkse`

The number of running containers hasn't changed for me. After I commented last night I increased the max PTY that could be allocated (from 4096 to 8192) sysctl -w kernel.pty.max=8192 This worked for my specific issue, but I don't deem that a proper fix since in reality unused PTY should be closed properly. Hopefully someone smarter can explain why this is happening, but at least there are a couple temporary solutions. I also restarted this morning after my usual backup routine was finished which hopefully just cleared up whatever funky was happening under the hood. Now to figure out why Grafana-Unraid-Stack is crashing no matter what I've done.

Sorry I'm not commenting with any solution, but I'm also having a similar issue that has appeared to come from nowhere. Can't access "console" or exec into any running container. Also, my GUS container that just updated will not start. Been on 6.11.5 for a bit now. Just over 25 days without issues. Today, an issue and nothing has changed. Server has been online since the reboot for the update. docker.img shows 50% used on "Main". `OCI runtime exec failed: exec failed: unable to start container process: open /dev/ptmx: no space left on device: unknown`

I'm at a loss as well. Many containers have been set up over the years, some of your other game servers as well, but none have given me as much trouble. 🤷‍♂️ Thanks for your time.

I did. No change.

Right. I checked by cd'ing into `cache/appdata/...` and `user/appdata/...` from CLI. Accessed with nano and config file was matching what I had in notepad ++. It could be cached on the client 🤷‍♂️ Have any idea how I could clear that cache? Restarting the game and refreshing the server list didn't work. clearing cache in documents/ didn't help.

It's only in one place, on the cache drive.

Closed the game. Stopped the server. Made changes to the template Added the description (only had the lobby name changed before) Saved Started the container. Loaded up the game and went to Convoys. "Docker Server" still appears in the list and I can connect to it

appdata is set to "prefer cache" and the template shows `/mnt/user/appdata/...

Using notepad++ But I've had an interesting change.. Deleted all appdata and restarted the container so it could completely rebuild again. Saw the "Docker Server" appear in the list and connected to it. Opened the config file and edited the name and desc. Restarted the container. Server now appears and I can connect to it, however it's still showing as "Docker Server" with the default desc.

I didn't try to connect but it appears in the convoy list when I don't change anything. As soon as I change one line in the config file and restart, no dice.

Same issue. I left the password even defaulted to "docker" Opened the created config file and only changed the name and desc. Same issues.

I tried it without any moderators set. I left all it all default and only changed name and desc.

SiiNunit { server_config : _nameless.366.dda0 { lobby_name: "NI Truck Stop" description: "Clean and Clear to Flag Town" welcome_message: "Looks like we have ourselves a little convoy" password: docker max_players: 8 max_vehicles_total: 100 max_ai_vehicles_player: 50 max_ai_vehicles_player_spawn: 50 connection_virtual_port: 100 query_virtual_port: 101 connection_dedicated_port: 27015 query_dedicated_port: 27016 server_logon_token: "" player_damage: true traffic: true hide_in_company: false hide_colliding: true force_speed_limiter: false mods_optioning: false timezones: 0 service_no_collision: false in_menu_ghosting: false name_tags: true friends_only: false show_server: true moderator_list: 0 } }

I didn't change anything in the template. Only the config file. If I don't change anything, it starts up fine and appears in the convoy list. I changed the name, description, changed the password, and added my steam token, and my steam ID as a moderator. Once I do that and restart it stops at the `Setting breakpad...` part and the server does not appear in the convoy list.

Finally got around to updating my server to 6.11.5 and gave this another shot. Same issues as before, unfortunately. If I change anything in the config file it just stops at Setting breakpad minidump AppID = 270880 and the server does not appear in the convoy list when searching by the name I provided in the config.

Why would my unraid version have anything to do with changing text from one thing to something else?

Unraid 6.9.2 I have also tried changing one at a time. Changed only the lobby name. Same results. Cleared and tried only adding my steam token, same result. I tried for each setting that I was wanting to change, one at a time, and that's how it ends every time I restart

Attaching screenshots. One is a clean install of the image and fresh start of the container. This is what it looks like at the end. Some [MP] info and a session search ID. I can then use that ID to search and find the server in the convoy list. If I go into `.local/share/American Truck Simulator` and edit the `server_config.ssi` where I'm changing the lobby name, description, welcome message, adding my steam token, and a mod list, when I restart, log looks way different and simply stops at `Setting breakpad minidump AppID = 270880` If this is normal, that's fine. Just curious as to why the server doesn't appear in the convoy list by name and after I make the changes and restart, I'm not given a Session ID at least, because I could at least find it by that before.

But it is different if I make zero changes compared to after I make changes? Server doesn't appear in the convoy list and I don't have a session ID to search with, unlike if I just start the container the first time without making any changes

Having an issue with American Truck Simulator. When I first download from Community apps and it runs, it works perfectly fine. Gets all the way to the `Session automated Start` panel with some info and the session search ID. If I try to edit the server_config.sii in any way (change title, description, welcome message, or include my login token string) when it restarts it simply just gets stuck at "Setting breakpad minidump AppID = 270880" and never gets passed that. I even just tried to change one of those options at a time, starting with the title. Restart the container, same issue.

I sure hope so.

I was using wireguard with PIA, but as of yesterday morning it's not working.