[thederpysage]

I'm trying to setup a docker deployment that includes plugins that rely on TF2Items. However, it seems that TF2Items is causing crashing in the environment that I've been using.

Using this base image, and then adding a few things that shouldn't to my knowledge interact at all with TF2Items and TF2Items latest version, I've been getting a pretty persistent crash.

I installed Accelerator to figure out what the root cause is, but I'm still not quite able to make sense of it.
https://crash.limetech.org/fxpi7dqqt43k

I am unable to replicate this issue on Windows, and others don't seem to be reporting this problem so it may very well have something to do with the base deployment.

Any help would be appreciated.

[asherkin]

You appear to have logging off on the server so it can't be seen from the crash dump, but check what TF2Items prints that it is using for the GiveNamedItem offset on startup.

Your Docker volume configuration isn't correct though, addons/sourcemod/data/ and addons/sourcemod/gamedata/ should be persistent - I suspect the latter is the problem and you're throwing away auto-updated SM / TF2Items gamedata (a new TF2Items snapshot hasn't been built in many years).

[thederpysage]

Originally Posted by asherkin You appear to have logging off on the server so it can't be seen from the crash dump, but check what TF2Items prints that it is using for the GiveNamedItem offset on startup. Your Docker volume configuration isn't correct though, addons/sourcemod/data/ and addons/sourcemod/gamedata/ should be persistent - I suspect the latter is the problem and you're throwing away auto-updated SM / TF2Items gamedata (a new TF2Items snapshot hasn't been built in many years).

I rewrote the dockerfile to make those folders persistent.

There was some point in my testing that it was showing me the offset, but at this point it is not and will still crash when I try to join.

I tried to enable Logging but my dumps still look *generally* the same...
https://crash.limetech.org/bth3twwviby7

Update: I have some other ideas so I will continue to tinker and report back...

[thederpysage]

Originally Posted by thederpysage I rewrote the dockerfile to make those folders persistent. There was some point in my testing that it was showing me the offset, but at this point it is not and will still crash when I try to join. I tried to enable Logging but my dumps still look *generally* the same... https://crash.limetech.org/bth3twwviby7 Update: I have some other ideas so I will continue to tinker and report back...

Ok, I've ACTUALLY resolved Volume issues and any potential permissions issued within those folders, and I'm still getting the crash on user join.

Funnily enough, now that I've verified logging is working and can write, it's not even writing anything to the files it makes which is troublesome.
https://crash.limetech.org/5qmwarr72iqz

I'm still not seeing it print the offset of GiveNamedItem either.

[asherkin]

It's a very strange crash, it is definitely gamedata-shaped but the stack doesn't make a lot of sense (but that is common with this sort of issue).

Could you see what you have in `addons\sourcemod\gamedata\tf2.items.txt`? And make sure you've got 1.6.4-279 installed from https://builds.limetech.io/?p=tf2items

The gamedata in the download should have 479 as the linux offset, which should then be auto-updated by SourceMod to 488 on first server start.

[thederpysage]

Originally Posted by asherkin It's a very strange crash, it is definitely gamedata-shaped but the stack doesn't make a lot of sense (but that is common with this sort of issue). Could you see what you have in `addons\sourcemod\gamedata\tf2.items.txt`? And make sure you've got 1.6.4-279 installed from https://builds.limetech.io/?p=tf2items The gamedata in the download should have 479 as the linux offset, which should then be auto-updated by SourceMod to 488 on first server start.

After server start/restart tf2.items.txt offset for linux remains 479. Console logs saying the extension is loaded but it's not attempting update? I am confident I am on the 1.6.4-279 version as well.

At what point is it supposed to update? What is supposed to kick it off?

[asherkin]

updater.ext comes as part of SourceMod and checks for gamedata updates on map start. The sanest bet at this point is probably to edit the tf2items gamedata manually, but you will want to figure out why the gamedata autoupdater isn't working (do make sure you haven't turned it off if you're using a non-default core.cfg).

[thederpysage]

Originally Posted by asherkin updater.ext comes as part of SourceMod and checks for gamedata updates on map start. The sanest bet at this point is probably to edit the tf2items gamedata manually, but you will want to figure out why the gamedata autoupdater isn't working (do make sure you haven't turned it off if you're using a non-default core.cfg).

Youve been completely right all along. Somehow permissions keep getting changed on the tf2.items.txt. Could also be that the permissions are screwed up to begin with on a docker host where root is the only user. In any case, thanks for the help.

[asherkin]

No worries, glad you’ve found the problem.