Standalone server crash

Question

Hello, our game's server has been running fine for months, but recently it crashed. Below is the crash report from output_log. There doesn't seem to be any useful information, but perhaps I'm missing something?

What can be done to debug this crash it it happens again?

I am using Unity 3.5 and running on Windows Server 2008 R2

 Crash!!!
 SymInit: Symbol-SearchPath: '.;C:\Users\Administrator\Desktop\SideQuest Server;C:\Users\Administrator\Desktop\SideQuest Server\Release;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Administrator'
 OS-Version: 6.1.7601 (Service Pack 1) 0x510-0x3
 Crash in winutils::ProcessInternalCrash(PEXCEPTION_POINTERS pExInfo)C:\Users\Administrator\Desktop\SideQuest Server\Release\Server.exe:Server.exe (00400000), size: 9973760 (result: 0), SymType: 'PDB', PDB: 'C:\Users\Administrator\Desktop\SideQuest Server\Release\Server.exe', fileVersion: 3.5.7.45015
 C:\Windows\SysWOW64\ntdll.dll:ntdll.dll (779A0000), size: 1572864 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\SysWOW64\ntdll.dll', fileVersion: 6.1.7601.17725
 C:\Windows\syswow64\kernel32.dll:kernel32.dll (753E0000), size: 1114112 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\kernel32.dll', fileVersion: 6.1.7601.17651
 C:\Windows\syswow64\KERNELBASE.dll:KERNELBASE.dll (750E0000), size: 286720 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\KERNELBASE.dll', fileVersion: 6.1.7601.17651
 C:\Windows\syswow64\USER32.dll:USER32.dll (754F0000), size: 1048576 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\USER32.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\GDI32.dll:GDI32.dll (75BA0000), size: 589824 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\GDI32.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\LPK.dll:LPK.dll (753D0000), size: 40960 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\LPK.dll', fileVersion: 6.1.7600.16385
 C:\Windows\syswow64\USP10.dll:USP10.dll (77040000), size: 643072 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\USP10.dll', fileVersion: 1.626.7601.17514
 C:\Windows\syswow64\msvcrt.dll:msvcrt.dll (75AF0000), size: 704512 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\msvcrt.dll', fileVersion: 7.0.7601.17744
 C:\Windows\syswow64\ADVAPI32.dll:ADVAPI32.dll (76D70000), size: 655360 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\ADVAPI32.dll', fileVersion: 6.1.7601.17514
 C:\Windows\SysWOW64\sechost.dll:sechost.dll (76E10000), size: 102400 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\SysWOW64\sechost.dll', fileVersion: 6.1.7600.16385
 C:\Windows\syswow64\RPCRT4.dll:RPCRT4.dll (75130000), size: 983040 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\RPCRT4.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\SspiCli.dll:SspiCli.dll (75080000), size: 393216 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\SspiCli.dll', fileVersion: 6.1.7601.17725
 C:\Windows\syswow64\CRYPTBASE.dll:CRYPTBASE.dll (75070000), size: 49152 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\CRYPTBASE.dll', fileVersion: 6.1.7600.16385
 C:\Windows\syswow64\SHELL32.dll:SHELL32.dll (75FD0000), size: 12886016 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\SHELL32.dll', fileVersion: 6.1.7601.17755
 C:\Windows\syswow64\SHLWAPI.dll:SHLWAPI.dll (75DE0000), size: 356352 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\SHLWAPI.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\ole32.dll:ole32.dll (75E40000), size: 1425408 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\ole32.dll', fileVersion: 6.1.7601.17514
 C:\Windows\system32\VERSION.dll:VERSION.dll (74F80000), size: 36864 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\VERSION.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\OPENGL32.dll:OPENGL32.dll (748C0000), size: 819200 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\OPENGL32.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\GLU32.dll:GLU32.dll (74AD0000), size: 139264 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\GLU32.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\DDRAW.dll:DDRAW.dll (6CE50000), size: 946176 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\DDRAW.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\DCIMAN32.dll:DCIMAN32.dll (74A50000), size: 24576 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\DCIMAN32.dll', fileVersion: 6.1.7600.16385
 C:\Windows\syswow64\SETUPAPI.dll:SETUPAPI.dll (76EA0000), size: 1691648 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\SETUPAPI.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\CFGMGR32.dll:CFGMGR32.dll (76C20000), size: 159744 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\CFGMGR32.dll', fileVersion: 6.1.7601.17621
 C:\Windows\syswow64\OLEAUT32.dll:OLEAUT32.dll (75220000), size: 585728 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\OLEAUT32.dll', fileVersion: 6.1.7601.17676
 C:\Windows\syswow64\DEVOBJ.dll:DEVOBJ.dll (76E80000), size: 73728 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\DEVOBJ.dll', fileVersion: 6.1.7601.17621
 C:\Windows\system32\dwmapi.dll:dwmapi.dll (74AA0000), size: 77824 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\dwmapi.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\WINMM.dll:WINMM.dll (74860000), size: 204800 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\WINMM.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\WS2_32.dll:WS2_32.dll (75390000), size: 217088 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\WS2_32.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\NSI.dll:NSI.dll (75920000), size: 24576 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\NSI.dll', fileVersion: 6.1.7600.16385
 C:\Windows\syswow64\IMM32.dll:IMM32.dll (75330000), size: 393216 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\IMM32.dll', fileVersion: 6.1.7601.17514
 C:\Windows\syswow64\MSCTF.dll:MSCTF.dll (757C0000), size: 835584 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\MSCTF.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\DNSAPI.dll:DNSAPI.dll (74C90000), size: 278528 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\DNSAPI.dll', fileVersion: 6.1.7601.17570
 C:\Windows\system32\IPHLPAPI.DLL:IPHLPAPI.DLL (74F60000), size: 114688 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\IPHLPAPI.DLL', fileVersion: 6.1.7601.17514
 C:\Windows\system32\WINNSI.DLL:WINNSI.DLL (74F50000), size: 28672 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\WINNSI.DLL', fileVersion: 6.1.7600.16385
 C:\Windows\system32\HID.DLL:HID.DLL (74AC0000), size: 36864 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\HID.DLL', fileVersion: 6.1.7600.16385
 C:\Windows\system32\WSOCK32.dll:WSOCK32.dll (74FB0000), size: 28672 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\WSOCK32.dll', fileVersion: 6.1.7600.16385
 C:\Windows\system32\MSACM32.dll:MSACM32.dll (74A30000), size: 81920 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\system32\MSACM32.dll', fileVersion: 6.1.7600.16385
 C:\Users\Administrator\Desktop\SideQuest Server\Release\Server_Data\Mono\mono.dll:mono.dll (10000000), size: 2207744 (result: 0), SymType: '-exported-', PDB: 'C:\Users\Administrator\Desktop\SideQuest Server\Release\Server_Data\Mono\mono.dll'
 C:\Windows\syswow64\PSAPI.DLL:PSAPI.DLL (77970000), size: 20480 (result: 0), SymType: '-exported-', PDB: 'C:\Windows\syswow64\PSAPI.DLL', fileVersion: 6.1.7600.16385
 C:\Windows\system32\MSWSOCK.dll:MSWSOCK

Answer 1

Answer by Cynikal · Apr 05, 2014 at 10:52 PM

It could've been just a general fault.

Easiest solution would be to create a "watch dog" app on the same server.

What watchdog is, it looks for your server... Makes sure it's still responding... If NOT, it'll terminate the current process (if it's still running) and then restart it.

If it's not responding, you should add somewhat of a timeout, because there might be a chance that it might of hiccuped.

You could even probably have it do a fake login into your game, to say "Hi!" and if it gets the response back of "Hello!" then you know it's functioning.

Watchdog apps are fairly common in servers that run mandatory software. Just because your server program's code is flawless, doesn't mean that the operating system is.

I would personally have my watchdog app, reboot the system, then on system load, reload the server app.

That would prevent any future OS issues if there were any still present.

Add comment · Show 1 · Share

Simon-O · Sep 17, 2015 at 10:24 PM 0

Share

Having a watchdog process is not a bad idea, but if there's a known issue, a watchdog will only mitigate the symptoms, it does nothing to prevent the intermittent downtime. The real answer here is to understand the cause and fix/work around it

Standalone server crash

1 Reply

Your answer

Follow this Question

Related Questions