[Bug 1529033] Re: Install/start fails when hostname is numeric

[Robie Basak]

I take that to mean that a system needs to cope with _other_ hosts
having numeric hostnames when communicating with them over the Internet.
It doesn't mandate that a given host must be able to be configured by
its user to have a numeric Unix hostname. It's perfectly reasonable for
a system architecture to have additional restrictions on its own
hostname over what the Internet permits.

You have, at best, a wishlist item that Ubuntu (or other POSIX-like or
Unix-like distributions if you wish) support all-numeric hostnames.
Although you might want this for rabbitmq-server, it is really a general
wishlist item, not one that is specific to rabbitmq-server.

I don't believe that this is something that will ever be supported by
any Linux distribution because it goes quite deep into how underlying
APIs operate - for example to tell the difference between a host
specified by IP and a host specified by name.

If you want to take this further, re-opening the bug won't help. This is
an architecture level wishlist item that would impact many packages. The
appropriate bug status is somewhere between Invalid and Won't Fix
because it isn't something that I believe the Ubuntu project (or even
the wider ecosystem) considers to be a problem that is worth addressing.

** Changed in: rabbitmq-server (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1529033

Title:
  Install/start fails when hostname is numeric

Status in rabbitmq-server package in Ubuntu:
  Invalid

Bug description:
  If a machine has a hostname made up entirely of numbers, install and
  start will fail reporting:

  ERROR: epmd error for host "1234": badarg (unknown POSIX error)

  This can be duplicated:

  hostame 1234
  echo 127.0.0.1 localhost 1234 > /etc/hosts
  apt-get install rabbitmq-server

  results in:

  Setting up rabbitmq-server (3.2.4-1) ...
   * Starting message broker rabbitmq-server                                                                          * FAILED - check /var/log/rabbitmq/startup_\{log, _err\}
                                                                                                              [fail]
  invoke-rc.d: initscript rabbitmq-server, action "start" failed.
  dpkg: error processing package rabbitmq-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for ureadahead (0.100.0-16) ...
  Errors were encountered while processing:
   rabbitmq-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  But try:

  hostname testing
  echo 127.0.0.1 testing > /etc/hosts
  apt-get install rabbitmq-server

  and it works.

  I'm not sure if this is a rabbitmq-server "bug" or an epmd (I always
  chuckle when I write that...) bug, but it cropped up when installing
  rabbitmq-server to play with OpenStack so I figured I'd submit it
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1529033/+subscriptions