Incident 2071=Swap partition 25 per cent full !!!

[stefanc]

Hi All

What is the incident "2071=Swap partition 25 per cent full" mean.

Can any one explain this to me, and how to fix it

9.1 on a 7.2 cpu

[Eliott]

I've given a wrong answer here: viewtopic.php?f=327&t=16925&p=59704&hilit=2071#p59704
But this time my answer could match.

More detailed:
If the OXE creates many incidents 2071=Swap partition xx per cent full (~1 per hour) you should check the following:
-Check memory usage and identify the process consuming all the memory
-With the command 'free' or 'vmstat' the system shows you the memory and Swap usage.
-The used swap size should not too big. Just some MB. 200 MB and more are too much.

It could be that the sipmotor process is your problem.
Check with 'top -b -n1'-command...
If possible, you could try a sipmotor restart (killall sipmotor) but careful - SIP calls will be dropped...
If the sipmotor is really the bad guy, I suggest you to contact ALU Tech Support and tell them to assign your issue to the eSR 1-117422071 as duplicated one...

[stefanc]

Yepp, didnt saw it first, as it was at the bottom of my screen, sipmotor draw 30 Mb of mem !!!! , after restart now it down to normal 2.7

I will contact the ALU reg. the slip.

Thanks

Regards ...

SC

[Eliott]

But 30 is not too much. In which column, do you read the value?
See SIZE column. See below - there we have 262M for example.

Code: Select all

(1)OXE> vmstat
   procs                      memory    swap          io     system         cpu
 r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
 0  7  4 232456  20376   5092 122948   0   0     0     2    1     0   0   0   2

(101)tkanlage> top (Großes M um nach Speichernutzung zu sortieren)
 10:10am  up 198 days, 21:41,  1 user,  load average: 11.30, 11.19, 11.11
242 processes: 240 sleeping, 2 running, 0 zombie, 0 stopped
CPU states:  8.1% user, 14.0% system,  0.0% nice, 77.7% idle
Mem:   255956K av,  235352K used,   20604K free,       0K shrd,    5092K buff
Swap: 1048784K av,  232456K used,  816328K free                  122664K cached

  PID USER     CLS  PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2778 mtcl     FIFO  99 -12  262M  52M   896 S <   0.0 20.8   0:00 #sipmotor
 2779 mtcl     UNIX  36 -12  262M  52M   896 S <   0.0 20.8   0:23 sipmotor
 2780 mtcl     UNIX  36 -12  262M  52M   896 S <   0.0 20.8   0:00 sipmotor
 2781 mtcl     UNIX  -75 211  262M  52M   896 S N   0.0 20.8   0:00 sipmotor
 2782 mtcl     UNIX  -75 211  262M  52M   896 R N   0.0 20.8   0:34 sipmotor

[stefanc]

You´re right, it should not be of a problem, but interesting is that my free mem increased from 6 Mb to 56 Mb !!!!

9:14am up 151 days, 10:02, 1 user, load average: 11.00, 11.00, 11.00
234 processes: 233 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 0.1% user, 0.2% system, 0.0% nice, 0.0% idle
Mem: 256464K av, 199896K used, 56568K free, 0K shrd, 7372K buff
Swap: 1048784K av, 18812K used, 1029972K free 136504K cached

PID USER CLS PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
11955 mtcl UNIX 23 0 1108 1108 824 R 5.5 0.4 0:00 top

11720 root FIFO 99 -12 3456 3456 3116 S < 0.0 1.3 0:00 #sipmotor
11721 root UNIX 36 -12 3456 3456 3116 S < 0.0 1.3 0:00 sipmotor
11722 root UNIX 36 -12 3456 3456 3116 S < 0.0 1.3 0:00 sipmotor
11723 root UNIX -75 211 3456 3456 3116 S N 0.0 1.3 0:00 sipmotor
11724 root UNIX -75 211 3456 3456 3116 S N 0.0 1.3 0:00 sipmotor

[Eliott]

Sure, but for the incident this line is relevant:

Code: Select all

Swap: 1048784K av, 18812K used, 1029972K free 136504K cached

[stefanc]

True true , can I change the thresholds somewhere

[Eliott]

I think no. )
And to change the threshhold will not solve the issue...

[stefanc]

Ok !, my idea was that a 25% use of swap isnt in my opinion a major incident , perhaps an minor one isnt it.

[Eliott]

25% of swap usage is not good => Swap = RAM on Harddisk = Slow =