SLBD using entire CPU

wjs

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?

Juve

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.

Juve

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

cmb

It's a known issue, using the uniprocessor kernel resolves it.

wjs

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.

Juve

Thanks cmb,

When we do the killall -9 on slbd what effects does it have on connections ? does it kills openned connections ?

eri--

1.2.1 should not suffer from it.

Juve

OK fine.
But what about connections when killing slbd ?

Thanks

cmb

slbd has no effects on your connections, its only function is to update the ruleset.

Juve

Ok thanks !
This mean I can my own crontab script to kill/restart it more often.

eri--

Try 1.2.1 it does not have the slbd problems with multi-wan and should behave better.