Data360 DQ+

Welcome to the Data360 DQ+ community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements  Product Documentation  Ideas Portal

Discussions

Members

Resources

Events

 View Only

  • 1.  loadbalance issue

    Posted 12-09-2019 04:29

    Auth Type=INTERNAL 
    sagacityLoadBalancer#0|: 
    Starting new docker container for sagacityLoadBalancer... 
    sagacityLoadBalancer#2|Unable to find image 'sagacity/load-balancer:3.1.0' locally 
    sagacityLoadBalancer#2|Trying to pull repository registry.access.redhat.com/sagacity/load-balancer ... 
    sagacityLoadBalancer#2|Trying to pull repository docker.io/sagacity/load-balancer ... 
    sagacityLoadBalancer#2|/usr/bin/docker-current: Get https://registry-1.docker.io/v2/: proxyconnect tcp: dial tcp 10.1.26.194:443: connect: connection refused. 
    sagacityLoadBalancer#2|See '/usr/bin/docker-current run --help'. 
    Failed command sagacityLoadBalancer#2 with status 125: docker run -p 80:80 -p 443:443 -p 9100-9120:9100-9120 --net=host --name sagacityLoadBalancer --restart unless-stopped -e SAG_UID=$(id -u) -e SAG_GID=$(id -g) -e MOD_CLUSTER_ADMIN_USER=sagacity -e MOD_CLUSTER_ADMIN_PASSWORD=GQSsqe321 -v /etc/localtime:/etc/localtime -v /opt/infogix/data/runtime/apache/conf/ssl:/usr/local/apache2/ssl -d sagacity/load-balancer:3.1.0

    > Task :startLoadBalancer FAILED



  • 2.  RE: loadbalance issue

    Posted 12-09-2019 10:05

    Hi Chenghao,

    I see you also submitted a ticket for this same question, and that you were able to resolve the issue. To document the resolution here for future reference, it looks like it was resolved as an external network connection issue