[SOLVED] Zimbra/postfix bound to dynamic (heartbeat) IP

[ekkas]

I have Zimbra 2 servers setup for HA using DRBD and heartbeat.
Both servers have private staic IPs (10.10.69.34 & 10.10.69.35)
Heartbeat assigns 10.10.69.33 to which ever server is active primary at that moment.
We have NAT setup to destination-NAT our public IP to 10.10.69.33 and source-NAT 10.10.69.33 out to our public IP.

The problem is that Zimbra (postfix?) is always talking out with the server's static IP (10.10.69.34) and not the assigned dynamic (heartbeat) IP.
Is there a way that I can force Zimbra (postfix) to always 'speak out' with the dynamically assigned IP?
Listening bound IP does not matter as incoming traffic (like port 80, 7071, etc) is going to the dynamic IP and working fine. Just to get outgoing IP to be correct is my problem.

Thanks
Ekkas

[uxbod]

You could try the following but please note that it has not been tested

su - zimbra
zmlocalconfig -e postfix_inet_interfaces=10.10.69.33

You will then need to update /opt/zimbra/conf/zmmta.cf and add a new line

POSTCONF inet_interfaces                        LOCAL postfix_inet_interfaces

Then restart Postfix using

su - zimbra
zmmtactl stop ; zmmtactl start

The smtp daemon should now be listening on the floating IP.

[ekkas]

Thanks a lot.

[uxbod]

Did that work for you ? If it did then you need to make a note as the changes will not be persistent across upgrades.

[ekkas]

We were in a bit of a tight spot and needed to fix it a.s.a.p, so we made a workaround on our breakout router with NAT to tranaslate the wrong IP to the correct one, so I did'nt try this method, but might need it in future again if I do not have control over the router.

[vavai]

Also, for a quick reference, I do always install Zimbra HA with the HA IP (in your case : 10.10.69.33) on initial setup and then-after setup finished successfully- replace the IP with it's original host IP.

I will have minimum 4 entries on /etc/hosts :

localhost
original host1 IP
original host2 IP
Zimbra IP, provided by HeartBeat

[ekkas]

Thank you for your response.
Yes, that is how I installed it, but it seems after installation and changing the IP to the static IP (on eth0) Zimbra use that to connect out and not the HA IP assigned to eth0:0
Unless, in my efforts to get my first HA working(!), I changed something to invoke that behaviour.
Ekkas

[vavai]

Originally Posted by ekkas

Thank you for your response.
Yes, that is how I installed it, but it seems after installation and changing the IP to the static IP (on eth0) Zimbra use that to connect out and not the HA IP assigned to eth0:0
Unless, in my efforts to get my first HA working(!), I changed something to invoke that behaviour.
Ekkas

I think it would bind to physical IP because Zimbra service was running on boot. It should not, because Zimbra service should be manage by Heartbeat.

if you don't mind, can you share you haresources file ?

Below is mine on testing server :

zcspdc1:~ # cat /etc/ha.d/haresources
zcspdc1 IPaddr::192.168.1.249/24/eth0 drbddisk::r0 Filesystem::/dev/drbd0::/opt::ext3 named zimbra smb

On the above ha resources, I manage DNS Server, Zimbra Server and Samba file server with Heartbeat. All the service are disable on boot, Heartbeat will take care all the service after DRBD running successfully.

[ekkas]

server1.mydomain.co.za 10.10.69.33 drbddisk::r0 Filesystem::/dev/drbd0:pt::ext3 zimbra

Zimbra is disabled on reboot as /opt is not mounted yet by then. But is is not a problem as I just added all 3 IPs to be source-natted to the router's public IP instead of just the HA IP.
Ekkas

[tyuhas]

Just wanted to post that I did try the commands in post #2 and it did work as far as binding smtp to the dynamic IP. Where it ran into an issue is that postfix was no longer (at least in my case) listening on 127.0.0.1 which then caused Zimbra to not be able to completely process messages. Appears that all messages then sat in the deferred queue.

I changed the inet_interfaces to "all" and that brought me back to the original issue but at least a functioning Zimbra.

Thought I'd post in case someone finds this thread and tries it out.