 |
 |
Hi - Our t3 has some very secure firewall settings (which I don't have permission to change), so this sort of stuff has to happen from outside the local network. Further to the "123 could not write the job state file" error below, I changed the permissions on /opt/globus/tmp/gram_job_state to 1777 (which matches those on our other CE which does work). I'll submit another glite-wms-job type job and see what happens. Cheers, Chris On Fri, 27 Nov 2009, Daniela Bauer wrote: > This is what I get from IC (using dteam) > > ************************************************************* > BOOKKEEPING INFORMATION: > Status info for the Job : > https://wmslb00.hep.ph.ic.ac.uk:9000/lBEGIfJc5o_PGXFC_FqQZw > Current Status: Ready > Status Reason: 123 could not write the job state file > Destination: epgr02.ph.bham.ac.uk:2119/jobmanager-lcgpbs-sl5_test > Submitted: Fri Nov 27 09:47:27 2009 GMT > ************************************************************* > Daniela > 2009/11/27 Christopher J.Walker <[log in to unmask]> > >> Stephen Burke wrote: >> >>> Testbed Support for GridPP member institutes >>> >>>> [mailto:[log in to unmask]] On Behalf Of Chris Curtis said: >>>> GRAM Job submission failed because the job manager failed to open stderr >>>> (error code 74) >>>> >>> >>> That's probably a firewall problem, I doubt it's directly related to the >>> error but it may stop you seeing the message. What about if you do it >>> from a local machine? >>> >> >> And I think that's a firewall problem at CERN's end. I had the same problem >> testing to one of our machines - but someone else was able to do the test >> for me without the problem. >> >> Chris >> > > > > -- West 326 Physics and Astronomy University of Birmingham Edgbaston Birmingham B15 2TT (Office) 0121 414 4700 (Mobile) 0798 666 1959