View Issue Details

IDProjectCategoryView StatusLast Update
0004185Kali LinuxGeneral Bugpublic2018-02-21 09:41
Reportergrimwiz Assigned To 
PrioritylowSeverityminorReproducibilitysometimes
Status closedResolutionopen 
Product Version2017.1 
Summary0004185: openvas with postgresql leaves busy task
Description

After a scan finishes, one openvasmd task remains running at 100% CPU.

This process seems to be locking and unlocking the postgresql shared memory.

root@kalipc:/home/openvas/mgr# top -p 49500
top - 17:45:10 up 9 days, 1:09, 4 users, load average: 1.01, 1.02, 1.19
Tasks: 1 total, 1 running, 0 sleeping, 0 stopped, 0 zombie
%Cpu(s): 10.0 us, 15.2 sy, 0.0 ni, 74.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 8169784 total, 4573144 free, 455832 used, 3140808 buff/cache
KiB Swap: 1048572 total, 1048572 free, 0 used. 7370044 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
49500 root 20 0 254940 87372 5584 R 99.7 1.1 177:58.95 openvasmd

root@kalipc:/home/openvas/mgr# strace -p 49500 2>&1 | head
strace: Process 49500 attached
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=125, l_len=1}) = 0

root@kalipc:/home/openvas/mgr# ls -l /proc/49500/fd/7
lrwx------ 1 root root 64 Aug 24 17:43 /proc/49500/fd/7 -> /home/openvas/mgr/tasks.db-shm

Steps To Reproduce

Enable postgresql in openvas, run a scan, wait for scan to finish.

Activities

g0tmi1k

g0tmi1k

2018-02-21 09:41

administrator   ~0008740

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.1), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2017-08-24 16:48 grimwiz New Issue
2018-02-21 09:41 g0tmi1k Note Added: 0008740
2018-02-21 09:41 g0tmi1k Status new => closed