[rabbitmq-discuss] Problem installing RabbitMQ with Puppet on CentOS 6.2

[Simon MacMullen]

Ah, thanks for the pointer.

Hmm, maybe we should explicitly set HOME in these scripts...

Cheers, Simon

On 01/02/13 07:24, James Carr wrote:
> I thought I'd point out the original author solved his problems:
> http://serverfault.com/questions/434942/veewee-vagrant-puppet-erlang-and-rabbitmq
>
> Only posting this on the list to help others who come across it as I
> had the exact same problem this evening. :)
>
>
> Thanks,
> James
>
>
> On Fri, Oct 5, 2012 at 4:45 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
>> Hmm. There's nothing very obvious that I can think of. I've looked in the
>> OTP source and that message really only appears if HOME is not set.
>>
>> Things you might try:
>>
>> * Run /usr/lib/rabbitmq/bin/rabbitmq-plugins instead, to remove a wrapper
>> script
>>
>> * Edit /usr/lib/rabbitmq/bin/rabbitmq-plugins to insert "echo $HOME" just
>> before "exec erl", see if it's really set at that point.
>>
>> * If all else fails, edit the enabled plugins file directly rather than
>> invoking rabbitmq-plugins. Set the contents of /etc/rabbitmq/enabled_plugins
>> to exactly the string:
>>
>> [rabbitmq_management].
>>
>> including the full stop.
>>
>> Cheers, Simon
>>
>>
>> On 05/10/12 07:05, Tobias Wissmüller wrote:
>>>
>>> Hi Everyone,
>>>
>>> I encounter a strange problem when applying my puppet module I have
>>> created for installing RabbitMQ. To be more precise, I encounter the
>>> problem when enabling the plugins.
>>>
>>> The relevant resources look as follows:
>>>
>>> |$version = "2.8.7"
>>> $url     =
>>> "http://www.rabbitmq.com/releases/rabbitmq-server/v${version}/rabbitmq-server-${version}-1.noarch.rpm"
>>>
>>> package{"erlang":
>>>       ensure => "present",
>>> }
>>>
>>> package{"rabbitmq-server":
>>>       provider => "rpm",
>>>       source   => $url,
>>>       require  => Package["erlang"]
>>> }
>>>
>>> exec{"rabbitmq-plugins":
>>>       path    => "/usr/bin:/usr/sbin:/bin",
>>>       command => "rabbitmq-plugins enable rabbitmq_management",
>>>       require => Package["rabbitmq-server"]
>>> }|
>>>
>>>
>>> The error I get:
>>>
>>> |/Stage[main]/Rabbitmq/Exec[rabbitmq-plugins]/returns: erlexec: HOME must
>>> be set|
>>>
>>> |/Stage[main]/Rabbitmq/Service[rabbitmq-server]: Dependency
>>> Exec[rabbitmq-plugins] has failures: true
>>> |
>>>
>>> The thing is, that HOME is set. Have checked that during a puppet run by
>>> creating an exec resource to echo HOME.
>>>
>>> When I log into the box that I create with veewee and vagrant, I can
>>> execute "rabbitmq-plugins enable rabbitmq_management" without any
>>> problems. But I always get the error from within puppet.
>>>
>>> Starting rabbitmq-server leaves me with the following:
>>>
>>> |[{pid,2834},
>>> {running_applications,[{rabbit,"RabbitMQ","2.8.7"},
>>>                       {ssl,"Erlang/OTP SSL application","4.1.6"},
>>>                       {public_key,"Public key infrastructure","0.13"},
>>>                       {crypto,"CRYPTO version 2","2.0.4"},
>>>                       {mnesia,"MNESIA  CXC 138 12","4.5"},
>>>                       {os_mon,"CPO  CXC 138 46","2.2.7"},
>>>                       {sasl,"SASL  CXC 138 11","2.1.10"},
>>>                       {stdlib,"ERTS  CXC 138 10","1.17.5"},
>>>                       {kernel,"ERTS  CXC 138 10","2.14.5"}]},
>>> {os,{unix,linux}},
>>> {erlang_version,"Erlang R14B04 (erts-5.8.5) [source] [64-bit] [rq:1]
>>> [async-threads:30] [kernel-poll:true]\n"},
>>> {memory,[{total,24993120},
>>>         {processes,10328496},
>>>         {processes_used,10321296},
>>>         {system,14664624},
>>>         {atom,1175905},
>>>         {atom_used,1143841},
>>>         {binary,17192},
>>>         {code,11416020},
>>>         {ets,766168}]},
>>> {vm_memory_high_watermark,0.4},
>>> {vm_memory_limit,205851852},
>>> {disk_free_limit,1000000000},
>>> {disk_free,7089795072},
>>> {file_descriptors,[{total_limit,924},
>>>                   {total_used,4},
>>>                   {sockets_limit,829},
>>>                   {sockets_used,2}]},
>>> {processes,[{limit,1048576},{used,131}]},
>>> {run_queue,0},
>>> {uptime,6}]|
>>>
>>>
>>> The whole puppet manifest can be found under
>>>
>>> https://github.com/tobias-wissmueller/dev_ops_central/blob/master/modules/rabbitmq/manifests/init.pp
>>>
>>> Also have posted this problem over at Serverfault
>>>
>>> <http://serverfault.com/questions/434942/veewee-vagrant-puppet-erlang-and-rabbitmq>.
>>>
>>>
>>> Any help is highly appreciated since I am totally stuck here.
>>>
>>> Thanks a lot!
>>>
>>> Cheers,
>>> Tobi
>>>
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>
>>
>>
>> --
>> Simon MacMullen
>> RabbitMQ, VMware
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> 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