Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 31

Thread: Installation fails during install of Zimbra-mta RPM

  1. #11
    Join Date
    Nov 2007
    Posts
    19
    Rep Power
    7

    Default

    About the editing. Noticed something I entered incorrectly. Brain no worky. Corrected it. Here's the output from the dig commands.

    Code:
    [root@TB003 zimbra]# dig mydomain.local mx
    
    ; <<>> DiG 9.2.4 <<>> mydomain.local mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25161
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mydomain.local.                        IN      MX
    
    ;; AUTHORITY SECTION:
    .                       900     IN      SOA     A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2007111400 1800 900 604800 86400
    
    ;; Query time: 46 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Wed Nov 14 15:00:13 2007
    ;; MSG SIZE  rcvd: 107
    Code:
    [root@TB003 zimbra]# dig mydomain.local any
    
    ; <<>> DiG 9.2.4 <<>> mydomain.local any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9393
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mydomain.local.                        IN      ANY
    
    ;; AUTHORITY SECTION:
    .                       873     IN      SOA     A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2007111400 1800 900 604800 86400
    
    ;; Query time: 4 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Wed Nov 14 15:00:40 2007
    ;; MSG SIZE  rcvd: 107
    If there's something in the output that signifies an error, please point it out. "ANSWER: 0" bad?

    Thanks a bunch...

  2. #12
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    That still shows nothing for your A & MX records. What's in your /etc/resolv.conf file?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #13
    Join Date
    Nov 2007
    Posts
    19
    Rep Power
    7

    Default

    nameserver 127.0.0.1

    Thanks for the help...

  4. #14
    Join Date
    Nov 2007
    Posts
    19
    Rep Power
    7

    Default

    Well, it took me doing a dig against our live email domain to see something like I should be seeing. Duh.

  5. #15
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    I'm not sure BIND actually listens to 127.0.0.1 in RHEL (or any other distro), you can see from the output in the dig command that it's using an external server for the response. Anyway, change your resolv.conf to the following:

    Code:
    search mydomain.local
    nameserver 192.168.100.241
    Restart bind and see with the dig commands if you get the correct response. If that works then try the install again.

    BTW, you may need to restart your network for it to pick-up the nameserver change - ifdown ethx & ifup ethx.
    Last edited by phoenix; 11-14-2007 at 01:30 PM.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  6. #16
    Join Date
    Nov 2007
    Posts
    19
    Rep Power
    7

    Default

    Hmm. Changed resolv.conf, rebooted. No dice.

    Here's the dig output. Not much different, other than the IP of the server at bottom. Install still also fails.

    Code:
    [root@TB003 zcs]# dig mydomain.local mx
    
    ; <<>> DiG 9.2.4 <<>> mydomain.local mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28246
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mydomain.local.                        IN      MX
    
    ;; AUTHORITY SECTION:
    .                       545     IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2007111400 1800 900 604800 86400
    
    ;; Query time: 4 msec
    ;; SERVER: 192.168.100.241#53(192.168.100.241)
    ;; WHEN: Wed Nov 14 15:27:36 2007
    ;; MSG SIZE  rcvd: 107
    Code:
    [root@TB003 zcs]# dig mydomain.local any
    
    ; <<>> DiG 9.2.4 <<>> mydomain.local any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32281
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mydomain.local.                        IN      ANY
    
    ;; AUTHORITY SECTION:
    .                       410     IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2007111400 1800 900 604800 86400
    
    ;; Query time: 4 msec
    ;; SERVER: 192.168.100.241#53(192.168.100.241)
    ;; WHEN: Wed Nov 14 15:29:51 2007
    ;; MSG SIZE  rcvd: 107

  7. #17
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Perhaps I was making a rather hasty assumption about the IP of your BIND server. Is it on the same server as Zimbra and is the IP I told you to paste into resolve.conf the IP of your BIND server?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #18
    Join Date
    Mar 2006
    Location
    Massachusetts
    Posts
    965
    Rep Power
    10

    Default

    In your named.conf file, shouldn't the zone be "mydomain.local", instead of "TB003.mydomain.local"?

    Also, not to push off track of getting DNS working properly, because that obviously needs to be working to get Zimbra going, but just another observation. I'm not sure the installation would bomb out like this simply because of DNS not being setup properly. Seems to me like most people with mis-configured DNS run into issues after the install is done. This sounds more like perhaps the installation package is damaged, a disk space issue, or something like that. Maybe I'm wrong and Zimbra has changed things so that people don't get too far if DNS settings are wrong, or maybe this is a NE vs FOSS thing (I've only used FOSS).

  9. #19
    Join Date
    Nov 2007
    Posts
    19
    Rep Power
    7

    Default

    Quote Originally Posted by phoenix View Post
    Perhaps I was making a rather hasty assumption about the IP of your BIND server. Is it on the same server as Zimbra and is the IP I told you to paste into resolve.conf the IP of your BIND server?
    Yep. They are one in the same. Perhaps it would help to note that this is a test installation. The intention was to get zimbra functional in a fully contained system, in such a way that it could be tested independently of our existing POP3 installation.

    The Zimbra/Bind server's internal IP is 192.168.100.241.

  10. #20
    Join Date
    Nov 2007
    Posts
    19
    Rep Power
    7

    Default

    Quote Originally Posted by soxfan View Post
    In your named.conf file, shouldn't the zone be "mydomain.local", instead of "TB003.mydomain.local"?

    Also, not to push off track of getting DNS working properly, because that obviously needs to be working to get Zimbra going, but just another observation. I'm not sure the installation would bomb out like this simply because of DNS not being setup properly. Seems to me like most people with mis-configured DNS run into issues after the install is done. This sounds more like perhaps the installation package is damaged, a disk space issue, or something like that. Maybe I'm wrong and Zimbra has changed things so that people don't get too far if DNS settings are wrong, or maybe this is a NE vs FOSS thing (I've only used FOSS).
    Excellent Soxfan! Making that change in the named conf file produced the following output...

    Code:
    ; <<>> DiG 9.2.4 <<>> mydomain.local mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49089
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mydomain.local.                        IN      MX
    
    ;; ANSWER SECTION:
    mydomain.local.         2592000 IN      MX      10 TB003.mydomain.local.
    
    ;; AUTHORITY SECTION:
    mydomain.local.         2592000 IN      NS      192.168.100.241.mydomain.local.
    
    ;; Query time: 6 msec
    ;; SERVER: 192.168.100.241#53(192.168.100.241)
    ;; WHEN: Thu Nov 15 09:49:41 2007
    ;; MSG SIZE  rcvd: 84
    Code:
    ; <<>> DiG 9.2.4 <<>> mydomain.local any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41620
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mydomain.local.                        IN      ANY
    
    ;; ANSWER SECTION:
    mydomain.local.         2592000 IN      SOA     TB003.mydomain.local. hostmaster.TB003.mydomain.local. 10118 43200 3600 3600000 2592000
    mydomain.local.         2592000 IN      NS      192.168.100.241.mydomain.local.
    mydomain.local.         2592000 IN      A       192.168.100.241
    mydomain.local.         2592000 IN      MX      10 TB003.mydomain.local.
    
    ;; Query time: 7 msec
    ;; SERVER: 192.168.100.241#53(192.168.100.241)
    ;; WHEN: Thu Nov 15 09:51:47 2007
    ;; MSG SIZE  rcvd: 147
    Now for the downer. The install still fails at the same point.

Similar Threads

  1. Replies: 2
    Last Post: 10-04-2007, 03:20 PM
  2. [SOLVED] Error Installing Zimbra on RHEL 5
    By harris7139 in forum Installation
    Replies: 10
    Last Post: 09-25-2007, 11:39 AM
  3. upgrade woes -made into new thread
    By JustinHarlow in forum Installation
    Replies: 18
    Last Post: 06-08-2007, 12:11 PM
  4. 4.5 Upgrade failure
    By brained in forum Installation
    Replies: 9
    Last Post: 03-03-2007, 02:30 PM
  5. port 7071 not listening OS X install
    By leeimber in forum Installation
    Replies: 7
    Last Post: 03-21-2006, 09:47 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
  •