[REPORTED] Server Crashes Merged

[Cougar]

I've gone through my bantables as well as the log from the crash last night and none of the guys who were in the mission at that time were on my bantables. I'm using SLMOD mind you- not servman.

 

I haven't seen anything from speed on the matter but he's been pretty busy lately so I wonder if he's in the weeds right now?

 

Well it was worth a shot...ill look at the missions in a few....to find that bugger gotta clear the path till we reach them ;).

[ENO]

Wonder if the lock civ traffic/ lock scenes issue from 7570 is still around.

[159th_Falcon]

Just for info, this is the Servman bantable format.

 

    }, 
   [26] = { 
       comment = "",
       active = ,
       ucid = "",
       ipaddrs = "",
       names = ""
   }, 

Comment is just for administration so we can see later who band the person

Active is if the ban is active or not, can be set true or false

ucid = is a unique code for all players generated by DCS World, this is used to enforce the ban

ipaddrs is also used to enforce the ban

names is the name (or names if more then one) that this user used, names are not used for enforcement of kicks/bans

 

Not quite sure how the kicks work though.

Ill go ahead and discuss whit the squad if we want to run our server completely vanilla for testing.

 

Ill also ask if its ok to give one of the ED testers remote acces trough TeamViewer if that helps.

 

 

***EDIT***

Ok everyone, found another source of potential usefull information;

In start menu type Event Viewer

In event viewer go to, windows logs\applications

look for mainly the application errors. (red symbol whit white exclamation mark in it)

 

This lists some different crash causes then the .crash files in the dcs log like;

Faulting application name: DCS.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: AsyncNet.dll, version: 1.2.6.17746, time stamp: 0x5225b96a
Exception code: 0xc0000005
Fault offset: 0x000000000001f57b
Faulting process id: 0xe44
Faulting application start time: 0x01cea99d91a2133d
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\AsyncNet.dll
Report Id: cfe161c9-1593-11e3-9cd1-001f16fbb7c5

Faulting application name: dcs.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: AsyncNet.dll, version: 1.2.6.17746, time stamp: 0x5225b96a
Exception code: 0xc0000005
Fault offset: 0x000000000001f57b
Faulting process id: 0xdd8
Faulting application start time: 0x01cea9b4f546360b
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\dcs.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\AsyncNet.dll
Report Id: 936ba463-15b2-11e3-9cd1-001f16fbb7c5

Faulting application name: dcs.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: a10_protect.dll, version: 5.70.46.4, time stamp: 0x5225b4e6
Exception code: 0x40000015
Fault offset: 0x000000000002e2ee
Faulting process id: 0xb6c
Faulting application start time: 0x01cea9ced4d835b5
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\dcs.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\mods\aircrafts\A-10C\bin\a10_protect.dll
Report Id: b5a3b1c2-1616-11e3-9cd1-001f16fbb7c5

Faulting application name: DCS.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: edCore.dll, version: 1.2.6.17746, time stamp: 0x521633e0
Exception code: 0xc0000005
Fault offset: 0x0000000000001570
Faulting process id: 0x588
Faulting application start time: 0x01ceaa23dd7b7fcb
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\edCore.dll
Report Id: 893b894a-162f-11e3-9cd1-001f16fbb7c5

Faulting application name: DCS.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: a10_protect.dll, version: 5.70.46.4, time stamp: 0x5225b4e6
Exception code: 0x40000015
Fault offset: 0x000000000002e2ee
Faulting process id: 0xfb4
Faulting application start time: 0x01ceaa414c21a422
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\mods\aircrafts\A-10C\bin\a10_protect.dll
Report Id: abf3d70f-167a-11e3-9cd1-001f16fbb7c5

Faulting application name: DCS.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: ZweiBlau.dll, version: 1.2.6.17746, time stamp: 0x520e4b0b
Exception code: 0xc0000005
Fault offset: 0x0000000000030005
Faulting process id: 0xfb4
Faulting application start time: 0x01ceaa414c21a422
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\ZweiBlau.dll
Report Id: b81b700f-167a-11e3-9cd1-001f16fbb7c5

You can easily save the logs by selecting them, (can select multiple at once), right click and then Save Selected Events

 

Then put it in a .rar or .zip file and attach to your post

 

to view them in event viewer open it, and on the RH side select "open Saved Log"

 

more logs attached to this post as eventviewer files.

 

So some more .dll files causing issues are;

edCore.dll

a10_protect.dll

AsyncNet.dll

eventviewer1.rar

Edited September 6, 2013 by 159th_Falcon

[Pman]

Interesting Falcon,

 

The name is also used as a ban link as well, the player name. I have had to be careful with that in the past.

 

I can grab some event logs from our server as well when I am back from Duxford

 

Side note the server crashed even without the banlist, I will leave it off for now and see how it goes, but I am not sure its the root of all the issues although it may not be helping

[ENO]

Good find- I've added both files associated with the two crashes I've had to the attached.

 

We had another crash last night... tacview, logs, as well as some slmod information is included with the mission.

 

Faulting application name: DCS.exe, version: 1.2.6.17746, time stamp: 0x5225b96f

Faulting module name: edCore.dll, version: 1.2.6.17746, time stamp: 0x521633e0

Exception code: 0xc0000005

Fault offset: 0x0000000000001570

Faulting process id: 0xd68

Faulting application start time: 0x01ceaa73481f36da

Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe

Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\edCore.dll

