当前位置:网站首页>IIS faked death this morning, various troubleshooting, has been solved

IIS faked death this morning, various troubleshooting, has been solved

2022-07-07 09:26:00 -Coffee-

Last night, 8 Click to start. The website is indirectly inaccessible ,ping The server , Normal network , At this time, I found iis The largest website cannot be accessed after it appears , Then iis All large and small websites on the website are inaccessible , The first payment request is IIS Fake death ……

My solution :

1. First create an application pool --- The working procedure will be recycled ( minute ) Set it smaller , What I set up is 500

2. Right click the largest website ---- attribute ---- Home directory ------ Application pool ( Click the newly created application pool )--- Sure you can.

3. here IIS All websites on are back to normal

The problem : There are too many websites hanging under the current application pool , Lead to When there's a lot of traffic CPU elevated , Once it reaches a certain level ,IIS There will be fake death , At the moment IIS All websites on cannot be accessed

Found some IIS Fake death information for your reference :

IIS Reasons for pretending to die :

open IIS You will see the application pool , By default, there is only one application pool , View the properties of the application pool , You will find his recycling time , Default up to ,1740 minute , That is to say , Need to be in 1740 Minutes before recycling this application pool , If at this time , The requested maximum limit has been reached , Then there will be ASP The condition of feigning death , This is the fake death of large websites , Instead, , This is not the case with small websites , Because he asked less , Low flow , The limit has not been reached . Of course, it depends on the number of websites on your server .

Here's the solution :

Information 1

Single site solution :

Reduce application pool recycle time to 300-600 minute , During the recovery process , It takes a little CPU resources , Can't , For stability , Set the recovery time to early morning 5 spot .

Multi site solution :

My server is currently down 70 About websites , I create six new application pools , Reduce the recovery time of each pool to 300 minute , Then allocate each pool 10 About websites ( This allocation is based on the number of visits to your website ) If a website , Large amount of visits , Just give him a separate program pool , But the consequence of this is that you need a lot of memory , A pool now occupies me 120M About memory , Anyway, the memory is large , No problem ,

How do so many websites allocate application pools , open IIS-- View the website properties you want to assign ,, View home directory -- You will see the application pool below , Just assign one .

Information 2

We are using iis6 when .. If the mobile Internet forum is installed . There must have been iis6 Pretend to be dead .. Namely asp Slow page opening .. however iis But it's normal .. Static web pages open at the same speed .. Now .. I've always been the way to restart .. Did you check the official data ... According to official data ..win2003 This patch will be applied soon .. yes iis6 Yes access Driver support doesn't look like .. It's a bug Well .. Because my server has many virtual hosts .. And most of them support asp.. If you fake death, you can't run .. Look up various information .. Found a relatively simple method .. Specifically, I passed the test ..iis6 Self contained data application pool .. Now use him to solve the fake death ..

First turn on the bbs Set up a separate directory .. Then click application pool .. New application pool . Enter application pool id..

And then put bbs Under the virtual directory of . Just use the program pool .. Select the application pool just created ...

Then go back to the application pool just set ... Click on .. attribute ... Count the number of recycling work processes ( minute ) And the number of recycling work processes are also checked in the following time recycling time processes .. Then add .. Choose a time .. Generally speaking .. The website arrives in the early morning 3 A.m. . There are few people .. Now recycle bbs The number of processes .. That's it iis The appearance of pretending to die ..

Of course, other information can also be configured .. for instance iis6 Username .. We can open the computer management .. Then open computer user management .. Add a user .. After setting up .. In the application pool .. identification .. Put the added users on .. Use users to test the recycling process .. Of course, .. Other configuration .. It's very simple .. As long as you look good .. You can understand the meaning ...

For me .. This method may not be convenient .. So I use a tool to recycle the application pool .. This is convenient and fast .. Individual users certainly don't need this tool .. I work in a company .. The server is under great pressure .. So we use tools to solve some problems . Included .iis Spare parts . And virtual host ip Unified modification of and port access ip Record .. Batch processing is a very simple and convenient method . therefore . Make a server safe .. It's not so easy .. especially iis.. It is a good habit to often go to the official website to search for information .. There are also frequent access logs .. And users of the registry, as well as loading and running programs . And service is also a good method .. therefore . Learn how to encounter problems and how to deal with them !!!!

原网站

版权声明
本文为[-Coffee-]所创,转载请带上原文链接,感谢
https://yzsam.com/2022/02/202202130624593453.html