Well, it's still running. You could try to trace processes using strace -f
-p PID to monitor processes.

Try also running ps aux | grep nasl

Eero

Eero
6.11.2015 6.46 ip. "cory cardio" <[email protected]> kirjoitti:

> attached, and pasted below
>
> root       342  0.0  1.0 150324 44304 ?        S    Oct29   0:02 openvassd: 
> testing 10.100.7.187 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root      4816  0.0  1.1 150064 44480 ?        S    Oct29   1:00 openvassd: 
> testing 10.100.7.237
> root      5085  0.8  1.0 148084 41052 ?        Ss   Oct29  98:29 openvassd: 
> Serving 127.0.0.1
> root      5094  1.1  7.2 456864 293668 ?       S    Oct29 136:34 openvasmd
> root      5623  0.0  0.8 149492 33512 ?        S    Oct27   1:06 openvassd: 
> testing 10.100.6.28
> root      5705  0.3  1.1 150020 44476 ?        S    10:02   0:17 openvassd: 
> testing 10.2.5.20
> root      5931  0.0  1.0 150328 44312 ?        S    Oct29   0:02 openvassd: 
> testing 10.100.7.237 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root      5977  0.0  1.1 150064 44480 ?        S    Oct29   1:01 openvassd: 
> testing 10.100.7.196
> root      6438  0.2  1.1 150020 44456 ?        S    10:03   0:13 openvassd: 
> testing 10.2.5.26
> root      6873  0.0  0.9 149492 37572 ?        S    Oct27   1:06 openvassd: 
> testing 10.100.6.230
> root      7550  0.0  1.0 150324 44248 ?        S    Oct29   0:02 openvassd: 
> testing 10.100.7.196 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root      8840  1.0  1.0 147776 43652 ?        Ss   Nov05  15:21 openvassd: 
> Serving 127.0.0.1
> root      8842  0.1  4.7 354600 192300 ?       S    Nov05   2:05 openvasmd
> root      8875  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.2
> root      8876  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.3
> root      8877  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.4
> root      8878  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.5
> root      8880  0.0  1.0 149756 43052 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.8
> root      8882  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.10
> root      8883  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.11
> root      8884  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.14
> root      8885  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.16
> root      8886  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.18
> root      8887  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.19
> root      8888  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.21
> root      8889  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.22
> root      8890  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.23
> root      8891  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.24
> root      8892  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.25
> root      8893  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.26
> root      8894  0.0  1.0 149756 43596 ?        S    Nov05   0:00 openvassd: 
> testing 10.2.1.27
> root      9686  0.0  0.8 149492 35040 ?        S    Oct27   1:07 openvassd: 
> testing 10.100.6.77
> root     11426  0.0  0.5 149752 21288 ?        S    Oct27   0:42 openvassd: 
> testing 10.100.6.28 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     11836  0.0  1.0 150420 43872 ?        S    11:06   0:00 openvassd: 
> testing 10.2.5.20 
> (/var/lib/openvas/plugins/2015/sw_fckeditor_file_upload.nasl)
> root     11999  0.0  1.0 150064 44352 ?        S    Nov04   0:20 openvassd: 
> testing 10.100.11.219
> root     12225  0.0  0.6 149752 26796 ?        S    Oct27   0:00 openvassd: 
> testing 10.100.6.230 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     12803  0.0  1.0 150288 43668 ?        S    11:21   0:00 openvassd: 
> testing 10.2.5.26 
> (/var/lib/openvas/plugins/2013/gb_open_xchange_server_mult_vuln.nasl)
> root     12828  0.0  1.0 150288 43668 ?        S    11:21   0:00 openvassd: 
> testing 10.2.5.26 
> (/var/lib/openvas/plugins/2013/gb_dotnetnuke_dnnarticle_sql_inj_vuln.nasl)
> root     12838  0.0  1.0 150420 43912 ?        S    11:21   0:00 openvassd: 
> testing 10.2.5.20 
> (/var/lib/openvas/plugins/2011/secpod_cubecart_mult_xss_and_sql_inj_vuln.nasl)
> root     12843  0.0  1.0 150288 43688 ?        S    11:21   0:00 openvassd: 
> testing 10.2.5.26 
> (/var/lib/openvas/plugins/2013/gb_greenstone_mult_vulns_06_2013.nasl)
> root     12859  0.1  1.0 150552 43892 ?        S    11:22   0:00 openvassd: 
> testing 10.2.5.20 
> (/var/lib/openvas/plugins/2011/secpod_liblime_koha_kohaopaclanguage_param_lfi_vuln.nasl)
> root     12865  0.1  1.0 150288 43692 ?        S    11:22   0:00 openvassd: 
> testing 10.2.5.26 
> (/var/lib/openvas/plugins/2013/gb_oracle_portaldemo_orgchart_sql_inj_vuln.nasl)
> root     12870  0.2  1.0 150420 43796 ?        S    11:22   0:00 openvassd: 
> testing 10.2.5.20 
> (/var/lib/openvas/plugins/2011/gb_ibm_rational_quality_and_test_lab_tomcat_mgr_default_account_vuln.na
> root     12876  0.0  0.0  12660  1688 pts/1    S+   11:22   0:00 grep 
> --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git 
> --exclude-dir=.hg --exclude-dir=.svn -i openvas
> root     13221  0.0  1.0 150324 44352 ?        S    Nov04   0:14 openvassd: 
> testing 10.100.11.219 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     13951  0.0  0.6 149752 24532 ?        S    Oct27   0:02 openvassd: 
> testing 10.100.6.77 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     15532  0.0  1.1 150064 44480 ?        S    Oct29   1:00 openvassd: 
> testing 10.100.7.208
> root     15543  0.0  1.0 150200 43896 ?        S    Oct29   1:14 openvassd: 
> testing 10.3.32.24
> root     16315  0.0  0.8 149492 34996 ?        S    Oct27   1:07 openvassd: 
> testing 10.100.6.88
> root     16912  0.0  1.0 150324 44312 ?        S    Oct29   0:03 openvassd: 
> testing 10.100.7.208 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     17005  0.0  0.9 150460 40260 ?        S    Oct29   0:02 openvassd: 
> testing 10.3.32.24 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     20679  0.0  1.1 150064 44476 ?        S    Oct29   1:02 openvassd: 
> testing 10.100.7.115
> root     21157  0.0  0.6 149752 25920 ?        S    Oct27   0:01 openvassd: 
> testing 10.100.6.88 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     22040  0.0  0.8 149492 35892 ?        S    Oct27   1:07 openvassd: 
> testing 10.100.6.47
> root     22864  0.0  1.0 150324 44244 ?        S    Oct29   0:00 openvassd: 
> testing 10.100.7.115 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     26023  0.0  0.6 149752 26220 ?        S    Oct27   0:01 openvassd: 
> testing 10.100.6.47 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
> root     28135  0.0  0.7 137956 31296 ?        Ss   Oct27   4:33 openvassd: 
> Waiting for incoming connections
> root     28160  0.0  4.7 355324 192452 ?       SL   Oct27   4:55 openvasmd
> root     28301  0.0  0.8 149492 35540 ?        S    Oct27   1:08 openvassd: 
> testing 10.100.6.155
> root     30810  0.0  1.1 150064 44480 ?        S    Oct29   1:01 openvassd: 
> testing 10.100.7.187
> root     31465  0.6  0.1 147380  5808 ?        Ss   Oct27  96:31 openvassd: 
> Serving 127.0.0.1
> root     31470  0.0  0.2 236096 10792 ?        S    Oct27   7:21 openvasmd
> root     32606  0.0  0.5 149752 23792 ?        S    Oct27   0:00 openvassd: 
> testing 10.100.6.155 (/var/lib/openvas/plugins/secspace_traceroute.nasl)
>
>
>
>
> On Fri, Nov 6, 2015 at 11:32 AM, Eero Volotinen <[email protected]>
> wrote:
>
>> Well, my scanning machine is usually physical hardware with 64 to 128gb
>> of memory or very powerful virtual server..
>>
>> Url is not working..
>>
>> Eero
>> 6.11.2015 6.23 ip. "cory cardio" <[email protected]> kirjoitti:
>>
>>> Machine is a decent laptop. I usually run 1 task at a time, but after a
>>> few days of no progress on 1, I did start another.
>>>
>>> Here is the process list: http://sprunge.us/RODU
>>>
>>> On Fri, Nov 6, 2015 at 5:02 AM, Eero Volotinen <[email protected]>
>>> wrote:
>>>
>>>> Well, it depends on your hardware and network and how many tasks are
>>>> running parallers.
>>>>
>>>> You should use slave scanners or multiple scanner machines to speed and
>>>> balance load.
>>>>
>>>> Eero
>>>> 6.11.2015 8.49 ap. "Helmut Koers" <[email protected]> kirjoitti:
>>>>
>>>>> As you call it huge tasks, is there any recommendation on the maximum
>>>>> number of targets per task?
>>>>>
>>>>> Helmut
>>>>>
>>>>>
>>>>> 05.11.2015----17:56:19"Openvas-discuss"
>>>>> <[email protected]> wrote on 05.11.2015
>>>>> 17:56:19:
>>>>>
>>>>> > From: Eero Volotinen
>>>>> <[email protected]>> To: cory cardio <
>>>>> [email protected]>, > Cc: openvas-disc
>>>>> [email protected]>
>>>>>  Date: 05.11.2015 17:56> Subject: Re: [Openv
>>>>> as-discuss] stuck tasks> Sent by: "Openvas-discuss"
>>>>> <openvas-discuss-bounc
>>>>> [email protected]>>
>>>>> > 400 or 1500 targe
>>>>> ts is a huge scan task.> What is output o
>>>>> f ps aux | grep openvas> And please put
>>>>>  outpu
>>>>> t into pastebin..> Eero> 5.11.2015 6.08 ip. "cory cardio" <clcardio7
>>>>> 1@gmail.
>>>>> com> kirjoitti:> Hello,>   I've got two tasks which will not complete,
>>>>> would somebody have a
>>>>>
>>>>> > suggestion for me?
>>>>> >   One task is about 400 targets, stuck at 97% for at least a weak.
>>>>> > The other is about 1500 targets, stuck
>>>>> at 96% for 3 days now.
>>>>> >   Should I stop them? Restar
>>>>> t them? Let them ru
>>>>> n?
>>>>> > Thanks in advance>
>>>>> > _______________________________________________
>>>>> > Openvas-discuss mailing list
>>>>> > [email protected]
>>>>> >
>>>>>
>>>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>>>>> > _______________________________________________
>>>>> > Openvas-discuss mailing list
>>>>> > [email protected]
>>>>> >
>>>>>
>>>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>>>>>
>>>>
>>>> _______________________________________________
>>>> Openvas-discuss mailing list
>>>> [email protected]
>>>>
>>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>>>>
>>>
>>>
>
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to