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

[Ali Basirat]

Thanks, Stephan!


I will try the newer version on Dynet installed as an nlpl module and will update you with the result.


Bests,

Ali

________________________________
From: Stephan Oepen <oe at ifi.uio.no>
Sent: Tuesday, April 16, 2019 10:33:41 PM
To: Ali Basirat
Cc: infrastructure
Subject: Re: No more available loop devices, try increasing 'max loop devices' in singularity.conf

hi again, ali,

yes, of course, i had forgotten that the UUParser module internally
builds on the containerized DyNet installation on Abel.  as of earlier
this year, there also is a non-containerized installation of DyNet 1.0
available as 'nlpl-dynet'.  i wonder how difficult it would be to make
the UUParser module run on top of this version of DyNet instead of the
older one inside a singularity container?

this week is dead-quiet at UiO, so it is quite possible we will not
hear back on my query to the system administrators until after the
easter break.  i would be glad if you gave the non-containerized
'nlpl-dynet' module a shot?  before too long, i am hoping we can
eliminate dependencies on those older singularity modules ...

best wishes, oe

On Tue, Apr 16, 2019 at 3:01 AM Ali Basirat <ali.basirat at lingfil.uu.se> wrote:
>
> Hi Stephan,
>
>
>
> Thanks for following up this issue!
>
>
>
> Regrading the singularity, I am not familiar with singularity and I have no idea about what we are running in singularity. I have been running our parser installed as part of NLPL. The parser uses a python neural network library called dynet which neede to be run by dynet_python. The other parts of the parser are the ordinary python codes.
>
>
>
> Bests,
>
> Ali
>
>
>
>
>
> From: Stephan Oepen <oe at ifi.uio.no>
> Date: Monday, 15 April 2019 at 22:59
> To: Ali Basirat <ali.basirat at lingfil.uu.se>
> Cc: "infrastructure at nlpl.eu" <infrastructure at nlpl.eu>
> Subject: Re: No more available loop devices, try increasing 'max loop devices' in singularity.conf
>
>
>
> 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/20190417/6a888140/attachment.htm>