Hi Muhammad,
I do not see any problem:
dorigoa@cream-08 14:34:22 ~>glite-wms-job-status https://lb.biruni.upm.my:9000/f7-MZziiHzFooLQWywdavw
*** Warning: Unable to retrieve the status for: https://lb.biruni.upm.my:9000/f7-MZziiHzFooLQWywdavw
Operation not permitted - matching jobs found but authorization failed
So apparently the hostname has been resolved (even if I do not have authz).
(my UI is a SL6_64)
Alvise
Il giorno 23/ago/2013, alle ore 03:49, Muhammad Farhan SJAUGI ha scritto:
> Hi,
>
> I just upgraded my EMI UI to EMI 3, however when I tried to check my job status
>
> by using glite-wms-job-status command, it gave me this error:
>
>
> $ glite-wms-job-status -i jid
>
> ------------------------------------------------------------------
> 1 : https://lb.biruni.upm.my:9000/8WNScI_YwjDAHfAWnJi5ow
> 2 : https://lb.biruni.upm.my:9000/VvTiNr6V5c8P1PMI5HhNYg
> 3 : https://lb.biruni.upm.my:9000/Y-N5L35SBG4KSIgvMWazhA
> 4 : https://lb.biruni.upm.my:9000/f7-MZziiHzFooLQWywdavw
> a : all
> q : quit
> ------------------------------------------------------------------
>
> Choose one or more jobId(s) in the list - [1-4]all:4
>
>
> *** Warning: Unable to retrieve the status for:
> https://lb.biruni.upm.my:9000/f7-MZziiHzFooLQWywdavw
>
> DNS resolver error - edg_wll_gss_connect()
>
>
> I can confirm that the node able to resolve both wms and lb domain name:
>
> $ host wms.biruni.upm.my
> wms.biruni.upm.my has address 119.40.121.5
> $ host 119.40.121.5
> 5.121.40.119.in-addr.arpa domain name pointer wms.biruni.upm.my.
> $ host lb.biruni.upm.my
> lb.biruni.upm.my has address 119.40.121.12
> $ host 119.40.121.12
> 12.121.40.119.in-addr.arpa domain name pointer lb.biruni.upm.my.
>
> Below is the software version that I installed:
>
> emi-resource-information-service-1.0.3-1.el5
> emi.saga-adapter.isn-common-1.0.1-3.sl5
> emi.saga-adapter.sd-cpp-1.0.4-1.sl5
> emi-release-3.0.0-2.el5
> emi-ui-3.0.2-1.el5
> emi.saga-adapter.isn-cpp-1.0.3-1.sl5
> emi.saga-adapter.context-cpp-1.0.2-3.sl5
> emi-version-3.5.0-1.el5
> emi.amga.amga-cli-2.4.0-1.sl5
> axis2-1.6.1-1.emi
> emi-bdii-site-1.0.1-1.el5
> emi-trustmanager-axis-2.0.2-1.sl5
> unicore-hila-emi-es-2.4.1-1.sl5
> glite-service-discovery-api-c-2.2.3-1.sl5
> glite-info-provider-ldap-1.4.5-1.el5
> glite-yaim-clients-5.2.0-1.sl5
> glite-ce-common-java-1.15.2-1.sl5
> glite-lbjp-common-gss-3.2.13-1.el5
> glite-lb-client-progs-6.0.7-1.el5
> glite-wms-wmproxy-api-python-3.4.0-4.sl5
> glite-lbjp-common-trio-2.3.10-1.el5
> glite-ce-cream-client-api-c-1.15.2-2.el5
> glite-wms-ui-commands-3.5.1-1.sl5
> glite-apel-publisher-2.0.16-1.sl5
> glite-wms-utils-exception-3.4.2-2.el5
> glite-yaim-core-5.1.2-1.sl5
> glite-wms-brokerinfo-access-lib-3.5.0-3.sl5
> glite-lb-client-6.0.7-1.el5
> glite-ce-cream-cli-1.15.2-2.el5
> glite-info-static-0.2.0-1.el5
> glite-apel-core-2.0.14-5.sl5
> glite-jobid-api-c-2.2.10-1.el5
> glite-wms-utils-classad-3.4.2-2.el5
> glite-info-provider-service-1.13.1-1.el5
> glite-yaim-bdii-4.3.14-1.el5
> glite-lbjp-common-gsoap-plugin-3.2.9-1.el5
> glite-ce-monitor-cli-1.15.2-2.el5
> glite-jdl-api-cpp-3.4.2-2.el5
> glite-ce-monitor-client-api-c-1.15.2-2.el5
> glite-wms-wmproxy-api-cpp-3.5.0-3.sl5
> glite-info-site-0.4.0-1.el5
> glite-apel-yaim-1.0.2-4.sl5
> glite-wms-wmproxy-api-java-3.4.0-4.sl5
> glite-wms-brokerinfo-access-3.5.0-3.sl5
> glite-lb-common-9.0.7-1.el5
> glite-wms-ui-api-python-3.5.0-3.sl5
> c-ares-1.6.0-5.el5
> gridsite-libs-2.1.2-1.el5
> gridsite-commands-2.1.2-1.el5
> gridsite-compat1.7-1.7.27-1.el5
> gridsite-service-clients-2.1.2-1.el5
>
>
> Any ideas how to fix it?
>
> Regards
>
>
> --
> Muhammad Farhan Sjaugi, S.Kom. M.Sc
> [log in to unmask]
|