Guest

Preview Tool

Cisco Bug: CSCur42250 - DTACS migrate script fails if ssh needs to be restarted, needs to sleep

Last Modified

Feb 09, 2017

Products (1)

  • Headend System Releases

Known Affected Releases

UPcore-5.0.30

Description (partial)

Symptom:
DTACS 4.0 upgrade fails

INFO: cmd outPut: Warning: Permanently added '10.251.68.211' (RSA) to the list of known hosts.

|-----------------------------------------------------------------|
| This system is for the use of authorized users only.            |
| To protect the system from unauthorized use and to ensure the   |
| system is functioning properly, activities on this system are   |
| monitored and recorded.                                         |
|                                                                 |
| Anyone using this system expressly consents to such monitoring  |
| and recording.  If such monitoring reveals possible             |
| evidence of criminal activity, system personnel may provide the |
| evidence of such monitoring to law enforcement officials and    |
| it could lead to criminal and civil penalties.                  |
|                                                                 |
| Please note that "dncs" user is now a Role and you can't login  |
| as "dncs" user.  Please contact your sysadmin for a login id.   |
|-----------------------------------------------------------------|

INFO: Setting up RSA keys on Source-Host...
INFO: Enabling root login on Source-Host...
INFO: Enabling root login...
INFO: Adding RSA key to authorized keys on Source-Host...
INFO: Executing command: addRsaKey Destination-Host
INFO: cmd outPut: INFO: Adding RSA key to authorized keys on Destination-Host...

ERROR:
ERROR: Unable to execute SSH command as root on the DTACS.
ERROR: Remote SSH root logins MUST be enabled on your DTACS!
ERROR:
Failed to migrate keyfiles: Illegal seek
#

Conditions:
DTACS migrate script determines the sshd_config file needs to be updated and then restarts sshd on the Sparc DTACS
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.