I have following problem
AppPool reset time is set to 4:45. Hovewer reset is done at 6:45.
I live in GMT+2 time zone.
Has anyone know what timezone / format is used by this setting in IIS ?
Should i use 2:45 value to get it recycled on 4:45 ?
Yes.
It will use the time set on the server.
Any time/setting on the server will always go by what the server clock is set to wither it be IIS AppPool reset, scheduled tasks, or anything else that goes off a time. By default Windows server installs will set there time zone to GMT +0 so if your GMT + 2 then anything you set on the server will run at two hours a head (like your 4:45 running at 6:45). You can either manually account for this when you set things up or, if you have root access to the server, you can just adjust the time zone settings from the clock like you would on your desktop so the server time is set to your time zone.
Related
I have hosted my application on IIS 6.0 and changed the idle time-out value and cookie state time-out values to 40mins.
But my application logs out after 30mins.
Why is this happening? Is there any upper limit to this?
Also, I cannot give 0(infinite) time out.
I'm working on configuring an Azure Log Analytics alert (using KQL) to capture the IIS Stop & Start events (from Events table) in my OMS Workspace, and if the alert query finds that there's no corresponding IIS Start event log generated from a PaaS Role for a particular IIS Stop event log- the user should get notified by an alert so that he can bring IIS back up.
Problem: Let’s say I setup my alert to run over a Time Period & Frequency of 15mins. If the alert triggered at 10:30AM, that means it will scan the IIS logs from 10:15:01 AM to 10:29:59 AM. Now, suppose an IIS Stop event got logged in around 10:28 AM, then the respective IIS Start log (if any) will be logged in after a couple of minutes around 10:31AM or 10:32 AM – and hence it will go out of the alert’s monitoring time period. This will create a false positive failure scenario. (IIS got started back but my alert didn’t captured the Start event log). And thus, it might lead to some unnecessary IIS Start/Reset operations on my PaaS roles.
Attaching a representative quick sketch to explain it figuratively.
Please let me know if there's any possible approach to achieve this. Any suggestions are welcome. Thanks in advance!
Current implementation as follows.
Here we can see False Alert generated at 10:30.
You can see the below approach, where we select last 10 minutes data(Overlapped) every 5 minutes.
For the below case you can generate the alert
See if its helping you.
We have a long time response for first time request call to Web API !
in spite we have changed the following Settings of WEB API's pool -and then we noticed a noticeable progress for the number of times for waiting time is decreased - :
StartMode To AlwaysRunning
Idle-Time-Out(minutes ) TO 0
But still having long time response for first time of the request, specially on the morning (before working time) or during weekend, what could cause this? any missing Settings you advice ?are there any other settings we need to change, to Run the pool automatically ? -snapshot of advanced settings below-
As it is look to me some how the IIS or Pool has been recycled periodically ! however I was thinking changing StartMode to "AlwaysRunning" will run automatically the Pool and keep it up and running even after recycle or shutdown !
BTW: the setting of Recycling /Regular time intervale is 1470
!
It might relate to your ORM framework, such as Entity framework.
See the below discussion.
How to "warm-up" Entity Framework? When does it get "cold"?
We need to install the Application Initialization Windows feature in order to make the Start Mode configuration take effect.
https://serverfault.com/questions/683017/first-request-after-a-while-always-slow-asp-net-mvc-iis-8-5-windows-server
Also, Precompiling website might be a good option to speed up first access.
Please check the below links.
Fixing slow initial load for IIS
Heroku says (free)
Must sleep 6 hours in a 24 hour period
Ok, that´s fine.
But can I influence the message or any text shown to the user like: "Hello user, unfurtunately the the website needs some rest, please try again from 6 a.m to 2 a.m ".
I can influence the uptime, because of sending a ping every 20 min.
I just found this:
... free dynos are allowed 18 hours awake per 24 hour period, and over the next few weeks we will begin to notify users of apps that exceed that limit ...
If you're using a CDN you could create a scheduled task that replaces the root page by a static page at a certain time of day, make sure the CDN updates to that page, and then spin down the app for 6 hours.
The docs for CloudFlare might be a good place to start learning how a CDN works and how to set it up (see: CloudFlare Support > Getting Started). Of course you could also use a different Content Delivery Network (CDN) service.
We've configured our application pool to recycle at a regular time interval of 180 minutes. But the worker processes are getting recycled every 60 minutes.
Is this a known issue, or do we need to configure something else?
Thanks
As stated in What causes an application pool in IIS to recycle?:
You might want to turn on full AppPool Recycle Event logs:
cscript adsutil.vbs Set w3svc/AppPools/DefaultAppPool/LogEventOnRecycle 255
You also might want to take a look at this Scott Guthrie blog article: [http://weblogs.asp.net/scottgu/archive/2005/12/14/433194.aspx][1] that shows how to write code in Global.ASAX to log the actual cause of an Application.End event.