[NLPL Task Force (A)] No more available loop devices, try increasing 'max loop devices' in singularity.conf

[Stephan Oepen]

hi ali,

i believe we should have no shortage of computing resources (cpu hours) on
the NLPL account these days.  you can inspect that using the cost(1)
command-line tool.

the error message sounds more as if there is a technical issue related to
singularity containers; possibly, there are just too many containers
currently in use.  i will forward your query to the system administrators
and copy you.

out of curiosity, what do you run in singularity? is it something we could
make available as part of the common NLPL software modules, i.e. avoiding
the container overhead?

best wishes, oe



On Mon, 15 Apr 2019 at 14:47 Ali Basirat <ali.basirat at lingfil.uu.se> wrote:

> Hi Stephan,
>
>
> I am Ali Basirat, working with Joakim Nivre on the parsing part of the
> NLPL project. I wonder if you can help me with the following error I have
> received a couple of days ago. When submitting new jobs to the Abel cluster
> I receive "No more available loop devices, try increasing 'max loop
> devices' in singularity.conf". I guess this is related to the lack of
> available resources associated with our project.
>
> Thanks a lot for your support!
>
> Bests,
> Ali
>
>
>
>
>
>
>
>
>
> När du har kontakt med oss på Uppsala universitet med e-post så innebär
> det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör
> det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/
>
> E-mailing Uppsala University means that we will process your personal
> data. For more information on how this is performed, please read here:
> http://www.uu.se/en/about-uu/data-protection-policy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlpl.eu/archives/infrastructure/attachments/20190415/a7c0a663/attachment.htm>