Does /globus/bin/ssh.d/ssh-keygen exist? It sounds like the build of
gsi_openssh failed. Sadly it sometimes fails but does not manage to
generate an error exit value, so the build continues. You can either
look at your build log, or do a
./configure --prefix=$GLOBUS_LOCATION --with-buildopts="-force -verbose"
make gsi_openssh-only
to get the build log again. It could be that your zlib library is too
old, maybe.
Charles
On Nov 5, 2008, at 1:17 PM, Lourenço wrote:
Hallo!
I got a similar error.
I'm using:
- Linux distribution: Ubuntu 8.04 (/etc/debian_version: lenny/sid)
- Linux Kernel version: 2.6.24 (uname -a: Linux tkt 2.6.24-21-generic
#1 SMP Tue Oct 21 23:43:45 UTC 2008 i686 GNU/Linux)
- Globus installer: `Debian Etch Binary Installer' Toolkit version
4.2.1.
- Quickstart tutorial:
http://www.globus.org/toolkit/docs/4.2/4.2.1/admin/quickstart/
I already installed Globus. But, there were 1 ERROR and 1 WARNING:
ERROR: Unable to execute /globus//bin/ssh.d/ssh-keygen -t rsa1 -f
/globus//etc/ssh/ssh_host_key -N "": No such file or directory
..Done
WARNING: The following packages were not set up correctly:
gsi_openssh_setup-noflavor-pgm
However, now I'm trying to set up security. As described at:
http://www.globus.org/toolkit/docs/4.2/4.2.1/admin/quickstart/#q-security
I already tried to do: GLOBUS_SH_TMP=`pwd` but the same error
continues.
This is the output I got:
[EMAIL PROTECTED]:~/grid/globus/gt4.2.1-x86_deb_4.0-installer$ perl gt-
server-ca.pl -y
Setting up /globus/
Using password from /home/globus/.globus/.simplecapass
Creating a new simpleCA, logging to gt-server-ca.log...setup-simple-ca
failed. See gt-server-ca.log for details.
This is the content of gt-server-ca.log:
###### begin: gt-server-ca.log ######
C e r t i f i c a t e A u t h o r i t y S e t u p
This script will setup a Certificate Authority for signing Globus
users certificates. It will also generate a simple CA package
that can be distributed to the users of the CA.
The CA information about the certificates it distributes will
be kept in:
/home/globus/.globus/simpleCA/
The unique subject name for this CA is:
cn=Globus Simple CA, ou=simpleCA-tkt, ou=GlobusTest, o=Grid
creating CA config package...done.
A self-signed certificate has been generated
for the Certificate Authority with the subject:
/O=Grid/OU=GlobusTest/OU=simpleCA-tkt/CN=Globus Simple CA
If this is invalid, rerun this script
/globus//setup/globus/setup-simple-ca
and enter the appropriate fields.
-------------------------------------------------------------------
The private key of the CA is stored in
/home/globus/.globus/simpleCA//private/cakey.pem
The public CA certificate is stored in /home/globus/.globus/
simpleCA//cacert.pem
The distribution package built for this CA is stored in
/home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
This file must be distributed to any host wishing to request
certificates from this CA.
CA setup complete.
The following commands will now be run to setup the security
configuration files for this CA:
$GLOBUS_LOCATION/sbin/gpt-build
/home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
$GLOBUS_LOCATION/sbin/gpt-postinstall
-------------------------------------------------------------------
ERROR: could not run build command: /globus//sbin/gpt-build -force
/home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
###### end: gt-server-ca.log ######
Variables at /globus/var/lib/perl/Grid/GPT/LocalEnv.pm are correctly
specified.
(...)
my %locations = (
gtar => "/bin/tar",
gzip => "/bin/gzip",
gunzip => "/bin/gunzip",
gmake => "/usr/bin/make",
perl => "/usr/bin/perl",
rpm => "Not Available",
rpmbuild => "Not Available",
);
(...)
I just searched this error in the `gt-user' list, but no possible
solutions listed could solve my case.
Bellow, I post some information that I think could help someone
identify what caused such error.
$ ls -l /globus/sbin/gpt-build
-rwxr-xr-x 1 globus globus 25116 2008-11-05 15:53 /globus/sbin/gpt-
build
$ ls -l /home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
-rw-r--r-- 1 globus globus 213338 2008-11-05 16:42
/home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
$ /globus/sbin/gpt-build -force
/home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
/home/globus/.globus/simpleCA//
globus_simple_ca_8ed2d9a2_setup-0.20.tar.gz
could not be untarred:512
Died at /globus//lib/perl/Grid/GPT/PkgMngmt/ExpandSource.pm line 42.
$ ls -ld /home/globus/grid/globus/gt4.2.1-x86_deb_4.0-installer/BUILD
drwxr-xr-x 3 globus globus 4096 2008-11-05 15:07
/home/globus/grid/globus/gt4.2.1-x86_deb_4.0-installer/BUILD
$ df -h /tmp/
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 288G 5.5G 268G 3% /
- Does anyone know what I can do to solve such error?
Thank in advance!
-- Lourenço
2008/2/6 Charles Bacon <[EMAIL PROTECTED]>:
I believe this bug was fixed in the GT4.0.5 release. On some
systems gunzip
--version returns "gunzip 1.3.5", and on some it returns "gzip
1.3.5". The
logic in GPT's Localize.pm (that creates LocalEnv.pm) has been
fixed to
accept either.
Glad we could get it fixed!
Charles
On Feb 5, 2008, at 10:10 PM, Mikko Vilenius wrote:
I found the problem and also the solution. "Thank you" goes to Mr.
Charles Bacon for pointing me to the right direction.
The file $GLOBUS_LOCATION/var/lib/perl/Grid/GPT/LocalEnv.pm defines
locations for gtar, gzip, etc.
Gunzip was listed as "NOT_DEFINED" or something like that and
therefore
the file globus_simple_ca_xxxxxxxx_setup-0.19.tar.gz could not be
unzipped. Editing the correct path on the file LocalEnv.pm to gunzip
solved the problem.
Thank you,
Mikko Vilenius
