Scalix 11 - Permissions error with tomcat/apache

[rverrips]

Hi

Fairly new to scalix, but enjoying it so far. I've installed using the manual install on a Ubuntu 6.06 server and everything except the web-client and admin seems to working fine.

Strange thing is if I goto http://myserver.net/Scalix/rw it loads the Rules Wizards, but when I goto http://myserver.net/webmail or http://myserver.net/sac I get an apache 403 access denied error.

I've gone through the howto's / FAQ's and setup the various properties files as best I can see from there, but still no go?

Any idea's where I can start looking for a solution

Thanks

Yours

Roy

[kanderson]

Is Tomcat running?

"ps -aux|grep java" should show tomcat up and running. If it isn't, then you should be able to restart it with /etc/init.d/scalix-tomcat start.

That would be my first guess.

[rverrips]

Thanks for the reply kanderson, but java is running, as root (could that be the problem?) ...

Code: Select all

root      4333     1  4 20:47 ?        00:00:12 /usr/local/lib/jre/bin/java -server -Xms256m -Xmx256m -Dscalix.instance=/var/opt/scalix/bi -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/var/opt/scalix/bi/tomcat/conf/logging.properties -Djava.endorsed.dirs=/opt/scalix-tomcat/common/endorsed -classpath /usr/local/lib/jre/lib/tools.jar:/opt/scalix-tomcat/bin/bootstrap.jar:/opt/scalix-tomcat/bin/commons-logging-api.jar -Dcatalina.base=/var/opt/scalix/bi/tomcat -Dcatalina.home=/opt/scalix-tomcat -Djava.io.tmpdir=/var/opt/scalix/bi/tomcat/temp org.apache.catalina.startup.Bootstrap start


[Lod]

A bit off-topic but which version of Scalix did you install? If it is 11 could you please tell me how you did it? When I tried to install Scalix 11 on Ubuntu 6.06 it wouldn't install because of the wrong apache version:

dpkg: dependency problems prevent configuration of scalix-tomcat-connector:
scalix-tomcat-connector depends on apache2 (>= 2.2.0); however:
Version of apache2 on system is 2.0.55-4ubuntu2.1.

[rverrips]

Hi

A bit off-topic but which version of Scalix did you install? If it is 11 could you please tell me how you did it? When I tried to install Scalix 11 on Ubuntu 6.06 it wouldn't install because of the wrong apache version:

dpkg: dependency problems prevent configuration of scalix-tomcat-connector:
scalix-tomcat-connector depends on apache2 (>= 2.2.0); however:
Version of apache2 on system is 2.0.55-4ubuntu2.1.

It's a nasty trick, but worked for me ...
Run aptitude dist-upgrade and make sure you're current 6.06 server is up to date.
Then edit /etc/apt/sources.list and change all the edgy to feisty
Run aptitude update
Run aptitude install apache2 (This will install apache2.2 and all it's dependancies)
Then edit /etc/apt/sources.list and change all the feisty back to edgy
Run aptitude update

You also need to do a symlink for sh and bash to resolve another lil' prob when installing on Ubuntu - Forum posting is here 'bout that viewtopic.php?t=5354&highlight=

Note though that I haven't gotten past the permissions issue with tomcat yet - Rest of scalix works fine on Ubuntu though.

[Lod]

Thank you for your help. I got a bit further in the installation now. There are some problems I don't understand however, my knowledge of linux is limited. So I'm going to be patient till the installation on ubuntu is more mature (and easier).

[chris]

It's a nasty trick, but worked for me ...
Run aptitude dist-upgrade and make sure you're current 6.06 server is up to date.
Then edit /etc/apt/sources.list and change all the edgy to feisty
Run aptitude update
Run aptitude install apache2 (This will install apache2.2 and all it's dependancies)
Then edit /etc/apt/sources.list and change all the feisty back to edgy
Run aptitude update

Don't have an Ubuntu available at the moment to the check the exact syntax works, but you should be able to do that with a single command:

#apt-get install apache2/feisty

[scalar1234]

Hello,

I manually installed Scalix 11.0.1.22 on Debian Sarge.
I also installed Apahce 2.2.3.

All servers and services are up and running.
But when I'm trying to access http://<FQDN>/sac
I get an error 403 from the apache2-webserver.

The error.log of apache2 says the following:

"client denied by server configuration: proxy:ajp://<FQDN>:8009/sac"

The file's content of scalix-tomcat-connector.conf and instance-<hostname>.conf
seem to be correct as far as I can see.
For installation I used the manual way as it is described within the Wiki for Debian.

Has anyone solved this problem.
I've alreday searched the forum and wiki but still haven't found any solution yet.

Thanks in advance

[hkurent]

Hi,

I have the same problem here.
Scalix 11.0.1.xx on a debian etch (unstable).

Followed every step in den wiki document.
Apache log says:

... [client 10.1.2.5] client denied by server configuration: proxy:ajp://koralle.int.ourdomain.de:8009/webmail

Even more interesting - looking at the tomcat log:

INFO: Server startup in 51065 ms
Feb 14, 2007 4:29:31 PM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 18245
Feb 14, 2007 4:29:31 PM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.lang.IndexOutOfBoundsException
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:607)
at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:564)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:672)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)

