[NLPL Task Force (A)] trickle problem

[Stephan Oepen]

hi asad,

there should be a log file from the trickle shell script in your home
directory.  does that reveal any more information?  if not that, what
happens if you take just one line from your job file and submit that
interactively from the command line?

looking at our current allocation, i wonder whether we may in fact
just be out of hours (again) on Abel.  there are only four more weeks
until the start of the new allocation period, but i can probably
request a 'bonus' allocation for this period.  can you estimate how
much more computing you expect to do before the end of the month?

ps: to inform yourself about how your jobs are 'billed' against our
allocation, take a look at the cost(1) command on Abel.

best wishes, oe


On Tue, Aug 27, 2019 at 11:31 AM Asad Basheer Sayeed <asad.sayeed at gu.se> wrote:
>
> Hi,
>
> I'm getting sbatch failures from a running trickle (which Stephan showed
> me to use), what might the problem be?
>
> [19-08-27 11:27:12] trickle[431]: 312 jobs; 240 running;trickle:
> sbatch(1) failure; exit.
>
>   0 new.
> [19-08-27 11:27:42] trickle[431]: 312 jobs; 240 running;trickle:
> sbatch(1) failure; exit.
>   0 new.
> [19-08-27 11:28:13] trickle[431]: 312 jobs; 240 running;trickle:
> sbatch(1) failure; exit.
>   0 new.
>
> The command was:
>
> while true; do /projects/nlpl/operation/tools/trickle --limit 370
> joblist6.txt ; sleep 30; done
>
> What's wrong with it? I pushed 2500 jobs earlier through it mostly
> successfully.  I did increase the clock time to 25h because a handful of
> my jobs were timing out.
>
> Yours,
> --Asad.
>
>