[rabbitmq-discuss] centos linux install failed to create rabbitmq-env.conf or rabbitmq.config

Jerry Kuch jkuch at gopivotal.com
Mon Oct 21 21:54:51 BST 2013

Hi, Ken:

So this thread's been going a while, and taken a bunch of twists and turns.

Some remarks inline to try to establish context on where we are and how we
might solve your problems...

On Wed, Oct 16, 2013 at 12:36 PM, ken macpherson <kmacpher67 at gmail.com>wrote:

> nope didn't work...
> # nohup rabbitmq-server &
> &
> # rabbitmqctl status
> Status of node rabbit at qaapp ...
> [{pid,30347},
>  {running_applications,
>      [{rabbitmq_tracing,"RabbitMQ message logging / tracing","3.1.5"},
>       {rabbitmq_management_visualiser,"RabbitMQ Visualiser","3.1.5"},
>       {rabbitmq_management,"RabbitMQ Management Console","3.1.5"},
>       {rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.1.5"},
>       {webmachine,"webmachine","1.10.3-rmq3.1.5-gite9359c7"},
>       {mochiweb,"MochiMedia Web Server","2.7.0-rmq3.1.5-git680dba8"},
>       {rabbitmq_management_agent,"RabbitMQ Management Agent","3.1.5"},
>       {rabbit,"RabbitMQ","3.1.5"},
>       {os_mon,"CPO  CXC 138 46","2.2.13"},
>       {inets,"INETS  CXC 138 49","5.9.6"},
>       {mnesia,"MNESIA  CXC 138 12","4.10"},
>       {amqp_client,"RabbitMQ AMQP Client","3.1.5"},
>       {xmerl,"XML parser","1.3.4"},
>       {sasl,"SASL  CXC 138 11","2.3.3"},
>       {stdlib,"ERTS  CXC 138 10","1.19.3"},
>       {kernel,"ERTS  CXC 138 10","2.16.3"}]},
>  {os,{unix,linux}},
>  {erlang_version,
>      "Erlang R16B02 (erts-5.10.3) [source] [64-bit] [smp:4:4]
> [async-threads:30] [hipe] [kernel-poll:true]\n"},
>  {memory,
>      [{total,41243224},
>       {connection_procs,5600},
>       {queue_procs,5600},
>       {plugins,382736},
>       {other_proc,13561960},
>       {mnesia,60272},
>       {mgmt_db,47344},
>       {msg_index,28496},
>       {other_ets,1108360},
>       {binary,34144},
>       {code,19598331},
>       {atom,703377},
>       {other_system,5707004}]},
>  {vm_memory_high_watermark,0.4},
>  {vm_memory_limit,1658167296},
>  {disk_free_limit,1000000000},
>  {disk_free,6997409792},
>  {file_descriptors,
>      [{total_limit,10140},
>       {total_used,3},
>       {sockets_limit,9124},
>       {sockets_used,1}]},
>  {processes,[{limit,1048576},{used,199}]},
>  {run_queue,0},
>  {uptime,192}]
> ...done.
> BUT ... the services are bumbkiss.

> #/sbin/service rabbitmq-server status
> pthread/ethr_event.c:98: Fatal error in wait__(): Function not implemented
> (38)
> It's running the server now, so there's 8 hours I'll never get back.

I can't quite understand what state you're in or how you got there.

Did you:

   1. On a relatively clean CentOS machine...
   2. ...set up the EPEL repositories as documented here:
   3. ...install a sufficiently modern Erlang from the EPEL repository set
   up in 2
   4. ...install the rabbitmq-server RPM as documented at the URL above
   5. Start the service with:  /sbin/service rabbitmq-server start
   6. Verify that it's alive by things like:
      1. Trying to telnet to port 5672 where Rabbit should be listening for
      AMQP connection attempts (bang on some keys and see if you get kicked out
      with an AMQP error message)
      2. Use ps to find processes whose name contains 'beam' (the name of
      the Erlang VM) and whose command line arguments show they're
running Rabbit
      3. 'sudo rabbitmqctl status' and see what you get back.

The chain of things in your mail thread suggests one or more of these
things have gone wrong, as well as some possible red herrings, like
worrying about the epmd process... this is the Erlang port mapper daemon,
which Erlang applications use to find one another for IPC, and will be
running if Erlang has previous started up on the machine.

The "function not implemented" error you're seeing is something that you'll
sometimes see on CentOS installs running Erlang on older Linux kernels that
version are you working with?

I'm also wondering a bit whether there might be more than one Erlang
install on this machine.

Can you back out and try again, following the instructions at the above URL
carefully, and reporting what you see as you go?

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131021/d382fb30/attachment.htm>

More information about the rabbitmq-discuss mailing list