Hi Kashif
> Did anyone manage to configure torque-4.2 from EPEL successfully?
Yes, but to get it running you need to fix manually:
- directories /var/lib/torque/spool/ , /var/lib/torque/checkpoint/ and /var/lib/torque/undelivered/
have wrong permissions (https://bugzilla.redhat.com/show_bug.cgi?id=1216037), the permissions should be 1777
- trqauthd init script is not included in EPEL packages (https://bugzilla.redhat.com/show_bug.cgi?id=1215207), you can download it from torque sources on github
> I have looked at torque spec file from EPEL and it is built with
> '-enable-munge-auth' but my understanding is that torque 4 should be using
> trqauthd.
You need both trqauthd and munge daemons running on server and all nodes where torque client commands have to run. The reason might be:
http://docs.adaptivecomputing.com/torque/5-1-0/Content/topics/torque/12-appendices/securityOverview.htm
"Neither trqauthd nor pbs_iff do authentication. They only do authorization of users."
http://docs.adaptivecomputing.com/torque/4-1-3/Content/topics/1-installConfig/serverConfig.htm#usingMUNGEAuth
"MUNGE is an authentication service that creates and validates user credentials."
> Any way I installed torque4 from EPEL but pbs_server didn't start
> with or without trqauthd.
Try to look into logs of torque server if you will find anything useful there.
Cheers,
Jan
--
Jan Astalos
NGI_SK - operations
Institute of Informatics, Slovak Academy of Sciences
|