DQM CDJ BVS EEP GSI IO cannot connect to IO X at startup with k_connect_auth_timeout(nodename/SIO) returns error [200]
Article ID: 261996
Updated On:
Products
Issue/Introduction
A new Dollar Universe node is installed, and post installation it fails to start with the following output:
# Problem during DUAS instance start.
# The following engines do not start:
# uxcdjsrv X
# uxbvssrv X
# uxdqmsrv X
# uxeepsrv X
# uxgsisrv X
# uxioserv A
# uxcdjsrv A
# uxbvssrv A
In the universe.log, we obtain:
| 2023-03-14 15:45:02 |INFO |X|DQM|pid=11403684.1| log_rlimits | signals received 0
| 2023-03-14 15:45:02 |ERROR|X|cmd|pid=8913178.1| owls_connect_auth | k_connect_auth_timeout(nodename/SIO) returns error [200]
| 2023-03-14 15:45:02 |ERROR|X|cmd|pid=8913178.1| o_callsrv_connect_r | Connection error 79 [Errno syserror 79: A remote host refused an attempted connect operation.]
| 2023-03-14 15:45:02 |ERROR|X|cmd|pid=8913178.1| owls_cmd_return | Can not connect to server. Error!
| 2023-03-14 15:45:02 |ERROR|X|DQM|pid=11403684.1| o_connect_auth | k_connect_auth_timeout returns error [200]
| 2023-03-14 15:45:02 |ERROR|X|DQM|pid=11403684.1| u_io_callsrv_connect_r | Error connecting to target IO server: Errno syserror 79: Connection refused (connect returns error)
| 2023-03-14 15:45:03 |ERROR|X|cmd|pid=10682814.1| owls_connect_auth | k_connect_auth_timeout(nodename/SIO) returns error [200]
| 2023-03-14 15:45:03 |ERROR|X|cmd|pid=10682814.1| o_callsrv_connect_r | Connection error 79 [Errno syserror 79: A remote host refused an attempted connect operation.]
| 2023-03-14 15:45:03 |ERROR|X|cmd|pid=10682814.1| owls_cmd_return | Can not connect to server. Error!
| 2023-03-14 15:45:03 |ERROR|X|DQM|pid=11403684.1| o_connect_auth | k_connect_auth_timeout returns error [200]
| 2023-03-14 15:45:03 |ERROR|X|DQM|pid=11403684.1| u_io_callsrv_connect_r | Error connecting to target IO server: Errno syserror 79: Connection refused (connect returns error)
| 2023-03-14 15:45:04 |ERROR|X|cmd|pid=10879244.1| owls_connect_auth | k_connect_auth_timeout(nodename/SIO) returns error [200]
| 2023-03-14 15:45:04 |ERROR|X|cmd|pid=10879244.1| o_callsrv_connect_r | Connection error 79 [Errno syserror 79: A remote host refused an attempted connect operation.]
| 2023-03-14 15:45:04 |ERROR|X|cmd|pid=10879244.1| owls_cmd_return | Can not connect to server. Error!
| 2023-03-14 15:45:04 |ERROR|X|DQM|pid=11403684.1| o_connect_auth | k_connect_auth_timeout returns error [200]
| 2023-03-14 15:45:04 |ERROR|X|DQM|pid=11403684.1| u_io_callsrv_connect_r | Error connecting to target IO server: Errno syserror 79: Connection refused (connect returns error)
| 2023-03-14 15:45:04 |ERROR|X|DQM|pid=11403684.1| o_io_perm_link_create | Cannot establish connection to the IO server: o_connect_auth returns -1
| 2023-03-14 15:45:04 |ERROR|X|DQM|pid=11403684.1| o_io_perm_link_init | Cannot establish connection to the IO server. o_io_perm_link_create returns -1
| 2023-03-14 15:45:04 |ERROR|X|DQM|pid=11403684.1| o_ouv_serv | o_io_perm_cnx_thread_create returns [-1]
| 2023-03-14 15:45:04 |ERROR|X|DQM|pid=11403684.1| u_dqm_srv_thread_main | Error opening service:
| 2023-03-14 15:45:04 |INFO |X|DQM|pid=11403684.1| u_dqm_srv_end | End of server
Only if we start the node in maintenance mode via the command "unistart -m", the IO X remains started but ALL other processes won't be able to connect to the IO X server so they won't start.
Environment
Release : 6.x and 7.x
OS: Unix/Linux
Component: Dollar Universe Application Server (Node)
Cause
Duplicated entry in the /etc/hosts file for the system name, the first entry (in bold) pointing to a wrong IP adress that did not correspond to the local ip adress of the server hostname.
xxx.xxx.xxx.xxx server_local_hostname
yyy.yyy.yyy.yyy server_local_hostname
As a result, the other Processes such as DQM and the commands would use a wrong IP to connect to the IO X Server which failed.
Resolution
Make sure that there are no wrong lines in /etc/hosts file regarding the local hostname and that the DNS record of the server is also correct.
Additional Information
Workaround:
Set the variable U_CLUSTER to the value Y before starting the node
$UNI_DIR_EXEC/unisetvar U_CLUSTER Y
Nevertheless, this should not be necessary, this forces the processes to listen/use only the IP corresponding to the U_LOCALHOSTNAME variable defined in values.xml
Feedback
