Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: Removing Zimbra on Port 80

Hybrid View

  1. #1
    Join Date
    Nov 2005
    Posts
    24
    Rep Power
    9

    Default Removing Zimbra on Port 80

    After installing Zimbra Open Source M2, I can no longer run Apache on Port 80 as Tomcat is running on Port 80. How can I disable Tomcat from running on Port 80?

    Also, can I still use mod_jk with Tomcat so I can access Zimbra in /zimbra/?

    Thanks

    Seb

    (It also works on CentOS 4.2 without any problems!)

    ----------------------------------------
    **MOD NOTE: This thread is locked because the information contained in it is depricated, and not longer of much use. Zimbra now includes a way to change the default port number in the configuration settings. It is STRONGLY reccommended that you do not edit the web.xml files***
    Last edited by jholder; 05-19-2006 at 06:38 PM.

  2. #2
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default server.xml

    Edit zimbra/tomcat/conf/server.xml and change the port. Also, there's an allowed port entry in (I think) tomcat/webapps/service/WEB-INF/web.xml - be sure you add your new port to that list.

  3. #3
    Join Date
    Nov 2005
    Posts
    24
    Rep Power
    9

    Default

    Also, mails are not getting through. There is nothing running on Port 25 although when i run 'service zimbra status', it says the mta is running.

    Any ideas (and thanks for the quick reponses)?

    Seb

  4. #4
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default postfix?

    is postfix running? (ps auxww | grep postfix)

    I take it you can't telnet to port 25 - was there a previous install of zimbra on this box? If so, make sure you stop the port forwarding (iptables -t nat -F)

    If postfix isn't running, start it:
    su - zimbra
    postfix start

  5. #5
    Join Date
    Nov 2005
    Posts
    24
    Rep Power
    9

    Default

    In /var/log/zimbra.log, I get these errors:

    Nov 15 19:23:56 hatbox postfix/master[23639]: warning: master_wakeup_timer_event: service pub
    lic/pickup: No such file or directory
    Nov 15 19:24:56 hatbox postfix/master[23639]: warning: master_wakeup_timer_event: service pub

    Nov 15 19:22:56 hatbox postfix/master[23639]: warning: master_wakeup_timer_event: service pub
    lic/pickup: No such file or directory
    Nov 15 19:23:10 hatbox postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfi
    x-2.2.3/conf/main.cf
    Nov 15 19:23:10 hatbox postfix/postfix-script: starting the Postfix mail system
    Nov 15 19:23:10 hatbox postfix/master[26033]: fatal: bind 127.0.0.1 port 10025: Address alrea
    dy in use

    Also, when I stop Zimbra, I get these errors:

    Killing mysqld with pid 25524 /opt/zimbra/bin/zmlogswatchctl: line 52: kill: (25341) - No such process



    Any ideas?

  6. #6
    Join Date
    Nov 2005
    Posts
    24
    Rep Power
    9

    Default

    It seems to be working now but only one mail has got through (after a restart) but I am still getting a few worrying errors in my zimbra.log:

    Nov 15 19:35:48 hatbox amavis[4812]: (04812-01) lookup_ldap_attr(amavisspamtag2l
    evel) (WARN: no such attribute in LDAP entry), "spayne@evolutionconsultancy.com"
    result=undef

    Nov 15 19:35:46 hatbox postfix/smtp[6289]: 08E1C1B85BC: to=<spayne@evolutioncons
    ultancy.com>, relay=127.0.0.1[127.0.0.1], delay=2, status=deferred (lost connect
    ion with 127.0.0.1[127.0.0.1] while sending RCPT TO)

    Nov 15 19:35:45 hatbox amavis[4809]: (04809-01) TROUBLE in process_request: Can'
    t continue after import errors at /opt/zimbra/zimbramon/lib/Net/LDAP/Bind.pm lin
    e 8\nBEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/Net/LDAP/Bin
    d.pm line 8, <DATA> line 353.\nCompilation failed in require at /opt/zimbra/zimb
    ramon/lib/Net/LDAP.pm line 296, <DATA> line 353.

    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: cannot get certificate from
    file /opt/zimbra/conf/smtpd.crt
    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: TLS library problem: 6284:e
    rror:02001002:system library:fopen:No such file or directory:bss_file.c:259:fope
    n('/opt/zimbra/conf/smtpd.crt','r'):
    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: TLS library problem: 6284:e
    rror:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:261:
    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: TLS library problem: 6284:e
    rror:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib:ssl_rsa
    .c:758:

    Any thoughts on this one (it is a production server ;-)

  7. #7
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default more errors

    Quote Originally Posted by sebpayne
    It seems to be working now but only one mail has got through (after a restart) but I am still getting a few worrying errors in my zimbra.log:

    Nov 15 19:35:48 hatbox amavis[4812]: (04812-01) lookup_ldap_attr(amavisspamtag2l
    evel) (WARN: no such attribute in LDAP entry), "spayne@evolutionconsultancy.com"
    result=undef
    This one is not a problem - we don't use the entire set of supported ldap attributes for amavis, so it's not finding this one (a per-user spam tag level, I think).


    Nov 15 19:35:46 hatbox postfix/smtp[6289]: 08E1C1B85BC: to=<spayne@evolutioncons
    ultancy.com>, relay=127.0.0.1[127.0.0.1], delay=2, status=deferred (lost connect
    ion with 127.0.0.1[127.0.0.1] while sending RCPT TO)
    This indicates that postfix can't hand off to amavis.

    Nov 15 19:35:45 hatbox amavis[4809]: (04809-01) TROUBLE in process_request: Can'
    t continue after import errors at /opt/zimbra/zimbramon/lib/Net/LDAP/Bind.pm lin
    e 8\nBEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/Net/LDAP/Bin
    d.pm line 8, <DATA> line 353.\nCompilation failed in require at /opt/zimbra/zimb
    ramon/lib/Net/LDAP.pm line 296, <DATA> line 353.
    The ldap bind perl module we shipped isn't happy on your system - is ldap running on this host (eg, is it a single node install)?

    One thing you may try, since this is a CentOS system, is re-install the LDAP::Bind module, and remove the version in /opt/zimbra/zimbramon/lib.


    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: cannot get certificate from
    file /opt/zimbra/conf/smtpd.crt
    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: TLS library problem: 6284:e
    rror:02001002:system library:fopen:No such file or directory:bss_file.c:259:fope
    n('/opt/zimbra/conf/smtpd.crt','r'):
    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: TLS library problem: 6284:e
    rror:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:261:
    Nov 15 19:35:39 hatbox postfix/smtpd[6284]: warning: TLS library problem: 6284:e
    rror:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib:ssl_rsa
    .c:758:

    Any thoughts on this one (it is a production server ;-)
    Postfix can't find the smtpd cert (and key, probably). Are you using the self-signed cert created at install? If so, run (as zimbra)
    zmcertinstall mta /opt/zimbra/ssl/ssl/server/smtpd.crt /opt/zimbra/ssl/ssl/ca/ca.key

  8. #8
    Join Date
    Nov 2005
    Posts
    24
    Rep Power
    9

    Default

    Also, I am now trying to get mod_jk working and having problems. It seems that there is no ajp13 running on port 8009 as they used to be.

    I'm not a Tomcat expert so not to sure what to do. What I think happened was that mod_jk used my workers.properties to connect to Tomcat by ajp13. However, this no longer exists so it can't connect.

    How can I enabled this? Is it possible?

    Thanks

  9. #9
    Join Date
    Oct 2005
    Location
    Marietta, GA
    Posts
    28
    Rep Power
    9

    Default I changed port 80 in files you outlined to port 8080 and now..

    The anitspam and mta services did not start when a did a shutdown and start. I did not add port 8080, I changed all refs to port 80 in server.xml and web.xml to port 8080. Please advise. Thanks.

  10. #10
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default errors

    These are both new to me.

    The second error (no such process) makes me think that swatch had died. Check /tmp/logswatch.out for errors - you may see something about DBD::mysql missing libraries?

    As for the postfix error. I'm assuming this is a binary install (you didn't build yourself). It looks like something is listening on 10025, which is the port postfix binds to for mail coming back from the content filter - you'll need to free that port up for postfix to start.

Similar Threads

  1. dspam logrotate errors
    By michaeln in forum Users
    Replies: 7
    Last Post: 02-19-2007, 11:45 AM
  2. Replies: 16
    Last Post: 09-07-2006, 06:39 AM
  3. Services stopped working
    By lilwong in forum Administrators
    Replies: 4
    Last Post: 08-15-2006, 09:19 AM
  4. Zimbra server crashed
    By goetzi in forum Administrators
    Replies: 6
    Last Post: 03-25-2006, 12:00 PM
  5. Replies: 1
    Last Post: 11-23-2005, 12:35 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
  •