I have built an application that often runs overnight but sometimes windows decide to restart even though the program is still running. This is problematic for both me and some users for obvious reasons.
I cannot expect the users to manually select the update pause bottom, hence, I want the automatic restart to be disabled by the program while it is running. Is there a way to automate this?
To note; I'm running my application from a jupyter notebook which might be important.
Thanks for any ideas.
My .net application process will not stop running. I can use ANTS to profile it, but all examples talk about increasing memory and new instances. How do I find out what is preventing the application from exiting.
I have done snapshots while the application is running properly and then a second snapshot after it is "closed" but is still running as a process. What should I be looking for?
I reckon my applications close down whenever my Azure VPS is disconnected (click the "X" at the top of the screen - NOT logging off). I have my MetaTrader programme running and not every trade is being executed whenever my pre-determined conditions are met.
I've looked at my logs for MetaTrader and there are no trade errors, no explanation as to why my trades are not executing. I've also looked at journals and there are no errors there either.
I've looked up my Windows Event Logs & I can't find anything for the MT4 application either.
The absence of error messages in my logs would say that my MT4 application is shutting down whenever I disconnect (resulting in no trades being executed - which is what you'd expect from an MT4 application that isn't running in the first place).
On the logs, it states that all symbols & EA's are being initialised - surely this shouldn't be saying this if they're running already.
Its bizarre and cannot get to the bottom of this. Can anyone shed some light on this and am I "barking up the wrong tree" as they say? Thanks in advance.
In a nutshell: Not all of my trades are being executed, & the presence of "initilsation logs" would indicate that MT4 is shutting down upon disconnection when its supposed to be running continuously.
You could try running the application as a service, this would allow the application to run in its own session and would not quit event after logging out:
Microsoft Windows services, formerly known as NT services, enable you to create > long-running executable applications that run in their own Windows sessions. > These services can be automatically started when the computer boots, can be paused > and restarted, and do not show any user interface.
Source: https://learn.microsoft.com/en-us/dotnet/framework/windows-services/introduction-to-windows-service-applications
Full steps on how to create a service:
https://learn.microsoft.com/en-us/dotnet/framework/windows-services/how-to-create-windows-services
Can someone provide a command or way to kill / stop an analysis from loading into memory while it is being opened by the impersonator / scheduled updates user?
I've tried stopping the service, and closing the analysis through the administration console (http://server/SpotfireWeb/Administration/Diagnostics.aspx) but it will not allow it. It will only allow you to close an anlysis that is fully loaded. We are trying to kill an analysis which is taking a long time to load into memory.
Remove it from scheduled updates. Restart website from IIS panel.
I have a node.js script that run once in a day on ubuntu EC2 instance. This script pulls data from some hundered thousand remote APIs and save to our local database. Is there any way we can monitor this node.js script on remote server? There have been few instances where script crashed due to some reason and we were unable to figure it out without SSHing into instance and checking the logs. I have however created a small system after first few crashes which send us an email whenever script crashes due to some uncaught exception and also when script completes execution.
However, we need to develop a better system where we can monitor the progress of script via web interface of our admin application which is deployed over some other instance and also trigger start/stop of script via this interface. What are possible options for achieving this?
If you like to stay in Node.js, then there are several process monitoring tools:
PM2 comes with lots of other features besides monitoring processes. You can monitor your processes via CLI or their official web interface: https://keymetrics.io/. A quick search on npm also gives a bunch of nice unofficial gui tools: https://www.npmjs.com/search?q=pm2+web
Forever is not as feature rich as PM2 but will do the basic process operations and couple of gui are also available in npm.
There are two problems here that you are trying to solve:
Scheduling work to be done
Monitoring a process for failure
At a simple level, this is easy: schedule a cron job and restart failed things so they keep trying.
However, when things don't go smoothly, it helps to have a lot more granularity over what you are scheduling, and how it is executed. This would also give you the visibility over each little piece of work.
Adding a little more complexity, you can end up with something like this:
Schedule the script that starts everything (via cron, if that's comfortable)
That script generates several jobs that need to be executed into a queue
A worker process (or n worker processes) consume that queue and execute pending jobs
You can monitor both the progress of the jobs, as well as the state of each worker (# of crashes, failures, jobs completed, etc.). The other tools mentioned above are good candidates for this (forever, pm2, etc.)
When jobs fail, other workers can pick up the small piece of work that was in progress and restart it. This is much more efficient than restarting the entire process, and also lets you parallelize things across n workers based on how you can split up the workloads.
You could easily throw the status onto a web app so you can check in periodically rather than have to dig through server logs.
You can also get more intelligent with different types of failures. Network error? Retry 5 times. Rated limited? Gradual back-off. Crash? Don't retry and notify via email. etc
I have tried this with pm2, you can get the info of the task, then cat out or grab the log files. Or you could have a logging server, see also: https://github.com/papertrail/remote_syslog2