Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Bots Causing Event ErrorsBots Causing Event Errors
Previous
 
Next
New Post
7/30/2014 11:42 AM
 

I have been investigating various performance issues (DNN 7.2.1) and have been trying to understand the many messages in the Event Log.  One that I seem unable to stop seems to be caused by a bot (Google). I think that this error may tie up a SQL Connection and over time I see the performance of the site(s) degrade - maybe due to the number of messages ending up in the Event Log?  There are several variations of the message, but all show "UserAgent:Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" An example of the full error message below.

Any advice would be welcome.

Thanks in advance

Nick Wallbridge

 --------------

AssemblyVersion:7.2.1

PortalID:2

PortalName:Endurance GB

UserID:-1

UserName:

ActiveTabID:132

ActiveTabName:Home

RawURL:/main/Register?returnurl=http%253a%252f%252fendurancegb.org%252fmain%252fJoining%252fGetting-Started-with-EGB&popUp=true

AbsoluteURL:/main/Default.aspx

AbsoluteURLReferrer:

UserAgent:Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:72590209-8f98-4ffe-b7b0-5c199f10b444

InnerException:Thread was being aborted.

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:System.Threading.Thread.AbortInternal

StackTrace:

Message:

System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.AbortCurrentThread()
   at DotNetNuke.Modules.Admin.Users.Register.OnInit(EventArgs e)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Control.AddedControl(Control control, Int32 index)
   at System.Web.UI.Control.EnsureChildControls()
   at DotNetNuke.UI.Containers.Container.get_ModuleControl()
   at DotNetNuke.UI.Containers.Container.ProcessModule()
   at DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo module)

 

Source:

Server Name: EventScore

 
New Post
7/31/2014 8:28 AM
 
the thread aborted issue appears to be thrown by the database during the process of user registration - typically this means that the operation times out. I suspect you're seeing the spam registration issue that is ongoing - we have fixes for it in 7.3.2 which is due out within a week or so, but I recommend you read http://www.dnnsoftware.com/community-... for workarounds (you may also want to clear out any unexpected users from your site)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/31/2014 10:04 AM
 

Once again thank you for your quick and relevant reply. It looks like the article you wrote has some possible solutions/improvements for me, although interestingly I don't allow registration on my site at all (it is done by a third part app and a separate DB with some Single-signon processes in the background.) It appears that just the bot hitting the site may (I can't be sure) have been having an impact.  Interestingly the number has dropped off in the last 24 hours, and my site response time is back up.  Again I can't be sure of cause and effect as I have done several other things to try to help. Maybe the hacker's code is clever enough to work out it is not getting anywhere!

 
New Post
8/2/2014 1:53 PM
 
in general most automated attacks register the http status and if they get a http 200 assume success (and log that to later return e.g. update profile) - where they get a different response (such as causing a 404 or 500 error), they move on assuming that the site is not a valid target. This is annoying, but is a fact of life on the internet where bots run constantly - take a look at your IIS logs sometime and you may be surprised, my personal site get's dozens of php based hack attempts each day. I have a task to create a blog post & wiki discussing this further and outlining how IIS request filtering can be used to reject the invalid requests before they reach the application so as to minimize any performance degradation

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Bots Causing Event ErrorsBots Causing Event Errors


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out