tag:blogger.com,1999:blog-32189452.post3664239111552327482..comments2020-10-01T16:11:58.925+01:00Comments on ScotGrid: pick a torque, any torqueGraeme Stewarthttp://www.blogger.com/profile/04113191724360870254noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-32189452.post-81135178666482806472010-03-04T22:54:41.301+00:002010-03-04T22:54:41.301+00:00Hi,
The're released the full monty of i386/x8...Hi,<br /><br />The're released the full monty of i386/x86_64 RHEL4 and 5. And in fact ppc and s390 if you have one lying around.<br /><br />libtorque.x86_64 2.3.10-1.el4 epel <br />libtorque.i386 2.3.10-1.el4 epel <br />libtorque-devel.i386 2.3.10-1.el4 epel <br />libtorque-devel.x86_64 2.3.10-1.el4 epel <br />torque.x86_64 2.3.10-1.el4 epel <br />torque-client.x86_64 2.3.10-1.el4 epel <br />torque-docs.x86_64 2.3.10-1.el4 epel <br />torque-gui.x86_64 2.3.10-1.el4 epel <br />torque-mom.x86_64 2.3.10-1.el4 epel <br />torque-pam.x86_64 2.3.10-1.el4 epel <br />torque-pam.i386 2.3.10-1.el4 epel <br />torque-scheduler.x86_64 2.3.10-1.el4 epel <br />torque-server.x86_64 2.3.10-1.el4 epel <br /><br />Apologies for the debian style package naming. Not my choice.Anonymoushttps://www.blogger.com/profile/08684121414761564302noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-24201628844465235952010-02-12T09:54:58.051+00:002010-02-12T09:54:58.051+00:00I was about to release 2.3.9 but given 2.3.10 is o...I was about to release 2.3.9 but given 2.3.10 is out have added that instead to EPEL testing.<br /><br />https://admin.fedoraproject.org/updates/torque<br /><br />It will take around three weeks before I can release this new one.Anonymoushttps://www.blogger.com/profile/08684121414761564302noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-52148307284393968362010-02-11T23:20:45.021+00:002010-02-11T23:20:45.021+00:00Also, you will want to look at the YAIM variables....Also, you will want to look at the YAIM variables....<br />BATCH_LOG_DIRTim Dycehttps://www.blogger.com/profile/01652879297591090992noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-22074461676529428102010-02-11T19:51:36.100+00:002010-02-11T19:51:36.100+00:00Hi Steve,
The /var/spool/pbs -> /var/torque mi...Hi Steve,<br /><br />The /var/spool/pbs -> /var/torque migration (as in the EPEL packages) was pretty straight forward, the big gotchas lie in adding the stuff that YAIM normally does for you. Since YAIM setup will auto-configure the worker nodes; but only populate the /var/spool/pbs directory.<br /><br />For the worker nodes this meant adding:<br />- /var/torque/server_name<br />- /var/torque/mom_priv/config<br />We distributed these via cfengine, but you could just as easily copy the existing YAIM generated versions:<br />- /var/spool/pbs/server_name<br />- /var/spool/pbs/mom_priv/config<br /><br />For the server side, since we upgraded both, we needed to alter cf to point at (we never let YAIM generate these anyway).<br />- /var/torque/server_name<br />- /var/torque/server_priv/nodes<br />Which you can get from:<br />- /var/spool/pbs/server_name<br />- /var/spool/pbs/server_priv/nodes<br /><br />Updating APEL<br />The APEL pasrer on our LGC-CE uses the pbs logs, NFS exported from the pbs server, to reconcile against the gatekeeper logs and generate the accounting information. Our LCG-CE and PBS server are separate, so I just updated the NFS export on the PBS server and the autofs import on the LCG-CE.<br />If the LCG-CE and the PBS server were on just one host, you would need to update /opt/glite/etc/glite-apel-pbs/parser-config-yaim.xml (take a look at /etc/cron.d/edg-apel-pbs-parser). Update the line containing:<br />/var/spool/pbs/server_priv/accounting<br /><br />CREAM-CE <br />Depending on which version of the blahd parser you are using, you may need to update the parser on the cream CE.<br /><br />Our PBS server and moms have been nice and stable since the upgrade. We have seen some occasional PBS crankiness when the pbs_server service is restarted, but that's pretty normal.<br /><br />The only thing to be wary of is that any YAIM reconfigures will no longer have any effect on the PBS config since they will operate on now defunct files.<br /><br />TimTim Dycehttps://www.blogger.com/profile/01652879297591090992noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-24832342355517959952010-02-11T05:39:43.854+00:002010-02-11T05:39:43.854+00:00This comment has been removed by the author.Tim Dycehttps://www.blogger.com/profile/01652879297591090992noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-90112353070350552312010-02-10T19:05:12.037+00:002010-02-10T19:05:12.037+00:00Hi Tim,
Could you describe what was needed to use...Hi Tim,<br /><br />Could you describe what was needed to use the epel packages in particular with respect to the /var/spool/pbs -> /var/torque migration.<br /><br /> SteveAnonymoushttps://www.blogger.com/profile/08684121414761564302noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-2903267675235302812010-01-31T23:14:38.260+00:002010-01-31T23:14:38.260+00:00Hey,
We saw the same issues with the 2.3.6 torque...Hey,<br /><br />We saw the same issues with the 2.3.6 torque release in Melbourne. We upgraded to Steve's 2.3.9 packages for server and mom, and no problems since.<br /><br />TimTim Dycehttps://www.blogger.com/profile/01652879297591090992noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-51718562168203367952010-01-29T11:26:45.263+00:002010-01-29T11:26:45.263+00:00Hi Dug,
Have you reported the crash at all? The ...Hi Dug,<br /><br />Have you reported the crash at all? The Torque community is very active and usually you can get a quick turnaround. It'd help strengthen the product as well.<br /><br />http://www.supercluster.org/pipermail/torquedev<br /><br />http://www.supercluster.org/pipermail/torqueuserschrishttps://www.blogger.com/profile/09209544658530231536noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-34351816608698127192010-01-22T00:26:08.971+00:002010-01-22T00:26:08.971+00:00On a related 2.3.9 is now available for some testi...On a related 2.3.9 is now available for some testing as an EPEL release.<br /><br />https://admin.fedoraproject.org/updates/torque<br /><br />packages available from the epel-testing repos.<br /><br />The significant difference is /var/spool/pbs becomes /var/torque.<br /><br />I've tested it with current EGEE maui release and at small scales at least works for trivial items.Anonymoushttps://www.blogger.com/profile/08684121414761564302noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-16185665797718338002010-01-20T11:30:42.467+00:002010-01-20T11:30:42.467+00:00Hey,
Well we thought that this was the case too. ...Hey,<br /><br />Well we thought that this was the case too. But when we had segfaults we have 2.3.6 in both client and server. We fixed the issue by upgrading the mom with the various versions stated in the post. <br /><br />So I would be wary of just blaming the different version of mom and server. Although I would rather have them the same!<br /><br />Dugdug mcnabhttps://www.blogger.com/profile/03682082856121718825noreply@blogger.comtag:blogger.com,1999:blog-32189452.post-53115516705219576512010-01-19T15:29:27.875+00:002010-01-19T15:29:27.875+00:00Hi,
it looks like torque is failing (seg fails) ...Hi,<br /> it looks like torque is failing (seg fails) when you mix versions between client and server.<br /><br />We had the same issue when using the 2.3.0 version of torque server and 2.3.6 version of clients.<br /><br />The other way around seemed to work (having updated server and downgraded client).<br /><br />ChristosChristos Triantafyllidishttps://www.blogger.com/profile/04138599447957010107noreply@blogger.com