Search results

wow... I guess origins is running myisam by default... sorry I'm stuck in bliss mode.

here is another article published by mysql.com about innodb tuning: http://dev.mysql.com/doc/refman/5.0/en/innodb-tuning.html

depending on how you install mysql on linux, package, compiled, etc... it may be configured differently. For instance, most fresh installs play nicely in that they will consume few resources assuming there will be other daemons fighting over resources. Here is a guide to maximize performance...

that's htop, he's running a linux server. My guess is that defrag isn't an issue unless he's running a windows formatted volume. If you are running a dedicated mysql server, you should change up your mysql.ini file so it takes advantage of more memory and threads.

You can't change that as far as I know. Sent from my Galaxy Nexus using Tapatalk 2

Through the mission file. Description.ext loadScreen = "bigt\bigt.jpg"; connect to my server and open up the cached mission file and you'll see it there.

So why am I getting memory address allocation errors if it is the processor? Also please tell me what processor you are running that is more capable than mine. It might be time for an upgrade. Yesterday afternoon I merged the server side files from the origins repo (@OriginsServer or whatever)...

I noticed something odd... the char_data table does not contain a record of "nuetral" kills (not hero, not bandit) is this a bug or does origins ignore this data.

I've merged the changes you made to the serverside PBO with mine and will test this out. Looks like you have a fix in there for corpse cleanup which my server is not doing. Also what is the table "character_data_dead" used for? I do not see any records in there

The service is set to automatic which means if I tell it to stop, it will not restart the service unless I send the start command or if the server reboots. FD (or windows service manager) will restart the service if it crashes.

are you running any anti hacks on your server? also what is your pop like? On my 2nd server (avg 30) it only crashed today for the first time.

yeah and it doesn't explain the crash after running for 2 hours and 45 min. I am also taking DB backups every 15 min but I don't think that would affect this...

well that's a relief. Now I'm thinking this could be related to the way I restart the dayz server... I am running my dayz server exe's as a firedaemon service. I have batch scripts that call "stop dayzOrigins" to stop the service, then I call "start dayzOrigins" 15 seconds later. Is it...

ok I created a trigger that will store the inventory on updates to the object_data table into a logging table. Are you guys running the latest a2oa beta? I tried to update today and it told me I had a bad cd key... not sure whats going on with that...

the 1290-v2 is the fastest intel e3 process on the market. Their highest clocking xeon processor that I am aware of. Never had this issue with regular dayz servers at that capacity (99). Also I am getting memory address errors. I doubt that the processor is the culprit here Dump Summary...

running a intel xeon 1290-v2 @ 4+ ghz I don't think the slot count is an issue. I was able to host 75+ players with a bit of lag but no crashing. the crashes happen anywhere from 15 - 50+ people. I'll try reducing slot count from 99 to 64

ok so I know I've asked this before but has anyone found a workaround for the server crashes? It seems to happen 15 min after restart and 15 min before. solution: restart every 14 min?

oh god! hit the turbo button!

removed

I figured that's what you meant. I'll be testing this out at next server restart (15 min)