can't enable plugin

[sonoman]

This is the output of the command line. rabbithub plug-in is expecting a plugin named "rabbitmq_mochiweb", which I can't find on my rabbitmq distribution. I've tried enabling similar plugins (see below), with no success.

root@ubuntu:/mnt/hgfs/Shared# sudo rabbitmq-plugins enable rabbithub
Error: The following dependencies could not be found:
rabbitmq_mochiweb
root@ubuntu:/mnt/hgfs/Shared# sudo rabbitmq-plugins enable mochiweb
Plugin configuration unchanged.
root@ubuntu:/mnt/hgfs/Shared# sudo rabbitmq-plugins enable webmachine
Plugin configuration unchanged.
root@ubuntu:/mnt/hgfs/Shared# sudo rabbitmq-plugins enable rabbithub
Error: The following dependencies could not be found:
rabbitmq_mochiweb

Is there a way to solve this ?

[tonyg]

I'm afraid I haven't been keeping the rabbithub codebase up-to-date with respect to RabbitMQ. It probably needs some work to run with recent releases; in particular, to run with the current RabbitMQ HTTP-server APIs.

[sonoman]

It seems like replacing rabbitmq_mochiweb by "mochiweb", allowed me to enable the plugin. now I'm gonna try if it actually works.
BTW, are you planning to evolve this plugin ? or is this project kind of "idle" ?do you know if there is another alternative for working with webhooks ?

[tonyg]

On 8 April 2013 14:51, sonoman notifications@github.com wrote:

It seems like replacing rabbitmq_mochiweb by "mochiweb", allowed me to
enable the plugin.

That's good news!

now I'm gonna try if it actually works.

I fear that it will not...

BTW, are you planning to evolve this plugin ? or is this project kind of
"idle" ?do you know if there is another alternative for working with
webhooks ?

Both: I do intend to come back to it someday, and for now it is "idle". I
recommend asking on the RabbitMQ mailing list for help with
webhooks/PSHB/HTTP-access-to-messaging.

Regards,
Tony

[brc859844]

I helped Tony bring the code up to date to work with 2.8.x, but I must
admit that I've not tried it with anything higher than 2.8.7. What version
of RabbitMQ are you using?

Also, you might find some of the junk in
http://assortedrambles.blogspot.co.nz/2012/11/the-polygot-rabbit.htmlvaguely
useful

On Tue, Apr 9, 2013 at 7:11 AM, Tony Garnock-Jones <notifications@github.com

wrote:

On 8 April 2013 14:51, sonoman notifications@github.com wrote:

It seems like replacing rabbitmq_mochiweb by "mochiweb", allowed me to
enable the plugin.

That's good news!

now I'm gonna try if it actually works.

I fear that it will not...

BTW, are you planning to evolve this plugin ? or is this project kind of
"idle" ?do you know if there is another alternative for working with
webhooks ?

Both: I do intend to come back to it someday, and for now it is "idle". I
recommend asking on the RabbitMQ mailing list for help with
webhooks/PSHB/HTTP-access-to-messaging.

Regards,
Tony

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-16071806
.

[sonoman]

Sadly i got some errors during startup of the broker after enabling rabbithub. I tried recompiling (a recommendation i found in some blog for the same error on another component), but it got worst...that time it didn't even start the broker. Bad luck :(

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
Loading of /var/lib/rabbitmq/mnesia/rabbit@ubuntu-plugins-expand/rabbithub/ebin/
rabbithub_subscription.beam failed: badfile

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
beam/beam_load.c(1365): Error loading module rabbithub_subscription_sup:
use of opcode 153; this emulator supports only up to 152

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
Loading of /var/lib/rabbitmq/mnesia/rabbit@ubuntu-plugins-expand/rabbithub/ebin/
rabbithub_subscription_sup.beam failed: badfile

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
beam/beam_load.c(1365): Error loading module rabbithub_sup:
use of opcode 153; this emulator supports only up to 152

