error while trying to connect aerospike DB with kubectl command - aerospike

Hi All am getting below error while trying to connect Aerospike DB
kubectl exec -it v11-nk-s01-csd5g1-db-0 -n v11csd -c csd-db-aerospike -- aql --tls-enable --tls-cafile /commonoamcerts/certs/cacert.pem -h csd-db -p 3000 --tls-protocols TLSv1.2 --tls-name .com
Seed: csd-db
User: None
Config File: /etc/aerospike/astools.conf /home/csduser/.aerospike/astools.conf
2021-12-10 05:23:40 WARN SSL_connect I/O error: 104
2021-12-10 05:23:40 WARN Failed to connect to seed csd-db 3000. AEROSPIKE_ERR_CONNECTION Socket connect failed: 192.168.51.218:3000
2021-12-10 05:23:41 WARN SSL_connect I/O error: 104
2021-12-10 05:23:41 WARN Failed to connect to seed csd-db 3000. AEROSPIKE_ERR_CONNECTION Socket connect failed: 192.168.46.40:3000
2021-12-10 05:23:42 WARN SSL_connect I/O error: 104
2021-12-10 05:23:42 WARN Failed to connect to seed csd-db 3000. AEROSPIKE_ERR_CONNECTION Socket connect failed: 192.168.2.206:3000
Error -10: Failed to connect
command terminated with exit code 255


Default TLS port is 4333. Perhaps if you are trying to make TLS connection you might should try -p 4333 or whatever your tls port is

Related

Fails to execute command

enter image description here
curl: (28) Failed to connect to raw.githubusercontent.com port 443 after 130114 ms: Couldn't connect to server
Getting this kind of error whenever I try to install some applications or oh-my-zsh/fish
same happens with the wget option as well
OS: ArchLinux

Start Chromium in Xvfb display: cannot start document portal: dial unix /run/user/0/bus: connect: permission denied

I want to run some tests with latest Chromium but experiencing errors.
I set up a new ubuntu 20 server without any additional packages.
Install chromium with apt install chromium-browser
Installed xvfb server
Created a display with
export DISPLAY=:2
Xvfb $DISPLAY -screen 0 1024x768x16 &
started chromium with
chromium-browser https://google.com
Error log shows:
2022/10/09 15:21:38.283814 cmd_run.go:1055: WARNING: cannot start document portal: dial unix /run/user/0/bus: connect: permission denied
mkdir: cannot create directory '/run/user/1000': Permission denied
[10264:10428:1009/152139.132312:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/user/0/bus: Permission denied
[10264:10428:1009/152139.132601:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/user/0/bus: Permission denied
[10264:10428:1009/152139.170741:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/user/0/bus: Permission denied
[10264:10428:1009/152139.170913:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/user/0/bus: Permission denied
Any hints how to fix that?

CentOS6 - curl NSS error -5961 resolved by updating packages. What did it actually do?

I was running into the same issue as described in this question: cURL SSL connect error 35 with NSS error -5961
$ curl --verbose https://api.hostname.com
* About to connect() to api.hostname.com port 443 (#0)
* Trying 1.2.3.4... connected
* Connected to api.hostname.com (1.2.3.4) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5961
* Closing connection #0
* SSL connect error
curl: (35) SSL connect error
I followed user qingbo's advice after noticing that the server (CentOS 6.5 VM) had not been updated in a while. I ran this command:
$ yum update -y nss curl libcurl
and then re-ran the curl command and this time I received an expected HTTP/1.1 200 OK.
My question is - what did updating the nss, curl and libcurl packages do that fixed the connection issue?

How to prevent "connection refused" with SOCKS on dataproc?

I'm trying to set up a SOCKS connection to my dataproc spark cluster following the Google Jupyter guide, but I keep getting "connection refused" errors after launching the browser, Chrome:
channel 4: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 6: open failed: connect failed: Connection refused
channel 7: open failed: connect failed: Connection refused
channel 8: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
channel 16: open failed: administratively prohibited: open failed
channel 17: open failed: administratively prohibited: open failed
channel 18: open failed: administratively prohibited: open failed
channel 16: open failed: connect failed: Connection refused
channel 18: open failed: connect failed: Connection refused
channel 18: open failed: connect failed: Connection refused
channel 18: open failed: connect failed: Connection refused
This happens with both --proxy-server="socks5://localhost:1080" and --proxy-server="socks5://127.0.0.1:1080"

So, I'm not 100% sure where the "administratively prohibited" messages come from, but in my experience those have always been false alarms, and I see those open failed: administratively prohibited: open failed messages even when my socks proxy is functioning correctly as expected.
As for the actual problem, due to the way things like YARN bind their web services, I've gotten Connection refused if trying to access the YARN UI with http://localhost:8088 instead of http://<master-hostname>:8088. This matches the behavior running get inside the cluster:
dhuo#dhuo-jupyter-m:~$ wget http://localhost:8124
...
Saving to: ‘index.html.13’
index.html.13 100%[=============================================================================================================================================================================>] 11.41K --.-KB/s in 0s
2016-07-15 23:26:25 (222 MB/s) - ‘index.html.13’ saved [11686/11686]
dhuo#dhuo-jupyter-m:~$ wget http://localhost:8088
--2016-07-15 23:26:28-- http://localhost:8088/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8088... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8088... failed: Connection refused.
dhuo#dhuo-jupyter-m:~$ wget http://`hostname`:8124
...
Saving to: ‘index.html.14’
index.html.14 100%[=============================================================================================================================================================================>] 11.41K --.-KB/s in 0s
2016-07-15 23:26:34 (260 MB/s) - ‘index.html.14’ saved [11686/11686]
dhuo#dhuo-jupyter-m:~$ wget http://`hostname`:8088
...
Saving to: ‘index.html.15’
index.html.15 100%[=============================================================================================================================================================================>] 10.81K --.-KB/s in 0s
2016-07-15 23:26:37 (248 MB/s) - ‘index.html.15’ saved [11067/11067]
As you can see, this is different from the Jupyter behavior (which I ran on port 8124), where the Jupyter webapp works correctly resolving localhost:8124 on the master. Since the name resolution with those linked instructions should be happening on the master, the browser's behavior resolving hosts will be the same as running wget in the node you've tunneled into.
So if you just use your master's hostname instead of localhost it should work.

CHECK_NRPE: Error - Could not complete SSL handshake with nsclient++

I'm using NRPE (v2.15) on my Icinga-Server to check the memory usage on a
windows host with nsclient++ (v0.4.3.143).
Unluckily I always get the same error message when I try to check it:
./check_nrpe -H host01 -p 5666 -c CheckMem -a MaxWarn=95% MaxCrit=98% ShowAll type=physical
CHECK_NRPE: Error - Could not complete SSL handshake.