I'm stumped here; hopefully someone can chime in (at least to verify that it's not just an issue on my particular setup, because the other TF2 servers I manage are running Ubuntu
18.04 16.04).
I updated my Debian instance from Stretch to Buster yesterday, and since then, at a worst case frequency of 15~20 minutes (the time between level changes -- the server has bots running 24/7), the server segfaults with a
SEGV_MAPERR on
this line. The error indicates an attempt to access unmapped memory.
Didn't expect a Debian upgrade to hose my setup in this way, haha.
No changes to the TF2 server install were made for me to feasibly bisect against, and to my knowledge the code triggering this fault doesn't have external dependencies. The stack trace doesn't provide any good information for me to work with, either; it doesn't look like a forward based on a hook.
Here are a few accelerator links: [
1] [
2] [
3] [
4] [
5] [
6]
Other information:
- meta: 1.10.7-dev:963:20c72b5, sm: 1.9.0.6281
- Server is a KVM VPS
- Kernel is 4.19 (also tested with 4.9 to no success)
I'll probably spin up a VM and try to get it reproducible, but otherwise suggestions short of rolling back and nuking the entire system are welcome (though I do have configuration backups to get things up and running again if it comes down to it).
----
Edit: Alright, so I've discovered that at least one of the causes on an empty server is map voting (with NativeVotes' mapchooser replacement). The server instantly segfaults with a forced invocation of
sm_mapvote. Odd, but I suppose I can switch that off for the time being while I isolate what's causing issues with it.
I'm still not sure why that would be an issue, and this solution isn't quite satisfactory, so I don't consider this completely solved (but marked as such since the culprit is known). Hopefully I don't have any other things throwing up segfaults.
Threaded Mode