Dear Uwnthesis,
I just need to run the Step 1: Configure OBS Repository right. The following steps from the website is not needed right. So is that why when I try to run open vas it get stuck at 1%?
Member
Dear Uwnthesis,
I just need to run the Step 1: Configure OBS Repository right. The following steps from the website is not needed right. So is that why when I try to run open vas it get stuck at 1%?
Member
I've searched for Openvas at 1% - it seems to be a common hiccup.Originally Posted by newbie14
One interesting comment - that might explain why OpenVas is getting stuck is here:
Sometimes when I an having scanning issues it helps me to see where it hangs by running
ps ax |grep openvas
You can see there which NASL is running in real time and which is hanging
from there you could always "kill" the hanging process too and the scan will continue as normal.
http://forums.alienvault.com/discuss...launching-scan
This might just work for you
Member
Dear Uwnthesis,
Ok I ran this command ps ax |grep openvas first I saw this /var/lib/opevas/pluglins/nmap.nasl then next I saw is this and the moment I do this kill the process id next when I refresh it say is done. I think some thing is wrong right?
Junior Member
It's really not a god idea to kill the nmap process.Which port range did you use? Note that a UDP port scan can take a very long time. Stuck at 1% means nearly always "Scanner is in port scan phase". Maybe run https://svn.wald.intevation.org/svn/...as-check-setup to be sure anything in your installation is ok.
Member
Dear Mime,
I have ran the script. Below is the results. To be very frank I am very lost at this stage cause if you follow the through this thread before I ran the lazykali script open vas could never run so I could only run via the lazykali. So I dont know what to do next from here?
Code:./openvas-check-setup.sh openvas-check-setup 2.2.3 Test completeness and readiness of OpenVAS-6 (add '--v4', '--v5' or '--v7' if you want to check for another OpenVAS version) Please report us any non-detected problems and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem. Use the parameter --server to skip checks for client tools like GSD and OpenVAS-CLI. Step 1: Checking OpenVAS Scanner ... ERROR: OpenVAS Scanner too old or too new: 3.3.1 FIX: Please install OpenVAS Scanner 3.4. ERROR: Your OpenVAS-6 installation is not yet complete! Please follow the instructions marked with FIX above and run this script again. If you think this result is wrong, please report your observation and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
Junior Member
You have to add the '--v5' switch...
Member
Dear Mime,
Here is the results. So what I did is that via the lazykali script update the kali first then I updated openvas. Why does the kaliupdate takes few hours ? So what is your guide from here? After the update I am running the openvas and again stuck at the nmap.
Code:ps ax | grep openvas 31274 ? Ss 0:00 openvassd: waiting for incoming connections 31282 pts/0 S+ 0:00 openvasmd -p 9390 -a 127.0.0.1 31284 pts/0 S+ 0:00 openvasad -a 127.0.0.1 -p 9393 31325 ? Ss 0:08 openvassd: serving 127.0.0.1 31326 pts/0 S+ 0:03 openvasmd -p 9390 -a 127.0.0.1 31340 ? S 0:00 openvassd: testing ************** 31521 ? S 0:00 openvassd: testing ********* (/var/lib/openvas/plugins/nmap.nasl) 31792 pts/2 S+ 0:00 grep openvasCode:./openvas-check-setup.sh -v5 openvas-check-setup 2.2.3 Test completeness and readiness of OpenVAS-6 (add '--v4', '--v5' or '--v7' if you want to check for another OpenVAS version) Please report us any non-detected problems and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem. Use the parameter --server to skip checks for client tools like GSD and OpenVAS-CLI. Step 1: Checking OpenVAS Scanner ... ERROR: OpenVAS Scanner too old or too new: 3.3.1 FIX: Please install OpenVAS Scanner 3.4. ERROR: Your OpenVAS-6 installation is not yet complete! Please follow the instructions marked with FIX above and run this script again. If you think this result is wrong, please report your observation and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem. root@kali:~/Desktop/lazykali# ./openvas-check-setup.sh --v5 openvas-check-setup 2.2.3 Test completeness and readiness of OpenVAS-5 Please report us any non-detected problems and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem. Use the parameter --server to skip checks for client tools like GSD and OpenVAS-CLI. Step 1: Checking OpenVAS Scanner ... OK: OpenVAS Scanner is present in version 3.3.1. OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem. OK: NVT collection in /var/lib/openvas/plugins contains 32480 NVTs. WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner. SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html). OK: The NVT cache in /var/cache/openvas contains 32480 files for 32480 NVTs. Step 2: Checking OpenVAS Manager ... OK: OpenVAS Manager is present in version 3.0.4. OK: OpenVAS Manager client certificate is present as /var/lib/openvas/CA/clientcert.pem. OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db. OK: Access rights for the OpenVAS Manager database are correct. OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled. OK: OpenVAS Manager database is at revision 56. OK: OpenVAS Manager expects database at revision 56. OK: Database schema is up to date. OK: OpenVAS Manager database contains information about 32480 NVTs. ERROR: No OpenVAS SCAP database found. (Tried: /var/lib/openvas/scap-data/scap.db) FIX: Run a SCAP synchronization script like openvas-scapdata-sync or greenbone-scapdata-sync. ERROR: Your OpenVAS-5 installation is not yet complete! Please follow the instructions marked with FIX above and run this script again. If you think this result is wrong, please report your observation and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
Posting Permissions
