Installation problem in globus toolkit 4.0.8


 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Installation problem in globus toolkit 4.0.8
# 1  
Old 07-04-2010
Installation problem in globus toolkit 4.0.8

I am installing globus toolkit 4.0.8 on ububtu 9.1. When i build gt4.0.8-all-source.... executing,
make | tee installer.log , as mentioned in quick start provided by globus, i got error saying,

Following packages are missing,
pgm_link-globus_ftp_client-ANY-dev version 5.2 is incompatible with globus_gram-job-manager-ANY-src
compile-globus_ftp_client-ANY-dev version 5.2 is incompatible with globus_gram-job-manager-ANY-src


what should i do?
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Ubuntu

Installation problem in globus toolkit 5.0.1

I have installed globus toolkit 5.0.1 on ubuntu 9. All the packages mentioned in quick start guide, like security, gridftp, gram, myproxy. But i don't know how to start web services in globus 5.0.1. There is no help provided in quick start for this. I need WSRF for making grid data mining... (0 Replies)
Discussion started by: naveencse
0 Replies

2. Ubuntu

Globus 5.0.0 installation error in ubuntu 9.1

I am installing globus toolkit 5 on ubuntu, i am getting error regarding openssl build. Unable to build Openssl. I am giving the whole installer.log file below. globus@naveen-laptop:~/gt4.0.6-all-source-installer$ make | tee istaller.log /usr/local/globus//sbin/gpt-build ... (0 Replies)
Discussion started by: naveencse
0 Replies

3. Linux

compatiblité fedora 11 and globus toolkit 4.0.1

hello i search if fedora 11 is compatible with Globus Toolkit 4.0.1.thank's (2 Replies)
Discussion started by: spam255
2 Replies

4. UNIX for Advanced & Expert Users

Globus toolkit WS Gram Build Problem

Dear Sir/Madam We are trying to configure Grid in our computer lab. We have already installed all the required software for configuring the grid. At present we are configuring it for 3 nodes. We are using Fedora 8 OS. We are using Sun Grid Engine (SGE) and Globus Tool Kit for configuring the... (0 Replies)
Discussion started by: garudawar
0 Replies

5. UNIX for Advanced & Expert Users

Globus Toolkit 4

Hello! I'm trying to install the Globus Toolkit 4 on a Fedora 8 system. The instructions I'm using to do so can be found here: Chapter 1. 4.0.x quickstart I'm at the Certificate Authorities point where I am supposed to sign the certificate though, and I'm having a bit of trouble that... (2 Replies)
Discussion started by: Curtor
2 Replies

6. Linux

globus toolkit installation error

i got this error while installing gt4 on fedora core 3. please help root@localhost gt4.0.6-x86_fc_3-installer]# make | tee installer.log cd gpt && OBJECT_MODE=32 ./build_gpt Can't locate Localize.pm in @INC (@INC contains: ./tools /usr/lib/perl5/5.8.5/i386-linux-thread-multi... (0 Replies)
Discussion started by: tushru2004
0 Replies

7. Shell Programming and Scripting

Installation problem

Hi , I have installed a s/w for work tracking (work tracking fecilitator) in linix OS. all my other perl programs are working fine. i have completed the backend part of it but unable to use this application . Please guide me regarding this . I have downloaded the source from... (4 Replies)
Discussion started by: alma
4 Replies
Login or Register to Ask a Question
globus_gram_job_manager_configuration(3)		      globus gram job manager			  globus_gram_job_manager_configuration(3)

NAME
globus_gram_job_manager_configuration - Job Manager Configuration The Job Manager is generally configured using the setup-globus-gram-job- manager setup script. This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file $GLOBUS_LOCATION/etc/globus-job-manager.conf. Configuration File Options -k Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential. -home GLOBUS_LOCATION Set the GLOBUS_LOCATION environment variable to the specified Globus-Location. -target-globus-location GLOBUS_LOCATION Set the GLOBUS_LOCATION environment variable to the execution node's GLOBUS_LOCATION, if different than the GRAM node's GLOBUS_LOCATION -type JOB_MANAGER_TYPE Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is needed. -history PATH Set the path to the directory to store job history files. -cache-location PATH Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available RSL substitutions. -extra-envvars VAR1[=VAL],VAR2,... The Job manager will attempt to get the listed VARs from its environment and set them the same for the job's environment. For example, -extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE -scratch-dir-base PATH Set the default scratch directory root for the job manager. Job-specific scratch directories will be created as a subdirectory of this directory. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available RSL substitutions. If this option is not present in the configuration file, then the job manager will create scratch directories as subdirectories of the user's home directory. -condor-arch ARCH Set the condor architecture for this job manager to be the specified ARCH. This is optional when the job manager type is condor. -condor-os OSNAME Set the condor operating system name for this job manager to be the specified OSNAME. This is optional when the job manager type is condor. -globus-gatekeeper-host HOST Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution. -globus-gatekeeper-port PORT Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution. -globus-gatekeeper-subject SUBJECT Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution. -globus-host-manufacturer MANUFACTURER Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution. -globus-host-cputype CPUTYPE Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution. -globus-host-osname OSNAME Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution. -globus-host-osversion OSVERSION Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution. -globus-tcp-port-range RANGE Set the range of TCP port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_PORT_RANGE environment variable and RSL substitution. -globus-tcp-source-range RANGE Set the range of TCP source port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_SOURCE_RANGE environment variable and RSL substitution. -state-file-dir PATH Set the path to store job manager state files (used for restarting a job manager which fails). If this is not set, then job state files will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state directory. -x509-cert-dir PATH Set the path to the X.509 trusted certificate directory on the job execution hosts. If not present, then the trusted certificate directory used by the job manager (usually set by the Gatekeeper) will be used -seg-module MODULE Use the named module as a way to interact with the scheduler instead of polling for job status. -audit-directory DIRECTORY Store job auditing records in DIRECTORY. This directory should be sticky and group writable but not group readable. Audit records can be uploaded to a database by using the globus-gram-audit command. -globus-toolkit-version VERSION-STRING Use the string VERSION-STRING as the toolkit version in audit records. -enable-syslog Send log messages to the system log. -stdio-log LOG_DIRECTORY Obsolete way to set the directory for writing log messages. Messages will be written to LOG_DIRECTORY/gram_DATE.log. Use -log-pattern instead -log-pattern PATTERN RSL-substituted pattern for naming log files. Possible variables are HOME, LOGNAME, DATE. The -stdio-log is equivalent to -log-pattern /tmp/buildd/gram_.log -log-levels [FATAL|ERROR|WARN|DEBUG|INFO|TRACE] List of log levels to enable site-wide. These may be joined by the '|' character. Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_configuration(3)