S8500 Full Backup failing 1

[glimma]

I have an s8500c, CM 3.1.2 which has a scheduled Full backup to an ftp server, which is failing.

If I try to run the scheduled backup I get the following error message:

backup: 10: Fatal error received from pre_backup routine for full; see log file
backup: 10: pre_backup for full failed -- Backup terminated for full
Performing ERROR RECOVERY, please wait.....
Can't locate object method "quit" via package "ftp" (perhaps you forgot to load "ftp"?) at /opt/ecs/sbin/backup line 3388.

However if I run a backup to the same ftp server and select Translations, System Files and Security Files, the backup completes successfully.

The system has no patches installed on it, so I'm organising to reboot the server and install the latest 3.1.2 patches.

Has anybody seen this issue before?

Cheers.

 

[AvayaTier3]

the logfiles should tell you why the failure

backup: 10: Fatal error received from pre_backup routine for full; see log file


A server reboot will most likely resolve this. And, an upgrade to cm3.1.5 which is the latest cm3 or to a higher cm4 or cm5 may resolve this permanently.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[glimma]

Which log files? Where will I find them?

 

[AvayaTier3]

dadmin@server2> cd /var/tmp/backups
dadmin@server2> ls -ltr
total 60
-rw-r--r--  1 root root 168 Apr 15 01:11 server2.011001-20090415.2204
-rw-r--r--  1 root root 169 Apr 16 01:11 server2.011001-20090416.14824
-rw-r--r--  1 root root 169 Apr 17 01:11 server2.011002-20090417.27422
-rw-r--r--  1 root root 168 Apr 18 01:11 server2.011001-20090418.7547
-rw-r--r--  1 root root 169 Apr 19 01:11 server2.011001-20090419.20207
-rw-r--r--  1 root root 169 Apr 20 01:11 server2.011001-20090420.15481
-rw-r--r--  1 root root 169 Apr 21 01:11 server2.011001-20090421.28378
-rw-r--r--  1 root root 168 Apr 22 01:11 server2.011001-20090422.8988
-rw-r--r--  1 root root 169 Apr 23 01:11 server2.011001-20090423.22033
-rw-r--r--  1 root root 168 Apr 24 01:11 server2.011001-20090424.2449
-rw-r--r--  1 root root 169 Apr 25 01:11 server2.011001-20090425.15803
-rw-r--r--  1 root root 169 Apr 26 01:11 server2.011001-20090426.28040
-rw-r--r--  1 root root 169 Apr 27 01:11 server2.011001-20090427.23541
-rw-r--r--  1 root root 168 Apr 28 01:11 server2.011001-20090428.4264
-rw-r--r--  1 root root 169 Apr 29 01:11 server2.011001-20090429.17286
dadmin@server2> cat server2.011001-20090429.17286
THEPID is: 17291
backup: 0: BACKUP SUCCESSFUL for full backup set, SCP to 135.122.38.100. 
backup: backup image - /home/cmbackups/server/full_server2_011002_20090429.tar.g
z

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[glimma]

Thanks AvayaTier3,

This is what I get:

dadmin@server1> cat server1.103710-20090429.5204
backup: 10: Fatal error received from pre_backup routine for full; see log file
backup: 10: pre_backup for full failed -- Backup terminated for full
Performing ERROR RECOVERY, please wait.....
Can't locate object method "quit" via package "ftp" (perhaps you forgot to load
"ftp"?) at /opt/ecs/sbin/backup line 3388.


It still doesn't say what caused the backup to fail.

It does say "see log file" but I don't know which log file I need or where it is saved.

 

[AvayaTier3]

cd /var/log/ecs

ls -ltr

logfile will have a timestamp closest to the after failure time.



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[glimma]

OK I've downloaded the log file, but what do you use to read the file?

I've opened it in notepad but it's impossible to read.

 

[phoneguy55]

start with the reboot and go from there.

 

[AvayaTier3]

don't take the file off the server. Use linux commands to look at the logfile

to view the complete file:
vi filename.log

to view every line in the file with back somewhere in the line:
grep back filename.log


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[phonebiz]

PSN001052u covers this issue. It was fixed in 3.13. I agree with bsh upgrade to 3.15 or risk having to deal with it again.