Hello Hanna,
> I recently encountered two (related) problems with GC3Pie.
Lucky you :-) I have encountered many more ;-)
> Sometimes, a job gets stuck in the terminating stage, and keeps on saving
> its output on my local computer, resulting in many folders with the same
> files in it (problem 1). I have no idea why this happens, it seems to
> happen randomly.
The only reason I can imagine is that the downloading is considered
"unsuccessful" for some reason, so it is attempted again during the next
cycle, and then again, and so on.
It would help to see if the DEBUG level logs have something to say.
Can you collect the DEBUG logs from such a problem situation?
To get the DEBUG logs: look into file `$HOME/.gc3/debug.log` or run
your session-based script adding the `-vvvv` option and save the console
output. For instance::
./my-script.py -s session -vvvv 2>&1 | tee debug.log
> If I then manually kill these jobs ("gselect -s SessionName --state
> TERMINATING | xargs gkill -s SessionName"), the jobs are killed and get the
> label 'failed'. The run stops saving output from these jobs to the local
> computer. However, these jobs are not removed from the cloud and occupy
> some of the chores. Therefore the progress of the session slows down a lot
> because it can not make full use of the available resources (problem 2).
Can you please post the output of `gcloud list --verbose` after killing
the problem jobs?
If no instance is running any job, it is safe to delete them all (e.g.,
via `gcloud terminate` or via the Science Cloud web interface) and then
restart your GC3Pie session-based script.
Ciao,
R
--
Riccardo Murri / Email: riccardo.mu...@gmail.com / Tel.: +41 77 458 98 32
--
You received this message because you are subscribed to the Google Groups
"gc3pie" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gc3pie+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
