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

[Breno Leitão]

I do not consider this as a bug, 'ping' is not able to work also.

➜  ~ hostnamectl                       
   Static hostname: 1610
         Icon name: computer-vm
           Chassis: vm
        Machine ID: da29c08f2e840385b1d700a257211f57
           Boot ID: f0dad3c50b2d42bb998955dee24cdef8
    Virtualization: kvm
  Operating System: Ubuntu 16.10
            Kernel: Linux 4.8.0-040800rc6-generic
      Architecture: ppc64-le
➜  ~ hostnamectl
➜  ~ ping 1610
connect: Invalid argument
➜  ~ cat /etc/hosts | grep 1610
127.0.1.1	1610

-- 
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:
  New

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