Home > Cannot Connect > Cannot Connect To A Hub Monitoring Server At Addresses

Cannot Connect To A Hub Monitoring Server At Addresses

This problem was fixed by making changes to the access list file kshxhubs.xml by changing the user to use their short login name. Document information More support for: IBM Tivoli Monitoring V6 ITM Tivoli Enterprise Mgmt Server V6 Software version: All Versions Operating system(s): z/OS Reference #: 1394903 Modified date: 09 July 2010 Site Watson Product Search Search None of the above, continue with my search tacmd login fails - Error message "KUIC00003E: tacmd login; KUIC00003E; Cannot connect to a hub monitoring server at addresses Resolving the problem Make sure that, you are able to ping the z/OS LPAR from current environment Make sure that, you are able to telnet to the z/OS LPAR from the news

KUIC00006E: The specified user name or password is incorrect. The http/https listening port can be found from the monitoring server RKLVLOG. Refer the below trace to identify the listening port (0018-E8FAEE63:kdhslqm.c,188,"add_listener") listening: ip.tcp.http:yyyyy where yyyy listening port other than the default port 1920 or 3661 Also, make sure that the XML definition Refresh the page to continue. https://www.ibm.com/developerworks/community/wikis/home/wiki/Troubleshoot%20tacmd%20login%20KUIC00003E%20Cannot%20connect%20to%20a%20hub%20monitoring%20server

The same can happen to the HTTPS port 3661. Use the valid RACF z/OS user id and password if you are still unable to login, please set the below trace on KDSENV member, recycle TEMS KBB_RAS1=ERROR (UNIT:KSH ALL) and Also, KUIC00003E: Cannot connect to a hub monitoring server at addresses: https://xxxxxx:3661] Make sure the hub monitoring server on xxxxxxx01 is available and configured for the specified protocols and ports. APAR status Closed as program error.

Show: 10 25 50 100 items per page Previous Next Feed for this topic United States English English IBM® Site map IBM IBM Support Check here to start a new This means that if the SUID bit is set for any application then your user ID would be set as that of the owner of application/file rather than the current user, Updated on 2011-09-05T21:33:38Z at 2011-09-05T21:33:38Z by julieb julieb 20000006Y4 14 Posts Re: can't login with TACMD with error KUIC00003E ‏2011-09-05T21:33:38Z This is the accepted answer. Log in to reply.

execute ./SetPerm -s to set the Set User ID (SUID) bit The -s (Optional) Used to set security validation on selected monitoring servers. Here is example of the message that will occur when tacmd login fails [ note, there are other reasons that can cause tacmd login to present this same message] : ~ Watson Product Search Search None of the above, continue with my search tacmd login fails, KUIC00003E KUIC00003E tacmd login Technote (troubleshooting) Problem(Abstract) When running tacmd login, the following errors occurs: KUIC00003E: read this post here Turn on JavaScript JavaScript has been disabled in your web browser.

SUID stands for Set User ID. Since the SUID bit tells Linux that the User ID root is set for this application and whenever this application executes it must execute as if root was executing it (since APAR status Closed as program error. This is the incorrect connection error: KUIC00003E: Cannot connect to a hub monitoring server at addresses: https:/// This error message might be hiding the face that the problem is validation related,

Local fix N/A Problem summary If SOAP security is configured, tacmd login returns an incorrect message, stating error on CONNECTION, for non-authorized users. this Watson Product Search Search None of the above, continue with my search tacmd login fails with invalid user id and password tacmd login; SUID; ./SetPerm -s; Verify the correct user name Resolving the problem After adding KDEB_INTERFACELIST=!x.x.x.x to ms.config (x.x.x.x is the IP ADDRESS from the error) STOPPING TEMS Waiting 5 minutes STARTING TEMS tacmd login was successful Historical Number 46875 057 Instead of the error text talking about a connection problem, the customer feels that the error message should provide a better description of the actual problem (something like "not authorized" instead

KUIC00006E: The specified user name or password is incorrect. http://electrictricycle.net/cannot-connect/cannot-connect-to-default-server-host-check-pbs-server.html Wikis requires JavaScript in order to function. Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility Watson Product Search Search None of the above, continue with my search IZ68369: INCORRECT TACMD LOGIN ERROR MESSAGE FOR NOT AUTHORIZED USERS ON TEMS Fixes are available IBM Tivoli Monitoring 6.2.1

Reconfigure the HUB TEMS using root id but TEMS can be started using non-root user id. Topic Forum Directory >‎ IBM Tivoli Monitoring (ITM) >‎ Forum: IBM Tivoli Monitoring (ITM) General Discussion >‎ Topic: can't login with TACMD with error KUIC00003E 1 reply Latest Post - ‏2011-09-05T21:33:38Z Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility United States English English IBM® Site map IBM IBM Support Check here to More about the author However, the error received when doing this does not match the actual problem.

Unanswered question This question has not been answered yet. There are two prerequisites for this APAR to occur : (1) hub monitoring server has been configured with 'Security: Validate User ?=yes' (2) hub monitoring server must be running on AIX, You may need to add the additional users to the member access list of the SOAP authorization file: Windows : %CANDLEHOME%\cms\HTML\kshxhubs.html Linux/UNIX : /tables//HTML/kshxhubs.xml z/OS KSHXHUBS member of RKANPARU dataset Log

error=26 status=8 (4E414692.0013-1:kdsvlunx.c,1253,"lockouts") Exit: 0x8 (4E414692.0014-1:kdsvlunx.c,343,"kdsvlunx") getspnam failed for itmuser.err = 13 (4E414692.0015-1:kdsvlunx.c,545,"kdsvlunx") Exit: 0x5 Diagnosing the problem To diagnose the problem, set the below trace on HUB TEMS config file

Validating user... Comments APAR Information APAR numberIZ68369 Reported component nameTEMS Reported component ID5724C04MS Reported release621 StatusCLOSED PER PENoPE HIPERNoHIPER Special AttentionNoSpecatt Submitted date2010-01-20 Closed date2010-04-27 Last modified date2010-07-23 APAR is sysrouted FROM one more detail about SUID.. I could login tacmd with sysadmin successfully.

The resulting effect is tacmd is comparing the entered password against different userID's password and thus the failure to authenticate entered for entered . Once you have turned it on, please refresh the page. KUIC00003E: Cannot connect to a hub monitoring server at addresses: https://abcxyz:3661 Make sure the hub monitoring server on abcxyz is available and configured for the specified protocols and ports. ~ ~ click site However, when I try to login tacmd with another administrative account which has admin right, the below error appears.

Cause Service index function is broken between the ITM components Resolving the problem The owner of the base HTTP port 1920 has lost its linkage to the TEMS HTTP port, making Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility United States English English IBM® Site map IBM IBM Support Check here to Document information More support for: IBM Tivoli Monitoring V6 ITM Tivoli Enterprise Mgmt Server V6 Software version: All Versions Operating system(s): Linux Software edition: All Editions Reference #: 1572403 Modified date: According to the document, if you are configuring user security, you should use root login ID to configure. 2.

If you are unable to recycle the ITM components, as a work around, you can use the below command: tacmd login -s https:// : The http/https listening port for the TEMS To re-establish the linkage all ITM applications running on the TEMS server must be stopped, and start the TEMS first, so that it acquire the ports 1920/3661. Watson Product Search Search None of the above, continue with my search Problem executing tacmd login command against z/OS Tivoli Enterprise Monitoring Server (TEMS) tacmd; login; z/OS; KUIC00003E; tacmd login; ITM_TEMS_CONFIG