Jump to content
  • Announcements

    • admin

      PBS Forum Has Closed   06/12/17

      The PBS Works Support Forum is no longer active.  For PBS community-oriented questions and support, please join the discussion at http://community.pbspro.org.  Any new security advisories related to commercially-licensed products will be posted in the PBS User Area (https://secure.altair.com/UserArea/). 
Marcelo

'Mom' atrrib

Recommended Posts

Hi

 

I have several nodes which present more than one node in the Mom attrib how can I remove the second one? Here is an example:

n016
     Mom = n016.default.domain,n013.default.domain
     Port = 15002
     pbs_version = PBSPro_11.3.2.130131
     ntype = PBS
     state = free
     pcpus = 24
     resources_available.arch = linux
     resources_available.host = n016
     resources_available.mem = 32829916kb
     resources_available.ncpus = 24
     resources_available.vnode = n016
     resources_assigned.accelerator_memory = 0kb
     resources_assigned.mem = 0kb
     resources_assigned.naccelerators = 0
     resources_assigned.ncpus = 0
     resources_assigned.netwins = 0
     resources_assigned.vmem = 0kb
     resv_enable = True
     sharing = default_shared
     license = l

 

I want to remove node013 from the node016 Mom attribute

 

Thanks for your help

Marcelo

 

Share this post


Link to post
Share on other sites

That is very interesting. 

The MOM attribute represents the hostname of host on which MoM daemon runs. The server can set this to the FQDN of the host on which MoM runs, if the vnode name is the same as the hostname.

By chance does n016 resolve to n016.default.domain and n013.default.domain?

On the PBS Server and on the PBS MOM (n016), please execute the following to see the possible hostname resolution

pbs_hostn -v n016 

If you have name resolution issue where n016 thinks it is n016.default.domain and n013.default.domain, make sure you fix that before proceeding with the following suggestion. 

Your node configuration looks very basic - meaning there are no custom resources. Your fastest method of cleaning this up would be delete the node from qmgr and re-create it. 

qmgr -c "d n n016"
qmgr -c "c n n016"

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×