Random Garry's Mod Server Crashing

[Snugzz]

I have been having an issue for the past week it will just randomly crash out of no where. No lua errors, no notification. Just crash. I have no clue what's causing it and I have tried debugging it my self and I can't figure it out. Is this a known issue for anyone else?

[Snugzz]

So I narrowed it down to it being from
STEAMAUTH FAILURE CODE 6
Any suggestions?

[kraze]

That would indicate that the client itself is dropping/crashing. Are you sure the server is crashing and not just the client?

[Snugzz]

Well I haven't had the issue any more but when it was it was happening to everyone including me and I wasn't crashing out of Garry's Mod. Just recently now the server just completely crashed no lua errors and just completely dropped connection for all of my players Twice within 10 minutes.

[Snugzz]

Anyone have any ideas? The server will just randomly crash with 5+ players and disconnect everyone for STEAMAUTH FAILURE CODE 6 but the server itself does not crash.

[kraze]

I'd recommend disabling your server addons as a test to see if that stops the server from crashing.

[Snugzz]

Kraze I've done this. I removed addons that I added before the servers started doing this, and even with as little amount of addons as needed and still the server crashes with 5+ players on.

[Snugzz]

Just a general question here, IF I were to switch over to a managed VPS, if the server does crash wouldn't NFO have to assist me in resolving the issue?

[kraze]

Kraze I've done this. I removed addons that I added before the servers started doing this, and even with as little amount of addons as needed and still the server crashes with 5+ players on.

You should disable everything, and run your server at stock so you can establish a baseline. Checking your console.log file after enabling -condebug would also be good to see if you can narrow down something specific.

[Snugzz]

You should disable everything, and run your server at stock so you can establish a baseline. Checking your console.log file after enabling -condebug would also be good to see if you can narrow down something specific.

I went ahead and switched to a managed VDS, so if it does happen, I can ask you guys for assistance

[kraze]

You should disable everything, and run your server at stock so you can establish a baseline. Checking your console.log file after enabling -condebug would also be good to see if you can narrow down something specific.

I went ahead and switched to a managed VDS, so if it does happen, I can ask you guys for assistance

Just remember we don't offer software based assistance via our help desk, so there's a good chance you'll end up back here.

[Snugzz]

Well the server is running smoothly and I have noticed any lag spikes or anything of the sorts yet soooo

[Snugzz]

Update 6/21/2016 Crashing has come to a complete stop. I figured it out to be the sv.db that was corrupted. Unfortunate though :/