Error Unable To Sftp From /common/drf
Contents |
CommunicationsCisco Unified Communications Manager (CallManager)Troubleshoot and AlertsTroubleshooting TechNotes Cisco Unified Communications Manager 7.x/8.x: Troubleshoot Backup Issue Download Print Available Languages Download Options PDF (15.3 KB) View with Adobe Reader on a cisco drf variety of devices Updated:Apr 03, 2012 Document ID:111796 Contents Introduction Prerequisites Requirements Components
Cisco Drf Failure
Used Conventions Problem Solution Error: Cannot write: Broken pipe DRS Hangs During CCMDB Backup Problem Solution Error: The system is currently unable to send network request to master agent. this may be due to master or local agent being down locked by another process. Please try again later Solution Backup Fails with Winsock Error Solution DRF Backup Does Not Backup Certificates Solution Error Message: bad decrypt 16404:error Solution Error on the backup page unable to contact server. master or local agent could be down on CUCM Problem Solution Unable to Add Backup Device Problem Solution Unable to Restore CUCM 8.x Server Problem Solution Unable to restore CUCM 8.5 Problem Solution Related Information Introduction Cisco Unified Communications Manager backups are not running as scheduled. All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. This document discusses how to troubleshoot this
Freeftpd
issue. Prerequisites Requirements There are no specific requirements for this document. Components Used The information in this document is based on the Cisco Unified Communications Manager 7.1(3)/8.x . The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Problem Cisco Unified Communications Manager backups are not running as scheduled. All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, this error message is received: Status: Local Agent is not responding. This may be due to Master or Local Agent being down. This RTMT alert is received during the backup failure: CiscoDRFFailure Reason : Master Agent was unable to send a backup/restore request to the local agent. Node [ELS-PUB1] is not connected. AppID : Cisco DRF Master ClusterID : NodeID: ELS-pub1 . The alarm is generated on Tue Nov 24 02:00:04 PST 2009 Solution Fir
receive error message. Where to look for the error- It is good to visit RTMT and check recent alerts or may be application logs in syslog veiwer to check the error message. You will see a message like below- Error message: CiscoDRFFailure Reason : DRF was unable to backup component CCMDB.Error : Please check the component logs for further details. Why backup was stuck at CCMDB- We get such an error mainly due to CDR entries in the database, which makes the DB too large http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-71/111796-cucm-drf.html to backup. If you take a look at the CCM DB component logs, you would be seeing similar messages like below- /var/log/active/cm/cdr_repository/preserve/20091230/cmr_Cluster-C_03_200912300317_1559/var/log/active/cm/cdr_repository/preserve/20091230/cdr_Cluster-C_09_200912300317_1562/bin/tar: -: Wrote only 4096 of 10240 bytes/bin/tar: Error is not recoverable: exiting nowCCMDB Backup failed, unable to tar data to master agentRestoring CAR services... Here, we might be hitting a classic bug when DRS gets stuck due to the size of preserved http://debuggingvoip.blogspot.com/2011/09/backup-failure-on-ccmdb.html folder. DRS stuck in CCMDB backup if many CDR files in Preserved folder Symptom: Callmanager 5.1.3 is able to backup the components to SFTP server successfully earlier, but as with the system running and the CDR records starting to build up, the backup start to fail at some stage. Condition: huge set of CDR/CMR files may accumulate in Preserve folders (e.g 110,000) caused a big backup.log file exceeded 1 MB(e.g 20MB) Typical Scneario: Customer does not want to use CAR but using third party billing server instead and CAR loader is disabled, in callmanager 5.1.3, this can result in large number of CDR/CMR accumulated in Preserve folder. Workaround: In 5.1.3 and later Stopping CAR service will not stop accumulating flat CDR Files. To clean up the CDR files temporarily to that DRS can proceed, 1. stop the CDR Agent service on all servers in the cluster, so no new CDR files will be pushed to the publisher. 2. check to make sure all the files have been pushed to the billing server(s), do the following command ls -R /var/log/active/cm/cdr_repository/destination* to make sure there is no symbolic link in any of th
mail ! gmail ! com [Download message RAW] [Attachment #2 (multipart/alternative)] Perfect! Thanks Florian On Thu, Dec 29, 2011 at 2:58 PM, Florian Kroessbacher < florian.kroessbacher@gmail.com> wrote: > hy http://marc.info/?l=cisco-voip&m=132519379904068 > > i think file list tftp * detail > > should do the job from cli > > > Am 29.12.2011 um 20:47 schrieb Ed Leatherman
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 00:12:53 GMT by s_ac15 (squid/3.5.20)