11-26-2012 11:10 PM - edited 03-16-2019 02:24 PM
Hello everyone!
Recently when performing backup on CUCM 8 it goes to 69% and then stops. On status windows I see:
CCM | CUCS8 | REPORTER | 0 | ERROR |
Log file says:
Server : CUCS8
Feature : CCM
Component : REPORTER
Time Completed: 2012-11-27-02-56-09
Result Code : 3-Backup failed
Result String : ERROR
=====================================================
2012/11/27 02:56: du -sckL /var/log/active/cm/report/rtmtreporter | grep total | awk '{print $1}'
2012/11/27 02:56: Free space on /common/drf = 27516600 KB, required space on /var/log/active/cm/report/rtmtreporter = 9536 KB
2012/11/27 02:56: Ready for backup
/var/log/active/cm/report/rtmtreporter/
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_23_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_20_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_22_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_24_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_19_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_26_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_25_2012.pdf
/var/log/active/cm/report/rtmtreporter/CallActivitiesRep/CallActivitiesRep_11_21_2012.pdf
/var/log/active/cm/report/rtmtreporter/DeviceRep/
/var/log/active/cm/report/rtmtreporter/DeviceRep/DeviceRep_11_22_2012.pdf
/var/log/active/cm/report/rtmtreporter/DeviceRep/DeviceRep_11_21_2012.pdf
/var/log/active/cm/report/rtmtreporter/DeviceRep/DeviceRep_11_25_2012.pdf
/var/log/active/cm/report/rtmtreporter/DeviceRep/DeviceRep_11_24_2012.pdf
/var/log/active/cm/report/rtmtreporter/DeviceRep/DeviceRep_11_19_2012.pdf
/var/log/active/cm/report/rtmtreporter/DeviceRep/DeviceRep_11_26_2012.pdf
tar: -: Wrote only 8192 of 10240 bytes
tar: Error is not recoverable: exiting now
2012/11/27 02:56: Backup failed.
----> BEGIN Standard Output
----> END Standard Output
----> BEGIN Standard Error
error writing output file
----> END Standard Error
What can cause this error?
Thank you in advance!
11-27-2012 01:36 AM
That definitely helped. However, I am looking at the logs and they are incomplete. You provided me with only one log file from both services. I require the next 2 files for each of these components as well to continue analyzing. So far there are no errors and everything is clean. So the failure is happening in the later files which I need.
Regards,
Harmit.
11-27-2012 05:42 AM
I have just performed a manual back up and it went through.. This is strange..
11-27-2012 05:50 AM
Guess I scared the problem away with all the logs I kept asking for :-)
Keep an eye on it. If it fails again, you know what's needed to dig deeper.
Regards,
Harmit.
11-27-2012 05:51 AM
Thank you!
11-27-2012 05:52 AM
Just so you know, here are the components the server was trying to backup:
2012-11-27 04:43:02,345 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: SYSLOGAGT
2012-11-27 04:43:02,346 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: PLATFORM
2012-11-27 04:43:02,346 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: CLM
2012-11-27 04:43:02,346 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: CDPAGT
2012-11-27 04:43:02,347 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: CCMPREFS
2012-11-27 04:43:02,347 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: CCMDB
2012-11-27 04:43:02,347 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: TCT
2012-11-27 04:43:02,348 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: CEF
2012-11-27 04:43:02,348 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: BAT
2012-11-27 04:43:02,348 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: REPORTER
2012-11-27 04:43:02,348 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: MOH
2012-11-27 04:43:02,349 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: TFTP
2012-11-27 04:43:02,349 INFO [NetMessageDispatch] - {STATE_IDLE} drfBackup:BuildComponentScript(Device=-): Processing component: ANN
The logs showed it had successfully backed up till the CCMPREFS component, after which the log file ended:
2012-11-27 04:43:08,295 DEBUG [NetMessageDispatch] - {STATE_BACKUP_SERVER_DIRECT} drfBackup:HandleResponse_RES(Device=-):
Feature : CCM
Server : CUCS8
Component : CCMPREFS
Result Code : 0-null
Result String: SUCCESS
Stderr :
So the next set of log files would have given us more clarity for the failure as there were several more components to get backed up still.
Regards,
Harmit.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide