This question already has answers here:
OPENSHIFT Cron job just stop working
(2 answers)
Closed 7 years ago.
I had one script running under the .openshift/cron/daily like a clockwork, but suddenly, three days ago, it stopped working, without my intervention.
I created a simple script with a "echo Hello" under the .openshift/cron/minutely, I grant execute permissions (just in case), and I pushed it.
Nothing! The scripts never trigger.
I also tried restarting the Cron 1.4 cartridge, but nothing happened.
I have a Tomcat 7 (JBoss EWS 2.0) cartridge, a PostgreSQL 9.2, and the Cron 1.4 embedded.
Any ideas?
Thanks!!
This issue should be fixed now. Please open a request at help.openshift.com if you continue to have issues with it.
Related
This question already has answers here:
Writing to files in Node.js
(18 answers)
How to run a hello.js file in Node.js on windows?
(17 answers)
Closed 2 months ago.
fictively running on a VM
Supposed flow:
I am receiving a request on one of my server endpoints
I'll do some processing and place my "to_do.js" in the local file system
Now I'd like to execute that program but how would I go about that? How can I tell my VM to do that and receive some response from where I am in my code? Am I missing a point or overseeing a technical limitation? I'd be more than happy to any redirections to APIs or opinions - thanks in advance!
PS:
I tried to formulate the question as simple and understandable as possible to make my intent clear. Also I have researched for some time now but there was no thread with a related question.
This question already has answers here:
How to prevent a background process from being stopped after closing SSH client in Linux [closed]
(20 answers)
How to make a program continue to run after log out from ssh? [duplicate]
(6 answers)
Closed 1 year ago.
I have a Go script that creates an HTTP request and responds to any incoming requests. I want this script to run on a Linux server. However, I can't keep the ssh connection active forever, and when it disconnects the script also stops, as expected. I know that you have 'forever' for NodeJS that fixes this issue. I was wondering if something similar also exists for Golang, as I was not able to find anything. Any other tips on how to fix this are also very welcome.
There are mainly three options here, one is to use the nohup command, the other is to use the screen command, and the last is the upgraded version of byobu of screen. After reading these three commands, I actually prefer to use the byobu command, because the byobu command is more powerful, an upgraded version of screen, and the interface is more friendly.
This question already has answers here:
How to prevent a background process from being stopped after closing SSH client in Linux [closed]
(20 answers)
Closed 5 years ago.
It's a time cost heavily job when compile something on server. But, my VPS ssh connection is unstable. Connection will be lost in about 10 minutes. How can I let my command continue run when ssh connection lost ?
If you have an unstable connection, the screen(1) command is your best solution. This keeps the terminal session alive when you get disconnected and allows you to log back in a reconnect with it, preserving the screen state and whatever else you had running. It may not be installed by default on your linux distribution (its not on Ubuntu), but is available in any package system.
There are useful tutorials in various places -- a web search for linux screen command gives many pointers.
A quick Google search pulled up the following 3 SO posts that should help:
Linux: Prevent a background process from being stopped after closing SSH client
Getting ssh to execute a command in the background on target machine
Use SSH to start a background process on a remote server, and exit session
TL;DR - use nohup
Our .NET application uses WinSCP software to work with SFTP servers. It's running on different machines, however 1 week ago 2 of them started to fail with the following exception:
WinSCP.SessionLocalException, WinSCP process terminated with exit code 3 and output "", without responding (response log file D:\local\Temp\wscp1028.00ADA812.tmp was not created). This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.,
at WinSCP.Session.Open(SessionOptions sessionOptions)
This error doesn't occur always, but after some period of time. Once error occurs it fails always until we restart the entire application. After application restart it successfully works 10-20 hours and approx. 15K-30K succeeded requests. Then the error starts again.
We have already upgraded to the last version of WinSCP (5.7.7) and restarted the machines, however the issue still takes place. What could be the root cause and what steps could be done to fix the issue? Any help is appreciated.
I've been reading about it, and I've tried one of the solutions that I've found in the internet, but it still doesn't work yet.
I want to execute
java -jar /home/ubuntu/MyJavaJar.jar
once a year starting in October 12 at 12:34
I'm sorry if this is a really basic question, but I can't find a solution yet. I don't have a graphic interface, so the solution should be using the console.
Also, if there was another way to do this (without using linux cron) e.g. connect using putty and launch the java jar and then disconnect from putty (in my windows-based computer, that needs to be turned off regularly) (but without cancelling the jar execution on the Linux computer, that doesn't need to be turned off) would be an even better answer.
Thanks in advance.
You can use nohup:
nohup java -jar /home/ubuntu/MyJavaJar.jar &