• Unfortunately, we have experienced significant hard drive damage that requires urgent maintenance and rebuilding. The forum will be a state of read only until we install our new drives and rebuild all the configurations needed. Please follow our Facebook page for updates, we will be back up shortly! (The forum could go offline at any given time due to the nature of the failed drives whilst awaiting the upgrades.) When you see an Incapsula error, you know we are in the process of migration.

(##ERROR## NoNotifyTimeLimit) Fix

Newbie Spellweaver
Joined
Apr 17, 2014
Messages
18
Reaction score
0
Hello my dear forum members! Well, I have found a theory why this error pops up.

Slow Initialization of Services (CentOS Hardware Configuration)
  • Lower than 2GB RAM
  • Lower than 2 Processor Cores

Well, do not change all "NoNotifyTimeLimit=60000" to any values anymore.

Scenario: When you type "service cabal start", you will notice that the starting of services from one another maybe have 2-3 sec. delay only. Now, to bypass it or to make it work. Stop all services by "service cabal stop", then enter each service one by one with a delay of 30 sec.

service AuthDBAgent start
service DBAgent_01 start
service RockAndRollITS start
service GlobalMgrSvr start
service GlobalDBAgent start
service CashDBAgent start
service PCBangDBAgent start
service EventDBAgent start
service PartySvr_01 start
service ChatNode_01 start
service EventMgrSvr start
service AgentShop_01 start
service LoginSvr_01 start
service WorldSvr_01_01 start

And please, those services should be in order.

You will notice in the log file, NoNotifyTimeLimit disappears. =)
 
Back
Top