This reeks of a permission issue. Check which users have access to /dev/nv*, and make sure that the user that Celery runs as also has access to those devices.
Hope that helps, Andreas Just as a test, I made sure it was not a permisson issue by doing a chmod 777 on /dev/nv*. Still getting problems initializing Cuda in the context of django/celery. On Tue, Jul 15, 2014 at 12:00 PM, <[email protected]> wrote: > Send PyCUDA mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.tiker.net/listinfo/pycuda > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of PyCUDA digest..." > > > Today's Topics: > > 1. Re: Trouble Getting Set Up (Andreas Kloeckner) > 2. Re: Problem with pow (elodw) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 14 Jul 2014 17:18:59 -0500 > From: Andreas Kloeckner <[email protected]> > To: [email protected] > Subject: Re: [PyCUDA] Trouble Getting Set Up > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Am 14.07.2014 um 16:47 schrieb Forrest Pruitt: > > The frustrating thing is that in a stand-alone python shell, pycuda > > behaves appropriately. It is only in a Celery process that things > > break down. > > > > Any help here would be appreciated! > > > > If I need to provide any more information, just let me know! > > > This reeks of a permission issue. Check which users have access to > /dev/nv*, and make sure that the user that Celery runs as also has > access to those devices. > > Hope that helps, > Andreas > > > > ------------------------------ > > Message: 2 > Date: Tue, 15 Jul 2014 08:54:49 +0200 > From: elodw <[email protected]> > To: [email protected] > Subject: Re: [PyCUDA] Problem with pow > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > On 14.07.2014 20:49, Andreas Kloeckner wrote: > > elodw <[email protected]> writes: > > > > Probably neither, since it's a two-index loop. I.e. you should probably > > write that one from scratch to be able to map both i and j to CUDA axes. > > > > Hope that helps, > > Andreas > Thank You Andreas, > > perhaps You know a Source in the Net ? > > Thanks in advance > Ernst > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > PyCUDA mailing list > [email protected] > http://lists.tiker.net/listinfo/pycuda > > > ------------------------------ > > End of PyCUDA Digest, Vol 73, Issue 10 > ************************************** >
_______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
