SLBD using entire CPU
-
i'm not an expert but i'll take a shot at it
-
Any steps we can take to install and test hostated, maybe having it alongside slbd just in case?
The change in the script is working, but in between several processes get started and start to chew up 100% CPU again. It would be nice to try out the newer service, but have the other to fall-back on just in case…
-
Sorry to pull that topic up again but I am suffering the same problem with a clean and fresh 1.2 install. The pool is a failover pool with two WANs. One of the line is currently down so one gateway can't be pinged.
Am I unlucky or is it something people still encounter ?
-
I was able to 'mitigate' the problem by switching to a new machine and doing a fresh install. It seems to me like a fairly random problem.
does slbd go to full load as soon as the pool is activated or after some time?
-
It is after some time or just after saving changes, it is really a random behaviour.
I'll monitor it to identify when it forks and goes to 99%. I have other machines where it goes very well.
-
21 hours without any problem an then 100% cpu usage on one CPU.
Where can we adjust the time the killall script is executed ?Thanks
-
It's a known issue, using the uniprocessor kernel resolves it.
-
@cmb:
It's a known issue, using the uniprocessor kernel resolves it.
That would explain why the problem resolved itself on the new machine, its single core.
Any reason why that is? I had been planning to build a new dual core router.
-
Thanks cmb,
When we do the killall -9 on slbd what effects does it have on connections ? does it kills openned connections ?
-
1.2.1 should not suffer from it.
-
OK fine.
But what about connections when killing slbd ?Thanks
-
slbd has no effects on your connections, its only function is to update the ruleset.
-
Ok thanks !
This mean I can my own crontab script to kill/restart it more often. -
Try 1.2.1 it does not have the slbd problems with multi-wan and should behave better.