Subject: [sup-talk] problem starting sup

From: Hamish D <[email-masked]>
Date: Wed, 26 Jan 2011 23:59:24 +0000

I have a strange problem when trying to start sup from master. I am
running Ubuntu 10.10 x86_64. I have installed ruby and rubygems from
the archive, but installed all the gems with "gem install" and sup is
from git. I don't seem to be able to install xapian due to it looking
for some 32 bit libraries on a path that doesn't exist on my 64 bit
system, so I have installed the xapian-full gem, which installs fine.

When I start sup I get:

$ SUP_LOG_LEVEL=debug ruby -I /home/mish/dev/sup/sup-mainline/lib -w
/home/mish/dev/sup/sup-mainline/bin/sup
...
[Wed Jan 26 23:58:42 +0000 2011] locking /home/mish/.sup/lock...
/home/mish/dev/sup/sup-mainline/lib/sup/index.rb:84: warning: instance
variable @lock_update_thread not initialized
/home/mish/dev/sup/sup-mainline/lib/sup/util.rb:602:in
`method_missing': no Redwood::HookManager instance defined in method
call to run! (RuntimeError)
	from /home/mish/dev/sup/sup-mainline/bin/sup:381

Any ideas?

Hamish Downer
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Marc Weber <[email-masked]>
Date: Thu, 27 Jan 2011 01:24:24 +0100

> Any ideas?

No, but you should talk about ruby --version output
and the git version of sup you're using?

Marc Weber

---

From: William Morgan <[email-masked]>
Date: Wed, 26 Jan 2011 20:57:36 -0500

>     from /home/mish/dev/sup/sup-mainline/bin/sup:381

This is masking another exception. Something is breaking before
HookManager is initialized, and in rescuing from it, we try and run the
shutdown hook, which of course dies.

Can you comment out that line? Or maybe try commenting out the three
lines starting with rescue and ending with ensure at line 372 in
bin/sup? This should at least unmask the exception.

Initting the hookmanager happens very early on in Sup, so I'm guessing
there's something wrong with your config file or the log file (the only
two things that happen before the hookmanager is brought up).
-- 
William <[email-masked]>
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Hamish D <[email-masked]>
Date: Sun, 30 Jan 2011 23:07:02 +0000

> two things that happen before the hookmanager is brought up).

I moved .sup out of the way and the error went away. Then with playing
with it I managed to delete the .sup directory that caused the errors
:/ If I ever happen to reproduce this I'll know what to do anyway.

Hamish