While executing jobs in Solaris we could see the below error and the job aborts
-1 - wrong message type
U0009909 TRACE: (wrong type error) 1008c57c0 01268
00000000 53455353 494F4E5F 4552524F 52000000 >SESSION_ERROR...<
00000010 00000000 00000000 00000000 00000000 >................<
00000020 2A414745 4E540000 00000000 00000000 >*AGENT..........<
00000030= 00000000 00000000 00000000 00000000 >................<
00000060 00000000 00000001 31302E37 2E38362E >........xx.x.xx.<
00000070 3136343A 35303230 31000000 00000000 >xxx:xxxx.......<
00000080= 00000000 00000000 00000000 00000000 >................<
000000E0 00000000 00000000 00000000 00000001 >................<
000000F0 001E85B9 2A414745 4E547C54 4C532D68 >....*AGENT|TLS-h<
00000100 616E6473 68616B65 2F312873 74726561 >andshake/1(strea<
00000110 6D207472 756E6361 74656429 00000000 >m truncated)....<
00000120= 00000000 00000000 00000000 00000000 >................<
000004F0 00000000 >....<
Release : 21.x
Component: Automation Engine
Sub-Component: Agent Unix/Linux
This happens if the c-function getaddrinfo is only returning localhost for the agent instance - which means only this would be trusted
If the job executed uses a different IP then this conflicts and is not accepted due to the TLS security.
This can be seen in the agent log ( as shown below the agent only returns the localhost )
=========================================================
U02000066 Host information: Host name='xxxxxxxxxx', IP address='127.0.0.1'
U02000066 Host information: Host name='xxxxxxxxxx', IP address='::ffff:127.0.0.1'
U02000066 Host information: Host name='xxxxxxxxxx', IP address='::1'
=========================================================
You can make use of the Trusted IP's section of the agent from client 0.
Client 0 --> Administration --> <AGENT> --> Open --> Attributes --> Trusted IPs
[OR]
You can set this within the config file:
UC_EX_JOB_MD_IP_ADDR = 127.0.0.1 (or) UC_EX_JOB_MD_IP_ADDR = localhost