Results 1 to 5 of 5

Thread: [SOLVED] Problem with httpd on alternate port

Hybrid View

  1. #1
    Join Date
    Feb 2009
    Location
    Shawnigan Lake, BC, Canada
    Posts
    66
    Rep Power
    6

    Exclamation [SOLVED] Problem with httpd on alternate port

    I am attempting to install ZCS OSS 5.0.18 as a secondary MX on a server with an existing Apache install, but cannot get the zimbra httpd to respond.
    Server is running Ubuntu 8.04-32bit, with Apache on port 80 before the zimbra install.
    The install detects a port conflict on port 80 as expected, and I resolve this in the initial setup as shown below:

    Store configuration

    1) Status: Enabled
    2) Create Admin User: yes
    3) Admin user to create: console@xxxx
    4) Admin Password set
    5) Enable automated spam training: yes
    6) Spam training user: spam.5wklrbl4cw@www.shawnigan.ca
    7) Non-spam(Ham) training user: ham.kygvjpp9b@www.shawnigan.ca
    8) Global Documents Account: wiki@xxxx
    9) SMTP host: xxxx
    10) Web server HTTP port: 8080
    11) Web server HTTPS port: 8443
    12) Web server mode: http
    13) IMAP server port: 143
    14) IMAP server SSL port: 993
    15) POP server port: 110
    16) POP server SSL port: 995
    17) Use spell check server: no
    18) Configure store for use with reverse mail proxy: FALSE
    19) Configure store for use with reverse web proxy: FALSE

    The services appear to start as expected, but I can't connect to the web interface on port 8080/8443 or the admin on port 7071, although I can see the httpd processes. A zmcontrol status shows:

    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Stopped
    zmmailboxdctl is not running.
    mta Running
    snmp Running
    stats Running

    A netstat before starting zimbra shows all necessary ports are available.

    Logs:

    zmmailboxd.out:

    Zimbra server reserving server socket port=110 bindaddr=null ssl=false
    Zimbra server reserving server socket port=995 bindaddr=null ssl=true
    Zimbra server reserving server socket port=143 bindaddr=null ssl=false
    Zimbra server reserving server socket port=993 bindaddr=null ssl=true
    Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
    1284 WARN [main] log - Config error at
    1284 WARN [main] log - Config error at
    1285 WARN [main] log - EXCEPTION
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.mortbay.xml.XmlConfiguration.call(XmlConfigura tion.java:534)
    at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:244)
    at org.mortbay.xml.XmlConfiguration.refObj(XmlConfigu ration.java:638)
    at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:252)
    at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:206)
    at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:968)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.mortbay.start.Main.invokeMain(Main.java:183)
    at org.mortbay.start.Main.start(Main.java:497)
    at org.mortbay.start.Main.main(Main.java:115)
    Caused by: java.net.BindException: Address already in use
    at sun.nio.ch.Net.bind(Native Method)
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSock etChannelImpl.java:119)
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAd aptor.java:59)
    at org.mortbay.jetty.nio.SelectChannelConnector.open( SelectChannelConnector.java:211)
    ... 17 more
    1290 WARN [main] log - Nested in java.lang.reflect.InvocationTargetException:
    java.net.BindException: Address already in use
    at sun.nio.ch.Net.bind(Native Method)
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSock etChannelImpl.java:119)
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAd aptor.java:59)
    at org.mortbay.jetty.nio.SelectChannelConnector.open( SelectChannelConnector.java:211)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.mortbay.xml.XmlConfiguration.call(XmlConfigura tion.java:534)
    at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:244)
    at org.mortbay.xml.XmlConfiguration.refObj(XmlConfigu ration.java:638)
    at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:252)
    at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:206)
    at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:968)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.mortbay.start.Main.invokeMain(Main.java:183)
    at org.mortbay.start.Main.start(Main.java:497)
    at org.mortbay.start.Main.main(Main.java:115)

    I suspect this section of the zmsetup.log may give a clue - is it possible that changing the base http port fails during setup as it needs to use zmprov to make the change? I got an error about creating documents during the install, bit didn't consider it significant...

    Tue Jul 14 16:07:56 2009 Initializing Documents...
    Tue Jul 14 16:07:56 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled TRUE
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    Tue Jul 14 16:07:57 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov mcf zimbraNotebookAccount wiki@xxxx
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    Tue Jul 14 16:07:58 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov in wiki@xxxx
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    Tue Jul 14 16:07:59 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled FALSE
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    Tue Jul 14 16:08:01 2009 failed to initialize documents...see logfile for details.
    Tue Jul 14 16:08:01 2009 Restarting mailboxd...
    Tue Jul 14 16:08:01 2009 *** Running as zimbra user: /opt/zimbra/bin/zmmailboxdctl restart
    Stopping mailboxd...mailboxd is not running.
    Starting mailboxd...done.
    Tue Jul 14 16:08:29 2009 done.

    This is a production web server, so I would rather not stop apache on port 80 just to install Zimbra. The Zimbra install on this machine will be for secondary mx ONLY, and yes, there is a good reason for it to co-exist on a production web server... We occasionally have to endure extended power outages during winter storms, and in the event of a generator failure, we can keep one server on UPS for about 24 hours if we shut everything else down. Having WWW and backup MX on a single server has saved us from total blackout a few times.

    Thanks.

  2. #2
    Join Date
    Feb 2009
    Location
    Shawnigan Lake, BC, Canada
    Posts
    66
    Rep Power
    6

    Default

    Confirmed - stopping the main apache instance on port 80, then starting zimbra resulted in ZCS listening on port 80, contrary to the port 8080 set during install. I assume this is because it must start on port 80 during install, then use a zmprov to change the listen port, which of course fails.
    Is there any workaround for this? I really don't wish to stop a production www server for the duration of the ZCS install just to get around this.

    Thanks.

  3. #3
    Join Date
    Jul 2009
    Posts
    8
    Rep Power
    6

    Default Same problem here

    I've got the same problem. Same version:
    Release 5.0.18_GA_3011.RHEL5_20090707164432 CentOS5 FOSS edition

    No matter what I set in the install, ZCS still comes up on port 80 and 443. (Proxy not installed)

    HTTPPORT=8080
    HTTPPROXY=FALSE
    HTTPPROXYPORT=8080
    HTTPSPORT=8443
    HTTPSPROXYPORT=8443

    Any ideas?

  4. #4
    Join Date
    Jul 2006
    Posts
    623
    Rep Power
    10

    Default

    Use something other then 8080 for HTTPPORT. If the HTTPORT and HTTPPROXY port conflict, regardless of whether the proxy is enabled, the HTTPPORT gets reset to the default 80.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  5. #5
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default

    Note that this is fixed in the 6.0 releases, but with 5.0.x, you must avoid 8080/8443 for the apache ports.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

Similar Threads

  1. My First Zimbra Install - Port Conflict issues
    By ryanashcraft in forum Installation
    Replies: 7
    Last Post: 02-17-2010, 11:54 AM
  2. New Installation
    By rdo2006 in forum Installation
    Replies: 4
    Last Post: 04-10-2009, 06:23 AM
  3. SSL error right after install, can't get into Admin UI
    By robotrock in forum Installation
    Replies: 5
    Last Post: 03-01-2009, 10:46 PM
  4. Erorr..initializing ldap failed(5362)
    By Logan_filter in forum Installation
    Replies: 10
    Last Post: 12-19-2008, 12:10 PM
  5. Is it started or not
    By kwelipatton in forum Installation
    Replies: 10
    Last Post: 03-28-2006, 10:11 PM

Posting Permissions

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