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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem running DNN on Amazon EC2 - Need helpProblem running DNN on Amazon EC2 - Need help
Previous
 
Next
New Post
5/8/2010 12:38 PM
 
I have run into a strange behavior that I cannot figure out.  This only happens on the production environment hosted at Amazon.

Here is our environment:
  1. Two small instances for web servers - Windows 2008 II7 - web1.mysite.com and web2.mysite.com
  2. web1 is set up as a simple file share, so web2 just points to website folder on web1
  3. One small instance as a db server - SQL Server 2008 - db1.mysite.com
  4. One load balancer
  5. Using Mozy to file replicate the code base to an offsite hot backup
  6. Using SQL replication to replicate the DB to an offite hot backup
Here is the behavior I am seeing (one symptom anyway):
  1. After adding a page, the browser would normally redirect to the new page.  Instead, sometimes, I'll get a “Resource not found” error.   If you refresh the page (F5) it will seemingly randomly switch between the new page and the “Resource not found” error.  There does not appear to be any pattern to when or why you sometimes get the new page and sometimes not.
  2. Add a couple more pages, then delete one.  Press F5 a bunch of times, and you might see various combinations of the pages in the menu structure.  It may appear like the original structure before any adding/deleting, it may appear like the final structure, or it may appear like any one of the intermediate steps along the way. 
  3. Similar behavior is observed when adding/deleting modules or making Admin->Site Settings changes.
  4. Restarting IIS solves the problem until you start adding/deleting stuff again.
  5. I cannot replicate this on any of my test servers not hosted on an Amazon webfarm despite having copied the codebase and database down exactly as-is.
It feels like the page requests are being handled by different web servers or page requests are being served from some cache somewhere.  Or perhaps the single webserver is hitting different db  servers

Here is what I have tried so far:

  1. Avoiding the load balancer by going to web1.mysite.com directly.
  2. Stopping the website on web2 just to be sure
  3. Deleting the SQL replication
  4. In IIS7, disabling the Output Caching module
  5. In DNN, setting ‘Cache Settings’ to None
  6. In DNN, setting ‘Authenticated Cacheability’ to NoCache

None of these solve the problem.   I cannot figure out how it is possible that I can get different content while hitting only one webserver and with all caching turned off.   Any help would be greatly appreciated.

 
New Post
5/9/2010 11:29 AM
 
After much head banging and gnashing of teeth, it was discovered that the application pool had been set up with multiple worker processes (web garden).  Since I didn't set this up initially, I never thought to look for that....  Anyways, setting the number of processes back to 1 solved the problem.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem running DNN on Amazon EC2 - Need helpProblem running DNN on Amazon EC2 - Need help


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