Absent Member.. Absent Member..
Absent Member..
4114 views

Distribution to node - problems

Hello, I have random problems occuring when I'm distributing templates (among other things) to managed nodes:

 

(OML 9.10)

 

Severity critical,

Message Text: Network communication problem occurred during distribution to node node_name. Distribution will be retried in half hour by default. Reason: (ctrl-21) Communication erro when executing 'Status' method (OpC40-1862).

 

bbcutil -ping is working, telnet @383 works both ways. I can also check agent status remotely.

 

I've checked System.txt on both management server and node:

 

Server shows (in addition to above message):

Unable to deploy 'DeplM1937710360' to node node_name. Reason (depl-81): unable to deploy 'DeplM1937710360' to node node_name;

 

I'm also having such entries in system.txt:

opcbbcdist: DBHandler.cpp:2042: error occured while getting instrumentation value: Type is MAP_OS_VERSION. Assd value is 6.1

 

This doesn't directly point to that node but it's in the log near message about failed distribution. Node is windows 2008.

 

 

 

Node log shows nothing. Policies are not updated.

 

Any help would be really appreciated 🙂

 

Regards,

Blichew

0 Likes
10 Replies
Highlighted
Absent Member.
Absent Member.

Re: Distribution to node - problems

Hello.

 

The message about "Assd" value means it won't be able to consider OS version for distributing instrumentation.

 

As for the other issue - you would get more details if you enable tracing for the 'opcbbcdist' process.  But if the issue is on the node then you might also need to enable tracing there.

 

And since it says "Status" failed - does it work if you use opcragt to query for node's status?

 

opcragt -status nodename

 

Regards,

    Goran

Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Distribution to node - problems

yup, opcragt -status works. All processes are running.

 

"The message about "Assd" value means it won't be able to consider OS version for distributing instrumentation." - distribution of scripts should still work, right ?

 

as for tracing, how can I enable this feature ?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Distribution to node - problems

Some scripts would mighjt not be distributed, depending on your configuration (i.e. OS based category assignment).

 

As for tracing - you would need to use newer style tracing, so:

 

/opt/OV/support/ovtrccfg -app opcbbcdist -sink /var/tmp/myfile.trc

 

Reproduce the issue and disable tracing:

 

/opt/OV/support/ovtrccfg -off

 

Convert the trace to text file:

 

/opt/OV/support/ovtrcmon -fromfile /var/tmp/myfile.trc -tofile /var/tmp/mytrc.txt -fmt verbose

 

The amount of details would be quite high so you might end up asking support to assist here.

 

Regards,

    Goran

Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Distribution to node - problems

The procedure outlined here will solve this problem:

 

[OA ST] OpC40-2700 after Deploy of Configuration to AIX based servers

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Distribution to node - problems

Hi again,

I have to update this topic: new installation, OML 9.21.100.

Agent is installed on RHEL 6.6 (11.14), now the message reads:

 

Error occurred while getting instrumentation value for node node_name_here: Type is MAP_OS_VERSION. Assd value is 'EMPTY'.

 

opcragt -status works, as for trace - nothing is written into file i specified as trace log.

 

Regards,

Blichew

 

0 Likes
Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..

Re: Distribution to node - problems

I'm having this same issue...only when I install an agent locally on the node (as opposed to installing it remotely via the management server). Maybe there is another setting that needs to be manually specified?  My MAP_OS_VERSION is also empty. This is installing on RHEL6.5, agent version 11.14.137.

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Distribution to node - problems

Hello.

 

What does this show for the node in question - run it on the OMU server?

 

opcnode -list_attrs node_name=...

 

Regards,

    Goran

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Distribution to node - problems

Hi Goran,

We have OML 9.20 ON Cluster with oracle 11gR2 RAC database.

We also deployed cpu, memeory, disk policies an system infrastructure instrumentation.

We are geeting error:

Error occurred while getting instrumentation value for node d137xrandv: Type is MAP_OS_VERSION. Assd value is 'EMPTY'.
  (OpC40-2700)

As per your post we executed the below command:-

 

[root@SIDCOML2N01 utils]# ./opcnode -list_attrs node_name=d137xrandv
====================================================================
Number of CPUs: 1
CPU Type:
OS Family:
OS Type:
OS Name:
OS Vendor:
OS Version:
OS Bits:        0
Agent Bits:     0
MAC Addresses:
====================================================================
Operation successfully completed.

 

Please help regarding this issue.

 

Regards,

Bharat

0 Likes
Highlighted
New Member.

Re: Distribution to node - problems

Hello Bharat,

 

FOR :

Error occurred while getting instrumentation value for node xxxx Type is MAP_OS_VERSION. Assd value is 'EMPTY'.
(OpC40-2700)

Follow the steps :

On Managed Node:

 opcagt -kill

 cd /var/opt/OV/tmp/public/OpC
 rm *
 opcragt -cleanstart

On Management server :

ovc -stop opcbbcdist
rm -f /var/opt/OV/share/tmp/OpC/distrib/*
ovc -start opcbbcdist

 Hope this should work !

---Rajesh
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Distribution to node - problems

Hi Rajesh,

I would like to inform you that this issue facing only for windows os as for linux it is displaying proper information.

[root@SIDCOML2N01 utils]# ./opcnode -list_attrs node_name=d173xrandv
====================================================================
Number of CPUs: 16
CPU Type: x64
OS Family: unix
OS Type: Linux
OS Name: Red Hat 5.4
OS Vendor: Red Hat
OS Version: 2.6.18
OS Bits: 64
Agent Bits: 64
MAC Addresses: 0026B98D51DA,0026B98D51DA

 

Please suggest

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.