[rabbitmq-discuss] heart_beat_kill_pid & no error logger present

Mon Oct 1 05:08:32 BST 2007

Joe,

joe lee wrote:
> Do I need to worry about heart_beat_kill_pid error?  What does it mean 
> no error logger present, where do you get error logger?  I am running 
> Erlang r11b-5 on Fedora 7.
> 
> [root at homie RabbitMQ]# rpm -i --nodeps rabbitmq-server-1.2.0-1.noarch.rpm
> warning: rabbitmq-server-1.2.0-1.noarch.rpm: Header V3 DSA signature: 
> NOKEY, key ID 056e8e56
> Starting rabbitmq-server: rabbitmq-server.
> heart_beat_kill_pid = 9108
> [root at homie RabbitMQ]# heart: Sun Sep 30 18:59:37 2007: Erlang has closed.
> heart: Sun Sep 30 18:59:37 2007: Would reboot. Terminating.
> init terminating in do_boot ()

That tells you that RabbitMQ died and that the system would have 
rebooted if the heartbeat process had been instruct to do so (which it 
hasn't).

The root cause is probably the following ...

> [root at homie joe]# /etc/init.d/rabbitmq-server start
> Starting rabbitmq-server: rabbitmq-server.
> [root at homie joe]# (no error logger present) error: "Error in process 
> <0.1.0> with exit value: 
> {badarg,[{erl_prim_loader,check_file_result,3},{init,get_boot,1},{init,get_boot,2},{init,do_boot,3}]} 
> 
> "
> init terminating in do_boot ()

Looks like rabbit fails to start up.

I don't think you need to worry about the "no error logger present" 
message - it's probably there because rabbit died before initialising 
error logging.

Things to try:

- is there anything of interest in the log files in /var/log/rabbitmq?

- what happens when you start the server with /usr/sbin/rabbitmq-server? 
  Does it work? Any errors on the console?

Matthias