DeadMeat0383 Posted July 20, 2018 Posted July 20, 2018 Brief description: DServer.exe keeps crashing Detailed description, conditions: No matter which mission is in the rotation the DServer.exe will crash for not apparent reason. Additional assets (videos, screenshots, logs): Log Name: Application Source: Application Error Date: 20/07/2018 11:38:35 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Deadserv Description: Faulting application name: DServer.exe, version: 1.0.0.1, time stamp: 0x5b4e5540 Faulting module name: DServer.exe, version: 1.0.0.1, time stamp: 0x5b4e5540 Exception code: 0xc0000005 Fault offset: 0x000000000001effe Faulting process id: 0x3c8 Faulting application start time: 0x01d4202ac3e38db2 Faulting application path: C:\IL2\bin\game\DServer.exe Faulting module path: C:\IL2\bin\game\DServer.exe Report Id: 5dde5efb-fa8b-4361-8e22-7fd33e432264 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-07-20T13:38:35.516687100Z" /> <EventRecordID>11420</EventRecordID> <Channel>Application</Channel> <Computer>Deadserv</Computer> <Security /> </System> <EventData> <Data>DServer.exe</Data> <Data>1.0.0.1</Data> <Data>5b4e5540</Data> <Data>DServer.exe</Data> <Data>1.0.0.1</Data> <Data>5b4e5540</Data> <Data>c0000005</Data> <Data>000000000001effe</Data> <Data>3c8</Data> <Data>01d4202ac3e38db2</Data> <Data>C:\IL2\bin\game\DServer.exe</Data> <Data>C:\IL2\bin\game\DServer.exe</Data> <Data>5dde5efb-fa8b-4361-8e22-7fd33e432264</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
DeadMeat0383 Posted July 20, 2018 Author Posted July 20, 2018 And the patch that just dropped (3.005b) did not fix the issue, still crashing.
TWHYata_PL Posted July 20, 2018 Posted July 20, 2018 (edited) yes the same here, 3 times in row and one 1 frezz on EU offical DED servers, chcecked also nvidia drivers and they are all up to date.. Edited July 20, 2018 by TWHYata_PL
II./JG1_Kadin Posted July 21, 2018 Posted July 21, 2018 I have started noticing it too on my Dedicated Server.
DeadMeat0383 Posted July 21, 2018 Author Posted July 21, 2018 9 minutes ago, II./JG1_Kadin said: I have started noticing it too on my Dedicated Server. Ive heard that Coconut, and Finnish are having issues, cant confirm yet though. @coconut@LLv34_Temuri
LLv34_Temuri Posted July 21, 2018 Posted July 21, 2018 Our server not running is related somehow to mission resaver, which after the hotfix still fails for some reason.
SAS_Storebror Posted July 21, 2018 Posted July 21, 2018 Confirmed from my end as well, random crashes and lots of "Unhandled SIM thread message: 60" lines on DServer since Patch 3.005b. But frankly, do you think any dev will notice this thread among all the clutter on this board? How about joining the well formatted, moderated Multiplay Bug Report Thread here instead: Cheers! Mike
DeadMeat0383 Posted July 21, 2018 Author Posted July 21, 2018 3 minutes ago, SAS_Storebror said: Confirmed from my end as well, random crashes and lots of "Unhandled SIM thread message: 60" lines on DServer since Patch 3.005b. But frankly, do you think any dev will notice this thread among all the clutter on this board? How about joining the well formatted, moderated Multiplay Bug Report Thread here instead: Cheers! Mike Not much more likely than them noticing that thread to be honest, there is a lot of noise everywhere and there are a lot of issues with the recent patch and hotfix and since multiplayer is a low priority... *shrug* for what its worth I upvoted your post.
coconut Posted July 21, 2018 Posted July 21, 2018 1 hour ago, LLv34_Temuri said: Our server not running is related somehow to mission resaver, which after the hotfix still fails for some reason. Glad to see I'm not the only one! The updater resaver doesn't work for me. It does it's job, but then DServer.exe refuses to load the msnbin file it produced. 6 hours ago, DeadMeat0383 said: Ive heard that Coconut, and Finnish are having issues, cant confirm yet though. I haven't really noticed crashes of DServer, but the good weather has kept me away from the game these two last months. Maybe it has been happening and I did not notice.
DeadMeat0383 Posted July 21, 2018 Author Posted July 21, 2018 Funny enough Resaver works for me... even if it was only this patch that I bothered to learn how to use it.
II./JG1_Kadin Posted July 21, 2018 Posted July 21, 2018 The Resaver applied again after the small patch did get the Server working for an hour or so. Unfortunately the "Unhandled SIM thread message: 60" message started again.
coconut Posted July 21, 2018 Posted July 21, 2018 6 hours ago, coconut said: I haven't really noticed crashes of DServer Strike that, now I have too. Also got the message about " Unhandled SIM thread message: 60 "
II./JG1_Kadin Posted July 21, 2018 Posted July 21, 2018 (edited) The Lapino map does NOT seem to crash. PS: Five hours and counting on lapino missions. No crash Edited July 21, 2018 by II./JG1_Kadin
DeadMeat0383 Posted July 22, 2018 Author Posted July 22, 2018 13 hours ago, II./JG1_Kadin said: The Lapino map does NOT seem to crash. PS: Five hours and counting on lapino missions. No crash I've had times where the same mission rotation will run without issues for a whole day or so, but then it will decide to crash repeately no matter what mission is running
sniperton Posted July 22, 2018 Posted July 22, 2018 Maybe it depends on user input, i.e. human player selecting a particular plane, vehicle, or weapon config (as was the case with the blister turret on the Peshka, or what has been reported for certain tanks). Perhaps you should ask players to report immediately when the server crashes upon selecting a particular something.
SAS_Storebror Posted July 22, 2018 Posted July 22, 2018 We've had two severe crashes within few minutes after DServer.exe restart yesterday, one of them without any player having been connected at all. Same mission same server after another restart now runs fine for 16.5 hours and counting. It's odd. Cheers! Mike
DeadMeat0383 Posted July 23, 2018 Author Posted July 23, 2018 Hi @Jason_Williams, Apologies for tagging you but I was hoping to get acknowledgement that this issue has been noted. Multiple server owners appear to be experiencing this issue and its getting very frustrating to have to log into my server multiple times a day to start DServer.exe back up and get the server available. Has this been put on the list of things to investigate yet? More details at this post from SAS_Storebror as well
SAS_Storebror Posted July 24, 2018 Posted July 24, 2018 I start to believe that this was a master server issue. Since 36 hours now, the same server and mission which crashed after 15 minutes before, is running smooth and fine now. At the same time, 3-4 hours ago all of a sudden the permanent log output of Unhandled SIM thread message: 60 into the DServer console stopped. Let's wait and see, and keep the fingers crossed. Mike
SAS_Storebror Posted July 24, 2018 Posted July 24, 2018 Scratch the previous post. 7 hours ago, after 39 hours of continuous operation, the random crash happened again. "Unhandled SIM thread message: 60" is back as well. Might be related. Mike
TGTucker Posted July 24, 2018 Posted July 24, 2018 Crash problem here also but only crashes in career mode during jumping to next day.
DeadMeat0383 Posted July 25, 2018 Author Posted July 25, 2018 Ive had 2 crashes in the last 24 hours, also had an odd thing happen with my missions suddenly deciding to start spawning germans underground and I had to roll back to a prior version, but im fairly sure that issue is unrelated however it did take my server offline for a few hours while I sorted the mission issue out.
SAS_Storebror Posted July 25, 2018 Posted July 25, 2018 1 hour ago, DeadMeat0383 said: Ive had 2 crashes in the last 24 hours Precisely confirmed. 2 crashes in the last 24 hours on the Flying Ass Clowns as well. Maybe we should compare times. Ours were 8:48 AM and 9:06 PM, both July 24. Mike
DeadMeat0383 Posted July 25, 2018 Author Posted July 25, 2018 13 hours ago, SAS_Storebror said: Precisely confirmed. 2 crashes in the last 24 hours on the Flying Ass Clowns as well. Maybe we should compare times. Ours were 8:48 AM and 9:06 PM, both July 24. Mike I am at work so access to the server is limited to starting it back up from crashes and installing updates, I will have a look when I get home tonight. In other news there was a patch that lists a possible fix to the random crashes, my server is updated now so it will be interesting to see if its fixed now I noted the "Unhandled sim thread message: 60" still comes up.
SAS_Storebror Posted July 26, 2018 Posted July 26, 2018 Unfortunately, 3.005c didn't change anything in terms of Server crashes for us. Let's list some crash times (all GMT), with game version numbers and uptimes (in hours): Version 3.005b: Jul 22 4:09 PM - uptime 3:32 Jul 22 4:52 PM - uptime 0:43 Jul 22 5:08 PM - uptime 0:16 Jul 22 5:25 PM - uptime 0:17 Jul 24 8:48 AM - uptime 39:23 Jul 24 9:06 PM - uptime 10:18 Jul 25 10:01 AM - uptime 12:55 - Update to Version 3.005c, Server started Jul 25 6:04 PM Jul 25 6:40 PM - uptime 0:36 Jul 25 6:48 PM - uptime 0:08 Jul 25 7:59 PM - uptime 1:11 Since then (8:11 hours now) the server is up. The logfile of 3.005c looks as cluttered with "Unhandled SIM" lines like before: ===== DeathMatch mode ===== ===== Dedicated server ===== Brief info: Max clients = 70 TCP: 1, UDP: 2, Downloader: 3, U/D Limits = 0/0 Login with UserName 'box@sas1946.com' ... Login success Server is being created ... Server name 'The Flying Ass Clowns' Loading mission 'Multiplayer/Dogfight\Mission.mission' (Multiplayer/Dogfight\Mission)... Server listener IP = '1.2.3.4' ... Mission loaded successfully Server succesfully registered on master server Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 ===== Rotation is in progress (2 seconds to wait before loading) ===== Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 ... Server name 'The Flying Ass Clowns' Loading mission 'Multiplayer/Dogfight\Mission.mission' (Multiplayer/Dogfight\Mission)... Server listener IP = '1.2.3.4' ... Mission loaded successfully ===== Rotation is in progress (2 seconds to wait before loading) ===== ... Server name 'The Flying Ass Clowns' Loading mission 'Multiplayer/Dogfight\Mission.mission' (Multiplayer/Dogfight\Mission)... Server listener IP = '1.2.3.4' ... Mission loaded successfully Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 ===== Rotation is in progress (2 seconds to wait before loading) ===== Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 Unhandled SIM thread message: 60 ... Server name 'The Flying Ass Clowns' Loading mission 'Multiplayer/Dogfight\Mission.mission' (Multiplayer/Dogfight\Mission)... Server listener IP = '1.2.3.4' ... Mission loaded successfully Mike
DeadMeat0383 Posted July 26, 2018 Author Posted July 26, 2018 (edited) And here are my logs from the most recent crash today. 22:32:56 Remote Console service started on 127.0.0.1 port 8991 22:32:56 ===== DeathMatch mode ===== 22:32:56 ===== Dedicated server ===== 22:32:56 Brief info: 22:32:56 Max clients = 85 22:32:56 TCP: 28000, UDP: 28000, Downloader: 28100, U/D Limits = 1000/1000 22:32:56 Login with UserName '' 22:33:06 ... Login success 22:33:08 Server is being created 22:33:08 ... Server name 'The Unprofessionals' 22:33:08 Loading mission 'Multiplayer/UP_Serv_Mis_03\Fall\_default\UP_Serv_Mis_03a_Fall_Default.msnbin' (Multiplayer/UP_Serv_Mis_03\Fall\_default\UP_Serv_Mis_03a_Fall_Default)... 22:33:08 Server listener IP = '192.168.1.14' 22:33:14 ... Mission loaded successfully 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Unhandled SIM thread message: 60 22:33:14 Server succesfully registered on master server 22:43:14 Unhandled SIM thread message: 60 22:43:14 Unhandled SIM thread message: 60 23:08:27 Unhandled SIM thread message: 60 23:08:27 Unhandled SIM thread message: 60 23:47:07 Unhandled SIM thread message: 60 23:47:07 Unhandled SIM thread message: 60 00:01:16 Unhandled SIM thread message: 60 00:29:59 Unhandled SIM thread message: 60 00:29:59 Unhandled SIM thread message: 60 00:29:59 Unhandled SIM thread message: 60 00:48:20 Unhandled SIM thread message: 60 00:48:20 Unhandled SIM thread message: 60 00:48:20 Unhandled SIM thread message: 60 00:48:20 Unhandled SIM thread message: 60 02:05:05 ===== Rotation is in progress (2 seconds to wait before loading) ===== 02:05:07 ... Server name 'The Unprofessionals' 02:05:07 Loading mission 'Multiplayer/UP_Serv_Mis_10\Summer\windy\UP_Serv_Mis_10_Summer_Windy.msnbin' (Multiplayer/UP_Serv_Mis_10\Summer\windy\UP_Serv_Mis_10_Summer_Windy)... 02:05:07 Server listener IP = '192.168.1.14' 02:05:14 ... Mission loaded successfully 05:37:04 ===== Rotation is in progress (2 seconds to wait before loading) ===== 05:37:06 ... Server name 'The Unprofessionals' 05:37:06 Loading mission 'Multiplayer/UP_Serv_Mis_03\Spring\dawn\UP_Serv_Mis_03a_Spring_Dawn.msnbin' (Multiplayer/UP_Serv_Mis_03\Spring\dawn\UP_Serv_Mis_03a_Spring_Dawn)... 05:37:06 Server listener IP = '192.168.1.14' 05:37:11 ... Mission loaded successfully 09:09:03 ===== Rotation is in progress (2 seconds to wait before loading) ===== 09:09:05 ... Server name 'The Unprofessionals' 09:09:05 Loading mission 'Multiplayer/UP_Serv_Mis_10\Winter\windy\UP_Serv_Mis_10_Summer_Windy.msnbin' (Multiplayer/UP_Serv_Mis_10\Winter\windy\UP_Serv_Mis_10_Summer_Windy)... 09:09:05 Server listener IP = '192.168.1.14' 09:09:11 ... Mission loaded successfully Edited July 26, 2018 by DeadMeat0383
SAS_Storebror Posted July 27, 2018 Posted July 27, 2018 Last night's crashes: Jul 26 10:05 PM - uptime 26:06 Jul 26 10:07 PM - uptime 0:02 (!!!) Jul 26 10:11 PM - uptime 0:04 (!!!) Since then (6:02 hours now) the server is up. Clearly something's happening that is outside of the local server's property. Mike
DeadMeat0383 Posted July 27, 2018 Author Posted July 27, 2018 Ive no idea, had another crash overnight last night, not sure how long it was up this time, I just started it again when people pointed out it was down.
SAS_Storebror Posted July 27, 2018 Posted July 27, 2018 I mean if it was something happening locally, there would have to be some kind of golden thread of all those crashes, but so far I fail to see any. The mission we're running is always the same, whether the server runs stable for 40 hours or crashes within 2 minutes, it's the same mission, so the mission to me is out of suspicion. It's not server load either. I've been monitoring this and the crashes happen at any load state, like e.g. when there are 30 players online and the process consumes 60-70% of a single core's CPU power, with a tick delay of 10~15, as well as when no one is online at all, tick delay is 0.1 and CPU load is <2%. So the Server load is out of suspicion too. If it was anything happening on the server in parallel, it would have been visible in the Event logs, but there's nothing going on at the times when DServer crashes. Anything going on locally on the server is apparently not affecting the DServer reliability, which to me means that it's something happening on the other end of the DServer <-> Master Server connection. Mike
SAS_Storebror Posted July 28, 2018 Posted July 28, 2018 Just for the record: No crashes last night, Server is up and running since 33 hours now (and was quite crowded in the meantime). Mike
coconut Posted July 28, 2018 Posted July 28, 2018 (edited) I've had crashes last night, so no, I don't think it's fixed. I have two servers running, one expert, one normal. Both run the same dynamic campaign system. Normal has been stable, Expert hasn't. Expert typically has more population, but I don't know if it matters. Both run pretty heavy missions, 4MB msnbin files, can be 8ms tick delay without players on. Also the details of the crashes I've seen point at a dangling/corrupted pointer kind of error. That should never happen in a bug-free program, so even if the master server was involved in the crash, all it should do, at worst, is cause the program to emir error messages, not crash. A crash is always a bug in itself, even if it is the environment/user that triggers it. Edited July 28, 2018 by coconut
DeadMeat0383 Posted July 28, 2018 Author Posted July 28, 2018 Unfortunately ive not been able to closely monitor my server as ive been away from my computer due to life, ive just been restarting the server as soon as I notice it having crashed. ive not had it go a full 24 hours without crashing though?
SAS_Storebror Posted July 29, 2018 Posted July 29, 2018 Sorry if my previous post reads like I'd think the issue was fixed. Of course it's not. I also agree that the "crash to desktop" is a program issue, however what triggers this issue doesn't seem to be related to anything happening locally on the server itself. Current status update is that our server ditched again yesterday: Jul 28 4:45 PM - uptime 42:34 Mike
SAS_Storebror Posted July 31, 2018 Posted July 31, 2018 Just for the record, the server is still up with no crash since Jul 28. Uptime right now is 71 hours. Mike
DeadMeat0383 Posted August 1, 2018 Author Posted August 1, 2018 14 hours ago, SAS_Storebror said: Just for the record, the server is still up with no crash since Jul 28. Uptime right now is 71 hours. Mike mine has crashed 4 times in the last 24 hours
SAS_Storebror Posted August 1, 2018 Posted August 1, 2018 We've had our next crash, too: Jul 31 9:14 PM - uptime 76:29 hours It's just random. One feeling I get when looking at the list of available dogfight servers is that the more AI you have on your missions, the more you suffer from this issue. Just a feeling, no hard facts. Mike
sniperton Posted August 1, 2018 Posted August 1, 2018 2 hours ago, SAS_Storebror said: We've had our next crash, too: Jul 31 9:14 PM - uptime 76:29 hours Was it a server crash? I believed it was a disconnection issue, since I had the usual #10009 "Game server connection lost" error message
II./JG1_Kadin Posted August 1, 2018 Posted August 1, 2018 (edited) Any more information on "Unhandled SIM thread message: 60". What is it related to? I have missions that do not have that message and missions that do. It is not map related. Most likely is mission content related but I have not narrow it down yet. Edited August 1, 2018 by II./JG1_Kadin
SAS_Storebror Posted August 1, 2018 Posted August 1, 2018 No Information available. This is a sad example of complete absence of customer care. I mean we server operators are not supposed to be the dumbest people on earth, therefore we could be valuable assets in tracking this bug down. But instead we're left here with nothing, no information, not even a confirmation of this issue. It simply cannot be our task to narrow down the issue, especially when we're being ignored like that. Mike 3
THERION Posted August 1, 2018 Posted August 1, 2018 Yes, and thinking of it - you provide those servers for public purpose with no fee of charge for the community. This flight sim also depends on the positive feedback of the hardcore multi players who don't really care about single player mode nor the campaign system. Not very grateful form them...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now