Hi Christian,

Yes, actually the openvassd.log did not show anything.

I waited and retried deleting the redis dump file and restarting the
service. This resolved the issue! The service started and is scanning
successfully now.

Thanks a lot for your help!

Regards,
Harsh


On Wed, Jun 28, 2017 at 11:43 PM, Christian Fischer <
christian.fisc...@greenbone.net> wrote:

> Hi,
>
> On 28.06.2017 18:56, Harsh kapadia wrote:
> > 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
>
> this is the manager logfile (openvasMd) which probably doesn't contain
> any information as you have an issue with the scanner (openvasSd).
>
> > 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
> > <christian.fisc...@greenbone.net
> > <mailto:christian.fisc...@greenbone.net>> 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
>
> --
>
> 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
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to