Results 1 to 6 of 6

Thread: Moved Zimbra VM now cannot send/receive

  1. #1
    Join Date
    May 2009
    Posts
    21
    Rep Power
    6

    Default Moved Zimbra VM now cannot send/receive

    We have been testing Zimbra Network Edition in a VMWare Server 2.0 environment and it has been working fine (send, receive, archiving, etc.) As a test we stopped the VM, copied all of the files to a new server and ran the VM on the new host. We brought down the old server and configured the host and guest with the same IP addresses and brought it all up.

    There was an issue where Ubuntu Server 8.04 (the guest OS) was not seeing eth0 on the copied guest, but that seems a common problem and while it doesn't see eth0, it does see eth1 so I configured that with the correct IP address.

    Zimbra started up fine from zimbra user (zmcontrol start).

    I could log in as admin and a user via another computer on the Internet and everything is reported as working in the admin panel. All of the users and data seems to be present as it was before.

    I attempted to send an email from the new Zimbra VM and it appeared to send but it was never received by the external email address. I tried sending mail into the new Zimbra server from the external address and it never appeared either. I then telnetted to port 25 from a computer on the Internet successfully and attempted to send an email... all of the commands went through fine and it said the message was queued but it also did not get sent.

    I am stumped as to what could be the disconnect here, and any help would be great!

    Thanks!

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    Sounds like a DNS issue to me so please post the following
    Code:
    cat /etc/hosts
    cat /etc/resolv.conf
    dig yourdomain mx
    dig yourdomain any
    host `hostname` <- note backticks and not single quotes

  3. #3
    Join Date
    May 2009
    Posts
    21
    Rep Power
    6

    Default

    It appears that the issue is with VMWare and the fact that Linux (Ubuntu) binds the eth# to a MAC address. When the VM was moved, a new fake MAC was created and since it didn't jive with the original one it sees not eth0 and now sees only eth1. I am working to fix this but if anyone has any experience here or knows of an easy solution, do tell.

  4. #4
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    does mail stay in queue ?
    what does /var/log/zimbra.log says when you send mails ?

  5. #5
    Join Date
    Jul 2007
    Location
    Baltimore
    Posts
    1,649
    Rep Power
    11

    Default

    you probably have to remove the old mapping from /etc/udev/rules.d/

  6. #6
    Join Date
    Mar 2006
    Location
    Beaucaire, France
    Posts
    2,322
    Rep Power
    13

    Default

    Quote Originally Posted by killc View Post
    It appears that the issue is with VMWare and the fact that Linux (Ubuntu) binds the eth# to a MAC address. When the VM was moved, a new fake MAC was created and since it didn't jive with the original one it sees not eth0 and now sees only eth1. I am working to fix this but if anyone has any experience here or knows of an easy solution, do tell.
    Remove (or fix) the "hwaddress" line in /etc/network/interfaces.

Similar Threads

  1. Replies: 8
    Last Post: 01-12-2012, 02:20 AM
  2. Replies: 8
    Last Post: 01-20-2009, 01:06 PM
  3. admin consol blank after 5.0.3 upgarde
    By maumar in forum Administrators
    Replies: 6
    Last Post: 03-21-2008, 06:16 AM
  4. Replies: 12
    Last Post: 02-25-2008, 07:28 PM
  5. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 09:55 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •