* [sup-talk] Exception crashing sup
@ 2011-04-26 17:03 Marc Hartstein
2011-04-26 20:43 ` Marc Hartstein
0 siblings, 1 reply; 2+ messages in thread
From: Marc Hartstein @ 2011-04-26 17:03 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Something happened causing sup to crash, and now I get this exception
every time I try to start. I'm currently tracking master.
I tried (afterward) doing a dump/sync --restore cycle, which didn't
fix it. I thought maybe the message which had been being sent when it
first crashed had gotten corrupted in sent.mbox, so I went in with
mutt and deleted that manually. After another sync after that, sup
started up fine and I was able to use it for a bit, but then it
crashed again. It felt like it was as it tried to load more messages
to the inbox view, so I'm now thinking the reason it was briefly
working was just that enough messages had come in over a couple of
days to push the culprit past what was getting loaded at startup.
The log doesn't look like it will be much help, but I'm attaching it ayway.
Any ideas?
[-- Attachment #2: exception-log.txt --]
[-- Type: text/plain, Size: 1992 bytes --]
--- RuntimeError from thread: load threads for thread-index-mode
/home/magus/src/sup/lib/sup/index.rb:555:in `find_docid'
/home/magus/src/sup/lib/sup/index.rb:560:in `find_doc'
/home/magus/src/sup/lib/sup/index.rb:570:in `get_entry'
/home/magus/src/sup/lib/sup/index.rb:200:in `build_message'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/home/magus/src/sup/lib/sup/index.rb:579:in `synchronize'
/home/magus/src/sup/lib/sup/index.rb:200:in `build_message'
/home/magus/src/sup/lib/sup/index.rb:194:in `each_message_in_thread_for'
/home/magus/src/sup/lib/sup/thread.rb:349:in `call'
/home/magus/src/sup/lib/sup/thread.rb:349:in `load_thread_for_message'
/home/magus/src/sup/lib/sup/index.rb:194:in `each_message_in_thread_for'
/home/magus/src/sup/lib/sup/index.rb:194:in `each'
/home/magus/src/sup/lib/sup/index.rb:194:in `each_message_in_thread_for'
/home/magus/src/sup/lib/sup/thread.rb:347:in `load_thread_for_message'
/home/magus/src/sup/lib/sup/thread.rb:339:in `load_n_threads'
/home/magus/src/sup/lib/sup/index.rb:155:in `each_id_by_date'
/home/magus/src/sup/lib/sup/index.rb:250:in `each_id'
/home/magus/src/sup/lib/sup/index.rb:250:in `each'
/home/magus/src/sup/lib/sup/index.rb:250:in `each_id'
/home/magus/src/sup/lib/sup/index.rb:155:in `each_id_by_date'
/home/magus/src/sup/lib/sup/thread.rb:334:in `load_n_threads'
/home/magus/src/sup/lib/sup/modes/thread-index-mode.rb:640:in `__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
/home/magus/src/sup/lib/sup/modes/thread-index-mode.rb:624:in `load_n_threads_background'
/home/magus/src/sup/lib/sup.rb:78:in `reporting_thread'
/home/magus/src/sup/lib/sup.rb:76:in `initialize'
/home/magus/src/sup/lib/sup.rb:76:in `new'
/home/magus/src/sup/lib/sup.rb:76:in `reporting_thread'
/home/magus/src/sup/lib/sup/modes/thread-index-mode.rb:623:in `load_n_threads_background'
/home/magus/src/sup/lib/sup/modes/thread-index-mode.rb:694:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/home/magus/src/sup/bin/sup:223
[-- Attachment #3: 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] 2+ messages in thread
* Re: [sup-talk] Exception crashing sup
2011-04-26 17:03 [sup-talk] Exception crashing sup Marc Hartstein
@ 2011-04-26 20:43 ` Marc Hartstein
0 siblings, 0 replies; 2+ messages in thread
From: Marc Hartstein @ 2011-04-26 20:43 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 1067 bytes --]
Excerpts from Marc Hartstein's message of Tue Apr 26 13:03:19 -0400 2011:
> Something happened causing sup to crash, and now I get this exception
> every time I try to start. I'm currently tracking master.
Finally got it (though that outgoing message is lost because I foolishly
deleted it earlier; but that's ok, it wasn't that important anyway).
The message_id for the problem message appears to have appeared twice in
a row in the index. This caused find_docid to fail, ungracefully. Going
into the devel console, finding the message id, and doing
Index.delete("<message_id>") appears to have cleared things up nicely.
I believe the problem may have been caused in the first place by my
impatiently pressing ^L while a message was still sending. Not sure why
this would have this effect, but that was what I did when it crashed.
The outgoing message was GPG-signed, which might be relevant.
Sorry I didn't think to preserve the message for analysis. Although it
appears it made it out to gmail and out to the recipient (and it looks
fine).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 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] 2+ messages in thread
end of thread, other threads:[~2011-04-26 21:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-26 17:03 [sup-talk] Exception crashing sup Marc Hartstein
2011-04-26 20:43 ` Marc Hartstein
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox