I am new to odoo and code profiling. I am using py-spy to profile my odoo code, as I need a flame graph as the output of profiling. Everything is working fine with py-spy, but the issue is, the py-spy needs to be stopped by pressing ctrl + C on the terminal where it is running or shutting the odoo server down. I can't stop or reset the odoo server neither I can do ** Ctrl + C** on the server.
I had tried to create to do this
To start py-spy
def start_pyflame(self):
pyflame_started = self.return_py_spy_pid('py-spy')
error = False
if not pyflame_started:
self.start_pyflame()
else:
error = 'PyFlame Graph process already created. Use Stop button if needed.'
_logger.error(error)
which is working fine, the problem is with this one
def stop_pyflame_and_download_graph(self):
pyflame_running = self.return_py_spy_pid('py-spy')
if pyflame_running:
subprocess.run(["sudo", "pkill", "py-spy"])
Now the issue is when I am killing the process with pkill or kill it kills the process but along with this, it also terminates the py-spy, because of which, the output file is not generated.
Is there any way to stop or soft kill py-spy so that the output file will be created.
Thanks in advance for help
After some research, I came to know that all these kill commands are just killing the process whereas in this case, we need to stop the process.
This thing I have achieved by
sudo kill -SIGINT <pid>
As it is clear from the name, this command is not killing/terminating the process, it is simply asking the process to stop working by passing an interrupt signal.
This worked for me.
Related
I have a script that fetches data from the internet.
It uses commander, axios, https-proxy-agent, pg and a bunch of other modules, probably unrelated to the issue.
The logic is not complicated: get a list of URLs from the DB, loop downloading data using a proxy and saving it back to the DB, exit.
It works fine, except sometimes the script exits in the middle of the job.
No errors, just sudden termination. I haven't found a way to replicate it reliably.
When launched through an IDEA debugger, the final message reads:
^C
Process finished with exit code 130 (interrupted by signal 2: SIGINT)
I haven't pressed Ctrl+C, just in case.
strace final lines are:
--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
+++ killed by SIGINT +++
There's a SIGINT handler attached to process. It runs if I interrupt the script manually, but not when it happens by itself.
Attached are 2 excerpts from strace output: one when things are working as expected and the other is the final output before the script is terminated.
success.txt
failure.txt
It looks like things break when it comes to these lines:
epoll_wait(13, [{events=EPOLLIN, data={u32=19, u64=19}}], 1024, 8131) = 1
read(19, "", 65536) = 0
19 is a socket descriptor.
Could anyone help to figure out what is going on exactly and why the process is terminated, please?
Kubuntu 21.10, Node.js 16.13.
I'm using the groovy language in robotic application (RPA Express). I can not figure out how to do two things in the groovy language.
I start an application with these command:
def proc = new ProcessBuilder( args )
Process process = proc.start()
My questions are:
How do I close this application? (I want to close the application at the end of the script)?
How do I switch to this application window? (I want to be sure the application window is always focused)?
Both depend on the OS.
You need to invoke a kill task command to kill the process by its pid (e.g. kill on Linux). As Joachim mentions in the comments, Process has destroy() and destroyForcibly().
You need to use the window manager API to focus the window of the given pid you want.
I'm writing a small application for my Raspberry Pi to surveil my surroundings and I want to know when the Raspberry Pi loses power using NodeJs.
I've found that you can use a signal that the Pi send, SIGPWR, when it loses power.
I made this little test script:
// test.js
var fs = require('fs');
var path = '/home/pi/Documents/Code/surveillanceCam/log/logfile.txt';
fs.writeFileSync(path, new Date().toString() + ': Start\n');
process.on('exit', function () {
fs.appendFileSync(path, new Date().toString() + ': exit\n');
});
process.on('SIGPWR', function () {
fs.appendFileSync(path, new Date().toString() + ': SIGPWR\n');
});
process.stdin.resume();
If I run the script with node test.js I get a line in logfile.txt that end with Start so that works, and if I remove the last line (so the scripts don't run until I stop it), I also get a new line with exit in the end.
But if I keep the last line so the script keeps on running, and then I pull the cable of the Pi, then insert it again. When I go to watch the file after it boots I only get the line with the start in the end..
I want to have 2 lines in my logfile.txt one with the time of start, and one with the time of power loss..
And from what I've read the SIGPWR signal is sent when power is lost. Does the script not have enough time to write to the file or is there something else I can do?
EDIT: What I want to do is to simulate a power loss and when the power is lost write to the file.
EDIT2: I think how I will solve this problem is to add a process.on('SIGINT',...) signal. So when the user ends the program with Ctrl+C I will then and only then write to the file. And then when the node server start I will check if there is something in the file. If there isn't then the node server didn't shut of gracefully and I should display an error.
Unplugging the power would not be a graceful shutdown, and I doubt that you could depend on the reliability of any event for figuring out if it shut down. This is why so many things have troubles recovering when the power goes out, because things are not able to be shut down gracefully. Everything dies before the OS can probably even realize it, so nothing gets gracefully shutdown.
The standard way you detect this sort of situation is by creating flag file when the Pi boots up, and removing it on a normal shutdown.
If the flag file exists next time the Pi starts up (you check before creating it), you know that that Pi crashed for someone reason (you don't know if it was a power loss, kernel panic, or something else).
There is no way to respond directly to a power loss in your code unless you add some sort of battery backup unit that sends the appropriate signal.
I'm working on a server bot in python3 (using asyncio), and I would like to incorporate an update function for collaborators to instantly test their contributions. It is hosted on a VPS that I access via ssh. I run the process in tmux and it is often difficult for other contributors to relaunch the script once they have made a commit, etc. I'm very new to python, and I just use what I can find. So far I have used subprocess.Popen to run git pull, but I have no way for it to automatically restart the script.
Is there any way to terminate a running asyncio loop (ideally without errors) and restart it again?
You can not start a event loop stopped by event_loop.stop()
And in order to incorporate the changes you have to restart the script anyways (some methods might not exist on the objects you have, etc.)
I would recommend something like:
asyncio.ensure_future(git_tracker)
async def git_tracker():
# check for changes in version control, maybe wait for a sync point and then:
sys.exit(0)
This raises SystemExit, but despite that exits the program cleanly.
And around the python $file.py a while true; do git pull && python $file.py ; done
This is (as far as I know) the simplest approach to solve your problem.
For your use case, to stay on the safe side, you would probably need to kill the process and relaunch it.
See also: Restart process on file change in Linux
As a necromancer, I thought I give an up-to-date solution which we use in our UNIX system.
Using the os.execl function you can tell python to replace the current process with a new one:
These functions all execute a new program, replacing the current process; they do not return. On Unix, the new executable is loaded into the current process, and will have the same process id as the caller. Errors will be reported as OSError exceptions.
In our case, we have a bash script which executes the killall python3.7, sending the SIGTERM signal to our python apps which in turn listen to it via the signal module and gracefully shutdown:
loop = asyncio.get_event_loop()
loop.call_soon_threadsafe(loop.stop)
sys.exit(0)
The script than starts the apps in background and finishes.
Note that killall python3.7 will send SIGTERM signal to every python3.7 process!
When we need to restart we jus rune the following command:
os.execl("./restart.sh", 'restart.sh')
The first parameter is the path to the file and the second is the name of the process.
I'm writing a CGI script that is supposed to send data to a user until they disconnect, then run logging tasks afterwards.
THE PROBLEM: Instead of break executing and the logging getting completed when the client disconnects (detected by inability to write to the stdout buffer), the script ends or is killed (I cannot find any logs anywhere for how this exit is occurring)
Here is a snippet of the code:
for block in r.iter_content(262144):
if stopRecord == True:
r.close()
if not block:
break
if not sys.stdout.buffer.write(block): #The code fails here after a client disconnects
break
cacheTemp.close()
####write data to other logs and exit gracefully####
I have tried using "except:" as well as "except SystemExit:" but to no avail. Has anyone been able to solve this problem? (It is for a CGI script which is supposed to log when the client terminates their connection)
UPDATE: I have now tried using signal to interrupt the kill process in the script, which also didn't work. Where can I see an error log? I know exactly which line fails and under which conditions, but there is no error log or anything like I would get if I ran a script which failed in a terminal.
When you say it kills the program, you mean the main python process exits - and not by some thrown exception? That's kinda weird. A workaround might be to have the task run in a separate Thread or process, and then monitor that until it dies and subsequently execute the second task.