White Papers
Abstract
Error: SOLID Communication Error 21306: Server 'tcp 6001' not found, connection failed.
Content
Configuration Manager Database (CMDB) on VIO Server failure causes.
Steps to resolve SOLID Communication Error 21306.
Overview Of CMDB:
Steps to resolve SOLID Communication Error 21306.
Overview Of CMDB:
https://www.ibm.com/docs/en/control-desk/7.6.1.x?topic=overview-configuration-management-database
Log files to check from snap data:
a) ./svCollect/CM_DB/solexp.stdout
b) ./svCollect/viod_CM.log
c) ./svCollect/viod.log
d) ./kernel/kernel.snap
1) Checking for vio_daemon in kernel/kernel.snap if process is active or inoperative.
Under the "lssrc -a" date collection stanza.
vio_daemon 3333333 active
2) In the kernel/kernel.snap check that the "solid" process is running.
Under the "ps -ef" data collection stanza.
# grep -e bin/solid -e sbin/vio_daemon -e vio_chgmgt kernel/kernel.snap
root 3333333 2222222 /usr/sbin/vio_daemon -d 4
root 5555555 4444444 /usr/ios/db/bin/solid -f -c /home/ios/CM/DB
root 4444444 3333333 vio_chgmgt
3) Check when the last time
"Stopped due to Fatal Error" is reported in ./svCollect/viod_CM.log
# grep "Stopped due to Fatal Error" ./svCollect/viod_CM.log
Mar 26 2018, 20:19:08 0x102 viod_chg_notify.c 1.54 1737
ERR Q Stopped due to Fatal Error. kill -1 <vio_chgmgt PID> to restart Q
On the VIO Server, checking if CMDB is working.
Each of the below commands are run on the live VIO Server from within "oem_setup_env"
environment, indicated by the "#" prompt.
1) Check to make sure vio_daemon is operating correctly.
The "Node ID" will be populated if "vio_daemon" is operating correctly.
# lssrc -ls vio_daemon
Node ID: 6b383002484511e68004e41f13fb7929
Log File: /home/ios/logs/viod.log
VSP Socket: 0
AF family: 0
Port:
Addr:
VKE Kernel Socket: 4
VKE Daemon Socket: 5
Bound to : /home/ios/socks/vioke_unix
API Socket: 8
Bound to : /home/ios/socks/api_eve_unix
2) Check that "solid" file exists.
# ls -l /usr/ios/db/bin/solid*
-r-xr-xr-x 1 root system 11171153 Jul 24 2015 /usr/ios/db/bin/solid
-r-xr-xr-x 1 root system 12628915 Jul 24 2015 /usr/ios/db/bin/solidhac
-r-xr-xr-x 1 root system 7791 Jul 24 2015 /usr/ios/db/bin/solidsma
If the "solid" file does not exist escalation is required
for additional debugging and tracing.
3) Check that "solidb" is running.
Log files to check from snap data:
a) ./svCollect/CM_DB/solexp.stdout
b) ./svCollect/viod_CM.log
c) ./svCollect/viod.log
d) ./kernel/kernel.snap
1) Checking for vio_daemon in kernel/kernel.snap if process is active or inoperative.
Under the "lssrc -a" date collection stanza.
vio_daemon 3333333 active
2) In the kernel/kernel.snap check that the "solid" process is running.
Under the "ps -ef" data collection stanza.
# grep -e bin/solid -e sbin/vio_daemon -e vio_chgmgt kernel/kernel.snap
root 3333333 2222222 /usr/sbin/vio_daemon -d 4
root 5555555 4444444 /usr/ios/db/bin/solid -f -c /home/ios/CM/DB
root 4444444 3333333 vio_chgmgt
3) Check when the last time
"Stopped due to Fatal Error" is reported in ./svCollect/viod_CM.log
# grep "Stopped due to Fatal Error" ./svCollect/viod_CM.log
Mar 26 2018, 20:19:08 0x102 viod_chg_notify.c 1.54 1737
ERR Q Stopped due to Fatal Error. kill -1 <vio_chgmgt PID> to restart Q
On the VIO Server, checking if CMDB is working.
Each of the below commands are run on the live VIO Server from within "oem_setup_env"
environment, indicated by the "#" prompt.
1) Check to make sure vio_daemon is operating correctly.
The "Node ID" will be populated if "vio_daemon" is operating correctly.
# lssrc -ls vio_daemon
Node ID: 6b383002484511e68004e41f13fb7929
Log File: /home/ios/logs/viod.log
VSP Socket: 0
AF family: 0
Port:
Addr:
VKE Kernel Socket: 4
VKE Daemon Socket: 5
Bound to : /home/ios/socks/vioke_unix
API Socket: 8
Bound to : /home/ios/socks/api_eve_unix
2) Check that "solid" file exists.
# ls -l /usr/ios/db/bin/solid*
-r-xr-xr-x 1 root system 11171153 Jul 24 2015 /usr/ios/db/bin/solid
-r-xr-xr-x 1 root system 12628915 Jul 24 2015 /usr/ios/db/bin/solidhac
-r-xr-xr-x 1 root system 7791 Jul 24 2015 /usr/ios/db/bin/solidsma
If the "solid" file does not exist escalation is required
for additional debugging and tracing.
3) Check that "solidb" is running.
# ps -ef | grep solid
root 10485848 10551382 /usr/ios/db/bin/solid -f -c /home/ios/CM/DB
a) If "solid" is NOT running, no output will be displayed from above command.
Run "lssrc -ls vio_daemon" to get possible reason why it is not running.
# lssrc -ls vio_daemon
0513-036 The request could not be passed to the vio_daemon subsystem.
Start the subsystem and try your command again.
If error "0513-036" reported, re-start vio_daemon using:
# startsrc -s vio_daemon
0513-059 The vio_daemon Subsystem has been started. Subsystem PID is 6422600.
Note: If the "vio_daemon" does not start or an error other than "0513-036" is reported, then escalation is required for additional debugging and tracing.
4) Check to see if you can access port 6001 using below query.
# /usr/ios/db/bin/solsql -x outputsql -e "SELECT * FROM TABLES"
-o /tmp/24055.100.838.cmdb_tables.out "tcp 6001" viosadmin _k2defPasswd ;
Note: The ";" at the end of the above command is required.
If CMDB it is working, the command will list the tables and how many rows fetched.
Example below.
IBM solidDB SQL Editor (teletype) - Version: 6.5.0.19 Build 2015-05-07
Copyright UNICOM Systems, Inc. 1993, 2014.
TABLE_CATALOG TABLE_SCHEMA TABLE_NAME TABLE_TYPE REMARKS
VIOSCM _SYSTEM SYS_TABLES BASE TABLE NULL
141 rows fetched.
If CMDB is NOT operative, "/usr/ios/db/bin/solsql" command will error.
Sample:
IBM solidDB SQL Editor (teletype) - Version: 6.5.0.19 Build 2015-05-07
Copyright UNICOM Systems, Inc. 1993, 2014.
Error HY000: SOLID Communication Error 21306: Server 'tcp 6001' not found, connection failed
If you get the "Error HY000:" there are few common configuration problems to check.
If any of the common configuration problems are discovered then the vio_daemon will need to be stopped and restarted.
a) Possible configuration in /etc/hosts.
Check for duplicate hostname or IP address.
b) Check that the /etc/hosts file has the following entry.
127.0.0.1 loopback localhost # loopback (lo0) name/address
c) Check the /etc/netsvc.conf file includes below line at end of the file.
hosts=local,bind4
d) Check to make sure /etc/services file has the solid ports listed.
solid 3801/tcp
If a common configuration problem was discovered and corrected then stop and restart the vio_daemon.
# stopsrc -s vio_daemon
# startsrc -s vio_daemon
0513-059 The vio_daemon Subsystem has been started.
Subsystem PID is 6422600.
Additional checks to make sure that localhost IP resolves correctly:
- # host ip_address
- # host hostname
- # host localhost ( this should return for IPV4: 127.0.0.1 )
If the "vio_daemon" does not start then escalation is required for additional debugging and tracing.
Contact support for further assistance if necessary after running "cleanup_cmdb_with_logging.sh" on VIO Server.
Location of "cleanup_cmdb_with_logging.sh" script:
https://public.dhe.ibm.com/systems/virtualization/vio/ztools/CMDB/cleanup_cmdb_with_logging.sh
$ oem_setup_env
# ./cleanup_cmdb_with_logging.sh
If this does not restart "vio_daemon" process then escalation is required for additional debugging and tracing.
[{"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"}],"Version":"2.2.5;2.2.4;2.2.3;2.2.2","Edition":"Enterprise;Express;Standard","Line of Business":{"code":"LOB57","label":"Power"}}]
Was this topic helpful?
Document Information
Modified date:
06 July 2023
UID
isg3T7000745