How to get more debugging info on a crypted "Killed" job?

Skip to first unread message


Apr 14, 2014, 5:25:20 PM4/14/14
I've got a complex document (courseware) that, with different invocations of the command, produces both a PDF slidedeck and an Instructors guide suitable for printing. 

When I render it into the slides format, it works.  But when I attempt to render the Instructor guide, I can track its progress (through messages about the resizing being done to the various images) to very near the end of the document -- but then the job terminates with a cryptic "Killed" message.

Any tips on how to track down what is causing this?

Command line invocation: 

rst2pdf  "${SRCNAME}" --strip-elements-with-class=slidesonly --fit-background-mode="scale" -b 1 -s "${IGSTYLENAME}" -o "../PDFS/${IG_NAME}" 

final output:

[WARNING] image /var/lib/jenkins/jobs/Course-OSFundamentals-Dev-Havana/workspace/SRCS/../.Course-Core/line_deco1.png is too wide for the frame, rescaling
[WARNING] image /var/lib/jenkins/jobs/Course-OSFundamentals-Dev-Havana/workspace/SRCS/../.includes/PartitionPower.png is too wide for the frame, rescaling
[WARNING] image /var/lib/jenkins/jobs/Course-OSFundamentals-Dev-Havana/workspace/SRCS/../.Course-Core/line_deco1.png is too wide for the frame, rescaling

Scott Purcell

Apr 14, 2014, 6:23:53 PM4/14/14
Do this syslog entries tell me anything meaningful?

Apr 14 20:49:21 rst2pdf kernel: [10620783.385803] Killed process 19168 (rst2pdf) total-vm:672212kB, anon-rss:618736kB, file-rss:4kB
Apr 14 20:57:55 rst2pdf kernel: [10621297.469916] Killed process 19745 (rst2pdf) total-vm:672208kB, anon-rss:619052kB, file-rss:8kB
Apr 14 21:13:41 rst2pdf kernel: [10622243.457563] Killed process 20765 (rst2pdf) total-vm:672188kB, anon-rss:619232kB, file-rss:4kB

You received this message because you are subscribed to the Google Groups "rst2pdf-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
For more options, visit

Roberto Alsina

Apr 15, 2014, 5:17:59 AM4/15/14
Yes, that's the OOM killer, you ran out of memory. Now, why rst2pdf would use 672 MB of RAM I have no clue.
Reply all
Reply to author
0 new messages