Greetings,
I found strange behavior with the LB component of our WMS (EMI-WMS). I
able to submit
job to the WMS successfully as well as the WMS able to submit the job
to the CE successfully.
However, WMS fails to provide the status of the job by using
glite-wms-job-status command,
unless I restart the glite-lb-bkserverd service, then i can get the
status, but when i submit
a job once again, then the WMS fails to provide me the status of the
job, unless i restart the
glite-lb-bkserverd service once again.
Here are the software version of the WMS:
glite-jobid-api-c-2.0.3-1.sl5.x86_64
glite-lbjp-common-server-bones-2.1.3-1.sl5.x86_64
glite-jobid-api-cpp-1.1.3-1.sl5.x86_64
glite-lb-common-8.0.6-1.sl5.x86_64
glite-jobid-api-java-1.1.3-6.sl5.noarch
glite-jdl-api-cpp-3.2.6-1.sl5.x86_64
glite-wms-jobsubmission-3.3.2-1.sl5.x86_64
glite-wms-utils-exception-3.2.2-2.sl5.x86_64
glite-wms-matchmaking-3.3.2-1.sl5.x86_64
glite-lb-server-2.2.9-1.sl5.x86_64
glite-lbjp-common-trio-2.1.2-7.sl5.x86_64
glite-ce-cream-client-api-c-1.13.2-3.sl5.x86_64
glite-lbjp-common-db-3.0.3-2.sl5.x86_64
glite-lb-client-5.0.8-1.sl5.x86_64
glite-lb-state-machine-1.2.2-5.sl5.x86_64
glite-lb-utils-2.1.4-1.sl5.x86_64
glite-lb-doc-1.2.9-1.sl5.noarch
glite-initscript-globus-gridftp-1.0.4-1.sl5.noarch
glite-wms-purger-3.3.2-1.sl5.x86_64
glite-wms-configuration-3.3.2-1.sl5.x86_64
glite-wms-helper-3.3.2-0.sl5.x86_64
glite-wms-utils-classad-3.2.2-2.sl5.x86_64
glite-service-discovery-api-c-2.2.3-1.sl5.x86_64
glite-lbjp-common-maildir-2.1.2-7.sl5.x86_64
glite-lbjp-common-log-1.1.2-6.sl5.x86_64
glite-lbjp-common-gsoap-plugin-3.0.2-7.sl5.x86_64
glite-wms-classad_plugin-3.3.1-3.sl5.x86_64
glite-lb-logger-2.2.6-1.sl5.x86_64
glite-lb-ws-interface-3.2.4-1.sl5.noarch
glite-lb-ws-test-1.2.3-1.sl5.x86_64
glite-wms-manager-3.3.1-3.sl5.x86_64
glite-lb-client-java-1.1.6-1.sl5.x86_64
glite-lb-logger-msg-1.0.6-1.sl5.x86_64
glite-lb-yaim-4.3.9-1.sl5.noarch
glite-wms-ism-3.3.2-1.sl5.x86_64
glite-ce-monitor-client-api-c-1.13.2-2.sl5.x86_64
glite-wms-ice-3.3.4-1.sl5.x86_64
glite-yaim-bdii-4.3.9-1.el5.noarch
glite-lbjp-common-gss-3.0.4-1.sl5.x86_64
glite-wms-brokerinfo-3.3.2-1.sl5.x86_64
glite-info-provider-service-1.8.1-2.el5.noarch
glite-px-proxyrenewal-1.3.25-3emi1.sl5.x86_64
glite-wms-wmproxy-3.3.5-1.sl5.x86_64
glite-lbjp-common-jp-interface-2.1.2-7.sl5.x86_64
glite-wms-broker-3.3.1-3.sl5.x86_64
glite-lb-harvester-1.1.6-3.sl5.x86_64
glite-wms-common-3.3.2-0.sl5.x86_64
glite-yaim-core-5.0.2-1.sl5.noarch
glite-yaim-wms-4.1.5-1.sl5.noarch
Any solution?
Regards
|