Jump to content
Tybilly

Virus scan task error [227627]

Recommended Posts

Hello,

 

Scenario is the following:

- A group virus scan task is configured with the option "Suspend scheduled scanning when the screensave is off and the computer is unlocked".

- The task starts properly on the managed host according to the schedule.

- During task execution, user decides to shutdown the operating system of the managed host.

- In the meantime, scan task has the "Paused for X computers" status

- Next time the managed host starts, status of the virus scan task is updated and displayed as "Completed". Moreover an "Error = 80380fbb" (which is not very clear) is displayed in the "Description" field of task results:

post-1491-1412868820_thumb.png

 

This is a problem because the administrator could be mislead regarding the fact that the scan has been done completely.

 

Expected behavior:

- Task gets the "Returned error on X computers" status right after the computer shutdown.

- Error message returned in the "Description" field is more explicit such as : "Task has been stopped by user".

 

You can easily reproduce this, let me know if you need logs though.

 

Thank you.

Share this post


Link to post

Hi,

 

Thank you for that info.

 

Could you please collect traces at the local host and at admin server simultaneously while this issue reoccurs?

 

Thank you!

Share this post


Link to post

Hi,

 

File "ScanTaskError80380fbb.rar" has been uploaded onto data8 FTP server with requested traces, event logs, gsi reports, export of task and its results.

Scan task was scheduled to run once on 10.10.2014 at 15:39:00

 

Thank you.

Share this post


Link to post
Hi,

 

File "ScanTaskError80380fbb.rar" has been uploaded onto data8 FTP server with requested traces, event logs, gsi reports, export of task and its results.

Scan task was scheduled to run once on 10.10.2014 at 15:39:00

 

Thank you.

 

Hi,

 

Do I understand correctly that the issue is about displaying completed status along with the error message or the task itself does not get completed after the restart?

 

Thank You!

Share this post


Link to post

Hi,

 

Do I understand correctly that the issue is about displaying completed status along with the error message or the task itself does not get completed after the restart?

 

The issue is the task has the "Completed" status although the scan task has been stopped, this is confusing for the Administrator.

Correct statut should be "Error".

 

Fact that the task does not get completed after the restart is a feature request which I know has already been submitted.

 

Thank you.

 

Share this post


Link to post
Hi,

The issue is the task has the "Completed" status although the scan task has been stopped, this is confusing for the Administrator.

Correct statut should be "Error".

 

Fact that the task does not get completed after the restart is a feature request which I know has already been submitted.

 

Thank you.

 

 

Thank You for the information provided.

Share this post


Link to post

Hello,

 

The error "80380fbb" described along with the wrong task behaviour remain with KSC10/KES10 SP1 beta2.

 

Thank you.

Share this post


Link to post
Hello,

 

The error "80380fbb" described along with the wrong task behaviour remain with KSC10/KES10 SP1 beta2.

 

Thank you.

 

 

Thanks.

Share this post


Link to post

Hello,

 

Using KSC10 & KES10 SP1 beta3, the behavior has changed but it is still incorrect.

 

If the managed computer is restarted while a scan is running (and paused), then scan task is marked as "Task stopped" but its status is still "Paused":

post-1491-1417513951_thumb.png

 

If the managed computer is stopped while a scan is running (and paused) and later on it is started, then scan task is marked as "Task stopped" and its status is "Completed".

post-1491-1417514262_thumb.png

 

Finally, no more error "80380fbb" in the description field but scan task still has the wrong status in both cases: when the managed computer is stopped or restarted while a scan task is running.

 

Expected behavior:

- Task gets the "Returned error on X computers" status right after the computer shutdown.

- Error message returned in the "Description" field is more explicit such as : "Task has been stopped due to system shutdown"

 

Thank you.

Share this post


Link to post
Hello,

 

Using KSC10 & KES10 SP1 beta3, the behavior has changed but it is still incorrect.

 

If the managed computer is restarted while a scan is running (and paused), then scan task is marked as "Task stopped" but its status is still "Paused":

HostRestarted.png

 

If the managed computer is stopped while a scan is running (and paused) and later on it is started, then scan task is marked as "Task stopped" and its status is "Completed".

HostStopped.png

 

Finally, no more error "80380fbb" in the description field but scan task still has the wrong status in both cases: when the managed computer is stopped or restarted while a scan task is running.

 

Expected behavior:

- Task gets the "Returned error on X computers" status right after the computer shutdown.

- Error message returned in the "Description" field is more explicit such as : "Task has been stopped due to system shutdown"

 

Thank you.

 

Hello.

 

A new bug 227627 created for the mentioned issues.

 

Thank you.

 

Share this post


Link to post

Developers require additional info for bug 227627:

 

Nagent tracefiles $klnagent-1103.log and $klnagent-1103.log.bak from the problem managed computer are required while the problem is reproduced:

 

1. Turn on Nagent tracing of level 4 on the managed computer X

1. Pause the task "Virus scan" and wait until it is chaged its status to "paused" for the managed computerX in the Administration Console (as it is in the screenshot)

2. Reboot managed computer X

3. Ait until the problem is reproduced (" later on it is started, then scan task is marked as "Task stopped" and its status is "Completed"")

4. Turn off nagent tracing and provide files $klnagent-1103.log and $klnagent-1103.log.bak from the host X.

 

Thank you.

Share this post


Link to post
Developers require additional info for bug 227627:

 

Nagent tracefiles $klnagent-1103.log and $klnagent-1103.log.bak from the problem managed computer are required while the problem is reproduced:

 

1. Turn on Nagent tracing of level 4 on the managed computer X

1. Pause the task "Virus scan" and wait until it is chaged its status to "paused" for the managed computerX in the Administration Console (as it is in the screenshot)

2. Reboot managed computer X

3. Ait until the problem is reproduced (" later on it is started, then scan task is marked as "Task stopped" and its status is "Completed"")

4. Turn off nagent tracing and provide files $klnagent-1103.log and $klnagent-1103.log.bak from the host X.

 

Thank you.

 

1. Ok done

2. In the scenario described I'm not pausing the task, it is done automatically thanks to the option "Suspend scheduled scanning when the screensaver is off and the computer is unlocked".

3. As I described in my last message, for the task to get status "completed" managed host has to be stopped and later on started. If the host is rebooted then status is different.

 

Logs are available on the FTP server: NetworkAgentLogs.zip

 

Thank you.

 

Share this post


Link to post
1. Ok done

2. In the scenario described I'm not pausing the task, it is done automatically thanks to the option "Suspend scheduled scanning when the screensaver is off and the computer is unlocked".

3. As I described in my last message, for the task to get status "completed" managed host has to be stopped and later on started. If the host is rebooted then status is different.

 

Logs are available on the FTP server: NetworkAgentLogs.zip

 

Thank you.

 

 

Hello.

 

 

Thank You for the information provided.

 

We have handed it to the specialists.

 

Thanks.

Share this post


Link to post

Hello,

 

The case seems to be blocked on your side.

Would you please let me know if there is any update?

 

Thank you.

Share this post


Link to post

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.