Start scan and check out /var/log/openvas/* for any hints.

Eero
29.10.2015 9.00 ip. "Diego Gomes" <[email protected]> kirjoitti:

> Step 7: Checking if OpenVAS services are up and running ...
>         OK: netstat found, extended checks of the OpenVAS services enabled.
>         OK: OpenVAS Scanner is running and listening on all interfaces.
>         OK: OpenVAS Scanner is listening on port 9391, which is the
> default port.
>         ERROR: OpenVAS Manager is NOT running!
>         FIX: Start OpenVAS Manager (openvasmd).
>         OK: Greenbone Security Assistant is listening on port 9392, which
> is the default port.
>
>
> # systemctl status openvas-manager
> openvas-manager.service - OpenVAS Manager
>    Loaded: loaded (/usr/lib/systemd/system/openvas-manager.service;
> enabled)
>    Active: active (running) since Thu 2015-10-29 11:40:31 BRST; 5h 18min
> ago
>   Process: 1445 ExecStart=/usr/sbin/openvasmd $OPTIONS (code=exited,
> status=0/SUCCESS)
>  Main PID: 1473 (openvasmd)
>    CGroup: /system.slice/openvas-manager.service
>            └─1473 openvasmd
> Oct 29 11:40:31 ph-sec02.whebdc.com.br systemd[1]: Started OpenVAS
> Manager.
>
> # ps aux |grep openvasmd
> root      1473  0.3  0.9 253364 73540 ?        SL   14:41   0:27 openvasmd
> root      4195  0.0  0.0 112640   964 pts/0    S+   16:59   0:00 grep
> --color=auto openvasmd
>
> # netstat -nlpt
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address
> State       PID/Program name
> tcp        0      0 127.0.0.1:6379          0.0.0.0:*
> LISTEN      929/redis-server 12
> tcp        0      0 0.0.0.0:9391            0.0.0.0:*
> LISTEN      1433/openvassd: Wai
> tcp        0      0 192.168.254.198:9392    0.0.0.0:*
> LISTEN      1528/gsad
> tcp        0      0 192.168.254.198:80      0.0.0.0:*
> LISTEN      935/httpd
> tcp        0      0 192.168.254.198:22      0.0.0.0:*
> LISTEN      928/sshd
> tcp        0      0 127.0.0.1:25            0.0.0.0:*
> LISTEN      1822/master
> tcp        0      0 192.168.254.198:8834    0.0.0.0:*
> LISTEN      941/nessusd
> tcp6       0      0 :::9390                 :::*
> LISTEN      1473/openvasmd
> tcp6       0      0 ::1:25                  :::*
> LISTEN      1822/master
> tcp6       0      0 :::443                  :::*
> LISTEN      935/httpd
>
>
> ------------------------------
> From: [email protected]
> Date: Thu, 29 Oct 2015 18:57:18 +0000
> Subject: Re: [Openvas-discuss] No host result
> To: [email protected]
>
> What is output of openvas-check-setup --v8
>
> Eero
>
> to 29. lokakuuta 2015 klo 20.55 Diego Gomes <[email protected]>
> kirjoitti:
>
> # systemctl status redis
> redis.service - Redis persistent key-value database
>    Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled)
>    Active: active (running) since Thu 2015-10-29 11:40:30 BRST; 5h 11min
> ago
>  Main PID: 929 (redis-server)
>    CGroup: /system.slice/redis.service
>            └─929 /usr/bin/redis-server 127.0.0.1:6379
>
> Oct 29 11:40:30 ph-sec02.whebdc.com.br systemd[1]: Starting Redis
> persistent key-value database...
> Oct 29 11:40:30 ph-sec02.whebdc.com.br systemd[1]: Started Redis
> persistent key-value database.
>
> well, no changes in redis.conf
>
> # getenforce
> Disabled
>
> Maybe something in the target?
>
>
> ------------------------------
> From: [email protected]
> Date: Thu, 29 Oct 2015 18:39:33 +0000
>
> Subject: Re: [Openvas-discuss] No host result
> To: [email protected]
> CC: [email protected]
>
>
> Is redis running and configured correctly?
>
> What is output of getenforce command on root terminal?
>
> Eero
>
> to 29. lokakuuta 2015 klo 20.16 Diego Gomes <[email protected]>
> kirjoitti:
>
> Yes, it it:
>
> cat /etc/selinux/config
>
> # This file controls the state of SELinux on the system.
> # SELINUX= can take one of these three values:
> #     enforcing - SELinux security policy is enforced.
> #     permissive - SELinux prints warnings instead of enforcing.
> #     disabled - No SELinux policy is loaded.
> SELINUX=disabled
> # SELINUXTYPE= can take one of three two values:
> #     targeted - Targeted processes are protected,
> #     minimum - Modification of targeted policy. Only selected processes
> are protected.
> #     mls - Multi Level Security protection.
> SELINUXTYPE=targeted
>
> ------------------------------
> Date: Thu, 29 Oct 2015 19:27:44 +0200
>
> Subject: Re: [Openvas-discuss] No host result
> From: [email protected]
> To: [email protected]
> CC: [email protected]
>
>
> Are you sure that selinux is disabled? (setenforce 0) as It can affect
> results.
>
> --
> Eero
>
> 2015-10-29 19:09 GMT+02:00 Diego Gomes <[email protected]>:
>
> Hello,
>
> I am trying to run against a Linux server, and I am facing it:
>
> 0 results
>
> Empty reports can happen for the following reasons:
>
>    - The target hosts where regarded dead.
>    - The filter does not match any result.
>    - A very small or non-verbose scan configuration was applied.
>
> This report also contains no hosts.
>
>
> Target is UP.
>
> I can run nmap in OpenVAS server to target and fine:
>
> # nmap 10.10.10.10
>
> Starting Nmap 6.47 ( http://nmap.org ) at 2015-10-29 15:05 BRST
> Nmap scan report for 10.10.10.10
> Host is up (0.00096s latency).
> Not shown: 998 closed ports
> PORT   STATE SERVICE
> 22/tcp open  ssh
> 80/tcp open  http
> MAC Address: 11:11:11:33:55:CD (Cadmus Computer Systems)
>
> Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds
>
>
> I have configured the Target to "Consider Alive"
>
>
> So, is there anything else to do? I restarted the services and no way.
>
>
> Thanks,
>
>
> Diego
>
>
> _______________________________________________
> 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