"Net Retry" on a client all of a sudden?

[Maser]

So, one of my users -- has been backing up daily with no trouble -- all of a sudden gives me a "Net Retry" every time I connect.

 

System.log on the client shows:

 

Dec 10 14:49:49 falcon ReportCrash[166]: [CrashReport _initWithTask...] caught exception: Non-contiguous memory does not support view (\n 9036107,\n 12435003,\n 752152,\n 730168,\n 727436,\n 727287,\n 813148,\n 812400,\n 794697,\n 11892,\n 38050,\n 46548,\n 45345,\n 10723367,\n 43048,\n 10542969,\n 10542646\n)

Dec 10 14:49:49 falcon ReportCrash[166]: Formulating crash report for process retropds.24[165]

Dec 10 14:49:49 falcon ReportCrash[166]: Saved crashreport to /Library/Logs/CrashReporter/retropds.24_2008-12-10-144949_crash using uid: 0 gid: 0, euid: 0 egid: 0

 

 

and the crash logs look like:

 

Process: retropds.24 [165]

Path: retropds.24

Identifier: retropds.24

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: retroclient [72]

 

Date/Time: 2008-12-10 14:49:49.116 -0500

OS Version: Mac OS X 10.5.5 (9F2114)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c0000000

Crashed Thread: Unknown

 

Error Formulating Crash Report:

Non-contiguous memory does not support view

0x0089e14b

0x00bdbe3b

0x000b7a18

0x000b2438

0x000b198c

0x000b18f7

0x000c685c

0x000c6570

0x000c2049

0x00002e74

0x000094a2

0x0000b5d4

0x0000b121

0x00a3a027

0x0000a828

0x00a0df79

0x00a0de36

 

Backtrace not available

 

Unknown thread crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0x000171ca ecx: 0xbfffffc8 edx: 0x00000004

edi: 0xc0000000 esi: 0xbfffc27b ebp: 0xbfffc258 esp: 0xbfffc128

ss: 0x0000001f efl: 0x00010246 eip: 0x0052d2e7 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0xc0000000

 

Binary images description not available

 

 

 

 

Any thoughts here? Never seen this one.

 

And I'm running the current .234 client...

 

 

 

Edited December 10, 2008 by Guest

[CallMeDave]

Is retropds.24 crashing on each attempt to backup, giving you multiple .../CrashReporter/retropds.24_ logs?

 

- When in the sequence of your events does it crash? You say "every time I connect;" what exactly does that mean?

- What have you done in an effort to address this?

- Has retroclient been restarted?

- Has the Macintosh been restarted?

[Maser]

That is correct -- every time the backup server hit that machine (90 minute retry) it would generate this error message. Machine was restarted. Client was uninstalled and reinstalled.

 

 

And I should get a T-Shirt for figuring out what the problem was....

 

 

My client was set up to only back up the "Users" folder as a subvolume. No other volumes were selected.

 

HOWEVER, the user had a CD in the computer.

 

The CD had an extremely long name -- over 115 characters (not sure how it was created.)

 

So, long, that viewing the /Volumes folder in Terminal only shows the first 69 (?) characters of the name.

 

Ejecting the CD? Backup worked.

 

That was the only difference.

 

(This must be a 10.5 issue -- with the CD in, I could not move the CD icon, or copy any files off the CD -- though I could read the files on the CD.)

 

Go figure.

Edited December 10, 2008 by Guest