Fully managed cloud. 30-day FREE full featured trial. Start Now
cancel
Showing results for 
Search instead for 
Did you mean: 

docker-db xmlrpclib https://github.com/exasol/exaoperation-xmlrpc

torsten
SQL-Fighter

Hallo liebe Community,

ich versuche mittels xmlrpclib auf eine Standalone Instanz zu kommen, die ich per docker-compose gestartet habe - also wurde die Instanz mit sämtlichen Defaults aus dem Image bestückt - inklusive xmlrpclib Port 443. Diesen habe ich per docker-compose.yml auf 9043 veröffentlicht, so dass ich dann versucher mittels

https://github.com/exasol/exaoperation-xmlrpc und dem Script exaoperation-xmlrpc/tools-and-examples/xmlrpc-help/help.py

versuche die ExaOperation innerhalb der docker-instanz anzusprechen. Leider bekomme ich folgende Antwort vom Server: 

"xmlrpclib.ProtocolError: <ProtocolError for admin:admin@<***>:9043/cluster/: 405 Method Not Allowed>"

Bedeutet dies dass der Benutzer admin/admin nicht autorisiert ist oder nicht authentifiziert werden kann? Wie lautet der Defaultbenutzer im docker-db Image - wenn alles Default ist?

Falls sich jemand damit auskennt, dann wäre ich über eine Antwort sehr froh.

LG, Torsten

CEO at Alligator Company, providing Datavault automation and DataOps on Exasol with Datavault Builder and DBTVault
2 REPLIES 2

torsten
SQL-Fighter

Sorry folks - wrong language - here is a translation:

i'm trying to access a standalone docker-db instance using xmlrpclib which i started with docker-compose - so the instance was populated with all defaults from the image - including xmlrpclib port 443 which i published with docker-compose.yml on 9043, so i'm trying to get to it with

- https://github.com/exasol/exaoperation-xmlrpc and the script exaoperation-xmlrpc/tools-and-examples/xmlrpc-help/help.py

try to address the ExaOperation within the docker instance. Unfortunately I get the following answer from the server:

"xmlrpclib.ProtocolError: <ProtocolError for admin:admin@<***>:9043/cluster/: 405 Method Not Allowed>"

Does this mean that the user admin/admin is not authorized or cannot be authenticated? What is the default user in the docker-db image - if everything is default?

If someone knows about this, I would be very happy about an answer.

CEO at Alligator Company, providing Datavault automation and DataOps on Exasol with Datavault Builder and DBTVault

exa-Fagani
Exasol Alumni

Hi @torsten ,

Since the docker version of Exasol uses different architecture unfortunately it is not possible to use scripts in https://github.com/exasol/exaoperation-xmlrpc to manage cluster via XML-RPC.

But of course, you can use the XML-RPC module in order to manage docker cluster(s). Since Exasol uses ConfD, which is the EXASOL configuration and administration daemon that runs on all nodes of an EXASOL cluster and t provides an interface for cluster administration and synchronizes the configuration across all node you can manage docker cluster via calling ConfD jobs.

We've recently posted an article about Using XML-RPC to manage Docker cluster.

Regards,