This deadlocks started to appear just a few days ago, when nothing
was changed, although the traffic did increase alot!
hehe…this IS exactly the problem:
When a call is…lets say not freeing 24 byte of mem, you wont recognize with 100 calls a day.
But with 1000 calls you will recog it soon…
Its just hardening my ressource-slack theory, something isnt cleared there in asterisk…
Asterisk is supposed to clear every variable with the hangup.
I suspect that not working 100% , thats why we run out of ressources causing this problem on heavy-load pbx’
Well…thats what i guess, could be wrong tho.
So far, you only have two choices:
A cronjob rebooting your machine 6am in the morning time
See your local webmin interface and create one with the command
nohup shutdown -r now &
and shedule it to 6am every day.
Second choice, which i am trying tonite:
If you go with the cron reboot:
Make sure all needed services (cdr, mysql etc) are started automatically on boot !