Hi,

There seems to be enough memory.
[root@etvas8r4 ~]# free
              total        used        free      shared  buff/cache
available
Mem:        3882052     1497340      721696      102084     1663016
1941572
Swap:       4063228      239012     3824216
[root@etvas8r4 ~]#

The logs dont display anything new - attached openvasmd.log file

Also, tried and tested deleting the redis dump and restarted services.
Still no luck. The scanner service is still getting stuck.

Regards,
Harsh


On Wed, Jun 28, 2017 at 10:07 PM, Christian Fischer <
[email protected]> wrote:

> Hi,
>
> On 28.06.2017 17:14, Harsh kapadia wrote:
> > Hi,
> >
> > I am running openVAS 9 and the openvas scanner service is timing out -
> > because of this, I cannot run reports.
> >
> > The openvas-check-setup show everything is OK. Below is the error I see
> > when the services dont start up:
> > Redirecting to /bin/systemctl start  openvas-scanner.service.service
> > Job for openvas-scanner.service failed because a timeout was exceeded.
> > See "systemctl status openvas-scanner.service" and "journalctl -xe" for
> > details.
> >
> > Have attached the "journalctl - xe " output as well.
> >
> > Please suggest on this. There's no further info available online
> > regarding this issue.
> >
> > Thanks in advance!
> > Harsh
>
> most likely the known issue where redis is blocking any access by the
> scanner due to unknown reasons. This should do the trick:
>
> 1. Delete dump.rdb (somewhere in /var/run/redis or similar)
> 2. Comment out/remove all "save xy z" (e.g. save 900 1) from your
> redis.conf
> 3. restart redis
> 4. restart scanner and try again
>
> Regards,
>
> --
>
> Christian Fischer | PGP Key: 0x54F3CE5B76C597AD
> Greenbone Networks GmbH | http://greenbone.net
> Neumarkt 12, 49074 Osnabrück, Germany | AG Osnabrück, HR B 202460
> Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner
> _______________________________________________
> Openvas-discuss mailing list
> [email protected]
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
event task:MESSAGE:2017-06-28 05h51.28 UTC:2855: Status of task Immediate scan 
of IP localhost (09e98fe5-58ad-4e69-9a9f-65076b158823) has changed to Requested
event task:MESSAGE:2017-06-28 05h51.28 UTC:2855: Task Immediate scan of IP 
localhost (09e98fe5-58ad-4e69-9a9f-65076b158823) has been requested to start by 
etvasadmin
event task:MESSAGE:2017-06-28 05h53.05 UTC:2968: Status of task Immediate scan 
of IP 192.168.1.42 (bb3f5204-4038-4def-ad39-b72e24a197a4) has changed to 
Requested
event task:MESSAGE:2017-06-28 05h53.06 UTC:2968: Task Immediate scan of IP 
192.168.1.42 (bb3f5204-4038-4def-ad39-b72e24a197a4) has been requested to start 
by etvasadmin
md   main:MESSAGE:2017-06-28 05h53.39 utc:3074:    OpenVAS Manager version 
7.0.1 (DB revision 184)
md manage:   INFO:2017-06-28 05h53.39 utc:3074:    Getting users.
md   main:WARNING:2017-06-28 05h59.20 UTC:2856: openvas_scanner_read: Failed to 
read from scanner: Connection reset by peer
event task:MESSAGE:2017-06-28 05h59.20 UTC:2856: Status of task Immediate scan 
of IP localhost (09e98fe5-58ad-4e69-9a9f-65076b158823) has changed to Stopped
md   main:WARNING:2017-06-28 05h59.20 UTC:2969: openvas_scanner_read: Failed to 
read from scanner: Connection reset by peer
event task:MESSAGE:2017-06-28 05h59.20 UTC:2969: Status of task Immediate scan 
of IP 192.168.1.42 (bb3f5204-4038-4def-ad39-b72e24a197a4) has changed to Stopped
md   main:   INFO:2017-06-28 07h57.48 utc:8105:    internal NVT cache update
md   main:   INFO:2017-06-28 07h57.48 utc:8105: rebuild_nvt_cache_retry: 
Reloading NVT cache
md   main:   INFO:2017-06-28 07h57.48 utc:8106: update_or_rebuild_nvt_cache: 
Updating NVT cache
md   main:   INFO:2017-06-28 07h57.48 utc:8106:    Updating NVT cache.
md   main:MESSAGE:2017-06-28 07h58.04 utc:8201:    OpenVAS Manager version 
7.0.1 (DB revision 184)
md manage:   INFO:2017-06-28 07h58.04 utc:8201:    Getting users.
md   main:WARNING:2017-06-28 07h58.49 utc:8106: openvas_scanner_read: Failed to 
read from scanner: Connection reset by peer
md   main:MESSAGE:2017-06-28 07h58.58 utc:8609:    OpenVAS Manager version 
7.0.1 (DB revision 184)
base gpgme:MESSAGE:2017-06-28 07h58.58 utc:8610: Setting GnuPG dir to 
'/var/lib/openvas/openvasmd/gnupg'
base gpgme:MESSAGE:2017-06-28 07h58.58 utc:8610: Using OpenPGP engine version 
'2.0.22'
md  crypt:WARNING:2017-06-28 08h03.19 UTC:10370: error decrypting credential: 
Decryption failed <GPGME>
md  crypt:   INFO:2017-06-28 08h03.19 UTC:10370:    encrypted to keyid 
CE9F4B1E1A6A3C7B, algo=1: No secret key <GPGME>
md   main:MESSAGE:2017-06-28 08h04.41 utc:10570:    OpenVAS Manager version 
7.0.1 (DB revision 184)
md manage:   INFO:2017-06-28 08h04.41 utc:10570:    Checking alerts.
[root@etvas8r4 openvas]#
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to