supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Count László de Almásy" <calmasy@gmail.com>
To: supervision@list.skarnet.org
Subject: supervise causes cpu spike
Date: Sun, 14 Dec 2008 03:33:23 +0500	[thread overview]
Message-ID: <abb783b90812131433sa9183e5m21f8f1f853b2ec51@mail.gmail.com> (raw)

Hi,

I'm hoping someone can help me diagnose why supervising my OpenSim
process causes it to go up to 100% cpu, while when not supervised, I
have no such problems. This is on Debian/Linux amd64, with djb's
latest stock daemontools.

Here's my run script:

======
bee:/~# cat /service/opensim/run
#!/bin/sh
ulimit -s 262144
cd /home/opensim/opensim/bin
exec setuidgid opensim mono OpenSim.exe
======

stopping/restarting with svc works as expected. it's just, the cpu
goes right up to 100% with the supervised mono process. running strace
on the process shows what's happening:

read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0
read(0, ""..., 1024)                    = 0

[...]

over and over. it's like something is sending the process an empty
character repeatedly. Can someone tell me what I did wrong here, or
what is causing this?

-- 
Cheers, László


             reply	other threads:[~2008-12-13 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 22:33 Count László de Almásy [this message]
2008-12-13 23:49 ` OpenSim.exe causes cpu spike (Re: supervise causes cpu spike) Charlie Brady
2008-12-14  2:26   ` Count László de Almásy
2008-12-14  6:04     ` Charlie Brady
2008-12-14  6:18       ` Count László de Almásy
2008-12-16 10:48 ` supervise causes cpu spike Laurent Bercot

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=abb783b90812131433sa9183e5m21f8f1f853b2ec51@mail.gmail.com \
    --to=calmasy@gmail.com \
    --cc=supervision@list.skarnet.org \
    /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).