Difference between revisions of "Maximum loadavg limit exceeded"
From Kolmisoft Wiki
Jump to navigationJump to search
(Created page with 'If Asterisk CLI prins message like that: WARNING[2022] pbx.c: Maximum loadavg limit of 4.000000 load exceeded by 'SIP/12345-00001234' (currently 4.030000)! It means that load …') |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
If Asterisk CLI | If Asterisk CLI prints message like that: | ||
WARNING[2022] pbx.c: Maximum loadavg limit of 4.000000 load exceeded by 'SIP/12345-00001234' (currently 4.030000)! | WARNING[2022] pbx.c: Maximum loadavg limit of 4.000000 load exceeded by 'SIP/12345-00001234' (currently 4.030000)! | ||
| Line 17: | Line 17: | ||
After editing file please restart Asterisk to apply changes. | After editing file please restart Asterisk to apply changes. | ||
/etc/init.d/asterisk | /etc/init.d/asterisk restart | ||
If problem continues with increased load limit, solutions are following: | If problem continues with increased load limit, solutions are following: | ||
Latest revision as of 17:48, 21 March 2017
If Asterisk CLI prints message like that:
WARNING[2022] pbx.c: Maximum loadavg limit of 4.000000 load exceeded by 'SIP/12345-00001234' (currently 4.030000)!
It means that load limit is reached and therefore Asterisk is not accepting new calls to prevent load to go even higher.
Load limit can be adjusted in file /etc/asterisk/asterisk.conf
... maxload = 4 ...
By default it set to number of CPU cores.
We recommend to set this value no more than "number of CPU cores" x 2. For 4 cores CPU it would be value "8".
After editing file please restart Asterisk to apply changes.
/etc/init.d/asterisk restart
If problem continues with increased load limit, solutions are following:
- Upgrade hardware or current server;
- Add additional Asterisk server and route traffic through it;
- Decrease amount of traffic.
