[Baruwa] mail release never completing in web interface
J.Ede at birchenallhowden.co.uk
Wed Aug 24 10:09:24 SAST 2011
> -----Original Message-----
> From: baruwa-bounces at lists.baruwa.org [mailto:baruwa-
> bounces at lists.baruwa.org] On Behalf Of Andrew Colin Kissa
> Sent: 23 August 2011 16:14
> To: Baruwa users list
> Subject: Re: [Baruwa] mail release never completing in web interface
> On 21 Aug 2011, at 9:36 AM, Jason Ede wrote:
> > That would make sense... The name of each box is different from that used
> for the web interface. All of the web IP's with the hostname used on them
> are in the hosts file and the broker is on the same box as the web interface
> that is used. The broker isn't clustered yet as the rabbitmq documentation
> on clustering (http://www.rabbitmq.com/clustering.html) doesn't seem to
> work for me and I've not had time to look at it properly yet.
> > If I run 'select distinct hostname from messages;' then I get the base
> hostnames of the servers... If I then ping the name that I use for the
> interface then I get same IP as for the basename... a nslookup fails though
> as it's only a hosts entry... I'll try adding a proper dns zone in and see if it
> makes any difference.
> > Surely if it was a name resolution issue then the actual release/learn
> operation wouldn't be performed?
> I spend some time looking at this, you should be able to fix it by setting
> transaction-isolation = READ-COMMITTED
> in your /etc/my.cnf file.
> Let me know it that works for you.
It seem that it really doesn't like that when you're in a master /slave configuration... :(
(1598, "Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'")
> - Andrew
> Baruwa - www.baruwa.org
> Baruwa mailing list
> Baruwa at lists.baruwa.org
> Keep Baruwa FREE - http://pledgie.com/campaigns/12056
More information about the Baruwa