This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed to get Scanner Instance

Have an ASG 220 with Current firmware version of 7.501. Our HTTP profile includes dual a/v scanning. For the first time today, we get the error 'failed to get scanner instance'. I saw this post in the beta forum and disabling and re-enabling the a/v did not work. I have disabled a/v scanning for now so that users can access the web, but that is a temporary workaround.

Do I need to restart the box (uptime is only 17d 20h 30m)? Any other ideas?

Sending this to support as well, but want to make any answer available to everyone.

This thread was automatically locked due to age.

Parents

0 Jim Tagert over 16 years ago

I did not scan all of the postd, but this is the error. If someone has already posted it, then so be it.

Is there a solution...NOT A WORK AROUND.

2009:11:30-15:36:10 IPA-XX-XX-XX-XX httpproxy[4014]: [ (nil)] avira_get_instance (avirascanner.c:175) Avira create instance failed (return code 3)
2009:11:30-15:36:10 IPA-XX-XX-XX-XX httpproxy[4014]: [ (nil)] avira_get_instance (avirascanner.c:276) Error while releasing instance: One of supplied parameters was invalid
2009:11:30-15:36:10 IPA-XX-XX-XX-XX httpproxy[4014]: [ 0x808ac90] avira_scan (avirascanner.c:324) failed to get scanner instance
Cancel
Vote Up 0 Vote Down

Cancel
0 jaredclarke over 16 years ago in reply to Jim Tagert

The solution is on it's way in pattern version 11179 according to Jack.
Cancel
Vote Up 0 Vote Down

Cancel
0 Jim Tagert over 16 years ago in reply to jaredclarke

Thanks Jared...see above
Cancel
Vote Up 0 Vote Down

Cancel
0 skumpe over 16 years ago in reply to Jim Tagert

According to Regina, the fix will be pushed out within the next 1-2 hrs
Cancel
Vote Up 0 Vote Down

Cancel
0 Lemo over 16 years ago in reply to skumpe

According to Regina, the fix will be pushed out within the next 1-2 hrs

As an Avira update or Astaro firmware?
Cancel
Vote Up 0 Vote Down

Cancel
0 Jim Tagert over 16 years ago in reply to Jim Tagert

I don't know if this has been posted yet or not, but if one disables only the AV in the web-proxy then the internet is available. The ENTIRE web-proxy does NOT have to be disabled.

Jack does this affect incoming email as well? I think that this is something we all should know...

I have disabled pre-fetch until my question is answered.

Will someone please answer the question?
Cancel
Vote Up 0 Vote Down

Cancel
0 Jack Daniel over 16 years ago in reply to Jim Tagert

I do not have any more details yet, but we are working on it and I assure you the significance is understood.

We expect the 11179 pattern out within a couple of hours, it would be faster but extra testing is being done for obvious reasons.

Jack
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Jack Daniel over 16 years ago in reply to Jim Tagert

I do not have any more details yet, but we are working on it and I assure you the significance is understood.

We expect the 11179 pattern out within a couple of hours, it would be faster but extra testing is being done for obvious reasons.

Jack
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 jchamp over 16 years ago in reply to Jack Daniel

For me at least, disabling the AV isn't a complete solution. Some sites still appear with the original error. I've cleared cache, both local and on the Astaro. My guess is that these sites were being accessed while the defective AV was still active. So, partial work-around, but still issues.
Cancel
Vote Up 0 Vote Down

Cancel
0 gnujuba over 16 years ago in reply to Jack Daniel

I'll leave AV scanning on - and go to bed now - hopefully everythings fine when I wake up [;)]
Cancel
Vote Up 0 Vote Down

Cancel
0 Jim Tagert over 16 years ago in reply to gnujuba

Murphy's Law states in this case, that if an AV def should go bad, then it will be on the primary AV so scanning with the secondary AV only, will be impossible...
Cancel
Vote Up 0 Vote Down

Cancel