ALERT! The community will be read-only on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only on April 19, 8am Pacific as the migration begins.Read more for important details.
Admiral
Admiral
1365 views

Node is not recognized by his shortname

Jump to solution

Hello,

i have a strange things occurs on one of my cluster.

One of my node is registred in database:

 opcnode -list_nodes | grep qvipberout01
Name         = qvipberout01.france.airfrance.fr
Label        = qvipberout01

but for un unknown reason any command is in failure if i do not specify the FQDN of my server:

opcragt -status qvipberout01
Node qvipberout01:
This node is not contained in the domain. (OpC40-712)

No node left for processing. (OpC40-722)
[root@tlspoml1 ~]# opcragt -status qvipberout01.france.airfrance.fr
Node qvipberout01.france.airfrance.fr:
HPOM Managed Node status :
-------------------------
OV Performance Core       coda        (39628) is running
OV Communication Broker   ovbbccb     (39566) is running
OV Control                ovcd        (39558) is running
OV Config and Deploy      ovconfd     (41408) is running
Subagent EA:
Action Agent              opcacta     (41432) is running
Message Agent             opcmsga     (41452) is running
Done.

I have no issue with others managers, i try to remove and recreate this server, no change.

 

echo "select label,node_name from opc_node_names,opc_nodes where opc_nodes.node_id=opc_node_names.node_id AND opc_nodes.label='qvipberout01';" | opcdbpwd -e sqlplus -s

LABEL
--------------------------------------------------------------------------------
NODE_NAME
--------------------------------------------------------------------------------
qvipberout01
qvipberout01.france.airfrance.fr

Every time i try to launch a command for this node, System.txt file logs:

Node qvipberout01 is not in the node bank. (OpC50-91)
opcnode (11713/47902758383184): [node.scp:3640]: No according data found in the database. (OpC50-3)

Any idea ?

 

Thx

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Admiral
Admiral

Hummm good remark, but the script construct the label with:

LABELNAME=`echo ${HOST} | cut -f1 -d.`

 

so i could not miss a space in FQDN server, especially that i make a ping test at the begining of my script (to confirm DNS are ok), with a space it would have failed immediatly.

 

View solution in original post

0 Likes
4 Replies
Vice Admiral
Vice Admiral

Does nslookup qvipberout01 work?

0 Likes
Admiral
Admiral

yes there is no issue with DNS, ping/nslookup work with long and short name.

Now all commands work also with shortname, i don't know why for this server if i try to use cli to integer label not seems linked to server, and if i declare it directly in midas, no trouble...

My issue is solved but it's quite rageous do not understand why it failed un cli, especially when it concerns only one server and not everyone i try to integer.

0 Likes
Vice Admiral
Vice Admiral
Could there be a space after the Label?
Because if I doubleclick on the whitespace after qvipberout01 in the SQL output, a space becomes selected...

Can you edit the Label in the AdminUI and retype it?
0 Likes
Admiral
Admiral

Hummm good remark, but the script construct the label with:

LABELNAME=`echo ${HOST} | cut -f1 -d.`

 

so i could not miss a space in FQDN server, especially that i make a ping test at the begining of my script (to confirm DNS are ok), with a space it would have failed immediatly.

 

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.