Hello,
Here is my clean start log. Why i can't see channels?
Attachment 135174
Printable View
Hello,
Here is my clean start log. Why i can't see channels?
Attachment 135174
Probably this:
Sun Jul 28 2013 13:49:20.792233 3077188464]: [##ERROR##] 1:1 server notify time over (time: 64388)
[Sun Jul 28 2013 13:49:20.792456 3077188464]: close(): closing(127.0.0.1)
[Sun Jul 28 2013 13:49:20.797002 3077188464]: 5.close user -1 [9F93E98] (127.0.0.1)
Check the Cfgs for NotifyTime=30000 (or 10000 can't recall acurractly) and set it to NotifyTime=70000 should be about it atleast for that error.
I get this time over log in GlobalMgrSvr.
Anyone can tell me what i need change?
I only see this with notify text: NoNotifyTimeLimit=60000
mind telling me.. did u use window OS x64 ?
i have same problem b4 this no channel appear..
my os window 7 x64 home prem. n centos 32bit i386 = result no channel appear..
it solved after i change centos to x86_64 = channel appear
yeah its that NoNotifyTimeLimit=60000 you have to increase it.Quote:
Originally Posted by inika
shaman96: I use win svr 2003 r2 32bit and centos 5.9 i386
GoldenHeaven: I increased to 60000000 and no differente.
And the error sometime:
Code:[##ERROR##] 1:1 server notify time over (time: 64388)
[##ERROR##] 1:1 server notify time over (time: 73874)
[##ERROR##] 1:1 server notify time over (time: 31548)
tell me exactly your computer configuration (ram,cpu)
I can tell but you 100% laugh. xD Anyway around 20 times the server started succesfully but now not. :S
The main pc: 4gb ram 4 core
The centos: 2gm ram 1 core
But please don't tell give more core i know the problem i only need the solution to change the time over limit. And the NoNotifyTimeLimit is not enought or i configure in bad place. I changed this in /etc/cabal.
I only have a possible quick fix for you copy all original inis over the ones you have at /etc/cabal but first try to change NoNotifyLimit=60000 in every .ini file that has it.
I reinstalled fully the centos and the cabal so its clean config but i changed in every ini where i found the NoNotifyTimeLimit to big number and nothing.
Code:[##ERROR##] 1:1 server notify time over (time: 25972)
Wtf man... :| i can't run it even with 4 gb ram and dual core 1.8 ... i got same error :). You have to buy a new machine with quad core processor and min 4 gb of ram...Quote:
Originally Posted by inika
You can try creating a .sh file on root folder with this then run it with ./nameoffile.sh (Note: replace XX with number of daemon, like service WorldSvr_01_01 start):
This will start a daemon then wait 2mins to start another giving them time to settle after that start the rest manuallyQuote:
#!/bin/sh
service cabal stop
service GlobalDBAgent_XX start
sleep(2000)
service CashDBAgent_XX start
sleep(2000)
service PCBangDBAgent_XX start
sleep(2000)
service DBAgent_XX start
sleep(2000)
service GlobalMgrSvr_XX start
sleep(2000)
service ChatNode_XX start
sleep(2000)
service LoginSvr_XX start
sleep(2000)
service WorldSvr_XX_XX start
oOSpikeOo: You are stupid. Its easy can run i already runed this server with this config but only i now get this error. Anyway do anything if you want for yourself buy strong machine for nothing. :)
GoldenHeaven: I now put 30 sec start time for each service and i try it. If now work i incrase this time.
GlobalMgrSvr.ini
NoNotifyTimeLimit=60000
cabal_start.sh
Spoiler:
GlobalMgrSvr needs time of at least 14 sec in particular to start.
There are 4 services that depend on GlobalMgrSvr.
DBAgent_01 5x (RockAndRollITS, GlobalMgrSvr, ChatNode_01, EventMgrSvr, AgentShop_01)
GlobalMgrSvr 4x (ChatNode_01, EventMgrSvr, AgentShop_01, LoginSvr_01)
GlobalDBAgent 1x (LoginSvr_01)
ChatNode 1x (AgentShop_01)
The services that are independent should start first and the services that are dependent should start the last.
You stop them in the reverse order.
I tested the first time on 1gb ram and 1 core (3.1ghz) vps. I can bet it worked fine.
Now I'm building a dedicated server configuration.