ronaldvandenberg-5545 avatar image
0 Votes"
ronaldvandenberg-5545 asked

The target namespace does not exist.

On the risk of getting an answer i don't understand I'm trying the following question.

From the community catalog I've found a managementpack that discovers and monitors docker on unix/linux. The pack has been removed for unknown reasons, there might be issues with it like the one I'm having now.

I've started my own managementpack based on the workflows I've found in the original pack.
It now discovers some daemons and containers so that part works fine only i'm missing most of my servers of which i know have docker daemons running.

The daemon discovery does a simple winrm query which i tested on a docker discovered server and another server where it's not discovered with this command:

winrm e -r:https://fqdn:1270/wsman -auth:basic -skipCACheck -skipCNCheck -encoding:utf-8 -format:pretty -u:svcscom -p:"password"

Now on the working server i get the details back like it should, on the other server i get this result (filtered out the important parts)
<SOAP-ENV:Text xml:lang="en-US">The target namespace does not exist.</SOAP-ENV:Text>

Now the second line is probably the root cause.

I know almost nothing about how omi/winrm works on the background with classes and namespaces so i started googling and reading but since i don't know the basics i don't know where to start or what is wrong and certainly not how to solve it.

Before I've found this community pack I've build my own pack that does a simple shell discovery, that way I've found out that there are multiple names of docker daemons, so i could fall back to that discovery, but i also want containers to be discovered and that's not possible from shell without the proper permissions so for that i also need the winrm discovery to work.

How are namespaces created, why could it be missing on many servers while docker is installed?
All ideas on how to proceed would be appreciated!

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

0 Answers