Reviewing the configuration I found a part in the setup I'm not quite sure off.
The wiki says

Now, you must set up a number of parameters in /var/opt/scalix/<instance>/webmail/swa.properties:
...
swa.platform.url=http://scalix.mycompany.com/api # Points to Platform Host
...

which ein changed to reflect our domain. However, the original entry
was:

swa.platform.url=http://%PLATFORMURL%:8080/api

I tested both - with and without the port number, didn't work.

Sorry for being so verbose.

Regards,
Hans

[rverrips]

Nope couldn't solve it

I gave up, on Ubuntu/Debian and installed CentOS4.4 - Scalix then installled without a single prob' in less than 2 minutes thinking it was a RHEL 4 server.

Sorry ...

[scalar1234]

Hi,

could you please tell me the version of Apache2,
that works fine with Scalix11 under CentOS?

Maybe I should use Apache 2.0 instead of Apache 2.2???

Thanks

[rverrips]

Yup, CentOS is running Apache 2.0.52 - But for some reason the Scalix 11 deb's wouldn't install without Apache 2.2 ... If you get it working, please let me know.

[florian]

On all our fully supported platforms (RedHat, SuSE, etc.), you should always use the Apache version that comes with the OS.

On unsupported debian-based platforms, you have the choice - either you use Apache 2.2 or you make sure a proper libapache2-mod-jk is installed in addition to Apache 2.0.

We do provide such a package, precompiled on debian sarge, in our debian package tarball.

Cheers,
Florian

[scalar1234]

Hello Florian,

as I stated before.
I use Debian (kernel 2.6.20) with Apache 2.2.3
Furthermore I use the configuration-files for AJP.

By means of apache's error.log I can see, that the AJP-configuration files
are used, as the call to http://<FQDN>/sac is proxied to <FQDN>:8009/sac.

But it seems, as if tomcat doesn't perceive anything of thtat call.
I see nothing in tomcat's logfiles (e.g. catalina.out)
Nevertheless I cann see that tomcat is listening on port 8009 (lsof -i :8009).

But I wonder if it is necessary that a process is also listening on port 8443?
Indeed there isn't anyone listening on port 8443. Might that be a problem?

I think I#ll try to use Apache 2.0 with the JK-module under Debian...
But nevertheless I would be glad, if you had any further ideas.
The only reason why I upgraded to Apache 2.2 was the dependeny of
the scalix-tomcat-connector-DEB-package on that apache-version during
the manual installation process.

Bye
Andreas

[florian]

as a standard, tomcat does not log access to catalina.out...... so seeing nothng there is normal.

just to confirm the 403 error, does that come from tomcat or from apache?

i believe i've never seen a 403 in this context. have you setup anything special over your apache default config?

Florian.