Scalix Forums

Hi all,

I have joined two communities today. The one being the Scalix community, and the other being the "I can't get Scalix installed on FC4 community"

I'm trying to get the community edition installed on a home system to use for the family - using outlook/evolution and perhaps even thunderbird as mail clients.

The machine is a dual P3 with enough ram and disk space, up to date FC4 installation.

WHat did I have to do thusfar to get to where I am:
Install a BIND server locally - the only way to progress past the initial system check.
Installed Tomcat5 as per the Scalix docs.

The installation progesses just fine, and then the initial configuration starts. I have to enter the name of the mailnode, or rather accept the suggestion, and click on forward. And then nothing happens. The install appears to "freeze" in the "E-mail address format" screen.

Ideas?

The install log follows:

2005-11-24 20:07:01,073 INFO System check start
2005-11-24 20:07:01,266 INFO Network interface is actually eth0
2005-11-24 20:07:01,277 INFO Operation passed: Network check passed.
2005-11-24 20:07:01,280 INFO Operation passed: Filesystem check passed.
2005-11-24 20:07:01,386 INFO Java and Tomcat check info -- JAVA_HOME environment variable is /opt/j2sdk_nb/j2sdk1.4.2/
2005-11-24 20:07:01,706 INFO Java and Tomcat check info -- Java version 1.4.2
2005-11-24 20:07:01,771 INFO Java and Tomcat check info -- Default Tomcat directory is /opt/jakarta-tomcat-5.0.28
2005-11-24 20:07:01,875 INFO Java and Tomcat check info -- Tomcat version is 5.0.28
2005-11-24 20:07:01,876 INFO Operation passed: Java and Tomcat check passed.
2005-11-24 20:07:06,112 INFO Apache appears to be installed.
2005-11-24 20:07:06,113 INFO Operation passed: Dependency check passed.
2005-11-24 20:07:07,969 INFO Operation passed: Running services check passed.
2005-11-24 20:07:07,971 INFO System check end
2005-11-24 20:07:07,976 INFO System check result: pass
2005-11-24 20:07:24,650 INFO Stopped Tomcat using command /opt/jakarta-tomcat-5.0.28/bin/shutdown.sh
2005-11-24 20:07:27,737 INFO Tomcat is stopped True
2005-11-24 20:07:27,959 INFO Install start
2005-11-24 20:07:28,958 INFO Starting installation of component scalix-server-community using RPM scalix-server-community-9.4.2.4-0.1.fc4.i386.rpm from /work/scalix-9.4.2-community-intel-rh/software/scalix_server
2005-11-24 20:08:13,601 INFO Operation passed: Install /bin/rpm -i /work/scalix-9.4.2-community-intel-rh/software/scalix_server/scalix-server-community-9.4.2.4-0.1.fc4.i386.rpm: (0) ['']
2005-11-24 20:08:14,599 INFO Starting installation of component scalix-swa using RPM scalix-swa-9.4.0.52-1.noarch.rpm from /work/scalix-9.4.2-community-intel-rh/software/scalix_server
2005-11-24 20:08:16,044 INFO Operation passed: Install /bin/rpm -i /work/scalix-9.4.2-community-intel-rh/software/scalix_server/scalix-swa-9.4.0.52-1.noarch.rpm: (0) ['Please configure Scalix Web Access (SWA) using the /opt/scalix/bin/configurator script.', 'For usage consult man page by typing man configurator. SWA minimally requires Tomcat 4.1.29 and JDK 1.4.2+.', 'After configuring SWA you may launch SWA within Tomcat with <Tomcat_installed_dir>/bin/startup.sh.', 'To check any startup errors look at <Tomcat_installed_dir>/logs/scalix-swa_log.<date>.txt']
2005-11-24 20:08:17,049 INFO Starting installation of component scalix-sac using RPM scalix-sac-9.4.2.5-1.noarch.rpm from /work/scalix-9.4.2-community-intel-rh/software/scalix_server
2005-11-24 20:08:18,863 INFO Operation passed: Install /bin/rpm -i /work/scalix-9.4.2-community-intel-rh/software/scalix_server/scalix-sac-9.4.2.5-1.noarch.rpm: (0) ['Please configure Scalix Administration Console (SAC) using', 'the Scalix Installer for configuration.', 'SAC minimally requires Tomcat 4.1.29 and JDK 1.4.2+', 'After configuring SAC you may launch the SAC within Tomcat with <Tomcat_installed_dir>/bin/startup.sh.', 'To check any startup errors look at <Tomcat_installed_dir>/logs/caa.log', 'Tomcat container must run as root if SAC is configured and deployed in Hybrid or Single Server local mode.', 'Have fun!']
2005-11-24 20:08:18,864 INFO Install end
2005-11-24 20:11:59,439 INFO Mailnode name derived from FQDN: beast
2005-11-24 20:14:37,598 INFO Mailnode is beast
2005-11-24 20:14:37,750 WARNING Could not fetch generation rule general.inet_domain_rule with result: ['']
[root@beast ~]#

I ran the installer with --debug.

DEBUG:root:Packages just upgraded: {}
DEBUG:root:All packages now installed: {'scalix-sac': '9.4.2.5', 'scalix-swa': '9.4.0.52', 'scalix-server-community': '9.4.2.4'}
INFO:merlin:Install end
DEBUG:root:WizardInstalling:Done timeout
DEBUG:root:Message store checking: /var/opt/scalix/sys/version exists: False
DEBUG:root:==> Leaving screen WizardInstalling
DEBUG:root:==> Entering screen WizardMailnodeName ============
DEBUG:root:WizardMailnodeName:debug mode True
DEBUG:root:Message store checking: /var/opt/scalix/sys/version exists: False
INFO:merlin:Mailnode name derived from FQDN: beast
INFO:merlin:Mailnode is beast
DEBUG:root:==> Leaving screen WizardMailnodeName
DEBUG:root:==> Entering screen WizardEmailConfiguration ============
DEBUG:root:WizardEmailConfiguration:debug mode True
WARNING:merlin:Could not fetch generation rule general.inet_domain_rule with result: ['']
Traceback (most recent call last):
File "build/py24/sxmerlin.py", line 320, in forward_event
File "build/py24/sxmerlin.py", line 280, in do_transition
File "build/py24/sxmerlin.py", line 537, in build_work_area
File "build/py24/sxscreens.py", line 2333, in build_work_area
TypeError: GtkEntry.set_text() argument 1 must be string, not None

Can you check that /etc/hosts doesn't have you hostname on the same line as the 127.0.0.1 (locahost) address ?

This is an annoying habit that the RedHat installation has which is plain wrong.

Your /etc/hosts files should be:

127.0.0.1 localhost.localdomain localhost
ip.ip.ip.ip your.fqdn.com alias

It's also possible that because you do not have a domain name that there is a problem. The installer is trying to determine the domain name to use and this is usually everything except the hostname of your server. So, in this case, you should also define a FQDN for the server.

Cheers

Dave

In my hosts file I had to swop the fqdn and the alias (perhaps a supid setting on my part
was:
127.0.0.1 localhost.localdomain localhost
192.168.10.12 beast beast.localhost.net

now
127.0.0.1 localhost.localdomain localhost
192.168.10.12 beast.localhost.net beast

On to the next step.