Cruisecontrol.net kicks off all check-ins after restarting the service or rebooting the system. How can I disable this?
Related
We have multiple AspNetCore applications hosted on an Azure Web App as OutOfProcess and deployed as virtual applications with separate paths.
We have the same setup in different environments, all infrastructure and applications are deployed automatically through our pipeline but it's only breaking in one environment and we can't find out why.
We have tried turning on stdoutLogEnabled to true. This reveals an invalid runtime.config.json error, I have read this can be caused by multiple issues but we can't identify any reason for it. We also intermittently see a 502.5 ANCM startup failure when navigating to the swagger URL for each application.
If we look in the application event logs in the Azure portal we are seeing this error failed to start process with command line 'dotnet .\<DLL>' with multiple retries. Failed to bind to port <PortNumber>
We can start the applications locally with Kudu by navigating to the location of the DLL and running dotnet <DLL>. The application starts successfully so it seems to be a problem on the web app. We've tried restarting and stopping and starting the web app, even tried scaling the app service to attempt getting a clean start but nothing has succeeded.
I'm not sure what other steps we can take to diagnose this issue or what we might have done wrong as the same applications are working fine in other environments.
I have a published .NET Core 2.0 API in production hosted through IIS.
This API has a hangfire dashboard and a single recurring job running through it.
This API exposes a service layer to us developers for jobs that we need to perform on certain databases so it is not always being hit with traffic - perhaps only occasionally when a dev hits an endpoint. The Recurring job runs hourly.
My Problem: Once the site receives no traffic for a while IIS idles the app effectively killing my hangfire job - I know this because in the dashboard when I click servers it says 0. As soon as I hit an endpoint on the API it spins back up.
What I've tried so far: In IIS Set startmode to AlwaysRunning and set the idle timeout to 0 for that specific application pool.
I know this is not working because every morning when I come into the office I check Kibana for logs that should be constant throughout the night due to the recurring hourly job but unfortunately nothing happens. As soon as I hit the API everything starts working again and the job queues.
We have two applications - WebAPI and WCF service. Our WebAPI is consuming WCF service.
We have two different app pools for both applications with different recycle settings:
wcf application recycles every day at 1 am fixed with overlapping sessions.
webapi has default recycle settings.
We are getting wierd IIS restart daily at 1 am.
No event is logged in Event Viewer.
Note: We have grafana setup to monitor server and it sends alert daily at 1 am for server down.
What could be reasons for IIS restart?
have you seen application pool recycle in event log? as you know when recycling happened , all session in iis will destroy and a log wrote in Windows event log. so I need to send deliberate information about what you detect in your monitoring application. this is because of it might a false positive of your monitoring application. as you mentioned it didn't logged in event log, I suspected this problem Is for that. please send practical information to solve your problem.
It might be your application cannot refresh the app pools when you set their app pool refresh to happen at 1am.
I would look at the permissions given to the application pool. It could be the permissions aren't enough to restart it.
Other than that I would also recommend enabling Logging. You will find out your problem with Logging enabled.
Look through the application pool settings under advanced setting and ensure Recycling > Generate Event Log Entry is set to true for all the entries. This will ensure everything related to the application pool will be logged and you will be able to see the reasons for the recycle.
I am get error below on publish to azure using web deploy profile i downloaded from azure website
Web deployment task failed. (The maximum number of connections for this site has been exceeded. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEEDED_MAX_SITE_CONNECTIONS.)
I am using visual studio 2012
I was having the same issue but after restarting management service it worked for me.
Here are the steps:
Go to your windows server where IIS Server configured.
Control Panel => System and Security => Administrative Tools => Services.
In the Services. Restart Web Deployment Agent Service and Web Management Service
Give a try now to web deploy.
This may occur if you are connecting to the internet via a 3G dongle or card.
I have the same error and earlier in my warnings was "Retrying the sync because a socket error (10054) occurred" I'm stuck on a 3G connection today and getting this for the 1st time so presume these are related.
I know that it's been a long time ago, but I was struggling with the same issue lately. For me, it helped to restart the Web Management Service.
It might hang in Stopping status - if so, you can forcibly kill it:
First, open cmd with elevated privileges, and use sc queryex wmsvc command to find out the PID of the service.
Then, use taskkill /PID [the pid] /F command to kill the process. After that, you just start it again with services.msc
Hope it'll help :)
I had a similar problem trying to publish a WebSite on Azure. I solved it by restarting the website from azure management. If you're deploying to IIS, I suggest to try a restart or a stop and start for your website and try publishing again.
I'm having problems with IIS in DEV vs QA. One thing I notices by watching task manager is that when a .exe runs on DEV it is running as the user instead of my generic iis user. Is this normal for IIS with integrated authentication or is there some other setting I need to look into?
With integrated authentication, processes are launched as the logged in user. When anonymous integration is enabled the process are launched as the iis user. It is also possible to enable both at the same time.