# Bad GID for job execution

**URL:** <https://community.openpbs.org/t/bad-gid-for-job-execution/1359>\
**Category:** Users/Site Administrators\
**Created:** [December 18, 2018, 4:59pm UTC](https://community.openpbs.org/t/bad-gid-for-job-execution/1359 "2018-12-18T16:59:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sijisaula](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@sijisaula](https://community.openpbs.org/u/sijisaula)\
**Post date:** [December 18, 2018, 4:59pm UTC](https://community.openpbs.org/t/bad-gid-for-job-execution/1359/1 "2018-12-18T16:59:17Z")

</div>

Hello,

We just recently migrated to AD from LDAP and we are noticing “qsub: Bad GID for job execution” errors when we submit job scripts with the “#PBS -W group\_list=x-ccast-users” directive:

> [oluwasijibomi.saula@bright01-thx ~]$ id oluwasijibomi.saula
> 
> uid=390302469(oluwasijibomi.saula) gid=390302469(oluwasijibomi.saula) groups=390302469(oluwasijibomi.saula),390368890(x-ccast-users)

However, we see id command showing the “x-ccast-users” group so we are not sure why PBS is complaining when we use the “#PBS -W group\_list=x-ccast-users” directive.

Now if we submitted without the “#PBS -W group\_list=x-ccast-users” directive, we don’t get an error…

Any help with this issue would be appreciated.

Thanks,  
Siji

---

<div class="post-metadata">

**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\
**Post date:** [December 19, 2018, 11:42am UTC](https://community.openpbs.org/t/bad-gid-for-job-execution/1359/2 "2018-12-19T11:42:07Z")

</div>

As per the code: getgrnam is used by pbs

> <https://github.com/PBSPro/pbspro/blob/293bce8c3f80d83895965f474ba154b1bfe0cfa0/src/server/geteusernam.c>

Suggestion would be to have a “c” program that used getgrnam, to print the member list on the server and on the node, to see that results match with respect users and their groups.

As per the qsub man page

```
group_list=g_list

                  List of group names. Job is run under a group name from this list. Sets job’s group_List attribute to g_list. Default: login group name of job owner.
                  Format of g_list:

                         group[@host][,group@host ...]

                  Only one group name may be specified without a host name. Only one group name may be specified per named host. The server on which the job resides will
                  select first the group name whose host name is the same as the server name. Failing that, the next selection will be the group name with no specified
                  hostname. The group names on the server and execution hosts must be the same.

                  Under Windows, the primary group is the first group found for the user by PBS when it queries the accounts database.
```

---

<div class="post-metadata">

**Author:** ![sijisaula](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@sijisaula](https://community.openpbs.org/u/sijisaula)\
**Post date:** [December 19, 2018, 2:44pm UTC](https://community.openpbs.org/t/bad-gid-for-job-execution/1359/3 "2018-12-19T14:44:05Z")

</div>

Thanks for the comments, Adarsh.

We’ve now resolved this issue by commenting out this line in our SSSD.conf:

#ignore\_group\_members = True