[rabbitmq-discuss] Running RabbitMQ server as embedded application

Jorge Diz Pico jorge.diz at nomasystems.com
Wed Mar 27 18:23:24 GMT 2013


I tried my luck at the OTP packaging in RHEL6 and it seems to work as
fine as it did on my MacBook, so I'll take my chances with it.

Thank y'all for your replies.

On Tue, Mar 26, 2013 at 2:30 PM, Alvaro Videla <videlalvaro at gmail.com> wrote:
> Hi,
>
> The OTP packaging has been merged into default, at the moment it works for
> Mac only. Some of the files involved in making the release are here:
> http://hg.rabbitmq.com/rabbitmq-server/file/0271f21bd596/packaging/standalone
>
> Then the sbin scripts have been modified to support different erlang boot
> files and so on.
>
> The related bug branch is bug25271.
>
> Regards,
>
> Alvaro
>
>
> On Tue, Mar 26, 2013 at 2:19 PM, Tim Watson <tim at rabbitmq.com> wrote:
>>
>> Another thing to consider is that you're starting the vm via a script, you
>> might be able to get away with setting SYS_PREFIX in rabbitmq-defaults (as
>> the generic unix packaging does). We're also working on OTP packaging (i.e.,
>> delivering rabbit as a self contained package/release), though I'm not sure
>> what kind of timescales are involved in that.
>>
>> Cheers,
>> Tim
>>
>> On 26 Mar 2013, at 13:11, Tim Watson wrote:
>>
>> > Take a good look at the startup scripts. There are environment variables
>> > aplenty and various things that get passed the beam as arguments - you'll
>> > need to filter through those and make sure everything is set up properly in
>> > order for the startup sequence to work.
>> >
>> > Cheers,
>> > Tim
>> >
>> > On 26 Mar 2013, at 12:18, Jorge Diz Pico wrote:
>> >
>> >> Hi folks, I'm trying to run a RabbitMQ server the OTP way, but it's
>> >> becoming harder than I thought. I added all dependencies to my
>> >> release, but when I run application:start(rabbit), I get the following
>> >> error:
>> >>
>> >> [...]
>> >> -- rabbit boot start
>> >> starting file handle cache server
>> >> ...done
>> >> starting worker pool
>> >> ...done
>> >> starting database
>> >> ...
>> >>
>> >> BOOT FAILED
>> >> ===========
>> >>
>> >> Error description:
>> >>
>> >> {error,{corrupt_or_missing_cluster_files,{error,enoent},{error,enoent}}}
>> >>
>> >> Log files (may contain more information):
>> >>  undefined
>> >>  undefined
>> >>
>> >> Stack trace:
>> >>  [{rabbit_node_monitor,read_cluster_status,0,
>> >>
>> >> [{file,"src/rabbit_node_monitor.erl"},{line,139}]},
>> >>   {rabbit_mnesia,cluster_status,1,
>> >>                  [{file,"src/rabbit_mnesia.erl"},{line,391}]},
>> >>
>> >> {rabbit_mnesia,node_type,0,[{file,"src/rabbit_mnesia.erl"},{line,410}]},
>> >>   {rabbit_mnesia,init,0,[{file,"src/rabbit_mnesia.erl"},{line,97}]},
>> >>   {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,
>> >>           [{file,"src/rabbit.erl"},{line,481}]},
>> >>   {rabbit,run_boot_step,1,[{file,"src/rabbit.erl"},{line,480}]},
>> >>
>> >> {rabbit,'-start/2-lc$^0/1-0-',1,[{file,"src/rabbit.erl"},{line,440}]},
>> >>   {rabbit,start,2,[{file,"src/rabbit.erl"},{line,440}]}]
>> >> [...]
>> >>
>> >> But of course there are no clusters and there had never been (fresh
>> >> run).
>> >>
>> >> Has anybody managed to do this? There has to be a way to embed the
>> >> RabbitMQ server in your own applications.
>> >> _______________________________________________
>> >> 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
>>
>> _______________________________________________
>> 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
>


More information about the rabbitmq-discuss mailing list