Feb 3 02:00:01 admnpr01 ssh-server-g3: 723 Keyboard_interactive_password_auth_error, Username: callmgr, Algorithm: password, "Could not exchange kbdint messages.", Session-Id: 6BF68A81CC5DC02752471F14BF4D97CEF5C5B403
Feb 3 02:00:01 admnpr01 ssh-server-g3: 723 Keyboard_interactive_password_auth_error, Username: callmgr, Algorithm: password, "Authentication failed for user `callmgr'.", Session-Id: 6BF68A81CC5DC02752471F14BF4D97CEF5C5B403
Detail from the logs which shows faiklures (f) and successes (s):
start key kbi fail kbi success login failure end copy
6BF68A81CC5DC02752471F14BF4D97CEF5C5B403 02:00:00 02:00:00 02:00:01 02:00:03 f
2359534D645D04D8A69B28F2421B53F5041BB8E3 02:00:01 02:00:02 02:00:03 s
27F3D091381898908F1DAD7DF81F25E33431B864 02:00:03 02:00:03 02:00:04 02:00:06 f
497C6EDFD6738EBB0F5A2D68E38FB990114060F7 02:00:04 02:00:05 02:00:06 s
As best i can tell, CUCM is trying to use a key to authenticate (fails) then tries kbi (Keyboard Interface) and fails. Then it trys kbi again and manages to successfully connect.... :o)
Can anyone shed light on what the default 6.1(2) backup tries to do? I thought it only used ssh with a username/password that we have set from the Backup GUI. The Unix sftp server logs would suggest it is trying a key, then username password, then username password again ?
Any ideas appreciated. 5 unsuccessful logins in a row lock the account on the sftp server - doh!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...