Closed sgenie68 closed 13 years ago
If you submit the exact same job using a local input file, it works? Can you please confirm?
Affirm - if you submit with the local file, it works staright after the failed submission.
Sorry closed it accidently.
Just done the submission again to double-check - failed with DF but worked with local file.
Markus, can you take a closer look at this?
Nick, Yuriy, can you confirm this issue?
I can't reproduce it.
Gene, can you provide a script that reliably fails?
The setup is very simple (and I tried it from both other user' and mine account):
it throws. If I use attach testMCMC.xml (local file) - everything works fine
Can you try
grid://groups/nz/nesi/test... ? Groups should be lowercase.
Hm. Now I got the error as well. Doesn't happen everytime though... Strange...
I'll try lower case but this is what the autocomplete gives. Also, when you do gls, you have to be simple: gls /nz/nesi - can we somehow make them the same?
Yeah, I'd like to get rid of gls altogether and only use ls (there's a ticket about that somewhere). Autocomplete for gls is borked, I re-wrote it (not ready yet) and it'll allow proper autocompletion for remote files, not just for group fs like the current one...
just tried lower case groups - failed as well.
weird. now print jobs started barfing....
Ok, this seems to be one of the things.
After a quick and dirty test session, it seems somehow connected to the load of the machine where the backend is running. But I couldn't reproduce it at all. At some stage I could submit 30 jobs in a row successfully, then one failed (without anything else running on the machine) and then 15 or so worked fine again.
Not quite sure how to proceed on this. I guess we need some kind of controlled test environment, but I have no idea how to do that.
Anybody got an idea?
Markus did ls in the home dir used to show grid:// ? I can't recall and it may be my imagination ; )
No, it should not show grid:// when doing an ls.
It would, however, show grid:// as an option when you do tab-completion (since it's always an option...)
Should we close this and #11 and combine it with #11 into a new ticket, something like "Gridftp testing framework". Which would belong in the Grisu issue tracker (or maybe even in the bestgrid jira, since it probably is an issue with underlying gridftp servers, not Grisu itself -- not 100% sure about that though), btw. I think those 2 tickets are of a more fundamental type. Also, way too much work to be able to fix them for this next milestone...
Sure, that sounds like a good plan. @smas036 to log?
When I try submit a job with attached file from DF, submission fails:
command failed. Either connection to server failed, or this is gricli bug. Please send /home/genie/.grisu.beta/gricli.debug to eresearch-admin@auckland.ac.nz together with description of what triggered the problem