Hi All,
I think I'm almost there with cream. All the packages seem to be
installing without any issues now.
When I come to do the yaim configuration I've managed to get it to get
quite far down the road.
Although we will be using SGE, at the moment I'm just doing...
/opt/glite/yaim/bin/yaim -c -s /etc/yaim/site-info.def -n creamCE
... to try to get that to work, then will do this...
/opt/glite/yaim/bin/yaim -c -s /etc/yaim/site-info.def -n creamCE -n
SGE_utils
...to finish things off.
The yaim config / initialisation is failing when it tries to set up a
bdii. I'm not sure if it should be doing this. I've got a seperate
machine set up with the bdii and that is working fine - see result of...
ldapsearch -x -H ldap://grid-bdii.hpc.susx.ac.uk:2170 -b
mds-vo-name=UKI-SOUTHGRID-SUSX,o=grid
...). I'm confused as I wasn't expecting it to try to set up a bdii on
the cream host as well. Presumably there's an issue with my site-info.def.
I'm attaching the yaimlog for your perusal. Does anyone have any hints
on where to go from here?
Regards,
Emyr
INFO: Using site configuration file: /etc/yaim/site-info.def
INFO:
###################################################################
. /'.-. ')
. yA,-"-,( ,m,:/ ) .oo. oo o ooo o. .oo
. / .-Y a a Y-. 8. .8' 8'8. 8 8b d'8
. / ~ ~ / 8' .8oo88. 8 8 8' 8
. (_/ '====' 8 .8' 8. 8 8 Y 8
. Y,-''-,Yy,-.,/ o8o o8o o88o o8o o8o o8o
. I_))_) I_))_)
current working directory: /root
site-info.def date: Nov 8 14:10 /etc/yaim/site-info.def
yaim command: -c -s /etc/yaim/site-info.def -n creamCE
log file: /opt/glite/yaim/bin/../log/yaimlog
Tue Nov 8 15:51:47 GMT 2011 : /opt/glite/yaim/bin/yaim
Installed YAIM versions:
glite-yaim-core 4.0.14-1
glite-yaim-cream-ce 4.1.2-0
glite-yaim-sge-utils 4.1.1-6
####################################################################
INFO: The default location of the grid-env.(c)sh files will be: /opt/glite/etc/profile.d
INFO: Sourcing the utilities in /opt/glite/yaim/functions/utils
INFO: Detecting environment
INFO: Executing function: config_cream_stop_check
INFO: Executing function: config_cream_clean_check
INFO: Executing function: config_cream_db_check
INFO: Executing function: config_add_pool_env_check
INFO: Executing function: config_host_certs_check
INFO: Executing function: config_vomsdir_check
INFO: Executing function: config_vomses_check
INFO: Executing function: config_users_check
INFO: Executing function: config_edgusers_check
INFO: Executing function: config_cream_glexec_user_check
INFO: Executing function: config_cream_clean_sudoers_check
INFO: Executing function: config_cream_sudoers_check
INFO: Executing function: config_secure_tomcat_check
INFO: Executing function: config_vomsmap_check
INFO: Executing function: config_globus_clients_check
INFO: Executing function: config_rgma_client_check
INFO: Executing function: config_lcas_lcmaps_gt4_check
INFO: Executing function: config_globus_gridftp_check
INFO: Executing function: config_cream_glexec_check
INFO: Executing function: config_cream_blah_check
INFO: Executing function: config_cream_ce_check
INFO: Executing function: config_cream_logrotation_check
INFO: Executing function: config_cream_gip_check
INFO: Executing function: config_gip_scheduler_plugin_check
INFO: Executing function: config_gip_vo_tag_check
INFO: Executing function: config_info_service_cream_ce_check
INFO: Executing function: config_info_service_cemon_check
INFO: Executing function: config_cream_cemon_check
INFO: Executing function: config_cream_gliteservices_check
INFO: Executing function: config_cream_locallogger_check
INFO: Executing function: config_glite_locallogger_check
INFO: Executing function: config_bdii_only_check
INFO: Executing function: config_cream_stop_setenv
INFO: Executing function: config_cream_stop
INFO: Stopping tomcat
Stopping tomcat5: [ OK ]
INFO: blah not running
INFO: lb processes not running
INFO: Executing function: config_cream_clean_setenv
INFO: Executing function: config_cream_clean
INFO: Executing function: config_cream_db_setenv
INFO: Executing function: config_cream_db
The database version requested by cream service is 2.4
The version retrieved from the creamdb database is 2.4
The creamdb database is synchronized with the one requested by cream service
The database version requested by cream service is 2.4
The version retrieved from the delegationdb database is 2.4
The delegationdb database is synchronized with the one requested by cream service
INFO: Executing function: config_add_pool_env_setenv
INFO: Executing function: config_add_pool_env
INFO: Executing function: config_ldconf
INFO: Executing function: config_sysconfig_edg
INFO: Executing function: config_host_certs
INFO: Executing function: config_crl
INFO: Executing function: config_vomsdir_setenv
INFO: Executing function: config_vomsdir
INFO: Executing function: config_vomses
INFO: Executing function: config_users
INFO: User configuration is disabled. YAIM won't configure the users in /etc/yaim/users.conf
INFO: Please, be aware the users must exist in the system for succesful configuration
INFO: Executing function: config_edgusers
INFO: User configuration is disabled. YAIM won't configure the users in /opt/glite/yaim/examples/edgusers.conf
INFO: Please, be aware the users must exist in the system for succesful configuration
INFO: Executing function: config_cream_glexec_user_setenv
INFO: Executing function: config_cream_glexec_user
INFO: CONFIG_USERS is set to no
WARNING: CONFIG_USERS is set to 'no'. User glexec and group glexec must exist in your system
INFO: Executing function: config_cream_clean_sudoers_setenv
INFO: Executing function: config_cream_clean_sudoers
INFO: /etc/sudoers file already clean. Probably installation from scratch
INFO: Executing function: config_cream_sudoers_setenv
INFO: Executing function: config_cream_sudoers
INFO: Installed sudo version: 1.7.2
INFO: Executing function: config_secure_tomcat_setenv
INFO: Executing function: config_secure_tomcat
INFO: Check that java is installed
INFO: Check that tomcat is installed
INFO: Stop tomcat in case it's running
Stopping tomcat5: INFO: Copying hostcert to /etc/grid-security/tomcat-cert.pem for tomcat:root......
INFO: Copying hostkey to /etc/grid-security/tomcat-key.pem for tomcat:root...
INFO: Configuring /etc/tomcat5/server.xml...
INFO: Copying trustmanager deps to tomcat server lib directory..
INFO: Defining JAVA_HOME in the Tomcat configuration file
INFO: Starting Tomcat
Starting tomcat5: [ OK ]
INFO: Executing function: config_vomsmap_setenv
INFO: Executing function: config_vomsmap
INFO: Creating grid-map directory in /etc/grid-security/gridmapdir
INFO: Creating voms grid-map file in /etc/grid-security/voms-grid-mapfile
INFO: Creating voms groupmap file in /etc/grid-security/groupmapfile
WARNING: VO 'ATLAS' not found in /tmp/yaim.h18448
WARNING: VO 'SNOPLUS.SNOLAB.CA' not found in /tmp/yaim.h18448
INFO: Copying the /etc/grid-security/voms-grid-mapfile in the standard location /etc/grid-security/grid-mapfile
INFO: Executing function: config_globus_clients_setenv
INFO: Executing function: config_globus_clients
INFO: Configure the globus service
setup-tmpdirs: creating ./config.status
config.status: creating globus-script-initializer
config.status: creating Paths.pm
creating globus-sh-tools-vars.sh
creating globus-script-initializer
creating Globus::Core::Paths
checking globus-hostname
Done
INFO: Executing function: config_rgma_client_setenv
INFO: Executing function: config_rgma_client
INFO: YAIM has detected the OS is SL5. The rgma client is no longer configured in SL5.
INFO: Executing function: config_lcas_lcmaps_gt4_setenv
INFO: Executing function: config_lcas_lcmaps_gt4
INFO: Creating LCAS_DB_FILE in /opt/glite/etc/lcas/lcas.db
INFO: Creating LCMAPS_DB_FILE in /opt/glite/etc/lcmaps/lcmaps.db
INFO: Executing function: config_globus_gridftp_setenv
INFO: Executing function: config_globus_gridftp
INFO: Starting gridftp service :
Shutting down globus-gridftp-server: [ OK ]
Starting globus-gridftp-server[ OK ]
INFO: Executing function: config_cream_glexec_setenv
INFO: Executing function: config_cream_glexec
INFO: Executing function: config_cream_blah_setenv
INFO: Executing function: config_cream_blah
INFO: BATCH SYSTEM = sge. Does not execute config_cream_blah!
INFO: Executing function: config_cream_ce_setenv
INFO: Executing function: config_cream_ce
Stopping tomcat5: [ OK ]
Starting tomcat5: [ OK ]
INFO: Executing function: config_cream_logrotation_setenv
INFO: Executing function: config_cream_logrotation
INFO: Executing function: config_gip_only
INFO: Executing function: config_cream_gip_setenv
INFO: Executing function: config_cream_gip
INFO: Executing function: config_gip_scheduler_plugin_setenv
INFO: Executing function: config_gip_scheduler_plugin
INFO: Executing function: config_cream_gip_software_plugin
INFO: Executing function: config_gip_vo_tag
INFO: Executing function: config_gip_service_release
INFO: Executing function: config_info_service_cream_ce_setenv
INFO: Executing function: config_info_service_cream_ce
INFO: Executing function: config_info_service_cemon_setenv
INFO: Executing function: config_info_service_cemon
INFO: Executing function: config_cream_cemon_setenv
INFO: Executing function: config_cream_cemon
INFO: Executing function: config_cream_gliteservices_setenv
INFO: Executing function: config_cream_gliteservices
INFO: Executing function: config_cream_locallogger_setenv
INFO: Executing function: config_cream_locallogger
INFO: Executing function: config_glite_locallogger_setenv
INFO: Executing function: config_glite_locallogger
INFO: The workaround for bug 22389 already exists
Stopping glite-lb-logd ... not running
Stopping glite-lb-interlogd ... not running
Starting glite-lb-logd ...This is LocalLogger, part of Workload Management System in EU DataGrid & EGEE.
done
Starting glite-lb-interlogd ... done
INFO: Executing function: config_glite_initd
INFO: Executing function: config_bdii_only
Stopping BDII: BDII already stopped
Starting BDII slapd: [ FAILED ]
/usr/sbin/slapd -f /etc/bdii/bdii-slapd.conf -h ldap://0.0.0.0:2170 -u edguser -d 256
ERROR: Error during the execution of function: config_bdii_only
[ FAILED ]
ERROR: Error during the configuration.Exiting.
ERROR: One of the functions returned with error without specifying its nature !
|