[brc859844]

This suggests that the RabbitHub plugin was built with a higher version of
Erlang than the one your using with RabbitMQ... whatever version(s) are you
using?

On Tue, Apr 9, 2013 at 9:30 AM, sonoman notifications@github.com wrote:

Sadly i got some errors during startup of the broker after enabling
rabbithub. I tried recompiling (a recommendation i found in some blog for
the same error on another component), but it got worst...that time it
didn't even start the broker. Bad luck :(

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
Loading of /var/lib/rabbitmq/mnesia/rabbit@ubuntu-plugins-expand
/rabbithub/ebin/
rabbithub_subscription.beam failed: badfile

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
beam/beam_load.c(1365): Error loading module rabbithub_subscription_sup:
use of opcode 153; this emulator supports only up to 152

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
Loading of /var/lib/rabbitmq/mnesia/rabbit@ubuntu-plugins-expand
/rabbithub/ebin/
rabbithub_subscription_sup.beam failed: badfile

=ERROR REPORT==== 8-Apr-2013::14:26:23 ===
beam/beam_load.c(1365): Error loading module rabbithub_sup:
use of opcode 153; this emulator supports only up to 152

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-16080117
.

[sonoman]

This is the output when I enter erlang's interactive shell:

root@ubuntu:/mnt/hgfs/Shared/aws-dev# erl
Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:2:2] [rq:2] [async-threads:0] [kernel-poll:false]

Eshell V5.8.5 (abort with ^G)

[sonoman]

I've successfully started rabbitmq with erlang R16B, but again, when I enable rabbithub, rabbitmq stops working. this is the log with the error at startup (after enabling rabbithub).

=INFO REPORT==== 9-Apr-2013::11:41:53 ===
Error description:
undef

Log files (may contain more information):
/var/log/rabbitmq/rabbit@ubuntu.log
/var/log/rabbitmq/rabbit@ubuntu-sasl.log

Stack trace:
[{rabbit_mochiweb,register_context_handler,
["rabbithub",[],#Fun<rabbithub_web.0.64600142>,
"RabbitHub"],
[]},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},
{rabbit,run_boot_step,1,[]},
{rabbit,'-start/2-lc$^0/1-0-',1,[]},
{rabbit,start,2,[]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,274}]}]

=INFO REPORT==== 9-Apr-2013::11:41:54 ===
stopped TCP Listener on [::]:5672

=INFO REPORT==== 9-Apr-2013::11:41:54 ===
application: rabbit
exited: {bad_return,{{rabbit,start,[normal,[]]},
{'EXIT',{rabbit,failure_during_boot,undef}}}}
type: temporary

[tonyg]

Right, this is the failure I expected. Certain modules have been renamed recent(ish)ly I think. Some code changes in Rabbithub will be required. They will be minor (I hope) but they are necessary.

[sonoman]

Help me understand and I will give a try (though I know nothing about erlang :) )...
This "application_master" that doesn't exist anymore, is a module from rabbit_mochiweb that rabbithub requires ?

[tonyg]

It's actually the other end of the stack trace that's the innermost: rabbit_mochiweb:register_context_handler/4 seems to no longer be present.

[brc859844]

If you just want to play around and experiment with the RabbitHub plugin, I
can give you internet access to an instance. If this would be of interest,
ping be an email directly (brett.r.cameron@gmail.com) and I'll send you
details.

Brett

On Wed, Apr 10, 2013 at 8:57 AM, Tony Garnock-Jones <
notifications@github.com> wrote:

It's actually the other end of the stack trace that's the innermost:
rabbit_mochiweb:register_context_handler/4 seems to no longer be present.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-16139695
.

[sonoman]

actually I'm trying to execute it in our rabbitmq environment....I think I'll try to finish with the re-compilation...running into some issues now (like for example, i can't find the xmerl.hrl include file anywhere in my system :( )