Hello, I require some help with my TTT server, I'm relatively new to server hosting and LUA so please be patient with me.
Anyway to the point, since the creation of my server it sometimes crashes at round intervals. The time difference varies, it can last 5 days without crashing or can crash twice a day. I've been doing some fishing online and can't find anyone having the same relative issue, I've tried using entity catchers as that could be a cause but to no avail. There are a few bits and pieces popping up in the crash log that I'm not sure what they are, such as :
CreateFragmentsFromFile: 'user_custom/7e/7e68acce.dat' doesn't exist (the filepath is never the same)
Changing collision rules within a callback is likely to cause crashes! (Usually gets spammed a few times but then stops)
DeactivateItemHooks: DeactivateItemHooks table: 0xeb203e70 (The table is never the same)
I currently run a server with GMC Hosting, 32 player slots and 24/7 minecraft_b5.
I can provide a list of addons that are currently being used etc if asked. Also there is nothing appearing in the crash log at the end hinting to why it's crashing the last thing that appears is : ServerLog: Round ended.
ServerLog: Result: traitors win (sometimes innocents win)
Any help contributed is much appreciated.
-feen
bump
You say it can last five days without crashing. Do you mean without a restart? the Source engine usually becomes unstable after a day or so, I would recommend restarting perhaps every 12 hours if not more to keep performance persistent.
I will assume that's not what you meant though.
One thing that is known to cause crashes on TTT (atleast was 2 years ago) is ragdoll physics. Especially on some maps, ragdolls will get stuck and glitch out to the point of crashing. I found a workaround for this when I used to run a TTT server a while back, not sure where though.
Through a quick google search I found this GitHub it tackles the issue I mentioned and removes the ragdolls before they spazz out completely.
I hope this helped, good luck
Yeah the server restarts everyday at 4AM.
Already have that installed on my server but it hasn't worked, thanks for the help though!
Maybe try tinkering with the settings on the addon? you can make it more aggresive i.e removes the ragdolls quicker. Other than that I'm not sure, once a day or every 4 days doesn't sound bad though, as long as you have a decently smart server host it should automatically get up and running again on its own
I shall try that, the server restarts fine which is great but just don't want to loose my playerbase.
I've made it higher and lower but it's still crashing, if anyone else has any input would be appreciated!
It's the middle message you posted, it's pretty self explanatory but hard to find since some functions change collision rules internally.
Ragdoll crashing can also be the cause, but the addon you got seems to fix that.
Thanks a lot I will start looking! Also I was browsing relative discussions and came across this
Server freezes / "Changing collision rules within a callback is ..
They talk about infinite loops possibly causing the freezing/crashing could this be the cause instead?
Custom playermodels from the workshop can crash servers if they are poorly setup. If you want to test if its a custom playermodel you can remove all of them from the server and see how long you stay up for
If its an infinite loop and you don't know which loop is causing it then go into your addons and search for every while loop and add some indicator that you're entering the loop such as print("entering while loop @ sv_coolstuff.lua 422"). Then when you crash you can just check your console log to see if it stopped on a loop
If its an item that is causing the server to crash you can add a script that prints every item when its created & removed and checking the final prints in the console to see if its a certain item. You would have to make some sort of whitelist though so your console isn't constantly spammed. In my experience this helped me find that a rope constraint was crashing my server randomly
If it is the entity changing collision rules then its difficult if you don't know what you're looking for but generally in my experience the entities had this function ENTITY/PhysicsCollide and the reason why it got called was because I was trying to remove the entity after it hit something. If you put it in a timer and wait a frame then it should be fine. Personally I don't think I have ever crashed from that though but its always best to fix those errors
Sorry, you need to Log In to post a reply to this thread.
