it's strange because  rabbitmq-server is running correctly

i show you the log
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@spamassassin
app descriptor : 
/usr/lib/rabbitmq/lib/rabbitmq_server-2.5.0/sbin/../ebin/rabbit.app
home dir       : /var/lib/rabbitmq
config file(s) : (none)
cookie hash    : 1FBTpCwGatm1dMc+fdWcpg==
log            : /var/log/rabbitmq/[email protected]
sasl log       : /var/log/rabbitmq/[email protected]
database dir   : /var/lib/rabbitmq/mnesia/rabbit@spamassassin
erlang version : 5.8.3

-- rabbit boot start
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, queue and binding 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
Mon Dec  5 14:15:58 CET 2011 - rabbitmq successfully started



and

=INFO REPORT==== 5-Dec-2011::14:15:57 ===
Limiting to approx 924 file handles (829 sockets)

=INFO REPORT==== 5-Dec-2011::14:15:57 ===
Memory limit set to 198MB.

=INFO REPORT==== 5-Dec-2011::14:15:57 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 5-Dec-2011::14:15:57 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 5-Dec-2011::14:15:57 ===
started TCP Listener on [::]:5672

=INFO REPORT==== 5-Dec-2011::14:16:03 ===
accepted TCP connection on [::]:5672 from 127.0.0.1:33227

=INFO REPORT==== 5-Dec-2011::14:16:03 ===
starting TCP connection <0.213.0> from 127.0.0.1:33227


in /etc/baruwa/settings.py the settings are correctly with 
broker_vhost,broker_password,broker_user,etc...




Da:     Andrew Colin Kissa <[email protected]>
Per:    Baruwa users list <[email protected]>
Data:   05/12/2011 14:23
Oggetto:        Re: [Baruwa] Rif: Re:  zombie process+no records returned




On 05 Dec 2011, at 3:19 PM, [email protected] wrote:

> seconds... 
> [2011-12-05 12:30:21,177: ERROR/MainProcess] Consumer: Connection Error: 
[Errno 111] Connection refused. Trying again in 6 seconds...

As you can see from that error, either rabbitmq is not running or the user 
details you have configured are incorrect,

as for the messages showing up are you sure the is mail flowing ?

--
Baruwa - www.baruwa.org

_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056

_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056

Reply via email to