Subject: [sup-talk] Crashing ssh + sup, bad combo

From: [email-masked] (Guillaume Quintard)
Date: Fri, 21 Aug 2009 18:00:29 +0200

Sooooo, here's what happened: I was running sup through ssh, minding
my own business, when suddenly, my local machine crashed. I reboot,
reconnect, sup is somehow still running, I kill it (with a good ol'
kill, because the lock file was empty so sup could ask for a seppuku),
and no I have this:
[Fri Aug 21 17:54:54 +0200 2009] ERROR: oh crap, an exception
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. If you don't mind, please send the
contents of ~/.sup/exception-log.txt and a brief report of the
circumstances to sup-talk at rubyforge dot orgs so that I might
address this problem. Thank you!

Sincerely,
William
----------------------------------------------------------------
--- RuntimeError from thread: load threads for thread-index-mode
wrong id called on nil
./lib/sup.rb:17:in `id'
./lib/sup/xapian_index.rb:155:in `each_message_in_thread_for'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
./lib/sup/xapian_index.rb:336:in `synchronize'
./lib/sup/xapian_index.rb:155:in `each_message_in_thread_for'
./lib/sup/thread.rb:341:in `load_thread_for_message'
./lib/sup/thread.rb:333:in `load_n_threads'
./lib/sup/xapian_index.rb:149:in `each_id_by_date'
./lib/sup/xapian_index.rb:142:in `each_id'
./lib/sup/xapian_index.rb:142:in `each'
./lib/sup/xapian_index.rb:142:in `each_id'
./lib/sup/xapian_index.rb:149:in `each_id_by_date'
./lib/sup/thread.rb:328:in `load_n_threads'
./lib/sup/modes/thread-index-mode.rb:623:in `__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
./lib/sup/modes/thread-index-mode.rb:607:in `load_n_threads_background'
./lib/sup.rb:77:in `reporting_thread'
./lib/sup.rb:75:in `initialize'
./lib/sup.rb:75:in `new'
./lib/sup.rb:75:in `reporting_thread'
./lib/sup/modes/thread-index-mode.rb:606:in `load_n_threads_background'
./lib/sup/modes/thread-index-mode.rb:676:in `__unprotected_load_threads'
(eval):12:in `load_threads'
bin/sup:192

me no likey :-(

-- 
Guillaume

---

From: [email-masked] (Mark Alexander)
Date: Fri, 21 Aug 2009 14:57:10 -0400

This isn't directly related, and you may already know about this, and
apologies if that's the case... but I highly recommend running screen
on the machine where you're running sup.  That way you don't lose any
work when your ssh connection drops for any reason.

---

From: [email-masked] (Guillaume Quintard)
Date: Fri, 21 Aug 2009 21:29:22 +0200

On Fri, Aug 21, 2009 at 8:57 PM, Mark Alexander<marka at pobox.com> wrote:
> on the machine where you're running sup. ?That way you don't lose any

Yup, I know, but screen isn't yet natural to me, and I tend to forgot
to use it :-)

-- 
Guillaume

---

From: [email-masked] (Rich Lane)
Date: Fri, 21 Aug 2009 16:57:55 -0400

> kill, because the lock file was empty so sup could ask for a seppuku),

I'm guessing this is an inconsistency between your xapian and entries.db
databases. A sup-sync -a might fix it.

I posted a patch a few days ago that moves all index data into Xapian to
prevent this sort of issue. William, could you take a look at / merge that
patch?

---

From: [email-masked] (William Morgan)
Date: Mon, 24 Aug 2009 15:46:12 -0700

> --- RuntimeError from thread: load threads for thread-index-mode

Let me know if this is still a problem.
-- 
William <wmorgan-sup at masanjin.net>