404 errors - 11.0.1 upgrade

[Mouseclone]

I was having trouble with displaying message on webmail. That server was 11.0.0. So now after reconfiguring the server several time.. uninstall web access and reinstalling. Trying to read information about this I come here.

I can get the Apache default index.html page from mail.domain.com or localhost i get 404 errors when i try to get to mail.domain.com/webmail or sac. same localhost. Anything anyone can think of?


scalix-tomecat-connector.conf

Code: Select all

# ---------------------------------------------------------------------------
# Load deflate and proxy_ajp modules used by Scalix:
# ---------------------------------------------------------------------------

<IfModule !mod_deflate.c>
LoadModule deflate_module modules/mod_deflate.so
</IfModule>

<IfModule !mod_proxy.c>
LoadModule proxy_module modules/mod_proxy.so
</IfModule>

<IfModule !mod_proxy_ajp.c>
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
</IfModule>

# ---------------------------------------------------------------------------
# Configure on-the-fly deflate compression of the pages:
# ---------------------------------------------------------------------------

<Location />
  AddOutputFilterByType DEFLATE text/xml text/html text/css
  AddOutputFilterByType DEFLATE application/x-javascript
</Location>

# ---------------------------------------------------------------------------
# mod_proxy_ajp connector configuration
# ---------------------------------------------------------------------------

<IfModule mod_proxy_ajp.c>
Include /etc/opt/scalix-tomcat/connector/ajp/instance-*.conf
</IfModule>


From what i can tell form

Code: Select all

HTTP Status 404 - /sac

type Status report

message /sac

description The requested resource (/sac) is not available.
Apache Tomcat/5.5.16


tomcat/apache may not know where the web dirs are. I have made sure from other post that i have read that the tomcat service is up and running java was running for tomcat.

[dkelly]

Please take a look at the FAQs that I posted at the top of each forum.

Cheers

Dave

[Mouseclone]

well...

Code: Select all

Scalix 11 FAQs
From Scalix Wiki
Jump to: navigation, search

This is a set of FAQs relating to installing and using Scalix 11 that didn't make it into the documentation. It will be updated as we get more information.
Contents
[hide]

    * 1 Scalix directory structure has changed
    * 2 The Apache configuration has changed between Scalix 10.x and Scalix 11.x
    * 3 sendmail.cf will be overwritten after an upgrade
    * 4 SWA uses SMTP authentication
    * 5 Mounting /var/opt/scalix/temp on a different file system
    * 6 Scalix web-based Rules Wizard fails to load images
    * 7 Java process takes 95% or above CPU time
    * 8 ommapsmtp is replaced by ldapmapper for sendmail
    * 9 sendmail aborts with a segmentation violation
    * 10 SWA displays "The evaluation period for this time-limited product has expired"

Scalix directory structure has changed

The structure of a Scalix installation has changed to make Scalix instances self-contained. Previously, the message store was under /var/opt/scalix, tomcat was /opt/scalix-tomcat and the web application configuration files were found under /etc/opt/scalix

This has been changed so that everything is under /var/opt/scalix/NN/ where NN is a 2-character value taking the first and last characters of the host name. The message store is in a sub-directory called 's', i.e. /var/opt/scalix/NN/s. Configuration files for the web applications are in directories corresponding to the URLs that you would use. For example, if a hostname is "scalix", the webmail configuration will be /var/opt/scalix/sx/webmail

This is documented in the release notes but the binary /opt/scalix/bin/omrealpath can return the correct path to the mount point as follows:

/opt/scalix/bin/omrealpath "~/"

should return

/var/opt/scalix/NN/s

Other examples are:

/opt/scalix/bin/omrealpath "~/sys"
/opt/scalix/bin/omrealpath "~/logs"

to return specific directories.

To use this in a script:

SCALIX_PATH=$(omrealpath "~/")

Details for each instance are now stored in /etc/opt/scalix/instance.cfg. You should make sure that the OMDATADIR value is correct.
The Apache configuration has changed between Scalix 10.x and Scalix 11.x

The wiki page at HowTos/ApacheConfiguration details how this is set up.
sendmail.cf will be overwritten after an upgrade

