Your true problem is almost certainly not related or caused by the "connection refcount" message. The "connection refcount" message could indicate a very slow memory leak but that is unlikely to cause issues for at least a few years after starting up the agent.

Your true problem is "_xmlrpc.error: Error encoding text"

What version of SA are you running? We have a known issue fixed in 24.1.001 and later that manifests in a similar way but it also has a workaround: before running an SA job ensure that the managed device has run a full software registration (bs_software). You can initiate this manually on unix and windows managed devices as well by running /opt/opsware/agent/pylibs3/cog/bs_software (or bs_software.bat). If this was your issue then you'd see it only on newly deployed agents or on agents that cannot do full software registration for some reason.

If the above doesn't apply then you would first look at the type of job you're running when the issue happens and the target device this happens on. You would then collect a session_dump and debug level waybot and agent logs.

boneimre said:

ll software registration (bs_software).

First of all , thanks for your answer. I am using SA Agent 80.0.92103.0 version on Windows Server 2019 machines. Also , like you said I've tried full software registration command before run install software job. But no luck.

I don't understand exactly that what you mean by "at the type of job you're running".

- I am creating ZIP package. (consisting one msi file and one bat file) 

- Then importing inside SA (via Import Software under Library)

- Right click on managed device then Install - Software 

lastly , How can we collect a session_dump and debug level waybot and agent logs? 

I am assuming you saying :

Windows agent logs:

%ProgramFiles%Common Files\opsware\log\agent\agent.log*

%ProgramFiles%Common Files\opsware\log\agent\agent.err*

waybot.err while reproducing the problem, from SA Core run:

tail -f /var/log/opsware/waybot.err

I don't know session dump.

What happens when you execute bs_software.bat ?

it works.

PS C:\Program Files\Opsware\agent\pylibs3\cog> .\bs_software.bat

Registering full software inventory information...
Contacting core for delta with SpinWrapper'> to spin:1004/spinrpc.py...
Software inventory delta registered.
PS C:\Program Files\Opsware\agent\pylibs3\cog>

Also ,  OPSWshadowbotservice.out

leeping for 120 seconds...
Failed to put results 55586800001 to the Way:
Traceback (most recent call last):
File ".\way.py", line 703, in putResults
File ".\xmlrpc\xmlrpclib.py", line 114, in __call__
File ".\xmlrpc\lcxmlrpclib.py", line 136, in __request
File ".\xmlrpc\xmlrpclib.py", line 192, in __request
File ".\xmlrpc\_pyxmlrpc.py", line 137, in dumps
File ".\xmlrpc\_pyxmlrpc.py", line 80, in dumps
_xmlrpc.error: Error encoding text

Sleeping for 300 seconds...
Failed to put results 55586800001 to the Way:
Traceback (most recent call last):
File ".\way.py", line 703, in putResults
File ".\xmlrpc\xmlrpclib.py", line 114, in __call__
File ".\xmlrpc\lcxmlrpclib.py", line 136, in __request
File ".\xmlrpc\xmlrpclib.py", line 192, in __request
File ".\xmlrpc\_pyxmlrpc.py", line 137, in dumps
File ".\xmlrpc\_pyxmlrpc.py", line 80, in dumps
_xmlrpc.error: Error encoding text

how to collect session_dump and debug level waybot ?

In the NGUI:

Administration->System Configuration->Configuration Parameters-> Command Engine(way):

way.debug_size: 1

way.remediate.logtofile:1

Run the job and wait until it fails.

Collect the /var/log/opsware/waybot/* logs from the core[s]

Collect the agent logs from the agent

Collect the session on the core with the command "/opt/opsware/support/bin/dump_session YOUR_JOB_ID"

ok I will sent log files. btw ,Session<jobID>.pkg.gz  file  will be write under opt/opsware/support/bin/ directory? right? Is pkg.gz enough? Do you need HTML?

Please open a support case with the data collected