Openvas-check-setup is only shell script for testing setup, no need to update it.
Openvas works fine on centos . I have used it in production for very long time. Remember to allocate enought memory for openvas, at least 3gb. Depending number of targets. Eero Eero 9.9.2015 6.14 ip. "Paul J" <[email protected]> kirjoitti: > Eero, you’re right again! The scans are working well, but the real test > is when I give it to my 50 students to see if they have any problems. Kali > was very hit and miss on being able to do credentialed scans, I hope this > works better. And I do see that Atomic is fully up to date, except for > openvas-check-setup which is currently is 2.3.0 but the latest is 2.3.3. > > > > I wonder if I should update this? > > > > paul > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Eero Volotinen > *Sent:* Wednesday, September 09, 2015 1:02 AM > *To:* Paul J <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [Openvas-discuss] FIX: You should start the redis-server > or configure it to listen on socket: /tmp/redis.sock > > > > That might be bug in atomic package.try to ignore it and test it if really > works. > > Eero > > 9.9.2015 11.00 ap. "Paul J" <[email protected]> kirjoitti: > > Great, thanks, that’s what I changed them to so I’ll leave them. > > > > Any idea with my new problem on why it’s complaining that I need to Start > OpenVAS Manager (openvasmd) when ps says it’s running? > > > > paul > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Eero Volotinen > *Sent:* Wednesday, September 09, 2015 12:52 AM > *To:* Paul J <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [Openvas-discuss] FIX: You should start the redis-server > or configure it to listen on socket: /tmp/redis.sock > > > > HI, > > > > You need to enable following lines in /etc/redis.conf (meaning that you > need to remove '#' character) > > > > *unixsocket* /tmp/redis.sock > > *unixsocket*perm 700 > > > > and then run command systemctl restart *redis*.service > > > > Eero > > > > 2015-09-09 10:46 GMT+03:00 Paul J <[email protected]>: > > Thanks Eero! > > > > Should I run both > > systemctl restart redis.service -and- > > systemctl restart redis-sentinel.service? > > > > Do these have to be run each time I restart? > > > > Should I change the settings in redis.conf back? (Comment back out > unixsocket /tmp/redis.sock and unixsocketperm 700 or leave them the say way > as shown in > http://lists.wald.intevation.org/pipermail/openvas-devel/2014-April/003380.html > ? > > > > The next issue is: > > > > ERROR: OpenVAS Manager is NOT running! > > FIX: Start OpenVAS Manager (openvasmd). > > > > However: > > ps -aux | grep openvasmd > > root 1368 0.0 3.6 247968 68176 ? SL 00:11 0:00 openvasmd > > > > So it is running, right? > > > > paul > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Eero Volotinen > *Sent:* Wednesday, September 09, 2015 12:29 AM > *To:* Paul J <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [Openvas-discuss] FIX: You should start the redis-server > or configure it to listen on socket: /tmp/redis.sock > > > > You need to manually configure redis correctly and restart service with > command like systemctl restart redis.service (you can get service name from > command systemctl list-unit-files |grep redis) > > > > I think this was already fixed in atomic repo, but looks like is not fixed > yet. > > > > -- > > Eero > > > > 2015-09-09 10:25 GMT+03:00 Paul J <[email protected]>: > > Trying to install OpenVAS on CentOS, installation looks good, except when > I run: > > > > openvas-check-setup > > > > I get: > > > > OK: redis-server is present in version v=2.8.21. > > OK: scanner (kb_location setting) is configured properly using the > redis-server socket: /tmp/redis.sock > > ERROR: redis-server is not running or not listening on socket: > /tmp/redis.sock > > FIX: You should start the redis-server or configure it to listen > on socket: /tmp/redis.sock > > ERROR: Your OpenVAS-8 installation is not yet complete! > > Please follow the instructions marked with FIX above and run this script > again. > > > > > > I’m using the redis.conf settings from here: > > > http://lists.wald.intevation.org/pipermail/openvas-devel/2014-April/003380.html > > > > Which is basically: > > > > port 0 > > unixsocket /tmp/redis.sock > > unixsocketperm 700 > > timeout 0 > > > > I don’t see the socket in the filemanager, so it doesn’t look like it has > been started. > > > > And ps -aux | grep redis is blank except for the grep command. > > > > Someday I’ll get this working! > > > _______________________________________________ > 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 > > > > > _______________________________________________ > 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 >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
