Re: [Openvas-discuss] OpenVAS not scanning when check setup appears to be OK

Ok, some idea’s to help further trouble shooting: · Can you verify that /tmp/redis.sock is actually really there? (ls the /tmp folder). · Try starting a scan after manually starting openvassd with --f (foreground) and see what it does/says · Start openvassd with

Re: [Openvas-discuss] sql errors

I am also on version 3 of the SQLite...not sure if that makes a difference or if OpenVAS uses version 2. Installed Packages Name: sqlite Arch: x86_64 Version : 3.7.17 Release : 8.el7 Size: 795 k Repo: installed From repo : anaconda Summary : Library

Re: [Openvas-discuss] sql errors

Luckily, this server doesn’t do anything else besides OpenVAS and most of my files are already backed up so really I am up for trying anything at this point. -Original Message- From: Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org] On Behalf Of Reindl Harald Sent:

Re: [Openvas-discuss] sql errors

Am 12.06.2017 um 15:38 schrieb Brandon Perry: On Jun 12, 2017, at 8:33 AM, Thijs Stuurman > wrote: No, never. These are also the kind of errors I never ever wish to see! If your data is still there, scan tasks

Re: [Openvas-discuss] OpenVAS not scanning when check setup appears to be OK

Are you sure your openvas certificate is OK? Not expired or anything? Make a backup (if you care for your current certs) and make ‘m again “openvas-manage-certs -a”. Thijs Stuurman Security Operations Center | KPN Internedservices

Re: [Openvas-discuss] sql errors

> On Jun 12, 2017, at 8:33 AM, Thijs Stuurman > wrote: > > No, never. These are also the kind of errors I never ever wish to see! > > If your data is still there, scan tasks .. history etc’ I strongly urge you > to make a backup and repeat making backups

Re: [Openvas-discuss] OpenVAS not scanning when check setup appears to be OK

Confirmed these settings are still in redis, from here https://forums.atomicorp.com/viewtopic.php?f=31=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

Re: [Openvas-discuss] sql errors

No, never. These are also the kind of errors I never ever wish to see! If your data is still there, scan tasks .. history etc' I strongly urge you to make a backup and repeat making backups just in case. Many things can cause these errors, I cannot give you any specific place to start looking

[Openvas-discuss] sql errors

Does anyone else get these as well? In my openvasmd.log I get this quite often. It appears when this happens my scans never seem to finish properly and things just get out of sorts. event task:MESSAGE:2017-06-08 08h00.13 EDT:25517: Task network_device_91 (3b792a23-25ab-459c-90db-2eb880099898)

Re: [Openvas-discuss] OpenVAS not scanning when check setup appears to be OK

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 wrote: Scan can take long time depending on scan settings,

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 : > Thanks. Jobs will get "stopped at 1%" not just take a while, they get > stopped. > > Thanks, > Dan > > 571.439.9230 > Sent

[Openvas-discuss] OpenVAS not scanning when check setup appears to be OK

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

[Openvas-discuss] BUG?: check_omp - override switch not working as expected

Hi all, I recently upgraded openvas from v8 to v9. We monitor the scan results with check_omp from icinga/check_mk. False positives are filtered via overrides by openvas. Before the upgrade, check_omp showed the correct results, including the applied overrides. After the upgrade the