From: Florian Wobbe <Florian.Wobbe@awi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: calling ConTeXt as a background process
Date: Fri, 08 Oct 2010 11:25:05 +0200 [thread overview]
Message-ID: <95274FC9-42F1-4842-9943-103608507CB4@awi.de> (raw)
In-Reply-To: <2F3F5D5C-FA78-4EA2-885E-A6DB86880B34@fiee.net>
> Am 2010-10-08 um 09:59 schrieb Florian Wobbe:
>
>>> Thank you, but the problem is most probably something in my server setup that doesn't fit something in LuaTeX.
>>> As I mentioned: I got no problems calling TeX directly, just from the server process.
>>
>> All right. I have one more suggestion. If you don't want to dive into debugging via gdb you should try another attempt at strace. Previously you posted a tracedump of context. But it only shows context (the shell script) waiting and nothing related to luatex. You may want to make strace follow forks (-f).
>
>
> Sorry, I've no experience using strace.
Some things are explained here: http://blog.ksplice.com/tag/unix/
> Here we are:
>
> This is how my process tree looked:
> 14025 ? Sl 0:01 | \_ /var/www/xxx/bin/python /var/www/xxx/.../manage.py runfcgi ...
> 14116 ? S 0:00 | \_ /bin/sh -c set >> _context.log && strace -f context --batchmode --once hello >> _context.log
> 14117 ? S 0:00 | \_ strace -f context --batchmode --once hello
> 14118 ? T 0:00 | \_ /bin/sh /var/opt/context/tex/texmf-linux-64/bin/context --batchmode --once hello
> 14119 ? R 0:11 | \_ texlua /var/opt/context/tex/texmf-linux-64/bin/mtxrun --script context --batchmode --once hello
>
> The logfile was empty, texlua seemed to hang. I killed 14119 and got:
> [...]
> [pid 14119] brk(0xaa3c000) = 0xaa3c000
> [pid 14119] brk(0xaa5f000) = 0xaa5f000
> [pid 14119] brk(0xaa82000) = 0xaa82000
> [pid 14119] brk(0xaaa3000) = 0xaaa3000
> [pid 14119] uname({sys="Linux", node="aine.fiee.net", ...}) = 0
This output looks quite messy because it is composed of the mixed output for five processes. I don't suspect the fault in luatex executable itself, however, mtxrun calls uname -m in a subshell and my guess is that it hangs there. Have you tried calling uname alone from your script? Next you could do
strace -ff -o ctxtrace mtxrun --script context --batchmode --once hello
This gives you hopefully four ctxtrace.<pid> files. Then do (for each pid)
strace -p <pid>
before killing luatex and see where it hangs. Interrupt and kill your luatex and have a look at the ctxtrace.* files.
Florian
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-10-08 9:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 7:06 Henning Hraban Ramm
2010-10-07 7:34 ` Henning Hraban Ramm
2010-10-07 8:42 ` Taco Hoekwater
2010-10-07 9:00 ` Henning Hraban Ramm
2010-10-07 9:06 ` Taco Hoekwater
2010-10-07 10:19 ` Henning Hraban Ramm
[not found] ` <90F33E64-7BB9-4DEB-9E89-A4FC99169401@awi.de>
2010-10-07 15:55 ` Henning Hraban Ramm
2010-10-07 16:32 ` Florian Wobbe
2010-10-08 7:36 ` Henning Hraban Ramm
2010-10-08 7:59 ` Florian Wobbe
2010-10-08 8:43 ` Henning Hraban Ramm
2010-10-08 9:25 ` Florian Wobbe [this message]
2010-10-08 10:00 ` Henning Hraban Ramm
2010-10-08 11:46 ` Florian Wobbe
2010-10-08 13:47 ` Henning Hraban Ramm
2010-10-08 13:54 ` luigi scarso
2010-10-08 13:54 ` Taco Hoekwater
2010-10-08 14:22 ` Patrick Gundlach
2010-10-08 14:30 ` Henning Hraban Ramm
2010-10-08 14:57 ` Taco Hoekwater
2010-10-08 15:10 ` Hans Hagen
2010-10-08 15:08 ` Florian Wobbe
2010-10-08 19:44 ` calling ConTeXt as a background process (SOLVED) Henning Hraban Ramm
2010-10-10 8:47 ` Patrick Gundlach
2010-10-10 9:01 ` Henning Hraban Ramm
2010-10-26 19:28 ` Taco Hoekwater
2010-10-26 20:09 ` Hans Hagen
2010-10-26 20:56 ` Taco Hoekwater
2010-10-26 21:32 ` Hans Hagen
2010-10-26 20:13 ` Henning Hraban Ramm
2010-10-08 15:05 ` calling ConTeXt as a background process Henning Hraban Ramm
2010-10-07 18:16 ` taco
2010-10-08 8:00 ` Henning Hraban Ramm
2010-10-08 8:12 ` Patrick Gundlach
2010-10-08 9:21 ` Henning Hraban Ramm
2010-10-08 9:27 ` luigi scarso
2010-10-08 8:37 ` luigi scarso
2010-10-08 8:47 ` Henning Hraban Ramm
2010-10-08 8:54 ` luigi scarso
2010-10-08 10:19 ` Hans Hagen
2010-10-07 10:16 ` Robin.Kirkham
2010-10-07 11:02 ` Henning Hraban Ramm
2010-10-07 10:27 ` Patrick Gundlach
2010-10-07 15:44 ` Henning Hraban Ramm
2010-10-07 15:48 ` luigi scarso
2010-10-07 16:15 ` Henning Hraban Ramm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95274FC9-42F1-4842-9943-103608507CB4@awi.de \
--to=florian.wobbe@awi.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).