help for Windows server 2008 R2 version

[Xinchun Qu]

In the RabbitMQ main website,  It say RabbitMQ can support windows server 2008,but when I run Windows server 2008 R2 standard version, I encountered some problems.

RabbitMQ will run on any Windows version that supported Erlang/OTP releases can run on, both desktop and server editions. This includes Windows 7 through 10, Server 2008 through 2016.

So My question is:  The latest version of RabbitMQ and Erlang can support Windows server 2008? or I need to download a low version?

Which version is best for windows server 2008 R2.

It's my hornor to expect your reply.

Thanks

[Luke Bakken]

Hello,

I have tested RabbitMQ using Windows Server 2008 R2 and it works just fine.

Help us to help you out by providing more information than just stating "I encountered some problems". Please provide the following information:

• What version of RabbitMQ and Erlang you are using
  
• How did you install RabbitMQ and Erlang? Did you install using the .exe installers? Did you use an administrative user to install both, which is required?
  
• Did you use any custom configuration for RabbitMQ? Please provide complete configuration files as well as any environment variables set
  
• What problems are you seeing? Please provide the complete output of commands that return errors, RabbitMQ log files, erl_crash.dump files, and so on
  

Thanks,

Luke

[Uwe hundertachtundachtzig]

I have testet RabbitMq rabbitmq-server-3.7.7 with Erlang esl-erlang_21.0~windows_amd64 on two 64bit Windows 2008 R2

Result: It is NOT working.

 Clients can not connect to the server even through the sever is running and not having any issues.

Password reset and ensured. No Firewall. Admin user installed twise. Still:

RabbitMQ.Client.Exceptions.BrokerUnreachableException: 'None of the specified endpoints were reachable'


The 2 machines can join into a cluster the client port is open also used by a erlang PID and no firewall is there.

The same configuration is working on 3 Windows 64bit 2012 servers

Attached crash log file

I will now try an older version on these two machines

[Michael Klishin]

The node fails to start a subprocess due to an "ENOENT". This is something system-specific.

We have basic package testing on Windows 2008 and they are

OK (barring some time sensitivity which is a problem with the test).

Please start new threads for new questions.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Uwe hundertachtundachtzig]

Ok sorry for just attanding that thread

so here i meanwhile changed back to erlang 19.1 and rabbitmq server 3.6.0 and clients can connect now.

Configuration did not work with rabbitmq.conf

         listeners.tcp.default = 5672
disk_free_limit.absolute = 2GB
log.file.level = info
default_vhost = /
default_user = <username>
default_pass = <password>
default_user_tags.administrator = true
default_permissions.configure = .*
default_permissions.read = .*
default_permissions.write = .*
loopback_users = none
proxy_protocol = true
auth_mechanisms.1 = PLAIN
auth_mechanisms.2 = AMQPLAIN
auth_backends.1 = internal

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[piyush sharma]

It seems to be a issue with tls protocol mismatch. Check which version of tls is enabled on server. 

--

[Michael Klishin]

You have left out a very important part: you have enabled Proxy Protocol support.

Are you sure you understand what enabling it entails? [1]

Do your clients connect over a compatible proxy?

3.6.x does not support that feature so you cannot enabling it even if you wanted to.

1. https://www.rabbitmq.com/networking.html#proxy-protocol

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Luke Bakken]

Hi Uwe,

Using the attached Vagrantfile, I have sucessfully tested Erlang 21 (https://www.erlang.org/downloads) with RabbitMQ 3.7.7 on Windows 2008 R2. I am able to run the entire Pika test suite against this VM, for instance.

I downloaded the .exe installers for Erlang and RabbitMQ 3.7.7, ran both as an admin user, and chose the default settings.

I also do not see the crash you are reporting, so there must be some issue in your environment.

Thanks,

Luke

[Uwe hundertachtundachtzig]

Ok
i will give it another try later with that config.
i have the C#  .Net with latest nuget package client running against the servers not using the proxy protocol. They could not connect to the 2008 server 'None of the specified endpoints were reachable'. the servers looked ok.

Still also getting on hte working 2012 servers a crash.log.
All servers are VM with several other software running 

[Michael Klishin]

Again, lots of ENOENT messages. A quick Google search (for "") reveals [1][2].

1. https://groups.google.com/d/msg/rabbitmq-users/Up9lF8kcdR4/L8xf9wsuCwAJ

2. https://grokbase.com/t/rabbitmq/rabbitmq-discuss/133k2gdk32/rabbitmq-crashes-just-after-start (a very old thread, from before at least 2014!)

--

You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.