Hey
Anyone have an idea what is causing this error with multi server setup. We use 2 ns in 2 different datacenters. But the 2 VPS and one of the nameservers are on 1 node in the same datacenter via proxmox. The other ns is stationed somewhere else. 1 VPS can connect to the ns on the other location but not the one in the same node. The other VPS can connect to the ns in the same node but not to the other one. And they were configured exactly the same.
This is the error for the vps which cant connect to the ns on another location :
ns2.xx.xx : DirectAdmin Daemon v1.61.4 : Unable to get api result. Check your configuration options.
This is the error the vps on the same node as the second ns gets :
ns1.xx.xx : : Timeout while trying to connect to xx.xxx.xxx.xxx
Unable to connect to secure socket
Some I/O error occurred. The OpenSSL error queue may contain more information on the error. If the error queue is empty (i.e. ERR_get_error() returns 0), ret can be used to find out more about the error: If ret == 0, an EOF was observed that violates the protocol. If ret == -1, the underlying BIO reported an I/O error (for socket I/O on Unix systems, consult errno for details).
openssl error queue:
empty error queue. ret=-1
errno: Bad file descriptor
Anyone have an idea what is causing this error with multi server setup. We use 2 ns in 2 different datacenters. But the 2 VPS and one of the nameservers are on 1 node in the same datacenter via proxmox. The other ns is stationed somewhere else. 1 VPS can connect to the ns on the other location but not the one in the same node. The other VPS can connect to the ns in the same node but not to the other one. And they were configured exactly the same.
This is the error for the vps which cant connect to the ns on another location :
ns2.xx.xx : DirectAdmin Daemon v1.61.4 : Unable to get api result. Check your configuration options.
This is the error the vps on the same node as the second ns gets :
ns1.xx.xx : : Timeout while trying to connect to xx.xxx.xxx.xxx
Unable to connect to secure socket
Some I/O error occurred. The OpenSSL error queue may contain more information on the error. If the error queue is empty (i.e. ERR_get_error() returns 0), ret can be used to find out more about the error: If ret == 0, an EOF was observed that violates the protocol. If ret == -1, the underlying BIO reported an I/O error (for socket I/O on Unix systems, consult errno for details).
openssl error queue:
empty error queue. ret=-1
errno: Bad file descriptor