Greig Alan Cowan wrote:
> Hi John,
>
> Sorry for the delay, I've been at an LHCb meeting all day.
Hi Grieg, no problem.
> What are the contents of the files (and their permissions) in
> /opt/lcg/var/gip/tmp ? Similarly for the plugin and provider
> directories. You should have something like:
>
> [root@srm gip]# ls -l tmp/
> total 12
> -rw-r--r-- 1 edginfo edginfo 3472 Feb 28 22:36
> infoDynamicSE-plugin-dcache.ldif.4869
> -rw-r--r-- 1 edginfo edginfo 3968 Feb 28 22:36
> infoDynamicSE-provider-dcache.ldif.5309
> -rw-r--r-- 1 edginfo edginfo 3007 Feb 28 22:36
> token_info_provider.ldif.4493
/opt/lcg/var/gip/tmp does not exist
> [root@srm gip]# ls -l provider/
> total 0
> lrwxrwxrwx 1 root root 47 Feb 5 2007 infoDynamicSE-provider-dcache ->
> /opt/d-cache/jobs/infoDynamicSE-provider-dcache
> lrwxrwxrwx 1 root root 39 Feb 11 08:31 token_info_provider ->
> /opt/d-cache/gip/token_info_provider.py
lrwxrwxrwx 1 root root 47 Feb 28 14:07 infoDynamicSE-provider-dcache ->
/opt/d-cache/jobs/infoDynamicSE-provider-dcache
this was added by me earlier today. token_info_provider.py does not
exist, nor does /opt/d-cache/gip/
> [root@srm gip]# ls -l plugin/
> total 0
> lrwxrwxrwx 1 root root 45 Aug 16 2007 infoDynamicSE-plugin-dcache ->
> /opt/d-cache/jobs/infoDynamicSE-plugin-dcache
lrwxrwxrwx 1 root root 45 Feb 28 14:07 infoDynamicSE-plugin-dcache ->
/opt/d-cache/jobs/infoDynamicSE-plugin-dcache
This was added by me earlier today.
> The tmp files should contain the same information as is published in the
> information system.
Doesn't exist which might go some way to explaining the problem. Looking
at the packages on the SE there may be yaim and other components missing
that cover the above, I'll have to install them and see if they fare any
better than the current yaim install.
These components were not mentioned on eg
http://www.gridpp.ac.uk/wiki/DCache_Yaim_Install_on_SL4 or the other
sites I used to install the system. Now that I know roughly what to
look for I can find different install guides that do include them. This
fragmentation of documentation is highly frustrating for first-time
installers. I still don't understand why yaim does not pull in the
necessary packages for a particular node-type either or at least
complain they don't exist.
I'm starting to feel that there are mystical and secret black arts to
installing dcache (and glite middleware in general).
John
> Cheers,
> Greig
>
>
>
> On 28/02/08 12:13, John Bland wrote:
>> Hi,
>>
>> The SAM tests for our SE hepgrid5.ph.liv.ac.uk are showing 0 free
>> space and have been since we reinstalled with dcache 1.8 and glite
>> 3.1. After much ferreting about I've found a command that should show
>> the available and used space on the SE,
>> /opt/d-cache/srm/bin/srm-storage-element-info, but running this
>> command just produces the following error:
>>
>> [jbland@hepgrid11 ~]$ /opt/d-cache/srm/bin/srm-storage-element-info
>> https://192.168.178.105/srm/infoProvider1_0.wsdl
>> AxisFault
>> faultCode: {http://xml.apache.org/axis/}Server.NoService
>> faultSubcode:
>> faultString: The AXIS engine could not find a target service to
>> invoke! targetService is infoProvider1_0
>> faultActor:
>> faultNode:
>> faultDetail:
>> {http://xml.apache.org/axis/}hostname:hepgrid5.ph.liv.ac.uk
>>
>> The AXIS engine could not find a target service to invoke!
>> targetService is infoProvider1_0
>> at
>> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>>
>> at
>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>>
>> at
>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
>>
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
>>
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>>
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
>>
>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>> at
>> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>
>> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>> at
>> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>>
>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>> at
>> org.dcache.srm.client.axis1.IInformationProviderStub.getStorageElementInfo(IInformationProviderStub.java:153)
>>
>> at
>> org.dcache.srm.client.InformationProviderClientV1.getStorageElementInfo(InformationProviderClientV1.java:309)
>>
>> at gov.fnal.srm.util.SRMDispatcher.work(SRMDispatcher.java:403)
>> at gov.fnal.srm.util.SRMDispatcher.main(SRMDispatcher.java:372)
>> srm client error: The AXIS engine could not find a target service to
>> invoke! targetService is infoProvider1_0
>> java.lang.RuntimeException: The AXIS engine could not find a target
>> service to invoke! targetService is infoProvider1_0
>> at
>> org.dcache.srm.client.InformationProviderClientV1.getStorageElementInfo(InformationProviderClientV1.java:312)
>>
>> at gov.fnal.srm.util.SRMDispatcher.work(SRMDispatcher.java:403)
>> at gov.fnal.srm.util.SRMDispatcher.main(SRMDispatcher.java:372)
>> Caused by: The AXIS engine could not find a target service to invoke!
>> targetService is infoProvider1_0
>> at
>> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>>
>> at
>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>>
>> at
>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
>>
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
>>
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>>
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>>
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
>>
>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>> at
>> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>
>> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>> at
>> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>>
>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>> at
>> org.dcache.srm.client.axis1.IInformationProviderStub.getStorageElementInfo(IInformationProviderStub.java:153)
>>
>> at
>> org.dcache.srm.client.InformationProviderClientV1.getStorageElementInfo(InformationProviderClientV1.java:309)
>>
>> ... 2 more
>>
>>
>>
>> The infoProvider cell is running on the SE, although I see this in the
>> logs when it is started, about problems creating a socket:
>>
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : messageArrived
>> : LastMess
>> ageEvent (opening gate)
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : CellAdapter :
>> prepareRemo
>> val : waiting for gate to open
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : Clean up
>> called ...
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : InfoExporter:
>> Finalized.
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : InfoExporter:
>> Problems cr
>> eating socket!
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : Done
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : Pinboard not
>> dumped (dump
>> Directory not sp. )
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : CellAdapter :
>> prepareRemo
>> val : done
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) :
>> java.net.SocketException:
>> Socket closed
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : at
>> java.net.Plain
>> SocketImpl.socketAccept(Native Method)
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : at
>> java.net.Plain
>> SocketImpl.accept(PlainSocketImpl.java:384)
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : at
>> java.net.Serve
>> rSocket.implAccept(ServerSocket.java:453)
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : at
>> java.net.Serve
>> rSocket.accept(ServerSocket.java:421)
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : at
>> org.dcache.ser
>> vices.infoCollector.InfoExporter.run(InfoExporter.java:118)
>> 02/28 12:03:34 Cell(InfoCollector@infoProviderDomain) : at
>> java.lang.Thre
>> ad.run(Thread.java:619)
>> Starting BatchCell on /opt/d-cache/config/infoProvider.batch
>> Main thread finished
>>
>>
>> I found some info about edginfo user and the CN used in dcache.kpwd,
>> this is currently set as:
>>
>> mapping
>> "/C=UK/O=eScience/OU=Liverpool/L=CSD/CN=hepgrid5.ph.liv.ac.uk/emailAddres
>> [log in to unmask]" edginfo
>>
>> login edginfo 101 102 / / /
>>
>> /C=UK/O=eScience/OU=Liverpool/L=CSD/CN=hepgrid5.ph.liv.ac.uk/emailAddress
>> [log in to unmask]
>>
>>
>> and the CN matches that used in the host certificate.
>>
>> So, any ideas why the infoProvider is unable to find infoProvider1_0?
>> Is this really why we're reporting 0 for GlueSAStateAvailableSpace and
>> other storage values, or is there something else fundamentally broken
>> (we don't have spacemanager enabled but surely that shouldn't kill the
>> ability to get information)?
>>
>> Thanks,
>>
>> John (rapidly growing weary of dCache tom-foolery)
>>
--
Dr John Bland, Systems Administrator
Room 210, Oliver Lodge
Particle Physics Group, University of Liverpool
Mail: [log in to unmask]
Tel : 0151 794 3396
|