You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we get the error "Unable to work with domain doc " the system never changes the doc and SFN keeps picking it up. Eventually, if you get enough of these, all the system does it pick up docs that it can't process and continuously tries to pick them up so nothing else ever gets processed.
Looks like something similar to issues I used to have previously:
[ERROR] : 2018-12-29 06:29:26,391 : dnsutils:getDomainDoc:[515]:140384644908800 : Unable to work with domain doc vlwcmgb48.ecfwg.xyz - 'filetype'
[DEBUG] : 2018-12-29 06:29:26,391 : dnsutils:getDomainDoc:[518]:140384644908800 : getDomainDoc() returns: NULL
[DEBUG] : 2018-12-29 06:29:26,392 : runner:searchDomain:[145]:140384644908800 : domainDoc is NULL
[ERROR] : 2018-12-29 06:29:26,392 : runner:searchDomain:[150]:140384644908800 : Unable to process event pmaM-GcBxraJFJddcjut beacause of problem with domain-doc for vlwcmgb48.ecfwg.xyz
[ERROR] : 2018-12-29 06:29:26,392 : runner:searchDomain:[151]:140384644908800 : Domain doc for vlwcmgb48.ecfwg.xyz
I think it would make sense to put a check against this type of errors in code and prevent a domain from requesting autofocus response. It just doesn’t allow other domains to be checked :-(. ```
The text was updated successfully, but these errors were encountered:
When we get the error "Unable to work with domain doc " the system never changes the doc and SFN keeps picking it up. Eventually, if you get enough of these, all the system does it pick up docs that it can't process and continuously tries to pick them up so nothing else ever gets processed.
From @dreshytnik
The text was updated successfully, but these errors were encountered: