Page 1 of 1
Incident 2071
Posted: 21 Feb 2012 08:20
by kisanbhai
Hello all,
It is related to one of my site on Release 9.0
I am getting a major incident-2071 " swap partition 31% full". I am unable to under the message clearly. Also tried to understand the same through incinfo command, but failed to understand.
Assistance is solicited.
Regards.
Re: Incident 2071
Posted: 21 Feb 2012 09:12
by MrAnMo
Like windows also linux uses a swap partition. In this case it means that the the swap partition is already for 30% full. For this problem a reset of the oxe will help.
Re: Incident 2071
Posted: 22 Feb 2012 08:59
by Yong_Zhao
Do you have high traffic or a lot of applications ?
Used command "free" or "cat /proc/swaps" check your swap partition in OXE.If you often error :
1). I think that may be the OXE R9.0's BUG.You can try to upgrade to the new patch;
2). Try to resize swap partition
a. use "root" login to OXE;
b. command "dd if=/dev/zero of=/tmp/swapfree bs=32k count=8192" (**swap size=bs*count e.g swap=32K*8192=262144 ≈256MB);
c. command "mkswap /tmp/swapfree" (**format swapfree)
d. command "swapon /tmp/swapfree" (**start swapfree)
e. command "swapon –s (**show swap status)
f. command "vi /etc/fstab" add "/tmp/swapfree swap swap defaults 0 0";
like this :
/dev/sda3 swap swap defaults 0 0
/tmp/swapfree swap swap defaults 0 0
command "reboot" (**restart your OXE.)
g. command "cat /proc/swaps" check your new swap partition.
like this:
xa000000> cat /proc/swaps
Filename Type Size Used Priority
/dev/hda11 partition 530104 2176 -1
/tmp/swapfree file 327672 0 -2
xa000000>free
Swap : 857776 (**Old is 530104)
Re: Incident 2071
Posted: 27 Feb 2012 07:25
by kisanbhai
Dear Yong_zhao,
There is very little traffic ( negligible) and there is no application. It happened after release upgrade from R7.1 to R9.0.
I would put an update, once I login to the system. I am not on site and the only way is to have remote login.
Anyway, thanks for the suggessions.
Re: Incident 2071
Posted: 06 Mar 2012 04:01
by Eliott
Restart sipmotor. Should solve the issue.
dhs3_init -R SIPMOTOR
(Check there are no running SIP communications or they will get lost)
You can see details with command top -b -n1 in SIZE column if I remember it correctly
Re: Incident 2071
Posted: 22 Mar 2012 06:18
by MrAnMo
I can confirm that the suggest from Eliott works. I had a site with a 2071 incident. After restarting the sipmotor the swap partition was free again.
Re: Incident 2071
Posted: 10 Sep 2014 00:43
by swinstu
Issue also resolved after restart of sipmotor. And I had to login root account to kill the sipmotor process due to R9.1 OXE. No incidents in over 2.5 hours.
10/09/14 11:47:11 000001M|---/--/-/---|=2:2071=Swap partition 72 per cent full.
10/09/14 11:51:47 000001M|000/00/-/---|=5:5800=5 SIP trunk group put into service
10/09/14 14:32:19 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
Re: Incident 2071
Posted: 11 Sep 2014 16:45
by tgn
better upgrade to the latest patch. incident will come back because of a bug. it starts to inform you if 30% of swap usage is reached.
regards...