Hi, Thank you for your help. I managed to resolve the issue back then, cloning and modifying the scan config template. Unfortunately after Monday update, I haven't been able to reproduce the "printer detection" situation (default scan configs obviously). The issue seems to have been resolved for me.
I am probably *getting off topic* here, but in case this helps in some way: Since then, the issue is that the scans take ages to complete(~20 hours for default: full and very deep), while sometimes it remains at 1% forever. High cpu usage (over 70% for every core during the scan ~ when it passes over 1%). I was thinking that I may be getting blocked by host provider's firewall and I tried with: *Maximum concurrently executed NVTs per host: 1Maximum concurrently scanned hosts: 1*which didn't change anything, as far as I can tell. My server is a debian Managed VPS at a2hosting. I set log_whole_attack=yes, but it didn't give me any usefull info, besides what I am attaching. On 7 May 2018 at 17:17, Christian Fischer <christian.fisc...@greenbone.net> wrote: > Hi, > > did you had a chance to re-scan your server with the updated feed to see > the extended output? > > Regards, > > On 30.04.2018 15:33, Stelios Barberakis wrote: > > thanks Christian > > > > On 28 April 2018 at 16:04, Christian Fischer < > > christian.fisc...@greenbone.net> wrote: > > > >> Hi, > >> > >> On 28.04.2018 01:30, Stelios Barberakis wrote: > >>> I apologise if this is a double post, but I think the previous one was > >>> not delivered. > >> > >> you can check the delivering status on your own if you browse the > >> mailing list archives available at: > >> > >> http://lists.wald.intevation.org/pipermail/openvas-discuss/ > >> > >> where you can see that your previous mail was delivered as well: > >> > >> http://lists.wald.intevation.org/pipermail/openvas-discuss/ > >> 2018-April/012012.html > >> > >>> Using the web UI, I can see the settings, including 'Exclude printers > >>> from scan' (screenshot attached in the link). > >>> > >>> but I can't find out *how to change it*. The configuration files > doesn't > >>> include any such option: > >> > >> The openvassd.conf is the wrong place you're looking at. You would need > >> to clone the "Full and Fast" scan configuration to be able to change > >> this setting. > >> > >> But instead of changing the scan configuration i'm quite interested in > >> why your server is detected as a printer. Starting with the next feed > >> update (around Monday next week) the following NVTs will print out the > >> reason why your system was detected as a printer: > >> > >> Do not scan printers > >> OID: 1.3.6.1.4.1.25623.1.0.11933 > >> > >> Do not print on AppSocket and socketAPI printers > >> OID: 1.3.6.1.4.1.25623.1.0.12241 > >> > >> It would be great if you could share the output of the NVTs either > >> privately or here at the mailing list. > >> > >> Thanks, > >> > >> > >> -- > >> > >> 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 > >> > > > > > > > > -- > > 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 > -- PGP key: http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x BF6EA91B7CBE3998
event task:MESSAGE:2018-05-09 18h28.50 UTC:4003: Status of task db_fast Clone 1 (a405659d-b021-4927-9dd8-7f20f0c8fc99) has changed to Stop Requested event task:MESSAGE:2018-05-09 18h28.50 UTC:4003: Task db_fast Clone 1 (a405659d-b021-4927-9dd8-7f20f0c8fc99) has been requested to stop by admin event task:MESSAGE:2018-05-09 18h29.51 UTC:4016: Status of task (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has changed to New event task:MESSAGE:2018-05-09 18h29.51 UTC:4016: Task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has been created by admin event task:MESSAGE:2018-05-09 18h30.01 UTC:4028: Status of task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has changed to Requested event task:MESSAGE:2018-05-09 18h30.01 UTC:4028: Task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has been requested to start by admin event task:MESSAGE:2018-05-09 18h30.12 UTC:4030: Status of task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has changed to Running md manage:WARNING:2018-05-09 20h31.38 utc:7175: sql_exec_internal: sqlite3_step failed: cannot start a transaction within a transaction md manage:WARNING:2018-05-09 20h31.38 utc:7175: sqlv: sql_exec_internal failed event task:MESSAGE:2018-05-09 20h32.04 UTC:7189: Status of task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has changed to Stop Requested event task:MESSAGE:2018-05-09 20h32.04 UTC:7189: Task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has been requested to stop by admin event task:MESSAGE:2018-05-09 20h32.05 UTC:4030: Status of task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has changed to Stop Requested event task:MESSAGE:2018-05-09 20h32.35 UTC:4030: Status of task db_deep (49a4f3b4-9683-44b5-8a7c-576a38d3f96e) has changed to Stopped event task:MESSAGE:2018-05-09 20h32.51 UTC:7218: Status of task (e6efd524-755d-46e6-bf0e-9d758517976a) has changed to New event task:MESSAGE:2018-05-09 20h32.52 UTC:7218: Task db_deep_defaults (e6efd524-755d-46e6-bf0e-9d758517976a) has been created by admin event task:MESSAGE:2018-05-09 20h33.00 UTC:7223: Status of task db_deep_defaults (e6efd524-755d-46e6-bf0e-9d758517976a) has changed to Requested event task:MESSAGE:2018-05-09 20h33.00 UTC:7223: Task db_deep_defaults (e6efd524-755d-46e6-bf0e-9d758517976a) has been requested to start by admin event task:MESSAGE:2018-05-09 20h33.09 UTC:7225: Status of task db_deep_defaults (e6efd524-755d-46e6-bf0e-9d758517976a) has changed to Running event task:MESSAGE:2018-05-10 12h37.42 UTC:7225: Status of task db_deep_defaults (e6efd524-755d-46e6-bf0e-9d758517976a) has changed to Done
openvasmd.log.1
Description: Binary data
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
