[rabbitmq-discuss] getting started, broker runs; can't get status
dave farkas
dave at interactivemediums.com
Sat Jan 31 02:31:07 GMT 2009
I'm seeing a similar problem on RHE 5 (64 bit). I've installed verision
1.5.1-1 from the fedora linux (64-bit) rpm. When I start the server, I
get the following:
[root at db1 init.d]# ./rabbitmq-server start
Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_log, _err
rabbitmq-server.
This script hangs for a long time eventually giving the failed message.
The process are still running and i can connect with an amqp client.
[root at db1 init.d]# ./rabbitmq-server status
Status of all running nodes...
Error: no_nodes_running
Here are the logs:
root at db1 rabbitmq]# more startup_log
Starting all nodes...
Starting node rabbit at db1...
RabbitMQ 1.5.1 (AMQP 8-0)
Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies
LLC., and Rabbit Technologies Ltd.
Licensed under the MPL. See http://www.rabbitmq.com/
Logging to "/var/log/rabbitmq/rabbit.log"
SASL logging to "/var/log/rabbitmq/rabbit-sasl.log"
starting database ...done
starting core processes ...done
starting recovery ...done
starting persister ...done
starting builtin applications ...done
starting TCP listeners ...done
broker running
[root at db1 rabbitmq]# more startup_err
Error: cannot_get_pid
The rabbit.log is (this is after i connect with an amqp client):
[root at db1 rabbitmq]# more rabbit.log
=INFO REPORT==== 30-Jan-2009::20:20:54 ===
disk_log: repairing
"/var/lib/rabbitmq/mnesia/rabbit/rabbit_persister.LOG" ...
=INFO REPORT==== 30-Jan-2009::20:20:54 ===
Repaired persister log - 1 recovered, 0 bad
=INFO REPORT==== 30-Jan-2009::20:20:54 ===
Rolling persister log to
"/var/lib/rabbitmq/mnesia/rabbit/rabbit_persister.LOG.previous"
=INFO REPORT==== 30-Jan-2009::20:20:54 ===
started TCP listener on 0.0.0.0:5672
=INFO REPORT==== 30-Jan-2009::20:21:47 ===
accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:49811
=INFO REPORT==== 30-Jan-2009::20:21:47 ===
starting TCP connection <0.202.0> from 127.0.0.1:49811
=ERROR REPORT==== 30-Jan-2009::20:21:47 ===
error on TCP connection <0.202.0> from 127.0.0.1:49811
connection_closed_abruptly
=INFO REPORT==== 30-Jan-2009::20:21:47 ===
closing TCP connection <0.202.0> from 127.0.0.1:49811
and here's info on how the processes are running:
[root at db1 bin]# ps -ef | grep rabbitmq
root 18666 18642 0 20:20 pts/2 00:00:00 /bin/sh
./rabbitmq-server start
root 18667 18666 0 20:20 pts/2 00:00:00 su rabbitmq -s /bin/sh
-c /usr/lib64/rabbitmq/bin/rabbitmq-multi start_all 1
rabbitmq 18668 18667 3 20:20 ? 00:00:00
/usr/lib64/erlang/erts-5.6.3/bin/beam.smp -- -root /usr/lib64/erlang
-progname erl -- -home /var/lib/rabbitmq -pa
/usr/lib64/rabbitmq/bin/../ebin -noshell -noinput -hidden -sname
rabbitmq_multi18668 -s rabbit_multi -extra start_all 1
rabbitmq 18676 1 0 20:20 ? 00:00:00
/usr/lib64/erlang/erts-5.6.3/bin/epmd -daemon
rabbitmq 18692 18668 0 20:20 ? 00:00:00 inet_gethost 4
rabbitmq 18693 18692 0 20:20 ? 00:00:00 inet_gethost 4
rabbitmq 18694 18668 40 20:20 ? 00:00:01
/usr/lib64/erlang/erts-5.6.3/bin/beam.smp -W w -K true -A30 -- -root
/usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -pa
/usr/lib64/rabbitmq/bin/../ebin -noshell -noinput -s rabbit -sname
rabbit -boot start_sasl -kernel inet_default_listen_options
[{nodelay,true},{sndbuf,16384},{recbuf,4096}] -kernel
inet_default_connect_options [{nodelay,true}] -rabbit tcp_listeners
[{"0.0.0.0", 5672}] -sasl errlog_type error -kernel error_logger
{file,"/var/log/rabbitmq/rabbit.log"} -sasl sasl_error_logger
{file,"/var/log/rabbitmq/rabbit-sasl.log"} -os_mon start_cpu_sup true
-os_mon start_disksup false -os_mon start_memsup false -os_mon
start_os_sup false -os_mon memsup_system_only true -os_mon
system_memory_high_watermark 0.95 -mnesia dir
"/var/lib/rabbitmq/mnesia/rabbit" -noshell -noinput
rabbitmq 18749 18694 0 20:20 ? 00:00:00
/usr/lib64/erlang/lib/os_mon-2.1.6/priv/bin/cpu_sup
rabbitmq 18750 18694 0 20:20 ? 00:00:00 inet_gethost 4
rabbitmq 18751 18750 0 20:20 ? 00:00:00 inet_gethost 4
Please let me know if there is any other information that would be helpful.
Thanks,
Dave
Matthias Radestock wrote:
> Michael,
>
> Michael Steinfeld wrote:
>
>> Well, for the life of me I could not get it to work on RHEL4 x86_64.
>> Oddly enough the broker would run.
>>
>> I tried source and binary.
>>
>
> Can you send us a transcript of the installation and your subsequent
> attempts to access the broker?
>
>
> Matthias.
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
More information about the rabbitmq-discuss
mailing list