Zimbra 3 on FC4 having problems with zimbraMailPort and SOAP service

[marcmac]

Are you sure that apache is correctly rewriting the request?

[cjhall]

Here is what I have in my apache httpd.conf...


# myhost.com
ServerName myhost.com
ServerAdmin admin@myhost.com
ErrorLog logs/myhost.com__error.txt
CustomLog logs/myhost.com__access.txt combined
JkMount /* ajp13
JkMount /service/soap/* ajp13
JkMount /zimbra/mail ajp13
JkMount /zimbra/auth/ ajp13
JkMount /zimbra/js/*.jgz ajp13
JkMount /zimbra/ ajp13
JkMount /service/* ajp13


# MOD JK
# mod_jk

# Load mod_jk module
LoadModule jk_module modules/mod_jk.so
# Where to find workers.properties
JkWorkersFile /etc/httpd/conf.d/workers.properties
# Where to put jk logs
JkLogFile /var/log/httpd/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
# SHM info
#JkShmFile /etc/httpd/logs/jk.shm
#JkShmSize 10M
# Select the log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
# JkOptions indicate to send SSL KEY SIZE,
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
# JkRequestLogFormat set the request format
JkRequestLogFormat "%w %V %T"

Alias /zimbra/img/ /opt/zimbra/jakarta-tomcat-5.5.7/webapps/zimbra/img/
Alias /zimbra/js/ /opt/zimbra/jakarta-tomcat-5.5.7/webapps/zimbra/js/
Alias /zimbra/public/ /opt/zimbra/jakarta-tomcat-5.5.7/webapps/zimbra/public/
Alias /zimbra/skins/ /opt/zimbra/jakarta-tomcat-5.5.7/webapps/zimbra/skins/
Alias /zimbra/test/ /opt/zimbra/jakarta-tomcat-5.5.7/webapps/zimbra/test/
Alias /zimbra/zimlets/ /opt/zimbra/jakarta-tomcat-5.5.7/webapps/zimbra/zimlets/

[cjhall]

It is pretty clear the problem is with the SOAP login request... that request isn't getting forwarded to Tomcat.

In the access log for my virtual host I see:
[02/Mar/2006:12:14:45 -0500] "POST /service/soap/ HTTP/1.1" 500

It's getting a server 500 error.

Ideas??? ANYONE???

[marcmac]

I'm afraid I can't help, never having set this up myself.

[cjhall]

FYI -- I never did get mod_jk to work correctly. I am still searching for answers...

I ended up changing to use ProxyPass to Tomcat. It's not the most scaleable but it will work for now.

** I welcome other's input if you come across a solution! **

[bbska]

Originally Posted by cjhall

FYI -- I never did get mod_jk to work correctly. I am still searching for answers...

I ended up changing to use ProxyPass to Tomcat. It's not the most scaleable but it will work for now.

** I welcome other's input if you come across a solution! **

This is leading me a bit closer to the cause of my own problems (exactly the same as yours on every level)

It would appear that the zmprov ms SERVER zimbraMailPort xxx command isn't actually causing the mail port to change.

hence why running a zmprov gcf zimbraMailPort shows 80

[bbska]

Originally Posted by bbska

This is leading me a bit closer to the cause of my own problems (exactly the same as yours on every level)

It would appear that the zmprov ms SERVER zimbraMailPort xxx command isn't actually causing the mail port to change.

hence why running a zmprov gcf zimbraMailPort shows 80

looking through the output of zmprov gs | less i see something quite interesting....

zimbraMtaAuthURL: http:myserver.com:80/service/soap/

that's gotta be the culprit right there.

going to attempt changing that and see if that makes a difference.

[marcmac]

You're changing one value, and fetching another.

zmprov ms servernam blah blah

changes an attribute on the server.

zmprov gcf blah fetches a GLOBAL config attribute.

You want:
zmprov gs servername | grep attrib to see if it changed.

And when you change it, restart tomcat. You're on 3.0.1, right? I don't think 3.0 had this.

zimbraMtaAuthUrl is for SMTP auth. Nothing to do with the web client.

[bbska]

Originally Posted by marcmac

You're changing one value, and fetching another.

zmprov ms servernam blah blah

changes an attribute on the server.

zmprov gcf blah fetches a GLOBAL config attribute.

You want:
zmprov gs servername | grep attrib to see if it changed.

It was a typo on my part.


I ran "zmprov gs servername | less" so I could read through all of the attributes to see if perhaps there as something I could see to indicate why zimbra is trying to do soap authentication over port 80 when i've changed every reference to port 80 to 7070.

And when you change it, restart tomcat. You're on 3.0.1, right? I don't think 3.0 had this.

I'm on the latest production build, downloaded it yesterday. I also always restart tomcat after making changes, we're an all java shop so I'm familiar with the inner-workings of tomcat, apache and mod_jk.

zimbraMtaAuthUrl is for SMTP auth. Nothing to do with the web client.

Didn't know that, though it does make sense. It didn't make sense that, after changing the port for http away from port 80, the url still was set specifically for port 80. That threw up red flags.

I think this is a wonderful product, btw, so don't take anything I do/say as critisizm. I am hoping to get to the bottom of this problem so that I, and others who are trying to do something similar will be able to do it the "right way" through mod_jk.

I'm pretty sure the soap login process is what is causing the problem by trying to do something over port 80 (either that or the soap response message is statically set to say port 80 ).

[bbska]

I too have resorted to using Apahce Mod_proxy with reverse proxying (ProxyPass).

My config for that, which works just fine now:

< Location "/service"\ >
ProxyPass http:my.server.com:7070/service
ProxyPassReverse http:my.server.com:7070/service
ProxyPassReverse /
< /Location >
< Location "/zimbra" >
ProxyPass http:my.server.com:7070/zimbra
ProxyPassReverse http:my.server.com:7070/zimbra
ProxyPassReverse /
< /Location >

To me this is not the best solution. mod_jk is the correct way to connect between apache and tomcat, but there's something in /service/soap that is trying to talk on port 80 and causing problems when using mod_jk.

I'm running version 3.0.1 on CentOS 4.2. It seems earlier releases did not have the same issues with mod_jk

If anyone has any information on using this version of Zimbra in conjunction with mod_jk, please let me know either on the forums or via email , aim, icq, whatever.