Also just noticed, if I try to run it manually, it does the same thing unless I 
remove the schedule. Once the schedule is removed from the task, it runs fine. 
:/

Scott Knauss
[email protected]

ITS
Immauss Technology Solutions
It's about solutions
https://www.immauss.com <https://www.immauss.com/>




> On Jan 18, 2018, at 7:18 AM, Scott Knauss <[email protected]> wrote:
> 
> Forgot to include the relevant entries from openvasmd.log
> 
> Curiously, the time stamps in openvasmd.log are in EST, while the time stamps 
> in opennessd.log are in UTC.
> 
> 
> 
> event task:MESSAGE:2018-01-15 00h30.06 EST:8206: Task mytaks.linux.monthly 
> (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) could not be resumed by admin
> event task:MESSAGE:2018-01-15 00h30.07 EST:8206: Status of task 
> mytaks.linux.monthly (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has changed to 
> Requested
> event task:MESSAGE:2018-01-15 00h30.07 EST:8206: Task mytaks.linux.monthly 
> (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has been requested to start by admin
> event task:MESSAGE:2018-01-15 00h30.13 EST:8209: Status of task 
> mytaks.linux.monthly (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has changed to 
> Running
> event task:MESSAGE:2018-01-15 00h30.22 EST:8215: Status of task 
> mytaks.linux.monthly (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has changed to 
> Stop Requested
> event task:MESSAGE:2018-01-15 00h30.22 EST:8215: Task mytaks.linux.monthly 
> (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has been requested to stop by admin
> event task:MESSAGE:2018-01-15 00h30.22 EST:8209: Status of task 
> mytaks.linux.monthly (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has changed to 
> Stop Requested
> event task:MESSAGE:2018-01-15 00h31.33 EST:8209: Status of task 
> mytaks.linux.monthly (66d82ec3-8aa6-4b5d-9a80-9ef2d54b3b0f) has changed to 
> Stopped
> 
> 
>  
> Scott Knauss
> [email protected] <mailto:[email protected]>
> 
> ITS
> Immauss Technology Solutions
> It's about solutions
> https://www.immauss.com <https://www.immauss.com/>
> 
> 
> 
> 
>> On Jan 18, 2018, at 7:11 AM, Scott Knauss <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hello All,
>> 
>>      I’m trying to have all of my monthly scans scheduled. Unfortunately, 
>> every scan stops at 1%.  in openvassd.log , it appears the scan is started, 
>> then terminated by the client in less than 1 second. The Duration on this 
>> schedule item is set to 8 hours and if I run it manually, it finishes with 
>> no problem.  This is happening with 6 different tasks (All of them I have 
>> scheduled) so I expect it to be something system related, but have no idea 
>> where to look.  
>> 
>>      Any help would be greatly appreciated.
>> 
>> Thanks,
>> Scott
>> 
>> [Sun Jan 14 08:30:02 2018][1253] Reloading the scanner.
>> [Sun Jan 14 08:30:18 2018][1253] Finished reloading the scanner.
>> [Sun Jan 14 08:31:01 2018][30017] Client closed the communication
>> [Mon Jan 15 05:30:26 2018][8208] Starts a new scan. Target(s) : 10.1.101.2, 
>> 192.168.75.203, 192.168.75.255, with max_hosts = 20 and max_checks = 4
>> [Mon Jan 15 05:30:26 2018][8208] hosts_ordering: Random.
>> [Mon Jan 15 05:30:26 2018][8208] exclude_hosts: Skipped 0 host(s).
>> .....
>> [Mon Jan 15 05:30:26 2018][8208] Testing 10.1.101.31 (10.1.101.31) [8235]
>> [Mon Jan 15 05:30:26 2018][8208] Testing 192.168.75.21 (192.168.75.21) [8236]
>> [Mon Jan 15 05:30:26 2018][8208] Testing 10.1.101.240 (10.1.101.240) [8237]
>> [Mon Jan 15 05:30:26 2018][8208] Stopping the whole test (requested by 
>> client)
>> [Mon Jan 15 05:30:26 2018][8208] Stopping host 10.1.101.240 scan
>> .....
>> [Mon Jan 15 05:30:26 2018][8208] Stopping host 10.1.101.30 scan
>> [Mon Jan 15 05:30:26 2018][8208] Stopping host 192.168.75.25 scan
>> [Mon Jan 15 05:30:26 2018][8208] Stopping host 10.1.101.242 scan
>> [Mon Jan 15 05:30:26 2018][8208] Stopping host 10.1.101.28 scan
>> [Mon Jan 15 05:30:26 2018][8208] Stopping host 192.168.75.36 scan
>> [Mon Jan 15 05:30:35 2018][8231] Stopped scan wrap-up: Launching 
>> pre2008/scan_info.nasl (1.3.6.1.4.1.25623.1.0.19506)
>> [Mon Jan 15 05:30:35 2018][8231] Stopped scan wrap-up: Launching 
>> cpe_inventory.nasl (1.3.6.1.4.1.25623.1.0.810002)
>> ...
>> [Mon Jan 15 05:31:31 2018][8234] Stopped scan wrap-up: Launching 
>> Policy/gb_policy_cpe_ok.nasl (1.3.6.1.4.1.25623.1.0.103963)
>> [Mon Jan 15 05:31:31 2018][8234] Stopped scan wrap-up: Launching 
>> Policy/gb_policy_cpe_violation.nasl (1.3.6.1.4.1.25623.1.0.103964)
>> [Mon Jan 15 05:31:31 2018][8234] Stopped scan wrap-up: Launching 
>> 2013/gb_host_scanned_ssh.nasl (1.3.6.1.4.1.25623.1.0.103625)
>> [Mon Jan 15 05:31:31 2018][8234] Stopped scan wrap-up: Launching 
>> 2011/host_details.nasl (1.3.6.1.4.1.25623.1.0.103997)
>> [Mon Jan 15 05:31:31 2018][8208] Test complete
>> [Mon Jan 15 05:31:32 2018][8208] Total time to scan all hosts : 80 seconds
>> Scott Knauss
>> [email protected] <mailto:[email protected]>
>> 
>> ITS
>> Immauss Technology Solutions
>> It's about solutions
>> https://www.immauss.com <https://www.immauss.com/>
>> 
>> 
>> 
>> 
> 

_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to