From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
Date: Thu, 2 Dec 2010 12:36:21 +0000 [thread overview]
Message-ID: <AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com> (raw)
In-Reply-To: <1291287153-sup-8966@midna.zekjur.net>
[-- Attachment #1.1: Type: text/plain, Size: 2090 bytes --]
Well, I'm not seeing any errors. But the log file does explain what is
going on, I think. Sup says the other process that it is trying to kill
.... is itself; the process that is doing the killing.
I can still try and upload the log file if anyone is interested; not sure
where right now. Would a public folder on Dropbox be okay?
Relevant last few lines pasted below. Note, three from the bottom,
"kill(18723, SIGTERM)". 18723 is the *current* process number, so if I'm
reading this right, it's self-destructing.
>>>>
write(2, "Error: the index is locked by another process! User '' on\nhost ''
is running with pid .\nThe process was alive as of at least 4365 minutes
ago.\n\n"..., 145) = 145
write(2, "Should I ask that process to kill itself (y/n)? "..., 48) = 48
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f7d384bc000
read(0, "y\n"..., 1024) = 2
write(2, "Ok, trying to kill process..."..., 29) = 29
write(2, "\n"..., 1) = 1
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
kill(0, SIGTERM) = 0
--- SIGTERM (Terminated) @ 0 (0) ---
rt_sigreturn(0xf) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {0x7f7d380483e0, [INT],
SA_RESTORER|SA_RESTART, 0x7f7d37391040}, 8) = 0
rt_sigaction(SIGTERM, {SIG_DFL}, {0x7f7d380483e0, [], SA_RESTORER,
0x7f7d37da0080}, 8) = 0
kill(18723, SIGTERM) = 0
--- SIGTERM (Terminated) @ 0 (0) ---
+++ killed by SIGTERM +++
<<<<
[-- Attachment #1.2: Type: text/html, Size: 2330 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-02 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 10:06 Shadowfirebird
2010-12-02 10:53 ` Michael Stapelberg
2010-12-02 12:36 ` Shadowfirebird [this message]
2010-12-02 12:56 ` Paul Grove
2010-12-02 13:00 ` Michael Stapelberg
2010-12-02 12:54 ` Iain
2010-12-02 13:07 ` Shadowfirebird
2010-12-02 13:13 ` David Rysdam
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='AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com' \
--to=shadowfirebird@gmail.com \
--cc=sup-talk@rubyforge.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