Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-12-2006, 10:25 PM
Active Member
 
Posts: 25
Default Network problems

Looked at many topics about this. Tried a few.

Now in a situation where only ldap starts (guess I should have taken a backup like recommended. Slap me).

Everything was working like it should until this attempt to fix/change hostnames.

History: I have an internal LAN (192.168.x.x), I have an external WAN connection. Installation occurred on the internal LAN (all references to the
192.168.x.x address).

Why I wanted to change things: Couldn't see certain admin pages when doing internet requests (pages were being referenced to my internal LAN address).

Reconfiguration attempts: 1) tried the postconf example. No success system still okay 2) tried the libexec/zmsetup.pl example. No success, system screwed 3) Tried the zmsetservername example. No success, system still screwed

This was an install from the rpm supplied on your site for FC4. There have
never been any mods to the config before this stupid attempt to fix things.
Reply With Quote
  #2 (permalink)  
Old 04-13-2006, 09:38 AM
Zimbra Employee
 
Posts: 4,792
Default

Well your not giving us much to go on. What happensnow for starting the other server? What do the logs say?
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #3 (permalink)  
Old 04-14-2006, 12:06 PM
Active Member
 
Posts: 25
Default

I managed to get the system back up and running but now it won't receive mail.

I have tmocon.com defined as a domain in zimbra.
I have an internal (office.tmocon.com) and
external dns (tmocon.com)

dig returns this:

[root@enterprise zimbra]# dig tmocon.com MX

; <<>> DiG 9.3.1 <<>> tmocon.com MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59990
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;tmocon.com. IN MX

;; ANSWER SECTION:
tmocon.com. 86400 IN MX 10 vortex.tmocon.com.

;; AUTHORITY SECTION:
tmocon.com. 86400 IN NS dns3.cawsey.com.
tmocon.com. 86400 IN NS dns2.tmocon.com.

;; ADDITIONAL SECTION:
vortex.tmocon.com. 86400 IN A 142.179.183.240

;; Query time: 3 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Fri Apr 14 10:54:06 2006
;; MSG SIZE rcvd: 112

vortex.tmocon.com and enterprise.office.tmocon.com are different interfaces on my zimbra box. vortex has a public static IP address, enterprise has a private static IP address (192.168.2.2)

Similarly tmocon.com is also known as valiant.tmocon.com. This is the box that runs my dns. tmocon.com has two interfaces, one has a public static IP Address and defiant has a private static IP Address (192.168.2.1)

Currently, there is no firewall.

When I send a test message from tobuck@cawsey.com to to1@tmocon.com
this is what is dumped in the log

Apr 14 10:57:22 enterprise postfix/smtpd[3668]: initializing the server-side TLS engine
Apr 14 10:57:22 enterprise postfix/smtpd[3668]: connect from static24-72-53-29.regina.accesscomm.ca[24.72.53.29]
Apr 14 10:57:22 enterprise postfix/smtpd[3668]: 983DB111058E: client=static24-72-53-29.regina.accesscomm.ca[24.72.53.29]
Apr 14 10:57:22 enterprise postfix/cleanup[3672]: 983DB111058E: message-id=<200604141756.k3EHuxU09006@cawsey.com>
Apr 14 10:57:22 enterprise postfix/qmgr[32128]: 983DB111058E: from=, size=511, nrcpt=1 (queue active)
Apr 14 10:57:22 enterprise amavis[19525]: (19525-04) ESMTP::10024 /opt/zimbra/amavisd/tmp/amavis-20060414T103417-19525: -> Received: SIZE=511 from enterprise.office.tmocon.com ([127.0.0.1]) by localhost (enterprise.office.tmocon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19525-04 for ; Fri, 14 Apr 2006 10:57:22 -0600 (MDT)
Apr 14 10:57:22 enterprise postfix/smtpd[3668]: disconnect from static24-72-53-29.regina.accesscomm.ca[24.72.53.29]
Apr 14 10:57:22 enterprise amavis[19525]: (19525-04) Checking: q33kUDeFmJLX [24.72.53.29] ->
Apr 14 10:57:22 enterprise amavis[19525]: (19525-04) cached d8e8fca2dc0f896fd7cb4cb0031ba249 from (0,0)
Apr 14 10:57:23 enterprise postfix/smtpd[3676]: initializing the server-side TLS engine
Apr 14 10:57:23 enterprise postfix/smtpd[3676]: connect from localhost.localdomain[127.0.0.1]
Apr 14 10:57:23 enterprise postfix/smtpd[3676]: 40C721110598: client=localhost.localdomain[127.0.0.1]
Apr 14 10:57:23 enterprise postfix/cleanup[3672]: 40C721110598: message-id=<200604141756.k3EHuxU09006@cawsey.com>
Apr 14 10:57:23 enterprise postfix/qmgr[32128]: 40C721110598: from=, size=1160, nrcpt=1 (queue active)
Apr 14 10:57:23 enterprise postfix/smtpd[3676]: disconnect from localhost.localdomain[127.0.0.1]
Apr 14 10:57:23 enterprise amavis[19525]: (19525-04) FWD via SMTP: -> , 250 2.6.0 Ok, id=19525-04, from MTA([127.0.0.1]:10025): 250 Ok: queued as 40C721110598
Apr 14 10:57:23 enterprise amavis[19525]: (19525-04) Passed CLEAN, [24.72.53.29] [24.72.53.29] -> , Message-ID: <200604141756.k3EHuxU09006@cawsey.com>, mail_id: q33kUDeFmJLX, Hits: -1.762, 487 ms
Apr 14 10:57:23 enterprise postfix/smtp[3673]: 983DB111058E: to=, relay=127.0.0.1[127.0.0.1], delay=1, status=sent (250 2.6.0 Ok, id=19525-04, from MTA([127.0.0.1]:10025): 250 Ok: queued as 40C721110598)
Apr 14 10:57:23 enterprise amavis[19525]: (19525-04) extra modules loaded: Net/LDAP/Bind.pm
Apr 14 10:57:23 enterprise postfix/qmgr[32128]: 40C721110598: to=, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to tmocon.com[142.179.181.139]: Connection refused)
Apr 14 10:57:23 enterprise postfix/qmgr[32128]: 983DB111058E: removed

