when it is + / - about 25 people online on my server is already bad because I login?
my server is
Atlhon X2 4000
4 gb ram
80 hd
100 mb of internet
because this will be happening this problem?
when it is + / - about 25 people online on my server is already bad because I login?
my server is
Atlhon X2 4000
4 gb ram
80 hd
100 mb of internet
because this will be happening this problem?
Make sure UpdateInterval is 300000 in your worldsvr ini and make sure centos has plenty of free ram. You need ~ 200mb of ram for each channel or it starts to lag.
[WorldSvr]
ServerIdx = 9
GroupIdx = 1
Globaltime = 4:10000,5:5000,7:3600000,22:60000,8:2000
WorldTimer = 1:****2:150,3:3000,6:60000,8:2000,9:10000,14:2000,16:200,20:200,21:200
CommonIniPath = Common.ini
IPAddress = xxx
UpdateInterval = 300000
something's wrong here = /?
IPAddress. Specify your own, and not leave it as "xxx" :]Originally Posted by hellred3
I think he had his ip there but he censured it.
dont use the server computer. Because it will cause lags.
The setting i was worried about is ok so it probably is the server getting overloaded. How much ram is given to centos? Everybody always states how much the host machine has and not what they have given to centos :P
put 3GB in Centos Machine
http://img340.imageshack.us/i/imagem1r.jpg/
http://img154.imageshack.us/i/imagem2mu.jpg/
now giving this problem, this bm lasting 3 minutes, no longer know what to do more with these servers full full of problems -.-
Those settings look ok too so i'm not sure to be honest. I know a few people using my files with many more than that online without problems. All you can really do is study the problem looking for patterns.
The first thing i would do is clean out the logs and get people online to cause the problem, then look in the logs to see what errors show up or what connections between the cabal processes are failing. Logs will be your friend here.
has some specific command to clear the logs? or so to go on winscp and delete everything that is inside the log folder?
Yes just delete them. I usually stop the server first so the new logs show everything from startup to the problem.
Reply With Quote