Not able to connect to aerospike using go client from container

tried it on container of ubuntu 18 lts, centos 7 and alpine os

aerospike go client version is latest

go version 1.12

Attaching some debug logs

2020/02/21 11:39:36 NewClientWithPolicyAndHost Reached here
2020/02/21 11:39:36 No connections available; seeding...
2020/02/21 11:39:36 Seeding the cluster. Seeds count: 1
2020/02/21 11:39:36 Node Validator has 1 nodes and they are: [10.0.3.134:3000]
2020/02/21 11:39:36 Alias 10.0.3.134:3000 failed: Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 Seed 10.0.3.134:3000 failed: Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 Failed to connect to hosts:Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 No connections available; seeding...
2020/02/21 11:39:36 Seeding the cluster. Seeds count: 1
2020/02/21 11:39:36 Node Validator has 1 nodes and they are: [10.0.3.134:3000]
2020/02/21 11:39:36 Alias 10.0.3.134:3000 failed: Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 Seed 10.0.3.134:3000 failed: Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 Failed to connect to hosts:Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 Failed to connect to host(s): [10.0.3.134:3000]; error: Failed to connect to hosts:Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576
2020/02/21 11:39:36 Error initializing Aerospike. Error:  unable to initilize aerospike client error initializing aerospike managerFailed to connect to hosts:Requested new buffer size is invalid. Requested: 92703365869105, allowed: 0..1048576

through aql as well is not working

aql -h 10.0.3.134
Seed:         10.0.3.134
User:         None
Config File:  /etc/aerospike/astools.conf /root/.aerospike/astools.conf 
2020-02-24 11:02:27 WARN Failed to connect to seed 10.0.3.134 3000. AEROSPIKE_ERR_CLIENT Invalid proto type: 84 Expected: 1, 10.0.3.134:3000
Error -1: Failed to connect

but working through telnet on port 3003

telnet 10.0.3.134 3003
Trying 10.0.3.134...
Connected to 10.0.3.134.
Escape character is '^]'.
namespaces
prefix;**************************

It seems to me that you have major network issues.

What the clients are saying is that they are getting invalid data back from the server. Is the container local or on the internet?

Container is on the internet using kubernetes

And what problem can it cause having container on internet?

And what does that invalid data back from server means ??

Can we print the invalid data as well in the log in client ??

Tried the same thing outside container its working fine i.e. from ec2 machines …

As I mentioned, invalid data == network problems in most cases. You should try to investigate and see if other services on the same container work properly. You may have a service like tc or the like that is influencing the network traffic.

© 2015 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.