Report Id: 840b1ed4-16a5-11e3-a884-00038a000015

crash 09.06.13.zip

Edited September 6, 2013 by ENO

[NineLine]

Thanks for all your work guys, we have a MP testing session tomorrow, I am hopeful we can crash our server as well... if you know what I mean :)

[159th_Falcon]

Is that a cryptic way of saying you have a couple of likely culprits that you expect to cause the majority of the crashes?:music_whistling:

 

And please try to let us know how it went, keeping NDA in mind ofcourse.

[NineLine]

Is that a cryptic way of saying you have a couple of likely culprits that you expect to cause the majority of the crashes?:music_whistling:

 

No, but we are laying on the floor throwing a fit, hoping someone takes notice if that helps :)

[Wrecking Crew]

v126

Hollo Pointe server had a DCS Stopped Working message this afternoon, Friday Sep 6 2013.

 

Logs are attached.

 

WC

[sorcer3r]

Thanks for all your work guys, we have a MP testing session tomorrow, I am hopeful we can crash our server as well... if you know what I mean :)

 

Good luck! ;)

 

Will the server run with render3d=false? I think all of our dedicated server here are running without rendering.

[Cougar]

Here is the latest VA mission with the racetrack on it

 

As for updating servman it has been added to up until end of June. But nothing since then as there are no viable alternatives.

 

If we cant use Servman and there is no dedicated programme then I will close the Virtual Aerobatics Server as there is no alternative

 

Pman

 

edit: only other thing on there is some anti weapons code to prevent weapons fire. Afaik that code is unique to the VA server, so if it was just me crashing fair enough but with all of us doing it I doubt its that

 

I'm not at home but using your mission with only dcs world and spawning in any aircraft that are air starting, once they getvthe flare start going , I get a mission script error so maybe its the cause if someone don't own any modules and try to play other aircraft.

 

Have a try with someone who just have dsc world and see if it crash the server

[ENO]

Still not having the number of crashes that I may have expected given the circumstances.

 

A couple other recommendations:

 

Anyone using MIST should update to 3.1

 

MAKE SURE that ANY mission on the HOST's (either SP or MP) Mission Editor and resaved under a different version name.

 

System resource usage appears to have increased with this version and someone can correct me if I'm wrong but I don't think 4 gigs of RAM (read: 32bit operating systems) are going to cut it anymore. Those of you looking to skate by on minimum specs may or may not have success in avoiding crashes.

Edited September 9, 2013 by ENO

[sslechta]

System resource usage appears to have increased with this version and someone can correct me if I'm wrong but I don't think 4 megs of RAM (read: 32bit operating systems) are going to cut it anymore.

 

Agree with you on resource usage.

 

You mean 4 gig?

[ENO]

Oh- yes good catch. Will edit.

 

But on that note the statement is still true. 4MEGS of RAM definitely will not cut it lol

[sorcer3r]

Any results?

 

Thanks for all your work guys, we have a MP testing session tomorrow, I am hopeful we can crash our server as well... if you know what I mean :)

 

 

2 days - 5 crashes. :huh:

STP-8logs.zip

[NineLine]

Another session planned for tomorrow, so far things are looking better.

[Pman]

I will have all the scripts removed and the race coure removed to test it over the next few days

 

Pete

[TimeKilla]

Fingers crossed pman.

[TaliG]

I will have all the scripts removed and the race coure removed to test it over the next few days

 

Pete

 

better remove 126 and run 125 ? :huh: just saying :doh:

[Pman]

We had just as many issues in 1.2.5 and if we roll back it means that our pilots cant play on other servers or fly the Mi-8

 

I would rather try and work through the problems and get back to the stability we had in 1.2.4 if at all possible.

 

I have noticed that the RAM usage is MUCH MUCH lower with 1.2.6 its down to like 2gb on our server now, impressive.

 

I do run with render off as well for the record.

 

There are some albeit small private servers running for like 60 hours so it is possible, but we need to get it sorted sooner rather then later.

 

Pman

[TaliG]

We had just as many issues in 1.2.5 and if we roll back it means that our pilots cant play on other servers or fly the Mi-8

 

I would rather try and work through the problems and get back to the stability we had in 1.2.4 if at all possible.

 

I have noticed that the RAM usage is MUCH MUCH lower with 1.2.6 its down to like 2gb on our server now, impressive.

 

I do run with render off as well for the record.

 

There are some albeit small private servers running for like 60 hours so it is possible, but we need to get it sorted sooner rather then later.

 

Pman

 

Im criticising for the the better, please dnt get me wrong :smilewink:

 

EDIT: I am a client :)

Edited September 10, 2013 by TaliG

[TimeKilla]

The traffic pmans server gets is amazing its really leading the way in amount of clients and with that comes the unknown.

 

Anyway i'll stay on topic sorry.

[Pman]

Im criticising for the the better, please dnt get me wrong :smilewink:

 

EDIT: I am a client :)

 

Dont worry, it was not taken in a bad way :)

 

Pman

[ENO]

Firehouse server crash... about half a dozen guys in there. Weird slots not working. Anyway, was able to capture the Tacview file on it and that made the file huge.

 

Anyway, good luck!

 

https://docs.google.com/file/d/0B8MeQLQ7pOpjdlVzUFEzM1JxU3c/edit?usp=sharing

[NineLine]

When you say slots not working, you mean plane slots that could not be accessed by a player?