[rabbitmq-discuss] rabbitmq-server crashes

[David Schmidt]

On 05/03/2011 11:14 PM, Matthew Sackman wrote:
> On Thu, Apr 21, 2011 at 04:54:37PM +0200, David Schmidt wrote:
>> rabbitmq-server crashed, using rabbitmqctl quite understandably yields:
>>
>> rabbitmqctl list_queues name messages
>> Listing queues ...
>> Error: unable to connect to node rabbit at db19: nodedown
>> diagnostics:
>> - nodes and their ports on db19: [{rabbitmqctl26359,39062}]
>> - current node: rabbitmqctl26359 at db19
>> - current node home dir: /var/lib/rabbitmq
>> - current node cookie hash: MGjkgA5U5XxYMPKTviwAWw==
> 
> I was suggesting that you use rabbitmqctl before rabbit crashes in order
> to inspect whether you can identify any source of leaks (eg acks) that
> is causing the crash.
> 
> Also I would expect there will be some log entries suggesting what's
> going on.
> 
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


I am still having the same issues.

This time I started rabbitmq-server directly (not in daemon mode)

###############################

db19:~/tmp# rabbitmq-server
Activating RabbitMQ plugins ...
*WARNING* Undefined function gb_trees:map/2
*WARNING* Undefined function mnesia:read/2
*WARNING* Undefined function os:timestamp/0
*WARNING* Undefined function public_key:pkix_decode_cert/2
*WARNING* Undefined function random:seed/1
*WARNING* Undefined function ssl:ssl_accept/3
0 plugins activated:


+---+   +---+
|   |   |   |
|   |   |   |
|   |   |   |
|   +---+   +-------+
|                   |
| RabbitMQ  +---+   |
|           |   |   |
|   v2.4.0  +---+   |
|                   |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2011 VMware, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

node           : rabbit at db19
app descriptor :
/usr/lib/rabbitmq/lib/rabbitmq_server-2.4.0/sbin/../ebin/rabbit.app
home dir       : /var/lib/rabbitmq
config file(s) : (none)
cookie hash    : MGjkgA5U5XxYMPKTviwAWw==
log            : /var/log/rabbitmq/rabbit at db19.log
sasl log       : /var/log/rabbitmq/rabbit at db19-sasl.log
database dir   : /var/lib/rabbitmq/mnesia/rabbit at db19
erlang version : 5.6.3

starting file handle cache server
...done
starting worker pool
...done
starting database
...done
starting codec correctness check
...done
-- external infrastructure ready
starting statistics event manager
...done
starting logging server
...done
starting plugin registry
...done
starting auth mechanism amqplain
...done
starting auth mechanism cr-demo
...done
starting auth mechanism plain
...done
starting exchange type direct
...done
starting exchange type fanout
...done
starting exchange type headers
...done
starting exchange type topic
...done
-- kernel ready
starting node monitor
...done
starting cluster delegate
...done
starting guid generator
...done
starting alarm handler
...done
starting memory monitor
...done
-- core initialized
starting empty DB check
...done
starting exchange recovery
...done
starting queue supervisor and queue recovery
...done
-- message delivery logic ready
starting error log relay
...done
starting networking
...done
starting notify cluster nodes
...done
starting direct_client
...done

broker running
db19:~/tmp#

###############################


and my perl process that is using rabbitmq (with Net::RabbitMQ) failed with:

caught error: basic_get: Connection reset by peer
caught error: basic_get: (end-of-stream)


###############################


rabbitmq logfiles dont yield any information why the process stopped/crashed







the last 2 calls to rabbitmqctl

db19:~/tmp# rabbitmqctl list_queues name messages
Listing queues ...
q_raw_pages     12
q_result_pages  0
q_new_pages     37528
...done.

db19:~/tmp# rabbitmqctl list_queues name messages
Listing queues ...
Error: unable to connect to node rabbit at db19: nodedown
diagnostics:
- nodes and their ports on db19: [{rabbitmqctl23183,44081}]
- current node: rabbitmqctl23183 at db19
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: MGjkgA5U5XxYMPKTviwAWw==




I am not using acks, as far as I understand messages are automatically
acknowledged the way I use it. messages_unacknowledged always returns 0
for all queues.


thanks for any help

david