Page 1 of 1
quicky: How to stop a rendering report
Posted: Fri Apr 10, 2015 8:58 am
by MichielvM
Guys,
I accidentally hit send on a very large pdf report.
Now the Nagios Xi interface is inaccesable. It will take the greater part of 2 hours to complete.
From the Cli i see wkhtmltopdf using up a lot of resources.
Can I safely kill just that proces and be done with it?
Re: quicky: How to stop a rendering report
Posted: Fri Apr 10, 2015 10:22 am
by tmcdonald
That's the process that generates the PDF report and is likely what is taking up all the CPU. I can't say for sure if there are other processes that will need to be killed, but when I read the title of this thread my first thought was wkhtmltopdf.
Re: quicky: How to stop a rendering report
Posted: Mon Apr 13, 2015 2:07 am
by MichielvM
The "other processes" were worrying me.
I let this one run. As predicted it took about 1,5 hour to complete.
Question remains if and which other processes are involved and what's the best practise to kill 'em.
Re: quicky: How to stop a rendering report
Posted: Mon Apr 13, 2015 10:45 am
by jolson
I did a quick test, and it looks like 'wkhtmltopdf' is the only process that comes up when a PDF report is being generated. In my testing, it was perfectly safe the kill the process - doing so would immediately stop the PDF generation. Thanks!