# Trying to get CUDA\_VISIBLE DEVICES set with hook

**URL:** <https://community.openpbs.org/t/trying-to-get-cuda-visible-devices-set-with-hook/1207>\
**Category:** Users/Site Administrators\
**Created:** [September 21, 2018, 4:43pm UTC](https://community.openpbs.org/t/trying-to-get-cuda-visible-devices-set-with-hook/1207 "2018-09-21T16:43:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mkaro](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/mkaro/32/85_2.png) [@mkaro](https://community.openpbs.org/u/mkaro)\
**Post date:** [September 21, 2018, 5:26pm UTC](https://community.openpbs.org/t/trying-to-get-cuda-visible-devices-set-with-hook/1207/2 "2018-09-21T17:26:41Z")

</div>

Hi Joe,

Thanks for your questions. The message you’re seeing about libmemacct is benign. If you were on an Altix system where libmemacct.so is present, you wouldn’t see it. It may safely be ignored.

The cgroup hook sets CUDA\_VISIBLE\_DEVICES in the job’s environment. Your configuration looks correct, but some versions of nvidia-smi report information about the device IDs differently. There is another thread where this was discussed here: [GPU Access Limited by CGroup](http://community.openpbs.org/t/gpu-access-limited-by-cgroup/735)

Take a look at the pbs\_mom logs in /var/spool/pbs/mom\_logs and see if there is anything helpful there. If not, you can increase the verbosity of the logs by adding a line to /var/spool/pbs/mom\_priv/config that looks like this:  
`$logevent 0xffff`

You will need to restart pbs\_mom so that it rereads its configuration. Try running another job and see if the logs provide any clues. Feel free to post excerpts here if you need additional help.

Thanks,

Mike

---

_[View the full topic](https://community.openpbs.org/t/trying-to-get-cuda-visible-devices-set-with-hook/1207)._