On 09/11/11 09:23, Sam Skipsey wrote:
>
>
> On 8 November 2011 17:07, emyr.james <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> __
> On 08/11/11 16:30, Daniela Bauer wrote:
>> Hi Emyr,
>>
>>
>>> /opt/glite/yaim/bin/yaim -c -s /etc/yaim/site-info.def -n creamCE -n
>>> SGE_utils
>> You need to do this from the beginning. As far as know, you need to
>> make all modules simultaneously for it to work.
>
> Actually, I don't think I need the -n SGE_utils on the cream node.
> SGE isn't installed on this node, it's installed on the cluster head
> node. It complains about SGE not being installed when I add that so
> I guess I shouldn't have it.
>
>
> On the contrary. All of the installation and configuration documents
> (see, eg,
> https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320#The_SGE_batch_system
> for the gLite flavour instructions). explicitly note you need
> SGE_utils on the node with CREAM installed.
> Your CREAM CE node needs to have a BATCH_SERVER variable set in
> site-info.def pointing at the Qmaster, and needs to have the SGE client
> tools installed and configured (a CREAM CE, or indeed any CE, must be a
> submit host for the SGE batch system, with the SGE configuration that
> this implies - this is what the SGE_utils package complains about.)
Another warning.
You should almost certainly set:
SGE_SHARED_INSTALL=yes
The default is for yaim to configure your batch system - which is likely
to break it.
Chris
> Sam
>
>
>
> My understanding is I'll need to install the relevant glite things
> on the head node so that this command will work...
>
> /opt/glite/yaim/bin/yaim -r -s <site-info.def> -n creamCE -f
> config_cream_blparser
>
> So hopefully...
>
> /opt/glite/yaim/bin/yaim -c -s /etc/yaim/site-info.def -n creamCE
>
> ...on the cream node and....
>
> /opt/glite/yaim/bin/yaim -r -s /etc/yaim/site-info.def -n creamCE -f
> config_cream_blparser
>
> ....on the cluster head node should get this all working provided I
> have the right things in site-info.def ?
>
>
>>
>>> ...). 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.
>> It's not trying to set up a site bdii, it's trying to setup a
>> resource
>> bdii (which feeds into your site bdii).
>> I've not looked at the UMD bdii, but generally you need to tell site
>> bdii where to get their information from, something like this (in the
>> site bdii):
>>
>> BDII_REGIONS="BDII TOP CE1 CE2 CE3 CE4 SE WMS1 WMS2 LB1 LB2 LFC" #
>> list of the services provided by the site
>> [snip]
>> BDII_CE4_URL="ldap://ceprod06.grid.hep.ph.ic.ac.uk:2170/mds-vo-name=resource,o=grid"
>>
>>
>> etc
>>
>> Do you have SE linux turned on ?
>>
>
> Yes. I did...
>
> echo 0 >/selinux/enforce
>
> ... then tried again and the same thing happens. I had a look at the
> files in /etc/bdii...
>
>
> [root@grid-cream-01 bdii]# ls -l
> total 32
> -rw-r--r-- 1 root root 3970 Jun 7 10:23 BDII.schema
> -rw-r----- 1 ldap ldap 2819 Nov 8 15:25 bdii-slapd.conf
> -rw-r----- 1 ldap ldap 3273 Jun 7 10:23 bdii-top-slapd.conf
> -rw-r--r-- 1 root root 1010 Jun 7 10:23 DB_CONFIG
>
> ...I did a chmod to make everything world readable, and now it stops
> with the following...
>
> 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
> Warning: stale /opt/glite/var/cream_lb/glite-lb-interlogd.pid for
> glite-lb-interlogd
> Warning: stale /tmp/interlogger.sock for glite-lb-interlogd
> Starting glite-lb-interlogd ... done
> INFO: Executing function: config_glite_initd
> INFO: Executing function: config_bdii_only
> Stopping BDII update process: [ OK ]
> Stopping BDII slapd: [ OK ]
> Starting BDII slapd: Traceback (most recent call last):
> File "/usr/sbin/bdii-update", line 936, in ?
> create_daemon(config['BDII_LOG_FILE'])
> File "/usr/sbin/bdii-update", line 173, in create_daemon
> e = os.open(log_file, os.O_WRONLY | os.O_APPEND | os.O_CREAT, 0644)
> OSError: [Errno 13] Permission denied: '/var/log/bdii/bdii-update.log'
> [ OK ]
> BDII update process failed to startStarting BDII update pro[FAILED]
> ERROR: Error during the execution of function: config_bdii_only
> ERROR: Error during the
> configuration.Exiting. [FAILED]
> ERROR: One of the functions returned with error without
> specifying its nature !
>
> I had a look at the bdii directory in /var/log and it's listed as
> follows...
>
> drwxr-xr-x 2 ldap ldap 4096 Jun 7 10:23 bdii
>
> The fact that I had to chmod files in/etc/bdii to get that step to
> work and that now it's failing with another permissions issue
> suggest to me that I may not have my users and groups set up right ?
>
>
>
>
>> Cheers,
>> Daniela
>>
>>> I'm attaching the yaimlog for your perusal. Does anyone have any
>>> hints on
>>> where to go from here?
>>>
>>> Regards,
>>> Emyr
>>>
>>>
>>
>>
>
>
|