supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Frank Barknecht <fbar@footils.org>
Subject: runit (and diet) segfaulting on Debian stable vserver
Date: Fri, 29 Dec 2006 17:56:47 +0000 (UTC)	[thread overview]
Message-ID: <loom.20061229T185013-143@post.gmane.org> (raw)

Hi,

I use runit on a Debian stable UML virtual hosting server, which was recently
copied to a new Vserver installation. Now it has a kernel 2.6.18.1-bb2 ... and
runit doesn't start anymore. :(

All runsv*-tools give an immediate segfault, when called. The installed packages
are all plain Debian stable packages. I tried to recompile my own runit package,
but through this I found, that also the "diet" tool called in "compile" will
segfault. Now I'm a bit at loss. 

A gdb-backtrace of run* will only give something like: 
"Cannot access memory at address 0xbfb63000"

I would be grateful for any hints what might be the cause for this or where to
look for further clues.

Ciao
-- 
Frank Barknecht





             reply	other threads:[~2006-12-29 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 17:56 Frank Barknecht [this message]
2006-12-30 14:14 ` Frank Barknecht

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=loom.20061229T185013-143@post.gmane.org \
    --to=fbar@footils.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).