Scalix Forums

Hi, I don't know if anyone still is around who has successfully got Scalix to work on Debian Etch?

I am attempting the manual install and had got Scalix to the point where it wasn't logging in but the issue was with the connection to the administration server.

The user sxqueryadmin seemed to be locked even though: # omshowu -n sxqueryadmin

showed it as open!

However after reading:

http://www.scalix.com/wiki/index.php?ti ... min_Server

http://www.scalix.com/wiki/index.php?ti ... Query_User

viewtopic.php?t=6312&postdays=0&postorder=asc&start=0

and using the script from here: http://www.scalix.com/wiki/index.php?ti ... ebian_Etch

I almost am in to the admin console.

The specific error I'm getting is: Could Not Login, Could not fetch configuration information, Possible problem with administration server

From the script discussed above, the errors start here:

[...]
############################################################
#
# Setting up Scalix Mailnode
#
###########################################################
[...]

since it is installed already and starts up automatically on boot the wierd part is that none of the om commands work??

ie. omaddmn, ommakeom, omon -s all, omshowu -n sxadmin

After a reboot of the system I had to re-run:

export PATH=/opt/scalix/bin:$PATH
ommakeom

and now when I try to issue any of the om commands I get the error: Which Scalix Server system?



Is there anyone who has managed a manual install that can help me? I know Debian isn't supported and I don't know why it isn't since many people use it but I think my errors are similar to the guys in this post: viewtopic.php?t=6312&postdays=0&postorder=asc&start=0

using Fedora I think?

Anyway I would really apprieciate any advice!

Thanks

Hi,

as already said in a private mail, I would suggest starting from scratch and running the installation script line by line to see where the error happens.

I have run the installation script on Debian Etch systems several times without any problems so I would really be interested in where the script fails on your system.

Cheers,
Christoph

Hi Christoph,

I am just in the process of doing that!

It's really strange though the first error I got was: ldomain=$(hostname -d) here

It said unknown hostname then through me out of my ssh session??

Ok that problems sorted, just I hope the terminal will remember all the values from:



as it's not part of the script any more since am going line by line.

Ok this is getting really wierd!

I can't install line by line it seems my ssh session keeps exiting on me then when I come back to the script I have to start from the begining again??

I've resulted to modifying the script so that I go up to the point I left off line by line.

Apart from the downloads and package configurations which I excluded since they're in already everything else is in.

Now I am back to the previous Error area:



ommakeom doesn't work?

my modified script is as follows:



am gona try to add ommakeom to it and see if it works.

Ok this is the result of adding ommakeom into the script:



the error log shows this:

hmm now I disabled ommakeom from the script and added these lines:



and got this result:

Ok this is the last error I get:



with modified script:



At this point I don't know what to do so I will give it a rest for a while and wait for a response.

Ok this error: /var/opt/scalix/F0/webmail/

is coming up because my instance is lt and not F0!

I changed this: base=/var/opt/scalix/${short}

to: base=/var/opt/scalix/lt/

and then it worked!

gone through the script now and hopefully eliminated all the errors in there?

Admin console not starting though

Well after every thing was as documented I tried to login via localhost/sac and kept getting the errors service temporarily unavailable!

Now with my previous attempt that would go away after a while and the admin console would come up but no such luck here

I have just gone through all these settings in order to maybe try to rectify the situation:

http://www.scalix.com/wiki/index.php?ti ... min_Server

But now I cannot access from anywhere? Even after setting up DNS for the system from my router (it's a Cisco so has integrated DNS server) going to hostname.domainname.com/sac gives me URL not found.

I don't understand this!

after setting up this file: /var/opt/scalix/<instance>/webmail/swa.properties

everything should just work properly but it doesn't.

# ps aux|grep java gives me:



omshowu -n sxadmin

doesn't work untill I manually run:

export PATH=/opt/scalix/bin:$PATH

then I get:




# omshowu -n sxqueryadmin gives me:



omstat -a shows:



omstat -s shows



omshowu -a shows:



ps ax | grep tomcat shows:



ps -ax | grep httpd shows:



ps -ax | grep apache2 shows:



ps -ax | grep post shows:



and fianlly netstat- tap shows:

sparky wrote:Ok this is the result of adding ommakeom into the script:

Code: Select all

ERROR:   ompatchom script failed
         /var/opt/scalix/lt/s/sys/install/log contains error messages


the error log shows this:

Code: Select all


[..]

executing /opt/scalix/bin/omsendin

*** ERROR: FEATURE() should be before MAILER()
*** MAILER(`local') must appear after FEATURE(`always_add_domain')*** ERROR: FEATURE() should be before MAILER()
*** MAILER(`local') must appear after FEATURE(`allmasquerade')*** ERROR: FEATURE() should be before MAILER()
NOTE: A copy of your sendmail configuration with changes for Scalix is
      now in /opt/scalix/newconfig/om_sendmail.cf
      Use /opt/scalix/newconfig/sm.update to install it.




This is the only error I could find in your log. This is due to a slightly bogus sendmail.mc file. Simply put all the FEATURE lines before the first MAILER line. That should fix it.

sparky wrote:Ok this error: /var/opt/scalix/F0/webmail/

is coming up because my instance is lt and not F0!

I changed this: base=/var/opt/scalix/${short}

to: base=/var/opt/scalix/lt/

and then it worked!

gone through the script now and hopefully eliminated all the errors in there?

Admin console not starting though

Ok, This might be a problem in the installation script. From my experiences I guessed that the instance dir is determined from the first and last charachter of the hostname (being ferrari3200 in your case). But this might be wrong.

Could you please paste the output of:

hostname

hostname -f

and the contents of /etc/hosts?

If your instance directory differs from the one the scipt guesses than none of the config files gets written correctly which might explain why SAC and SWA are not accessible for you.

Cheers,
Christoph

Ok Christoph:

hostname: Ferrari3200

hostname -f: ferrari3200.optiplex-networks.com

/etc/hosts:

# cat /etc/hosts
127.0.0.1 localhost
192.168.1.5 ferrari3200.optiplex-networks.com Ferrari3200
192.168.1.1 ns1.optiplex-networks.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


Since the error you think is from here in you script:

[...]
base=/var/opt/scalix/${short}
[...]

I could just edit it and modify to: base=/var/opt/scalix/lt

of which I think I did anyway as posted above, but I will try re-running from there onwards again to hopefully get the correct files!

For future is the instance always the same or how is it determined??

As both times I've tried installing scalix instance has always been lt?

My previous attempt however did manage to get me as far as locahost/sac and webmail??

But it never connected to the db server I think as sxqluser was locked it said but wasn't

Ok if ever I try to login to mylaptop/sac or /webmail it gives me the URL not found warning.

Before at least I could login with localhost/sac

but with this install I can't.

Even after running the script again, I modified it to:



So I'm thinking that since the instance is correct the re-written files should be too - right?

Well I don't know at this point; back to playing around with my CentOS install of Scalix as it actually runs (same HD 3 OS's however dummy is for future main server install which is Debian hence reason for all this trouble )