* [sup-talk] Can't start Sup, allegedly because of a locked index.
@ 2010-12-02 10:06 Shadowfirebird
2010-12-02 10:53 ` Michael Stapelberg
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Shadowfirebird @ 2010-12-02 10:06 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]
Anyone got any ideas how I get out of this?
>>>>
$ sup
Error: the index is locked by another process! User '' on
host '' is running with pid .
The process was alive as of at least 4216 minutes ago.
Should I ask that process to kill itself (y/n)? n
Sorry, couldn't unlock the index.
$
$ sup
Error: the index is locked by another process! User '' on
host '' is running with pid .
The process was alive as of at least 4216 minutes ago.
Should I ask that process to kill itself (y/n)? y
Ok, trying to kill process...
Terminated
$
$ sup
Error: the index is locked by another process! User '' on
host '' is running with pid .
The process was alive as of at least 4217 minutes ago.
Should I ask that process to kill itself (y/n)?
<<<<
--
What a tangled web we weave / Go 'round with circumstance / Someone show me
how to tell / The dancer from the dance...
[-- Attachment #1.2: Type: text/html, Size: 1040 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 10:06 [sup-talk] Can't start Sup, allegedly because of a locked index Shadowfirebird @ 2010-12-02 10:53 ` Michael Stapelberg 2010-12-02 12:36 ` Shadowfirebird 2010-12-02 12:54 ` Iain 2010-12-02 13:13 ` David Rysdam 2 siblings, 1 reply; 8+ messages in thread From: Michael Stapelberg @ 2010-12-02 10:53 UTC (permalink / raw) To: sup-talk Hi Shadowfirebird, Excerpts from Shadowfirebird's message of 2010-12-02 11:06:16 +0100: > Anyone got any ideas how I get out of this? Do an 'strace -fF -s2048 -o /tmp/sup.log sup' and check the resulting /tmp/sup.log for errors (searching from the very bottom), like -EPERM or something. If that doesn’t help, bzip2 that file, upload it somewhere, and send us/me a link to it. Best regards, Michael _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 10:53 ` Michael Stapelberg @ 2010-12-02 12:36 ` Shadowfirebird 2010-12-02 12:56 ` Paul Grove 2010-12-02 13:00 ` Michael Stapelberg 0 siblings, 2 replies; 8+ messages in thread From: Shadowfirebird @ 2010-12-02 12:36 UTC (permalink / raw) To: sup-talk [-- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 12:36 ` Shadowfirebird @ 2010-12-02 12:56 ` Paul Grove 2010-12-02 13:00 ` Michael Stapelberg 1 sibling, 0 replies; 8+ messages in thread From: Paul Grove @ 2010-12-02 12:56 UTC (permalink / raw) To: sup-talk [-- Attachment #1.1: Type: text/plain, Size: 2690 bytes --] I had this problem myself, exactly as described by Shadowfirebird. I cant 100% recall the steps it took to resolve it, but I know I had to delete the ~/.sup/lock file, and then I manually killed all instances of sup just to be sure. Maybe I did something else as well - maybe I didn't, It was only a few weeks ago but I got such a bad memory. Hope this helps, Paul Grove Excerpts from Shadowfirebird's message of Thu Dec 02 12:36:21 +0000 2010: > 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: signature.asc --] [-- Type: application/pgp-signature, Size: 490 bytes --] [-- Attachment #2: Type: text/plain, Size: 140 bytes --] _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 12:36 ` Shadowfirebird 2010-12-02 12:56 ` Paul Grove @ 2010-12-02 13:00 ` Michael Stapelberg 1 sibling, 0 replies; 8+ messages in thread From: Michael Stapelberg @ 2010-12-02 13:00 UTC (permalink / raw) To: sup-talk Hi Shadowfirebird, Excerpts from Shadowfirebird's message of 2010-12-02 13:36:21 +0100: > 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. Heh, right. Passing 0 as pid to kill() is not such a good idea. In your case, I would suggest deleting the lock files manually (use ls -la .sup/xapian to find them) Best regards, Michael _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 10:06 [sup-talk] Can't start Sup, allegedly because of a locked index Shadowfirebird 2010-12-02 10:53 ` Michael Stapelberg @ 2010-12-02 12:54 ` Iain 2010-12-02 13:07 ` Shadowfirebird 2010-12-02 13:13 ` David Rysdam 2 siblings, 1 reply; 8+ messages in thread From: Iain @ 2010-12-02 12:54 UTC (permalink / raw) To: sup-talk > Anyone got any ideas how I get out of this? > > >>>> > $ sup > Error: the index is locked by another process! User '' on > host '' is running with pid . > The process was alive as of at least 4216 minutes ago. > Should I ask that process to kill itself (y/n)? n > Sorry, couldn't unlock the index. Something similar happened to me once. I just did "rm ~/.sup/lock", then started sup as normal. Does that work for you? _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 12:54 ` Iain @ 2010-12-02 13:07 ` Shadowfirebird 0 siblings, 0 replies; 8+ messages in thread From: Shadowfirebird @ 2010-12-02 13:07 UTC (permalink / raw) To: Iain; +Cc: sup-talk [-- Attachment #1.1: Type: text/plain, Size: 843 bytes --] Yes!! Thank you! On Thu, Dec 2, 2010 at 12:54 PM, Iain <rhomunuq+ml_sup@gmail.com<rhomunuq%2Bml_sup@gmail.com> > wrote: > > Anyone got any ideas how I get out of this? > > > > >>>> > > $ sup > > Error: the index is locked by another process! User '' on > > host '' is running with pid . > > The process was alive as of at least 4216 minutes ago. > > Should I ask that process to kill itself (y/n)? n > > Sorry, couldn't unlock the index. > > Something similar happened to me once. I just did "rm ~/.sup/lock", then > started sup as normal. Does that work for you? > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > -- What a tangled web we weave / Go 'round with circumstance / Someone show me how to tell / The dancer from the dance... [-- Attachment #1.2: Type: text/html, Size: 1410 bytes --] [-- Attachment #2: Type: text/plain, Size: 140 bytes --] _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 2010-12-02 10:06 [sup-talk] Can't start Sup, allegedly because of a locked index Shadowfirebird 2010-12-02 10:53 ` Michael Stapelberg 2010-12-02 12:54 ` Iain @ 2010-12-02 13:13 ` David Rysdam 2 siblings, 0 replies; 8+ messages in thread From: David Rysdam @ 2010-12-02 13:13 UTC (permalink / raw) To: sup-talk An agent or agents purporting to be Shadowfirebird said: > Anyone got any ideas how I get out of this? > > >>>> > $ sup > Error: the index is locked by another process! User '' on > host '' is running with pid . > The process was alive as of at least 4216 minutes ago. > Should I ask that process to kill itself (y/n)? n > Sorry, couldn't unlock the index. I don't have this exact problem, but I have had problems where sup has claimed to be unable to kill another instance because of a lock problem. I get a different message, but I'm running an old version. I find that sometimes Xapian has left a lockfile. If I delete .sup/xapian/flintlock then I can start sup just fine. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-12-02 13:49 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-12-02 10:06 [sup-talk] Can't start Sup, allegedly because of a locked index Shadowfirebird 2010-12-02 10:53 ` Michael Stapelberg 2010-12-02 12:36 ` Shadowfirebird 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox