Just started my development environment after a halfe year to update my app and at first debug
I get the ...
Waiting for application to start debug server
... and it waits forever.
After several kills and trials the issue is gone, but it takes always time and it is frustrating.
I know this issue since several years and there are lots of solution approaches out there which all do not really work.
What is the solution for 2022?
Related
So I have a node (v8.9.4) server that is running on an AWS EC2 instance using the forever package to start it up. The server has worked without any issues for years but now that it's grown and more people are using it, it suddenly starts to time out all requests at seemingly random times, after working for a few hours.
I've found that running forever restart on the server gets all requests working again so I've got a temporary cronjob to restart it every hour but this is not good design and I would much rather have the server running without any issues.
I've gone through my server logs and found this which may be significant:
error: Forever detected script was killed by signal: SIGKILL
error: Script restart attempt #131
Warning: connect.session() MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process.
Another thing that may be important, the server stays running while this issue occurs so any checks on the server status through UptimeRobot (or any server status checker) returns a success.
Considering the server will run fine for a few hours and also start up again with no issues after a restart, I'm thinking it is not an issue with the code but something else that I am not aware of. My current hypothesis is the requests will start timing out if the server runs out of CPU but I would like to explore more options before making the final call on the issue. If anyone had any insight into this issue, I would be super grateful! :)
I have recently deployed by nodejs ( with mongodb ) server on open shift which is being used by my android application. Every morning the first interaction from the app to the open-shift server always fails to get a response. After that any call made to the server always get a very fast response. I have a feeling that its sort of goes into sleeping mode because of no interaction from app to server for 8 hours or so (sleeping time)... I might be wrong . So I wish to know if someone has experienced that and if yes how do you resolve this . I do not get any logs at server for first call .
If you are using OpenShift Online Starter, you will find this behaviour explained on the product page.
https://www.openshift.com/products/online/
Quoting it:
Your project resources sleep after 30 minutes of inactivity, and must sleep 18 hours in a 72 hour period
OpenShift Online Starter is a free tier intended for experimentation and testing. It is not intended for production systems that need to be running permanently.
If you are running a production site, you would want to look at the Pro tier.
Following the steps in this article I am trying to turn on preloadEnabled and startMode in my applications (I have about 20 WCF services in their own app pools and then 3 client sites) https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-application-initialization
Now when I do an iisreset, WAS dies immediately. If I go back and start it manually and then the W3PS, everything starts like I want it to.
Is there any hope for being able to do an iisreset ever again?
Doing it with /stop and /start works fine. It's literally just the bang turnaround of no flags that's an issue.
Event code for WAS fail was 5011 and the code was 8007006d
IIS v 10.0.15063.0
Windows 10 1703 (15063.726)
For the future internet visitor to this question, what we discovered in our testing and working through the bug was that we have a background thread related to our pubsub internally that isn't shutting down cleanly, and is causing the process to hang before the reload has a chance to happen, causing corruption in WAS.
Starting the dependency stopped the issue for us during the next round of testing, and now we get to go research a new bug internally. Fun times.
I'm trying to keep my Heroku (free) application awake during daytime. I don't really care if it sleeps late at night.
The old technique of continuously pinging the app is no longer a valid solution because since 2015, all free-app's have to sleep at least 6 hours a day.
I'd like to know if any of you guys figured this out before.
I need to schedule the recharge state or maintenance mode in a specific time range.
Let's make this question and an up-to-date resource of accomplishing this task.
Please submit only constructive ideas.
You can just scale it down for the six hours you want it to be asleep:
heroku scale web=0
Then scale it back up when you want to wake it up:
heroku scale web=1
There are a lot of ways to implement this; a script on some other machine would work fine, but you could probably also use the Heroku Platform API and a scheduler service:
https://devcenter.heroku.com/articles/platform-api-reference#formation
https://devcenter.heroku.com/articles/scheduler
disclosure: I'm the Node.js Platform Owner at Heroku
There is also this add-on: https://devcenter.heroku.com/articles/process-scheduler
At first I thought it wasn't working as it doesn't seem to necessarily run right at the top of the hour, but other than that it's been working really well for me and allows me to sleep my app overnight.
I have two free subscriptions for windows azure and because I exceeded the limit on the first one, Microsoft closed it down. So I tried to deploy my application from the other subscription, and changed a few settings, and it seems to take a lot longer and the dns name of the depolyed application (in production area) does not seem to work. (I've been waiting for about 15 minutes.. in the other subscription it was almost immediate that the link started to work..). Also my webrole seems to be in a state of busy for a very long time..
The application always worked fine and now I'm getting all this trouble just by switching subscription?? I'm getting really frustrated with this especially because I all worked perfectly before. Now I have to 'waste' my time getting all the things to work again and I can't start with anything new. I don't think this is normal but I can't seem to find the solution to this either.
edit:
Over half an hour the dns finally started working but this still does not fix the problem with the extreme slow deploying and the busy state of the webrole..
Please study the discussion below to understand why the time to deploy an application could vary between 10-30 minutes:
Is there a way to reduce time between Azure deployment start and role OnStart() code being invoked?
Above details will helped you to get the answer about your statement ".. this still does not fix the problem with the extreme slow deploying and the busy state of the webrole.."..
To add more about that, when your application is deployment phase it goes through several state and in some cases the time taken in one state could be longer then expected and during this time you will see status as "Busy", "Initializing", "Starting.." etc and these state actually explain which level you are during your deployment. I hope this helps you to understand the time taken during deployment.