With Scalix 11, we switched to using a .m4 macro for sendmail configuration. The installation will set this up and regenerate a new sendmail.cf. This will remove any hand-edits that have been applied to the sendmail.cf file. Typically, this will be SpamAssassin and Smart Host configurations. To re-instate those settings, you can add the following to your sendmail.mc file:

INPUT_MAIL_FILTER(`spamassassin',`S=local:/var/run/spamass.sock, F=, T=C:15m;S:4m;R:4m;E:10m')dnl

should be put at the bottom of the file and replace the name of the socket file with the one that your installation of spamass-milter is using.

define(`SMART_HOST',`smtp.your.provider')

should be uncommented replacing smtp.your.provider with the smart host relevant to your organisation.

In both cases, note that each quoted string begins with a ` and ends in a '.
SWA uses SMTP authentication

SWA now authenticates with the SMTP Relay. If you are using external authentication such as OpenLDAP or Active Directory, you will need to make sure that the changes you made to /var/opt/scalix/NN/s/sys/pam.d/ual.remote is also applied to /var/opt/scalix/NN/s/sys/pam.d/smtpd.auth and the SMTP Relay is restarted.

If this is not configured, you may find that users are unable to send messages using SWA.
Mounting /var/opt/scalix/temp on a different file system

Prior to an upgrade, if you have mounted /var/opt/scalix/temp on a different filesystem, you MUST make sure that you unmount it. This has been known to cause upgrade problems where the message store is left in an inconsistent state that requires manual intervention. After the upgrade, you should ensure that /etc/fstab defines the new directory location, i.e. /var/opt/scalix/NN/s/temp.
Scalix web-based Rules Wizard fails to load images

The Apache configuration file for the Scalix web-based Rules Wizard is not updated correctly during an upgrade. To reconfigure the file, run the command

omwebconf -l LANG

where LANG is either C, AMERICAN, ENGLISH or GERMAN
Java process takes 95% or above CPU time

This can happen for a couple of reasons

    * Indexing is taking place for everybody's mailbox. This is expected behaviour and will die down over a few days depending upon the size of the message store. However, it has been known for large message stores to take up to 5 days for indexing to complete as the processes have to access every single message. To throttle this behaviour, you can add the following options to /var/opt/scalix/NN/s/sys/general.cfg

IDX_MAXLOAD=xx
IDX_MINLOAD=yy

where xx and yy are per-CPU load averages. The IDX_MAXLOAD setting will stop the indexer from indexing any further messages when the per-CPU load average goes above the defined value. The indexer will not resume indexing until the per-CPU load average goes below the value defined by IDX_MINLOAD.

    * We have seen that some messages can cause the Search and Index Service (sis) to lock up. This affects Scalix Management Services and also Scalix Web Access. In this case, the problem message can be determined as follows:

ps -ef | grep indexer

to get the process id of the indexer process.

kill -SIGUSR2 pid

where pid is the process ID from the ps -ef command This will create a file called /var/opt/scalix/NN/s/tmp/indexer.log. If SIS is not responding, you should see records like

Rendered File = /var/opt/scalix/as/s/temp/mime_cache/mime8AWIEZ
RENDERED         ADD    5d70110a-45761d37-459ee97d-b507 user=106
                         dref=00011e01df3a1ef9 pdref=00010005febfc6e7 flags=0
                         sis=0x9e4e578 sisrc=503 attempt=0
Failed to connect

Look specifically for records that show sisrc=503. Take the dref= value and run the command (for example)

omdref 00011e01df3a1ef9

This will return

USER FOLDER: Peter Principal / argolis/CN=Peter Principal
 IN TRAY: User 103 Intray                                  : RecNo : ItemNo
   MESSAGE: Mime test 1                                    :     8 : 62097

This message should be deleted and tomcat should be restarted.
ommapsmtp is replaced by ldapmapper for sendmail

With Scalix 10, we used ommapsmtp to allow sendmail to determine if a recipient address was a Scalix one.

Scalix 11 replaces this with ldapmapper as a "ldap hash" for sendmail. This effectively proxies requests from sendmail to each Scalix LDAP service.

Some issues can arise ( see below for details of a sendmail segmentation violation ) when ldapmapper isn't running or the Scalix LDAP service is not running. Sendmail will not be able to process messages effectively and they will queue up in /var/spool/mqueue.

Things to check are:

   1. Is ldapmapper running ?
          * If not, run the command /etc/init.d/ldapmapper start
          * Check that it is configured to start at reboot using the command chkconfig --list ldapmapper
          * The command chkconfig --level 345 ldapmapper on will set ldapmapper to start at run levels 3,4 and 5.
   2. Is the Scalix LDAP service running ?
          * Use omstat -a to check this. If it's not running, use the command omon ldap

When you have resolved the above issues, you can force sendmail to resubmit the messages using the command sendmail -q
sendmail aborts with a segmentation violation

This is not technically a Scalix problem as it reveals a library mismatch between sendmail and OpenLDAP.

As mentioned above, we switched from using ommapsmtp to determine if an address was owned by Scalix to using a new process called ldapmapper. Sendmail is built using cyrus-sasl v1 whereas OpenLDAP is built using cyrus-sasl v2. Because sendmail calls LDAP to talk to our ldapmapper process, some library calls are incompatible and so sendmail aborts.

This has only been seen so far on RedHat Enterprise Linux 3.0 prior to update 2.

Therefore, the fix for this is to apply the RedHat Enterprise 3 updates.
SWA displays "The evaluation period for this time-limited product has expired"

In some cases, customers upgrading to Scalix 11 will see SWA displaying an error "The evaluation period for this time-limited product has expired. Please contact support@scalix.com to upgrade".

This is a misleading error and restarting the scalix-tomcat service will resolve the problem

doesn't seem to have anything about getting a 404 error page form local host or via web browser.

as a further not when going to http://scalix.server.com:8009/webmail i get a blank page. If the redirect was working correction i think that i would get a blank page as well.

I don't mean to be rude dkelly, but that answer was short and obscure to say the least and took me t a dead end to find my answer. Thank you for responding though

[andreas]

I have the same problem since the update from 10 to 11.01

[Mouseclone]

I got it fixed. I don't know if this is anyone else problem or not.

I had renamed the host. That is right i did it. but everything was working in 11.0.0 before the upgrade. I'm not sure what it was but it is now fixed.

I followed the pages 120 and 131 for changing th host name in Scalix Admin pdf or 11.0.1. This fixed my problem now to get the slow emails being displayed in the webmail. the problem with wasn't displaying is that it is taking to long and I'm impatient.

[dkelly]

I don't mean to be rude dkelly, but that answer was short and obscure to say the least and took me t a dead end to find my answer. Thank you for responding though

Item #2 on the FAQ is "The Apache configuration has changed between Scalix 10.x and Scalix 11.x". This details how we configure Apache to respond to URLs for the web applications.

The big note in that document is:

NOTE: These VirtualHost entries define the hostname that should be included in the URL in order for the web applications to be called. If you use a different hostname, you can change them. HOWEVER if you use the *:80 or *:443 notation to indicate that you want to listen on ALL names, you are likely to get Apache warnings that these VirtualHost definitions conflict with existing ones. If this is the case, you should consider moving the Scalix-specific configuration into the general Apache configuration. Consult the Apache documentation for your distribution on how to do this as the configuation will be distribution-specific.

So, sorry that you thought the response was abrupt but the answer was there.

Cheers

Dave

[sbyrne]

I had a devil of a time myself with this. I upgraded scalix and (inadvertently) changed the hostname.

Consequently, I've been using scalix 11 without the web apps for a couple of months now.

Today, following my increased annoyance in needing to create a new user, I finally got the scalix admin console working.

I too followed the directions on pages 130 (not 120) and 131 of the admin pdf and duly changed everything in sight to the new hostname.

I still couldn't lose the 404 error when trying to access http://<myhost>/sac

The last step I took was to go into the /var/opt/scalix/a1/tomcat/conf/Catalina (I know this may be different depending upon your installation) directory and create a soft link to the localhost directory in there with the name of my host: ln -s localhost <myhost>

After I did that, everything works again...yay...

Just thought other frustrated folks would like to know.