Page 1 of 1

Issues after updating from 12.1 to 12.5

Posted: Tue May 19, 2015 1:46 pm
by fkienker
After updating my Scalix server from 12.1 to 12.5 on CentOS 6.6 I'm now seeing this error shortly after starting Scalix Web Access in both Firefox and Internet Explorer:
"An error occurred while fetching the messages in your calendar folder(s)"

In the HTTP error_log I see these messages:
[Tue May 19 13:23:58 2015] [error] ajp_read_header: ajp_ilink_receive failed
[Tue May 19 13:23:58 2015] [error] (70007)The timeout specified has expired: proxy: dialog to ( failed
[Tue May 19 13:24:01 2015] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
[Tue May 19 13:24:01 2015] [error] ajp_read_header: ajp_ilink_receive failed
[Tue May 19 13:24:01 2015] [error] (70007)The timeout specified has expired: proxy: dialog to ( failed

I have tried:
* Increasing maxSpareThreads in Tomcat as suggested elsewhere but this had no effect.
* Disabling all of the firewall rules (though I am loth to continue running the server without a firewall).
Neither action had any effect.

Has anyone else seen these issues? Any suggestions as to where to look?


Re: Issues after updating from 12.1 to 12.5

Posted: Tue May 19, 2015 1:54 pm
by fkienker
Also have now tried un-installing the Scalix DB and re-installing as had been suggested. This also had no effect.

Re: Issues after updating from 12.1 to 12.5

Posted: Wed May 20, 2015 6:14 am
by ScalixSupport

Could you check / post content of file ""

Re: Issues after updating from 12.1 to 12.5

Posted: Wed May 20, 2015 10:11 am
by fkienker
Current contents of the file:



# Comma-separated list of additional fonts to be displayed in the Rich Text editor

# Instructs the system to convert non-breaking space characters into space characters
# when sending text-based messages. This is usefully because the non-breaking space
# character falls outside the scope of the ASCII character set. Messages that would
# otherwise only require ASCII encoding will instead be forced to use latin ISO-8859-1
# or UTF-8 encoding to accomadate the non-breaking space. Set this value to false if
# you wish to maintain non-breaking space characters when sending messages.

# SWA can optionally use a platform API server to search for mail messages and to
# fetch message headers. In some cases, the platform API performs better than
# using IMAP directly. SWA uses IMAP directly for searches and header fetching
# if the platform URL is not available, or if the platform is disabled
# (see the "swa.platform.enabled" property).
# SWA can distribute its platform API load across platform instances on different hosts.
# SWA determines the host to use based on the IMAP referral host for a user. SWA
# examines the swa.platform.url.format property and replaces the {0}
# token with the user's IMAP referral host to produce the platform url for that
# user. For example, consider the following example setting:
# swa.platform.url.format=http://{0}/api
# Based on this setting, if the user is referred to the IMAP host
# "", SWA will also direct platform API traffic to
# "".
# If no IMAP host referral is configured for the user (the default), or if the
# default platform URL from property "swa.platform.url".
# (See the documentation on configuring a multi-server installation for more
# information about configuring IMAP referral.)
# Set true to use the platform server for searching and for fetching message headers.
# These properties control the pool of HTTP clients used by SWA for communicating
# with the platform.
# maxConnectionsPerHost limits the number of connections SWA will keep open to any
# single platform instance.
# maxTotalConnections limits the number of connections SWA will keep open to all
# platform instances put together. A typical installation has only one platform instance.

# maximum number of search results to return in one "page". Use -1 for "all" (not advised for where there are large indexes).

# This is the idle time in seconds after which a user's servlet session
# will expire. Usually this value does nothing in SWA because mail
# polling keeps the session alive until the user closes her browser
# triggering a logout.
# Determines whether to keep each user's current imap folder open between browser requests.
# Keeping the folder open may improve performance but requires additional
# runtime memory for the folder's messages. Under normal circumstances, keeping
# folders open requires a few megabytes of additional memory for each active
# user session.

# The default charset to use to interpret message bodies when no charset is specified in the message

# URL Schema used to display maps when the user clicks on a postal address.
# For Google Maps:
# For Yahoo! Maps:
# For MapQuest:

swa.user.msgCompositionFontFamily=times new roman, new york, times, serif
# The user will have the option to auto-acknowledge read receipts
# Default date/time format index
# 1 = month/day/year, 12 hour format
# 2 = month/day/year, 24 hour format
# 3 = day/month/year, 12 hour format
# 4 = day/month/year, 24 hour format
# 5 = year/month/day, 12 hour format
# 6 = year/month/day, 24 hour format
# Default date separator character
# Default time separator character
# Default days in a work week
# 0=Sunday, 1=Monday, 2=Tuesday, ..., 6=Saturday
# Default start of the work day in minutes (480 = 8AM)
# Default end of the work day in minutes (1020 = 5PM)
# Default first day of the week
# 0=Sunday, 1=Monday, 2=Tuesday, ..., 6=Saturday
# Default number of days covered by the upcoming appointments
# Default calendar view
# 0=Daily view
# 1=Work week view
# 2=Weekly view
# 3=Monthly view
# How many months of Free/Busy information should we publish on the server?
# How often (in minutes) should we update Free/Busy information on the server?
# Specifies whether email addresses should be shown
# or if SWA should only show display names
# Specifies whether SWA should block remote images in HTML emails.
# Default mail time-window filter size, options are:

# Global-user Admin controls
# Toggle whether you wish to allow the user to edit the From or Reply-To headers in the user prefs
# The admin can force SWA to auto-ackknowledge read receipts, hiding the option
# from all users' preference dialogs

# Defines which messages with sensitivity values set should be blocked, or
# prompted to the user to ask for confirmation to view.


# Defines in Seconds how long a SOAP request will remain in the current, uncomplete
# readyState (= 1, 2, or 3) before we force a timeout

# Defines the number of times to retry if the SOAP request times out. Certain other connection
# errors can be reported as a timeout. This setting will also affect those circumstances.
# The default is 0.

# Additional LDAP sources can be added here. The following attributes are valid
# Server Hostname or IP address (optional, default = localhost)
# swa.ldap.<n>.server=localhost
# If the special value '%h' is specified as the server hostname,
# the user's mailbox server (the server where SWA accesses their IMAP mailbox)
# is used. This is useful in multi-server deployments because it avoids
# LDAP referral chasing. If an LDAP server other than the user's 'home'
# server is used, it will generate a referral that has to be followed
# to their home server. This happens on every LDAP connection leading to
# extra load on the local LDAP server and increased response time.
# The '%h' directive optimizes the referral following away because
# the user's IMAP server, which we have already identified, is by
# definition the correct LDAP server to contact to avoid referrals.
# LDAP port number (optional, default = 389)
# swa.ldap.<n>.port=389
# Base DN (mandatory)
# swa.ldap.<n>.baseDN=o=Scalix
# Type (mandatory)
# Notes: (1) This is actually a name to tag the entry; "personal" and "system"
# are reserved values, as is any name starting with either.
# (2) to define the search order, this can be referenced in
# swa.user.dirSearchOrder
# swa.ldap.<n>.type=myldap
# LDAP search Filter (mandatory)
# Note: Use %s to represent user input to checknames or addressbook search
# swa.ldap.<n>.filter=(|(givenname=*%s*)(surname=*%s*))
# LDAP search Scope (optional, default = one)
# Possible Values: sub, one, base
# swa.ldap.<n>.scope=sub
# Maximum number of entries to return (optional, default 100)
# swa.ldap.<n>.addressSearchLimit=10
# Maximum time (in milliseconds) before timing out (optional, default 10000)
# swa.ldap.<n>.timeout=30000
# LDAP Authentication Type (optional, default = none)
# Possible Values: none, simple
# swa.ldap.<n>.authType=none
# LDAP Authentication Type (optional, default = none)
# Possible Values: none, simple
# swa.ldap.<n>.authType=none
# LDAP Bind DN (optional)
# Note: Use %u to represent the user's name as identified by his eMail address
# swa.ldap.<n>.bindDN=cn=Administrator,o=Scalix
# LDAP Source Label (mandatory) or ID for localized name in Resource file)
# swa.ldap.<n>.resourceLabel=My LDAP
# swa.ldap.<n>.resourceID=my_ldap_resource_label
# Name of attribute displayed as Friendly Name in CheckNames result
# (optional, default = omcn)
# swa.ldap.<n>.checkNames.nameAttribute=displayName
# Name of attribute displayed as Email Address in CheckNames result
# (optional, default = mail)
# swa.ldap.<n>.checkNames.nameAttribute=rfc822address
# Further attribute definitions (the address book expects at least 3 columns)
# LDAP Attribute Label (mandatory) or ID for localized name in resource file
# swa.ldap.<n>.search.<m>.resourceID=fax_number_resource
# display Header (optional)
# swa.ldap.<n>.search.<m>.header=true
# Attribute identification for special columns (optional)
# Possible values: name, email
# swa.ldap.<n>.search.<m>.type=name
# LDAP attribute mapped to column (mandatory)
# swa.ldap.<n>.search.<m>.dirAttribute=UID

swa.ldap.1.displayName.resourceLabel=System Directory
swa.ldap.1.addressSearchLimit=100 Address Phone Phone Phone

swa.ldap.2.displayName.resourceLabel=Personal Contacts

# Default theme name
# set to true is you want end user to be able to select from the list of predefined themes in Options

# Customized links to external sites may be added to the tools menu
# as follows:
# The URL (mandatory)
# swa.url.<n>.url=url
# Defines the url that will open in a new window when the menu
# item is clicked. It is recommended to explicitly include
# the desired protocol as part of the url, but SWA will use
# http:// in the absence of another protocol.
# You may use the %u variable as a placeholder that will be
# replaced by the currently logged-in user's e-mail address
# The id of a localizable string in the resource file to display
# in the menu (optional)
# swa.url.<n>.name.resourceID=resourceID
# If the given ID is present in the localization file,
# SWA will use the string associated with that ID as
# the label for this menu item.
# The label to do display in the menu (optional)
# swa.url.<n>.name.resourceLabel=resourceLabel
# If the resource ID is not defined or is not present in the
# resource file this label will be displayed as the label
# for the menu item.
# For example:
# swa.url.1.url=
# Notes:
# - Any links defined here will appear under the Tools menu of SWA
# for all users
# - <n> can be any number between 1 and 10. No more than 10 links
# can be displayed
# - Any labels beyond 35 characters in length will get truncated
# - If a label cannot be found or is not defined, the menu item will
# appear as "Untitled"

# swa.url.1.url=


# Comma-separated list of Internet address of users with client logging enabled

#The default client log level for debug users. 0 = OFF, 1 = ERROR, 2 = WARN, 3 = INFO, 4 = DEBUG
#3 is default.

#The default client log destination for debug users. 0 = LOCAL, 1 = REMOTE, 2 = BOTH

Re: Issues after updating from 12.1 to 12.5

Posted: Wed May 20, 2015 10:19 am
by fkienker
Note: was substituted for the real server hostname.

This should be a very "vanilla" file. We have made no changes to it manually.

SO glad we decided to test this before deploying it! Our testers can live with "broken" SWA's but not our users.

Re: Issues after updating from 12.1 to 12.5

Posted: Wed May 20, 2015 11:25 am
by ScalixSupport

please check last line, it should be "" instead of ""

Re: Issues after updating from 12.1 to 12.5

Posted: Wed May 20, 2015 2:37 pm
by fkienker
I made the change per your instructions, rebooted the Scalix server, cleared the browser cache, rebooted the Windows machine and tried it again. Now after about 15 seconds i have a message "An error occurred while fetching the messages in your calendar folder(s)" followed by a message "Your Scalix server is temporaily unavailable. Please try again later." If I click on the OK button and wait about 30 seconds it all "magically" starts working correctly and continues to do so until the browser window is closed hours later. But the next time it is opened again same thing happens.

BTW, the change you asked me to make seemed a bit counter-intuitive. The server hostname *is* but the email domain is (in fact) We have been running our severs successfully this way since the early days of Scalix 10.1 without issues. If this is a *problem* we need to know this.

Re: Issues after updating from 12.1 to 12.5

Posted: Thu May 21, 2015 4:38 am
by ScalixSupport

As i checked in file your mail domain name is showing "". And same domain name used for imap, smtp server and swa platform.

Re: Issues after updating from 12.1 to 12.5

Posted: Thu May 21, 2015 11:10 am
by fkienker
There appears to be some mis-communication. The Scalix hostname is and it lives on then network. The Scalix Default Domain is set to "" and it is the only domain Scalix recieves email for.

I'm at a complete loss as to where to look next. What does " ajp_read_header: ajp_ilink_receive failed" mean and what is it trying to tell me?

Re: Issues after updating from 12.1 to 12.5

Posted: Fri May 22, 2015 11:00 am
by ScalixSupport

Please share the output of below commands

hostname -f


Re: Issues after updating from 12.1 to 12.5

Posted: Sun May 24, 2015 3:02 am
by fkienker
# hostname -f
# omshowmnmp

Re: Issues after updating from 12.1 to 12.5

Posted: Mon May 25, 2015 5:01 am
by ScalixSupport

Then all is ok, when hostname and domain name are different in this case you should use hostname in all config file.

Apache 70007 error mean that session was closed because of timeout and after update it was rewrited all files in "/etc/opt/scalix-tomcat/connector/ajp/"
make some changes like timeout=800 retry=1 ttl=5 ping=5 or increase these parameters, and after that you should restart apache.

Re: Issues after updating from 12.1 to 12.5

Posted: Mon Jul 06, 2015 1:17 am
by fkienker
Well, further testing is starting to make me think this is and version conflict with a package from the OS. I'm running Scalix 12.1 and 12.5 test instances on CentOS 6.6 x64. I have *exactly* the same issue on *both* versions with the Webmail client. No issues with either one running CentOS 5.11 - none!

Further more, I have been using postfix for years with Scalix (back to 11.1 days) and now have intermittent problems sending email from both 12.1 and 12.5 using postfix 2.6.6-6.el6_5 in CentOS 6 x64 which *never* occur when the email is instead routed ot another machine running postfix 2.3.3-7.el5 on CentOS 5.11. This is a repeatable test using an email with attachements. Emails without attachements so far do not have the issue.

Am I the only one running these combinations?

Re: Issues after updating from 12.1 to 12.5

Posted: Thu Jul 09, 2015 1:33 pm
by fkienker
Have finally worked through all but one of the postfix issues. Once this last one is conquered all will be well.

There is a possibility the errors I see could be coming because Outlook is the typical client we use for testing. I plan to test this setup again and avoid using Outlook and see if the errors go away. I also question whether or not I'm using the current Scalix Connector. One of the issues with the new website is no version information seems available. This makes it hard to know whether or not we are using the current version or when updates are available.