Site Crash 7/20

[dranks_game]

2 minutes before midnight my server crashed with a tournament and cash games progress. Seemed like a deadlock. No one could take action on any table, attempts to refresh stalled on loading, but inbound/outbound looked fine. Stopping and starting the service allowed us to connect again.

[Kent Briggs]

What is "7/20"? If you meant version 7.20 then patch up to the latest version. It has a "Debug" button in the PM Service Manager that should be pressed in the event of a lockup (before you attempt to restart the software). That will create a stack trace of running/frozen threads that you can send me.

[dranks_game]

Apologies, 7/20 was the date of the crash - just before midnight. I am fairly certain I stopped and restarted the service last night, so my guess is getting the debug file now is of no value? Is there anything else I can provide that would shed light on the details of what happened?

[Kent Briggs]

You're reporting a July 20 crash in November?

[dranks_game]

I wish I could change the title. i have no idea why I added the wrong date. It was late at night and I made a mistake.

The issue occurred 2 minutes before midnight last night. There was a tournament and two tables in progress. Only other thing of note is that I see a lot more "rogue connection detected" entries in the log. IS there anything else that I could provide that would be helpful? Or do I just need to scrap this because I didn't execute the debug in the right order?

[Kent Briggs]

The rogue connections are likely just bots roaming random IP addresses. My logs are also full of them. You can turn that off in the log settings if you don't want to see them. But yes, the Debug function is only useful right after a crash and before you shut it down or restart it. It will show me where every thread has stopped in a deadlock situation and hopefully offer a clue as to the cause. Make sure you are patched up to the latest version because recent updates have fixed many potential deadlock situations.