An SDR request timeout occurred

[Beatschaer]

Hi all

since we have updatet to 12.0 release we become follow message:

The Warning message is:

The sender domain reputation lookup failed.

Reason : An SDR request timeout occurred.

 If you see consecutive SDR request timeouts, make sure that your appliance is able to connect to the SDR service.

Version: 12.0.0-419

Serial Number: 423E3DD279159FD27A47-7B6565737FD8

Timestamp: 14 Feb 2019 11:09:11 +0100

In network has no changed.

Any ideas?

THX

[BrianRoberson]

Same issue - since v12 upgrade.  Any solutions Cisco?

[florian.reber]

So, why are you constantly sending alerts for an expected behaviour? In my understanding, alerts are for unexpected behaviour, not for expected one!

How are we supposed to monitor the device with continous bogus alerts for expected behaviour?

[medievalist]

Cisco has added some very useful features since buying Ironport, but unfortunately they've an ongoing history of underprovisioning the back end.  A new release comes out, and the errors start streaming in...  eventually it will get sorted, but if the past is any guide, it won't be quick.

[florian.reber]

... and unfortunately they've an ongoing history of implementing new features in a way that throw a lot of alarm mails in General Deployment Releases, and only then finetune after productive customers get loads of false alerts ...

[agena-netzwerk]

meanwhile I also set the timeout to 10sec. and still get timeouts. 

Is there any status cisco can give us or should we all open a case to give this priority?

Best Regards,

Tim

[dmccabej]

Sorry that I missed some of the recent responses. It looks like notifications from the forums was down for a bit and I wasn't aware people were requesting additional information. 

As an update to everyone, I recently filed a defect for tracking (https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo94464), and this issue is now being worked on with high urgency from both the ESA engineering and SDR (Talos) teams. 

If you wish to add a sighting to the defect for added visibility, or if increasing the timeout does not seem to be helping, then please open a TAC case and we can help take a look.

Thanks!

-Dennis M.

[agena-netzwerk]

I opened a case, keeped it open, pointing to the bug CSCvo94464.
And I also pushed the button "I have this problem too" on the first post here, to give this bug more attention.

Actual there are just 28 open cases regarding this issue so it has a Severity: 3 Moderate.

When I ping the service page v2.sds.cisco.com i get time outs.

May be that's a german thing, but sorry that's a service I pay for...

[denny_strijdonck]

Getting the same alert after upgrading to 12.0.0-419. Seems there is no fix yet?

Yet in the bug page (https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo94464) I can find the following:

Status: Fixed

Severity: 3 Moderate

[agena-netzwerk]

I got an Update "12.1.0-071" about a week ago. Since then the alerts stopped.

Closing my case now.

Best Regards,

Tim

[dmccabej]

Hello,

Yes, they've decided to instead suppress the alerts in 12.1 while we work on balancing and increasing resources on the server end. Until those efforts have completed, this is, unfortunately, going to be an intermittent issue. If interested, you can still track the timeouts through the mail and/or SDR logs. 

Thanks!

-Dennis M.

[dmccabej]

Hello,

Fixed just means that we've found a way to resolve the behavior in the code, but have yet to deploy it via a public code branch. What you'll want to do is keep an eye on the Known Fixed Releases section.

Thanks!

-Dennis M.

[srfndoc]

Same issue here.  I see its sort of fixed in 12.1 (suppressed) and I've subscribed to the bug in case they update it to note the updated infrastructure has been added.