[rabbitmq-discuss] rabbitmq on yocto/openembedded

Sat Feb 2 09:20:17 GMT 2013

Looks like the rpm is populated with a minimal erlang subset. Is there a dependency list for rabbitmq on erlang libraries?  I added in mnesia and then found that os_mon was required, so if there's a definitive list, it would save me a few iterations…

Tim
On 1 Feb 2013, at 13:41, Simon MacMullen <simon at rabbitmq.com> wrote:

> I don't know if this is a silly mistake somewhere. The error description is 'undef', encountered invoking mnesia:system_info(directory) - i.e. that function wasn't found. Since that's the very first interaction RabbitMQ has with Mnesia, I suspect Mnesia just isn't there at all. I'm not sure I understand how you created the Erlang RPM, but could it be the case that Mnesia wasn't built at all?
> 
> Cheers, Simon
> 
> On 01/02/13 13:29, Tim Coote wrote:
>> I think that I've now got Erlang installed - 'hello world' works,
>> anyway, and openembedded has created what looks like a sensible rpm:
>> erlang-R15B-r3.armv5te
>> 
>> However, the generic unix install seems unable to get going - I get an
>> erlang crash dump and the /var/log/rabbitmq at nodename does not tell me
>> very much about where to look, if I start the server with
>> rabbitmq-server (as user rabbitmq or as user root):
>> 
>> [code]
>> =INFO REPORT==== 31-Jan-2013::22:26:04 ===
>> Error description:
>>    undef
>> 
>> Log files (may contain more information):
>>    /var/log/rabbitmq/rabbit at qemuarm.log
>> <mailto:var/log/rabbitmq/rabbit at qemuarm.log>
>>    /var/log/rabbitmq/rabbit at qemuarm-sasl.log
>> <mailto:var/log/rabbitmq/rabbit at qemuarm-sasl.log>
>> 
>> Stack trace:
>>    [{mnesia,system_info,[directory],[]},
>>     {rabbit_mnesia,ensure_mnesia_dir,0,[]},
>>     {rabbit_node_monitor,prepare_cluster_status_files,0,[]},
>>     {rabbit,'-boot/0-fun-1-',0,[]},
>>     {rabbit,start_it,1,[]},
>>     {init,start_it,1,[]},
>>     {init,start_em,1,[]}]
>> [/code]
>> 
>> 
>> I've checked the file permissions (or got around them by running as
>> root.)  How do I go about debugging a rabbitmq install?  Are there smoke
>> tests for erlang/rabbit that I can try that check out the set up? or
>> something else - the documentation that I've found so far seems to
>> assume that I can get past this point, so I'd assume that I'm making
>> some silly mistake somewhere.
>> 
>> Tim
>> On 11 Dec 2012, at 10:07, Alvaro Videla <videlalvaro at gmail.com
>> <mailto:videlalvaro at gmail.com>> wrote:
>> 
>>> Hi,
>>> 
>>> I know the Erlang Solutions guys have been playing with Erlang
>>> Embedded, you can find more info here:
>>> https://www.erlang-solutions.com/downloads/download-erlang-otp
>>> 
>>> I know they also have a github repo for it somewhere.
>>> 
>>> Regards,
>>> 
>>> Alvaro
>>> 
>>> 
>>> 
>>> On Tue, Dec 11, 2012 at 11:00 AM, Emile Joubert <emile at rabbitmq.com
>>> <mailto:emile at rabbitmq.com>> wrote:
>>> 
>>> 
>>>    Hi Tim,
>>> 
>>>    On 10/12/12 21:26, Tim Coote wrote:
>>>    > Has anyone got any insights into getting rabbitmq onto an open
>>>    > embedded/yocto linux build?
>>> 
>>>    I suspect the biggest challenge will be to get a sufficiently recent
>>>    version of Erlang installed. Once you have that the generic Unix
>>>    binary
>>>    should run just fine.
>>> 
>>>    For details about the generic Unix tarball:
>>>    http://www.rabbitmq.com/install-generic-unix.html
>>> 
>>>    For details about required versions of Erlang for various features:
>>>    http://www.rabbitmq.com/which-erlang.html
>>> 
>>> 
>>> 
>>>    -Emile
>>>    _______________________________________________
>>>    rabbitmq-discuss mailing list
>>>    rabbitmq-discuss at lists.rabbitmq.com
>>>    <mailto:rabbitmq-discuss at lists.rabbitmq.com>
>>>    https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>> 
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> 
> 
> 
> -- 
> Simon MacMullen
> RabbitMQ, VMware