 |
 |
Hi, Alvise, Thanks for your reply. Is the commend in new version, glite 3.2 - wms? [root@rocwms ~]# rpm -q glite-wms-ice glite-wms-ice-3.1.53-1.slc4 [root@rocwms ~]# rpm -ql glite-wms-ice /opt/glite/bin /opt/glite/bin/glite-wms-ice /opt/glite/bin/glite-wms-ice-proxy-renew /opt/glite/bin/glite-wms-ice-rm /opt/glite/bin/glite-wms-ice-safe /opt/glite/bin/putFL /opt/glite/bin/putFL_cancel /opt/glite/bin/queryDb /opt/glite/bin/queryStats /opt/glite/etc /opt/glite/etc/init.d /opt/glite/etc/init.d/glite-wms-ice And I am trying to install glite3.2 wms, but there is really little information. Can you please give me wiki or guide? Thanks. Cheers, Todd 2012/7/1 PD INFN <[log in to unmask]>: > Il 30/06/12 09.56, Todd Wu ha scritto: > >> Hi, Eric, >> >> I found one thing that I don't really know how to deal. >> In wms, the ice db contains lot of idle jobs: >> >> [https://kek2-ce01.cc.kek.jp:8443/CREAM212683020] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/nN _K7HUlf0osxo2ZAJyoZw] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM262568807] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/WLolaQgej9gVP55UJJReWg] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM366967337] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/RgVj-q0Yg6EK4F2jj4BFzg] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM618201904] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/2bA77oG9qiw0jLpbylqeqA] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM777419072] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/-HTl8IqwQVBgNwJaqlEiig] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM405865634] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/Io2MN1zlRrSVlc_LMw18aQ] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM843291383] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/sw-_lCKJGKZKVMJvw-Y4Ww] >> [https://kek2-ce01.cc.kek.jp:8443/CREAM402567621] [IDLE] >> [https://roclb.grid.sinica.edu.tw:9000/-bCrwCYctdhsU-v_PYwTJA] >> .. balabala >> >> >> And I tried to erase them: >> for i in `cat /root/kek`; do glite-wms-ice-rm -c glite_wms.conf $i ;done >> >> Some of old jobs: >> Sending JobCancel to CREAM for job >> [https://roclb.grid.sinica.edu.tw:9000/WYBt2mGKNxhsZJ-CYRwyjw] -> >> [https://kek2-ce01.cc.kek.jp:8443/ce-cream/services/CREAM2/CREAM835686906] >> *** For job [https://roclb.grid.sinica.edu.tw:9000/WYBt2mGKNxhsZJ-CYRwyjw] >> -> >> [https://kek2-ce01.cc.kek.jp:8443/ce-cream/services/CREAM2/CREAM835686906] >> the proxyfile >> [/var/glite/SandboxDir/WY/https_3a_2f_2froclb.grid.sinica.edu.tw_3a9000_2fWYBt2mGKNxhsZJ-CYRwyjw/user.proxy] >> is not valid: Unable to open the file >> >> [/var/glite/SandboxDir/WY/https_3a_2f_2froclb.grid.sinica.edu.tw_3a9000_2fWYBt2mGKNxhsZJ-CYRwyjw/user.proxy]: >> No such file or directory. Skipping cancellation of this job. >> >> Some of them >> Sending JobCancel to CREAM for job >> [https://roclb.grid.sinica.edu.tw:9000/xcs65A7nvIVfdST5yLd9_g] -> >> [https://kek2-ce01.cc.kek.jp:8443/ce-cream/services/CREAM2/CREAM112645432] >> CANCELLED JOB >> [https://roclb.grid.sinica.edu.tw:9000/xcs65A7nvIVfdST5yLd9_g] >> >> But non of them been cleaned afterword. ICEdb still got the old stuff. >> >> What can I do with this? > > > Hi Todd, > the behaviour you observer is by design: glite-wms-ice-rm just collects jobs > from ICE's DB and uses this information to send JobCancel operations to the > CE. > > If you want to clean your ICE database you've to use the command > glite-wms-ice-db-rm. Its usage is simple: > > glite-wms-ice-db-rm <SINGLE_GRID_JOBID> > > or > > glite-wms-ice-db-rm --from-file <FILE_CONTAINING_A_LIST_OF_GRIDJOBIDS> > > let me know if it solves... > > Alvise > > > >> Cheers, >> Todd >> >> >> 2012/6/29 Todd Wu <[log in to unmask]>: >>> >>> Hi, all, >>> >>> Any one have any idea? >>> >>> Cheers, >>> Todd >>> >>> 2012/6/26 Todd Wu <[log in to unmask]>: >>>> >>>> Hi, Eric, >>>> >>>> No, the problem is still there. >>>> Yes, the job inn log marked done-ok but wms won't update the status as >>>> usual. >>>> >>>> Cheers, >>>> Todd >>>> >>>> 2012/6/25 Eric Frizziero <[log in to unmask]>: >>>>> >>>>> Hi Todd, >>>>> >>>>> from the log file, Awms and Acreamce seem to work fine. All two jobs >>>>> are >>>>> terminated in the state DONE-OK. >>>>> >>>>> Have you solved the update problems? >>>>> >>>>> >>>>> Cheers, >>>>> E r i c. >>>>> >>>>> >>>>> >>>>> On 06/25/2012 12:40 PM, Todd Wu wrote: >>>>>> >>>>>> Hi, Eric, >>>>>> >>>>>> Here is the log, grep two job id result. >>>>>> Also, the CREMACE is: >>>>>> https://kek2-ce01.cc.kek.jp:8443/ce-cream/services >>>>>> >>>>>> Cheers, >>>>>> Todd >>>>>> >>>>>> >>>>>> 2012/6/22 Eric Frizziero<[log in to unmask]>: >>>>>>> >>>>>>> Please, could you provide us the Acreamce log file related to the >>>>>>> submission >>>>>>> of a job by the Awms that is having the update problem? >>>>>>> >>>>>>> Moreover, what's the url of the Acreamce? >>>>>>> >>>>>>> Cheers, >>>>>>> E r i c. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 06/22/2012 11:06 AM, Todd Wu wrote: >>>>>>>> >>>>>>>> Hi, Eric, >>>>>>>> >>>>>>>> Let's say the pair of Acreamce with Awms got update problem. >>>>>>>> But Acreamce to other wms is fine. >>>>>>>> Also, Awms to other creamce is fine. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Todd >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 2012/6/22 Eric Frizziero<[log in to unmask]>: >>>>>>>>> >>>>>>>>> Hi Todd, >>>>>>>>> >>>>>>>>> >>>>>>>>> On 06/22/2012 10:40 AM, Todd Wu wrote: >>>>>>>>>> >>>>>>>>>> Dear all, >>>>>>>>>> >>>>>>>>>> We encountered that wsm can't update job status with creamce. >>>>>>>>>> But with other wms, the status can be updated. >>>>>>>>> >>>>>>>>> Using the same creamce? >>>>>>>>> >>>>>>>>> Could you provide us the urls (wms1, wms2, creamce)? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> E r i c. >>>>>>>>> >>>>>>>>> >>>>>>>>>> We can't find anything on WMS and LB(they installed separately.) >>>>>>>>>> >>>>>>>>>> Any hint s are welcome. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Todd >>>>>>>>>> >>>>>>>>>> >