From what I recall, OpenDirectory was not at fault, it was actually the incredibly long group membership that users created in OpenDirectory. Once I truncated group membership down in OD I had no issues with OD users and grid engine.

Try running the command “id ” or “groups ” and if you see a massive group membership list that may be the culprit. Reduce the size and number of groups that the user belongs to and you might be ok.

-Chris

Do the users have to be added as local users on each machine?

Just a quick update and heads up.

I finally got it working! The problem is that I was using AFP as my network sharing protocol. I don’t know the exact reason, but I decided to change my automount options to NFS on a hunch. Nothing else had to be modified. So, just as a tip:

SGE does not work with AFP.

My guess is that the sge_execd checks for nfs mounted directories. That, or, the service is waiting for NFS to start before it will start. I haven’t done much testing, but I came here to share before I forgot.

Thanks for all of the help. You guys are great! Keep up the good work.

-Trey

To get your execution host going I’d first issue some commands on the qmaster to make sure that the compute known is known as a host (“qconf -ah “), “(qconf -as ), etc.

You can even use commands on the master to make your nodes parts of queues without having the exechosts running yet although this is not required. I’ve done many clusters in the past where we pre-staged all of the configuration settings for the compute nodes so that all we had to do was install the startup scripts on the nodes and it all worked.

I think you need to skip the install script, get the sge_execd daemon running via launchd and just configure queue related stuff manually. You may have to make a spool directory for the compute nodes manually as that is one step that the install script usually does. Even that may not be necessary – it could all just get sorted out automatically.

Once sge_execd is running under launchd it will accept commands and will be able to communicate. Getting things functional from there should be quite easy.

Awesome guide. It was extremely helpful and made quick work of setting up the qmaster correctly and efficiently.

Have you tried to start up an execution host on a separate machine? I can’t for the life of me get this to work. The dead end that I keep running into looks like this:

remotehost:SGE_ROOT root# bin/darwin-x86/sge_execd
daemonize error: timeout while waiting for daemonize state

Everything else is configured correctly as far as I can tell. The secondary host is configured as an administrative host, a submit host, an execution host, it has been added to the @allhosts group.

qmaster:~ sgeadmin$ qstat -f
queuename qtype resv/used/tot. load_avg arch states
————————————————————–
all.q@qmaster.cs BIP 0/0/16 0.09 darwin-x86
————————————————————–
all.q@remotehost.cs BIP 0/0/16 -NA- -NA- au

Thanks again for all the help.
- Trey Wessler