The temporarily suspended message is interesting. Is postfix trying to talk to port 25 on tmocon.com? If that is the case, why? The MX record for tmocon.com shows that vortex handles the mail...

Also, I was trying a number of different installation options out and noticed that when I login to the admin page I get two servers listed:
1) enterprise.office.tmocon.com
2) vortex.tmocon.com

How can I delete vortex.tmocon.com?

Any help would be greatly appreciated. I'm desparate in trying to get the system backup and running (I'm missing many and valuable emails).
Reply With Quote
  #4 (permalink)  
Old 04-14-2006, 12:53 PM
Zimbra Employee
 
Posts: 4,792
Default

Try to remove vortex.tmocon.com, might be looping since what you have as an Mx is local to postfix.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #5 (permalink)  
Old 04-14-2006, 01:26 PM
Active Member
 
Posts: 25
Default

Kevin,

How do I remove vortex.tmocon.com from zimbra?

Also, I'm supplying more info. See below:

hosts file on enterprise:

127.0.0.1 localhost.localdomain localhost
192.168.2.2 enterprise.office.tmocon.com enterprise
#142.179.183.240 vortex.tmocon.com vortex

resolv.conf on enterprise:

nameserver 192.168.2.1
search office.tmocon.com


/etc/sysconfig/network:

NETWORKING=yes
HOSTNAME=enterprise.office.tmocon.com


netstat -a|grep LISTEN (excluded stream sockets)


tcp 0 0 *:ldap *:* LISTEN
tcp 0 0 localhost.localdomain:10024 *:* LISTEN
tcp 0 0 *:41736 *:* LISTEN
tcp 0 0 localhost.localdomain:10025 *:* LISTEN
tcp 0 0 localhost.localdomain:7306 *:* LISTEN
tcp 0 0 localhost.localdomain:7307 *:* LISTEN
tcp 0 0 *:3310 *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:ipp *:* LISTEN
tcp 0 0 *:smtp *:* LISTEN
tcp 0 0 *:ldaps *:* LISTEN
tcp 0 0 *:imaps *:* LISTEN
tcp 0 0 *op3s *:* LISTEN
tcp 0 0 *:7780 *:* LISTEN
tcp 0 0 localhost.localdomain:8005 *:* LISTEN
tcp 0 0 *op3 *:* LISTEN
tcp 0 0 *:imap *:* LISTEN
tcp 0 0 *:http *:* LISTEN
tcp 0 0 *:7025 *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 *:https *:* LISTEN
tcp 0 0 *:7071 *:* LISTEN


ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:50:BA:CB:85:5D
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::250:baff:fecb:855d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25962 errors:0 dropped:0 overruns:0 frame:0
TX packets:13409 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2855385 (2.7 MiB) TX bytes:1499043 (1.4 MiB)
Interrupt:10 Base address:0x8000

eth1 Link encap:Ethernet HWaddr 00:50:BA:BD:98:62
inet addr:142.179.183.240 Bcast:142.179.183.255 Mask:255.255.248.0
inet6 addr: fe80::250:baff:febd:9862/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47760 errors:0 dropped:0 overruns:0 frame:0
TX packets:49395 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15739296 (15.0 MiB) TX bytes:7395944 (7.0 MiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:226139 errors:0 dropped:0 overruns:0 frame:0
TX packets:226139 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:105248720 (100.3 MiB) TX bytes:105248720 (100.3 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


Thanks in advance.
Reply With Quote
  #6 (permalink)  
Old 04-14-2006, 01:53 PM
Zimbra Employee
 
Posts: 4,792
Default

You should be able to delete the domain from the admin UI.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #7 (permalink)  
Old 04-14-2006, 03:16 PM
Active Member
 
Posts: 25
Default

Kevin,

vortex is not in the domain section. It is in the servers section.
Two servers show up here, one for enterprise.office.tmocon.com and
one for vortex.tmocon.com. Please see attached zip file that contains
screen shots of the admin login.
Attached Files
File Type: zip zimbra_problems.zip (248.1 KB, 65 views)
Reply With Quote
  #8 (permalink)  
Old 04-14-2006, 03:24 PM
Active Member
 
Posts: 25
Default

Also I get an error when I click on class of service. See screen shot in
attached file.
Attached Files
File Type: zip zimbra_problems_2.zip (78.4 KB, 49 views)
Reply With Quote
  #9 (permalink)  
Old 04-14-2006, 07:30 PM
Zimbra Employee
 
Posts: 4,792
Default

zmprov ds SERVERNAME (to remove the server)

You'll also want to reset the default COS mailhostpool

zmprov mc zimbraMailHostPool ID

Where ID is the ID of the other server from zmprov gs SERVER.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #10 (permalink)  
Old 04-14-2006, 08:38 PM
Active Member
 
Posts: 25
Default

I've executed the commands. Get a syntax error, though, on the
reset of the COS.

While in zmprov I get a usage error for this command:

mc zimbraMailHostPool 9636bfbb-a0d8-4df9-9ca8-417b68f8032d
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.