Confirmed these settings are still in redis, from here 
https://forums.atomicorp.com/viewtopic.php?f=31&t=8539#p44057 :
6) edit /etc/redis.conf. Add/uncomment the following
unixsocket /tmp/redis.sock
unixsocketperm 700

From File:
# Specify the path for the Unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
unixsocket /tmp/redis.sock
unixsocketperm 700


The logs have archived, so I rebooted the server and kicked off a scan (error 
still occurred)
from the logs – gsad.log:
gsad main:MESSAGE:2017-06-12 11h18.45 utc:3287: Starting GSAD version 7.0.2
gsad xslt:WARNING:2017-06-12 11h18.45 utc:3287: init_language_lists: Failed to 
open locale directory "/usr/share/openvas/gsa/locale": No such file or directory
gsad main:WARNING:2017-06-12 11h23.40 utc:3288: MHD: Failed to receive data: 
The TLS connection was non-properly terminated.
gsad main:WARNING:2017-06-12 11h23.41 utc:3288: MHD: Failed to receive data: 
The TLS connection was non-properly terminated.
gsad main:WARNING:2017-06-12 11h30.34 utc:3288: MHD: Failed to receive data: 
The TLS connection was non-properly terminated.


  *   There are several of the TLS connection message

from the logs – openvasmd.log:
md   main:MESSAGE:2017-06-12 11h18.45 utc:3285:    OpenVAS Manager version 
7.0.1 (DB revision 184)
base gpgme:MESSAGE:2017-06-12 11h18.59 utc:3286: Setting GnuPG dir to 
'/var/lib/openvas/openvasmd/gnupg'
base gpgme:MESSAGE:2017-06-12 11h18.59 utc:3286: Using OpenPGP engine version 
'2.0.22'
event task:MESSAGE:2017-06-12 11h39.32 UTC:4419: Status of task Localhost 
(d40618d9-0bad-4dea-8a03-199375f506a9) has changed to Requested
event task:MESSAGE:2017-06-12 11h39.32 UTC:4419: Task Localhost 
(d40618d9-0bad-4dea-8a03-199375f506a9) has been requested to start by [username]
md manage:   INFO:2017-06-12 11h39.33 UTC:4420: nvt_selector_plugins: NVTs not 
explicitly activated anymore for this config: 
1.3.6.1.4.1.25623.1.0.10265;1.3.6.1.4.1.25623.1.0.103914;1.3.6.1.4.1.25623.1.0.103978;1.3.6.1.4.1.25623.1.0.95888;1.3.6.1.4.1.25623.1.0.12241;1.3.6.1.4.1.25623.1.0.11933;1.3.6.1.4.1.25623.1.0.12288;1.3.6.1.4.1.25623.1.0.80010;1.3.6.1.4.1.25623.1.0.810010;1.3.6.1.4.1.25623.1.0.10870;1.3.6.1.4.1.25623.1.0.80011;1.3.6.1.4.1.25623.1.0.103585;1.3.6.1.4.1.25623.1.0.103697;1.3.6.1.4.1.25623.1.0.100509;1.3.6.1.4.1.25623.1.0.80104;1.3.6.1.4.1.25623.1.0.80086;1.3.6.1.4.1.25623.1.0.900238;.
 Please adjust the config if you think this is wrong.
md   main:WARNING:2017-06-12 11h58.48 UTC:4420: openvas_scanner_read: Failed to 
read from scanner: Connection reset by peer
event task:MESSAGE:2017-06-12 11h58.48 UTC:4420: Status of task Localhost 
(d40618d9-0bad-4dea-8a03-199375f506a9) has changed to Stopped


from the log – openvassd.log:
[Mon Jun 12 10:58:04 2017][26584] Failed to initialize nvti cache.

– this is the same error I saw last week, I have tried, willing to retry any of 
these as needed:

  *   Restarting the services
  *   openvasmd --update && openvasmd –rebuild to rebuild the cache – this 
seemed to work, however the scanner still seems down, maybe I need to do it 
again?
  *   Updating the server
  *   openvas-setup – to fix any issues
  *   confirmed verifying scanner works


Dan Beal
SILA
M: 571.439.9230

From: eero.t.voloti...@gmail.com [mailto:eero.t.voloti...@gmail.com] On Behalf 
Of Eero Volotinen
Sent: Monday, June 12, 2017 3:24 AM
To: Dan Beal <db...@silasg.com>
Cc: openvas-discuss@wald.intevation.org
Subject: Re: [Openvas-discuss] OpenVAS not scanning when check setup appears to 
be OK

well. that sounds like redis-server is not correctly configured.
Please also check out the logs of openvas.

Eero

2017-06-12 10:17 GMT+03:00 Dan Beal <db...@silasg.com<mailto:db...@silasg.com>>:
Thanks. Jobs will get "stopped at 1%" not just take a while, they get stopped.
Thanks,
Dan

571.439.9230
Sent from my mobile device, please excuse errors and brevity.

On Jun 12, 2017 2:28 AM, Eero Volotinen 
<eero.voloti...@iki.fi<mailto:eero.voloti...@iki.fi>> wrote:
Scan can take long time depending on scan settings, network, firewall and the 
scanner.

run following command on root terminal on openvas:

ps aux |grep -i openvas

and

ps aux |grep -i nmap

If you see multiple lines then scanning is still on processing., just wait 
until it's ready.

--
Eero

2017-06-09 22:03 GMT+03:00 Dan Beal <db...@silasg.com<mailto:db...@silasg.com>>:

Good Afternoon,



We are attempting to use OpenVAS for security scanning – scans are not working, 
stopping at 1%.  The check comes back with everything is ok.  I cannot find 
anything online about what could be causing this.



Dan Beal

SILA

M: 571.439.9230

<http://www.silasg.com/>

 <http://www.silasg.com/>

This communication may contain proprietary or other confidential information 
intended for a specific individual and purpose, and is protected by law. If you 
are not the intended recipient, you should delete this message. Any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.<http://www.silasg.com/>

_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss<http://www.silasg.com/>
 <http://www.silasg.com/>
 <http://www.silasg.com/>

This communication may contain proprietary or other confidential information 
intended for a specific individual and purpose, and is protected by law. If you 
are not the intended recipient, you should delete this message. Any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.<http://www.silasg.com/>
 <http://www.silasg.com/>

This communication may contain proprietary or other confidential information 
intended for a specific individual and purpose, and is protected by law. If you 
are not the intended recipient, you should delete this message. Any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to