Unable to start the installation

[enquirer]

Hello,

I am absolutely new to Scalix and wanted to install and evaluate it. I downloaded the community vesrion for fedora Core 4 and ran into the problem - the installer quits right after i start it.

The first attempt to run it produced the following result:

Scalix Installer - extracting archive, please wait...
tail: cannot open `+155' for reading: No such file or directory

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error exit delayed from previous errors
Error: Build does not contain version for the version of Python installed. Please ensure you have Python 2.2, 2.3 or 2.4 installed. Aborting.
Scalix Installer - cleaning up...

Then, I found that line 125 in scalix-installer read:

Code: Select all

tail +$SKIP $0 | tar xzm -C "$WRKDIR"

I believe, it should be

Code: Select all

tail -n +$SKIP $0 | tar xzm -C "$WRKDIR"

After I changed that and ran the script again, it quit will the following output:

Scalix Installer - extracting archive, please wait...
tar: Skipping to next header

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error
tar: Child returned status 1
tar: Error exit delayed from previous errors
/usr/bin/python: can't open file '/tmp/scalix-wizard.sqk543/py24/sxversion.pyc': [Errno 2] No such file or directory
Scalix Installer - starting version ...
Scalix Installer - using Python 2.4.2.
/usr/bin/python: can't open file '/tmp/scalix-wizard.sqk543/py24/sxmerlin.pyc': [Errno 2] No such file or directory
Scalix Installer - cleaning up...
Scalix Installer - stopped.

So, there seems to be a problem with the arcive that is incorporated into the installation script.

The md5 sum for the downloaded archive is

be3daeee9262c1938eaa1f9dfbdc464d scalix-core-intel-redhat-10.0.1.tar.gz

, which is what it should be.

Is there a corrupt archive in the script or I am missing something?

Thanks.

[ScalixSupport]

Actually the tail command was correct. It's basically saying skip the first X lines (in your case 155) in the file itself and pipe that through tar. So, you'll want to extract the scalix-installer file again (don't just remove your changes because by saving the file, you may have unknowily changed the binary portion of the file).

Now, once you've re-extracted the installer, we need to see what's going on with your tail command. First, are you running as root and if you logged on as someone other than root, did you "su - root" (note the - , it's important)? If that's correct, then can you type "which tail" and post the results. Also, did you start the installer by typing:

Code: Select all

./scalix-installer

or something else?

Thanks,
Rachel

[enquirer]

I am running as root and I did start the script as

Code: Select all

./scalix-installer

My tail is in /usr/bin/tail.

I re-extracted everything from the tarball and the script produced the same output:

Scalix Installer - extracting archive, please wait...
tail: cannot open `+154' for reading: No such file or directory

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error exit delayed from previous errors
Error: Build does not contain version for the version of Python installed. Please ensure you have Python 2.2, 2.3 or 2.4 installed. Aborting.
Scalix Installer - cleaning up...

And the reason I said the tail commans was, probably, wrong was that tail interpreted"+154" as a file name, not as an option. And the help to tail command reads:

Usage: tail [OPTION]... [FILE]...
Print the last 10 lines of each FILE to standard output.
With more than one FILE, precede each with a header giving the file name.
With no FILE, or when FILE is -, read standard input.

Mandatory arguments to long options are mandatory for short options too.
--retry keep trying to open a file even if it is
inaccessible when tail starts or if it becomes
inaccessible later; useful when following by name,
i.e., with --follow=name
-c, --bytes=N output the last N bytes
-f, --follow[={name|descriptor}]
output appended data as the file grows;
-f, --follow, and --follow=descriptor are
equivalent
-F same as --follow=name --retry
-n, --lines=N output the last N lines, instead of the last 10
--max-unchanged-stats=N
with --follow=name, reopen a FILE which has not
changed size after N (default 5) iterations
to see if it has been unlinked or renamed
(this is the usual case of rotated log files)
--pid=PID with -f, terminate after process ID, PID dies
-q, --quiet, --silent never output headers giving file names
-s, --sleep-interval=S with -f, sleep for approximately S seconds
(default 1.0) between iterations.
-v, --verbose always output headers giving file names
--help display this help and exit
--version output version information and exit

If the first character of N (the number of bytes or lines) is a `+',
print beginning with the Nth item from the start of each file, otherwise,
print the last N items in the file. N may have a multiplier suffix:
b 512, k 1024, m 1024*1024.

With --follow (-f), tail defaults to following the file descriptor, which
means that even if a tail'ed file is renamed, tail will continue to track
its end. This default behavior is not desirable when you really want to
track the actual name of the file, not the file descriptor (e.g., log
rotation). Use --follow=name in that case. That causes tail to track the
named file by reopening it periodically to see if it has been removed and
recreated by some other program.

I am perplexed.

[enquirer]

Update: running

Code: Select all

tail -n +154 scalix-installer |tar -xvzf -

did create the necessary "py" directories. But when I modified the script to reflect the necessary change in the command, it reported an error:

Scalix Installer - extracting archive, please wait...
tar: Skipping to next header

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error
tar: Child returned status 1
tar: Error exit delayed from previous errors
/usr/bin/python: can't open file '/tmp/scalix-wizard.lq3753/py24/sxversion.pyc': [Errno 2] No such file or directory
Scalix Installer - starting version ...
Scalix Installer - using Python 2.4.2.
/usr/bin/python: can't open file '/tmp/scalix-wizard.lq3753/py24/sxmerlin.pyc': [Errno 2] No such file or directory
Scalix Installer - cleaning up...
Scalix Installer - stopped.

which means that editing this file modifies its binary content as well. I guess, it depends on the editor.
But now I will have to modify the script to let it know that I already have the "py" directories.

[enquirer]

Well, using plain vi to modify the script did the trick - it correctly extracted the files from the archive.

[ScalixSupport]

Hi. Are you certain you're running FC4 and not FC5? We've never had a reported problem with FC4. However, as reported by a few users, it seems that FC5 has changed the tail command so it no longer supports the +n notation.

It's possbile there's been an update to FC4 that implemented this change, we'll have to look into it.

Thanks,
Rachel

[enquirer]

Actually, I am running FC5 :oops:
I could not have thought that "tail" syntax could be changed.

But now that I am out of the woods of tail and tar, I ran into another set of problems (these are clearly attributable to FC5). Although Scalix is not supprted on FC5, I was wondering if I could stil install it, because FC5 is the only version currently available to me.
The problems are with the libssl.so.5 and libcrypto.so.5, which are reqired by scalix. FC5 comes with libssl.so.6 and libcrypto.so.6. Am I correct to assume that these libraries are backwards comaptibe?
I made symlinks in /lib to version 6 of the libraries and named then version 5. But, naturally, this did not resolve the dependency problem. Neither did copying the libraries from the FC4 rpm file.
Is there a way to deal with this issue?

Thanks

[ScalixSupport]

Unfortunately FC5 is currently not supported with Scalix (do a search for "fc5", there are various threads discussing the issues). You're going to be better off installing fc4.

Thanks,
Rachel