[rabbitmq-discuss] Erro when Install in Windows Server 2003 - Entry point inet_pton not found in WS2_32.dll
Thiago Burgo Belo
thiagoburgo at gmail.com
Wed Jun 13 14:04:48 BST 2012
With Erlang 32 bits version, RabbitMQ worked properly. We will wait for
Erlang correction to test with x64 version.
2012/6/13 Thiago Burgo Belo <thiagoburgo at gmail.com>
> Thank you for feedback,
> About the problem with Erlang, you are right, the commands that you sent
> to me are sufficient to cause the problem, want you report the problem to
> Erlang Team? (you seem know more than me about the problem =) ).
> I will try use Erlang 32 bits version and before I will send the results
> (You think I will have problems using this version and about colateral
> effects, what do you think?)
> Thank you so much,
> Thiago Burgo
> 2012/6/13 Emile Joubert <emile at rabbitmq.com>
>> On 12/06/12 18:01, Thiago Burgo Belo wrote:
>> > My Windows is Windows Server 2003 R2 Enterprise x64 SP2, the problem
>> > happens when I install RabbitMQ version 2.8.2 (with Erlang
>> > otp_win64_R15B01). In attachment has a printscreen.
>> > The problem happens too when I try execute rabbitmqctl.bat -status (the
>> > dump in attachment)
>> From the information you provided it is likely that this is caused by
>> the Erlang distributed networking not working on windows 2003 64bit.
>> This platform is sufficiently rare that no-one else has reported this
>> problem for Erlang, but I see there was a similar report in Wireshark
>> caused by a library ordering problem:
>> If you can find the shortest set of steps that provokes the error then
>> that should be enough to give the Erlang developers a handle on the
>> problem. I would expect these commands to cause a failure - can you
>> confirm? Make sure the Erlang bin directory is in your PATH:
>> werl -sname testnode@%COMPUTERNAME%
>> werl -sname foo -remsh testnode@%COMPUTERNAME%
>> If you need a working RabbitMQ broker in the meantime then consider
>> installing the 32bit version of Erlang. I not expect it to suffer from
>> the same problem.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss