Jump to content
Maser

Leopard issue -- "can't open/create startup file"

Recommended Posts

Hoping for a quick answer here...

 

Updated my 3 Retrospect servers to the latest version and 10.5

 

On one of my systems, when I *quit* Retrospect, I get a dialog box that says:

 

Can't open/create startup file.

 

My other two servers do not do this.

 

 

Any suggestions as to what's generating this and what I need to do to resolve it?

 

Thanks!

 

- Steve

Share this post


Link to post
Share on other sites

I dumped my "retrorun" file from /Library/Preferences/Retrospect (well, I dumped everything besides the "config" file) and that seems to have cleared it up.

 

Thanks!

Share this post


Link to post
Share on other sites

Steve,

 

This is a bit critical (at least to me) because it (corrupt retrorun file) relates to the "failure to autolaunch" bug that supposedly was fixed in 6.1.138, and this has been a recurring PITA (about once or twice a month) for years. Is this something that developed after the update, or is is a corrupt retrorun file that persisted from before the update?

 

Russ

Share this post


Link to post
Share on other sites

I only noticed this (ever) after I did my 10.5/6.1.138 update -- on one of my 3 machines. The other two aren't showing any problems.

 

It only happens when I *quit* Retrospect after these updates.

 

I never noticed it (ever!) on 10.4.x/6.1.126.

Share this post


Link to post
Share on other sites

Oddly, enough -- this came back -- on the machine I "cleaned up" and one of my other two systems that hadn't shown this previously.

 

I've since updated to 10.5.1 and repaired permissions, but it hasn't come back yet.

 

It's *possible* this only occurs after the backup server script has been running (and backing things up) for a number of days.

Share this post


Link to post
Share on other sites

Not sure how I can give you steps to reproduce this, but I can say this happens:

 

1) Went through the URL steps above: http://kb.dantz.com/article.asp?article=5441&p=2

 

2) My computer is a G4 mini with 1G RAM. I have it set to automatically launch Retrospect at computer restart. The backup server script then kicks in after whatever that normal default time is...

 

2) Backup server (the only script I run) is running 24x7. If I let a few computers back up, I can quit the program with no dialog box about the "startup file".

 

3) If I let the computer run for a day (it's about 24 hours since I last rebooted it) after it backs up a number of clients, if I quit the program *at that point*, I get this prompt. I'm not sure exactly what the right number of clients would be (or time passing) before this would happen.

 

The contents of /Library/Preferences/Retrospect looks like this:

 

backupal:preferences admin$ cd Retrospect

backupal:Retrospect admin$ ls -la

total 693544

drwxrwxr-x@ 9 admin admin 306 Nov 20 14:26 .

drwxrwxr-x 37 root admin 1258 Nov 20 13:01 ..

-rwxrwxr-x@ 1 admin admin 6148 Nov 20 14:26 .DS_Store

-rwxr-xr-x@ 1 admin admin 0 Oct 1 1999 Icon?

-rwsrwxr-x 1 root admin 65800 Sep 19 2005 LaunchRetroHlper

-rw-rw----@ 1 root admin 10484574 Nov 20 14:22 Operations Log

-rwxrwxr-x@ 1 root admin 344507392 Nov 20 14:22 Retro.Config (6.0)

-rw-rw----@ 1 root admin 11924 Nov 7 09:02 Retro.Icons (6.0)

-rw-r--r-- 1 root admin 987 Jun 1 2005 device01.rdi

 

 

(including those two files Retrospect files dated 2005).

 

 

NOW: After I restart this computer, I get a different set of files (including "retrorunfile"):

 

backupal:~ admin$ cd /library/preferences/retrospect

backupal:retrospect admin$ ls -la

total 693552

drwxrwxr-x@ 10 admin admin 340 Nov 20 14:33 .

drwxrwxr-x 37 root admin 1258 Nov 20 14:33 ..

-rwxrwxr-x@ 1 admin admin 6148 Nov 20 14:26 .DS_Store

-rwxr-xr-x@ 1 admin admin 0 Oct 1 1999 Icon?

-rwsrwxr-x 1 root admin 65800 Sep 19 2005 LaunchRetroHlper

-rw-rw----@ 1 root admin 10484842 Nov 20 14:34 Operations Log

-rwxrwxr-x@ 1 root admin 344507392 Nov 20 14:32 Retro.Config (6.0)

-rw-rw----@ 1 root admin 11924 Nov 7 09:02 Retro.Icons (6.0)

-rw-r--r-- 1 root admin 987 Jun 1 2005 device01.rdi

-rw-rw----@ 1 root admin 578 Nov 20 14:32 retrorunfile

backupal:retrospect admin$

 

 

 

The two machines I'm seeing this on *only* backup Windows and Linux clients -- mostly Windows clients.

 

I have a third system which only backs up OSX boxes that has *not yet* shown this problem.

 

suggestions? I don't want to have to restart my backup servers every couple of days to resolve this, but something (somehow) is purging the retrorunfile file during the backups.

 

I'll see if I can't keep an eye on when this happens.

 

 

Share this post


Link to post
Share on other sites

Quote:

My computer is a G4 mini with 1G RAM. I have it set to automatically launch Retrospect at computer restart.

 


 

What does this mean, exactly?

 

The only way to have the computer launch an application at system start is by placing something in /Library/StartupItems/

is this something you have done?

 

On the other hand, if you have added the Retrospect application to the list of processes to launch at login, then you have bypassed the need for the retrorunfile anyway, since the purpose of that file is to schedule the program to be launched in advance of pending scripts.

 

This may or may not have anything to do with the error, but knowing exactly how you have things configured can only help to figure it all out.

 

Dave

Share this post


Link to post
Share on other sites

What it means exactly is that I have the Retrospect application in my "Login Items" (along with the default "iTunes Helper") for my account which automatically logs in when I start up the computer.

 

 

(This is the same on all 3 of my backup servers -- including the one that never has shown this problem...)

Share this post


Link to post
Share on other sites

I have never tested having Retrospect launch via the startup items. I am not surprised this causes some sort of confusion for Retrospect.

 

If you are doing this, then I would turn off the RetroRun (using the first few steps of the KB doc) so Retrospect is no longer autolaunching

Share this post


Link to post
Share on other sites

OK. I'll change my Notification to deselect "Automatically launch Retrospect" and my Unattended to "Stay in Retrospect" on the two machines showing this and let you know what happened after the long holiday weekend.

 

But, that all said, I've been doing this setup for years now...

Share this post


Link to post
Share on other sites

Just wanted to add that I'm running almost the exact configuration - 6.1.138 on 10.5.1 Server (on an 8x2.8 Xserve) and have Retrospect in the login items and I'm seeing this error too. Not a big deal itself by I'm also having trouble with the Backup Server losing the media - in this case Files on an iSCSI partiton mounted with GlobalSAN iSCSI. After a running fine for a while it cycles through the backup scripts declaring each one has no media available, and then it writes a bunch of "can't open/create startup file" errors to the log. The backup media is most certainly mounted and available as it does this. Wierd. Its like it suddenly cant see/write to anything.

Share this post


Link to post
Share on other sites

Quote:

The backup media is most certainly mounted and available as it does this

 


 

What happens when you visit Configure->BackupSets->YourBackupSet->Configure...?

Share this post


Link to post
Share on other sites

Good question - I wrote an applescript that quits/relaunches Retrospect every 24 hours and it seems to clear this issue up but I will disable it and check when its in its failed condition.

 

As an aside, I find weekly or even daily restarts clear up a world of glitches when running Retrospect on current hardware. I suspect its more to do with long-term stability of Rosetta than anything as I also have to do it with a couple of PowerPoint 2004 presentations they like to keep up 'round here. Still, I'm looking forward to Retrospect X!

Share this post


Link to post
Share on other sites

New to this board/thread, but I have an issue where the Retro server on a older G4 running Tiger no longer backs up an Intel Imac 10.5; appears to scan 1 folder then hangs. I have gone back and forth turning the client off and on etc. but the server stop sign window still tells me that there are no files to copy; the client warns me that I have not been back up in a month. Do I need a clean install?

Share this post


Link to post
Share on other sites

Hmmm... well two things - 1 my daily relaunch script does not seem to help this issue as much as I'd thought, and 2, in answer to your question, Retrospect terminates without so much as an error message when attempting to configure one of the "missing" backup sets. I was abruptly staring at the desktop! On relaunch, there is nothing in the log. Console.app states in the Console Messages section:

Code:



2/8/08 5:36:41 PM [0x0-0x48048].AuthenticateUser 2008-02-09 01:36:41.044 Retrospect[1997:70b] unable to find nib named: NSNavPanelContentView in bundle path: /System/Library/Frameworks/AppKit.framework/Resources

2/8/08 5:36:41 PM [0x0-0x48048].AuthenticateUser 2008-02-09 01:36:41.092 Retrospect[1997:70b] unable to find nib named: NSNavView in bundle path: /System/Library/Frameworks/AppKit.framework/Resources

2/8/08 5:36:52 PM com.apple.launchd[156] ([0x0-0x88088].AuthenticateUser[4605]) Stray process with PGID equal to this dead job: PID 4610 PPID 4608 sh


And the following under CrashReporter:

Code:



Process: Retrospect [1997]

Path: /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect

Identifier: Retrospect

Version: ??? (???)

Code Type: PPC (Translated)

Parent Process: launchd [1]

 

Date/Time: 2008-02-08 17:36:41.427 -0800

OS Version: Mac OS X Server 10.5.1 (9B2117)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c0000023

Crashed Thread: 0

 

Thread 0 Crashed:

0 ??? 0x816b2a6f 0 + 2171284079

 

Thread 1:

0 ??? 0x800bb8e6 0 + 2148251878

1 ??? 0x800c30dc 0 + 2148282588

2 translate 0xb818b69a CallPPCFunctionAtAddressInt + 202826

3 ??? 0x800ec075 0 + 2148450421

4 ??? 0x800ebf32 0 + 2148450098

 

Thread 2:

0 translate 0xb8152ad4 spin_lock_wrapper + 92328

1 translate 0xb8167d9e CallPPCFunctionAtAddressInt + 57166

2 translate 0xb80df67b 0xb8000000 + 915067

 

Thread 3:

0 translate 0xb8152bc4 spin_lock_wrapper + 92568

1 translate 0xb816c7f5 CallPPCFunctionAtAddressInt + 76197

2 translate 0xb80bd6fb 0xb8000000 + 775931

3 translate 0xb80b6b77 0xb8000000 + 748407

4 translate 0xb80d4530 0xb8000000 + 869680

5 translate 0xb813d2cf spin_lock_wrapper + 4259

 

Thread 4:

0 translate 0xb815298f spin_lock_wrapper + 92003

1 translate 0xb8183603 CallPPCFunctionAtAddressInt + 169907

2 translate 0xb8186194 CallPPCFunctionAtAddressInt + 181060

3 translate 0xb80df67b 0xb8000000 + 915067

 

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0xc0000003 ebx: 0x810e9a54 ecx: 0x2370dbb0 edx: 0x00000000

edi: 0xb81d8794 esi: 0xb81d8770 ebp: 0x8080d180 esp: 0xb7fffacc

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

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

cr2: 0xc0000023

 

Binary Images:

0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate

 

Translated Code Information:

Rosetta Version: 20.44

Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect

Exception: EXC_BAD_ACCESS (0x0001)

 

Thread 0: (0xb011cd38, 0xb8152bc4)

0x95999e60: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260

0x087de04c: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonOperationThreadFunc + 136

0x959e839c: /usr/lib/libSystem.B.dylib : __pthread_body + 40

0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x95999fa4 ctr: 0x95961cdc

r00: 0x0000014e r01: 0xf0101a50 r02: 0xf0101a90 r03: 0x00005f03

r04: 0x00006003 r05: 0x00000000 r06: 0x00000000 r07: 0x00000000

r08: 0x00000000 r09: 0x00000001 r10: 0xfffffff1 r11: 0xa0b16898

r12: 0x95961cdc r13: 0xf0101b28 r14: 0xf0101b24 r15: 0xf0101b20

r16: 0xf0101b1c r17: 0xf0101b18 r18: 0xf0101ce8 r19: 0x00000000

r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000

r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0xa0b19988

r28: 0x00178c60 r29: 0x0086c600 r30: 0x00178c08 r31: 0x95999988

 

Thread 1: Crashed (0xb7fffacc, 0x816b2a6f)

0x94835900: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFArrayApplyFunction + 352

0x95203480: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSView _invalidateGStatesForTree] + 416

0x95203298: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSView _invalidateFocus] + 36

0x95209068: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSView setFrameSize:] + 256

0x952c23c8: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSThemeFrame setFrameSize:] + 388

0x952c1c94: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSWindow _setFrame:updateBorderViewSize:] + 596

0x952c15f0: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSWindow _oldPlaceWindow:] + 744

0x952c1094: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSWindow _setFrameCommon:display:stashSize:] + 1124

0x95815624: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSNavOpenPanel setFrame:display:] + 68

0x9540ada4: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : _ResizeWindowLeavingTopCenterFixedAndAnimateIfNeeded + 460

0x9540a184: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSSavePanel(NSSavePanelLayout) _layoutViewsVerticallyAndResize] + 700

0x9540b8cc: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSSavePanel setMessage:] + 152

0x958172c0: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : __NSNavCreateGetFileDialog + 752

0x96b1e684: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices : _NavCreateGetFileDialog + 112

0x8511f5e8: No symbol

0x8515f86c: No symbol

0x8516069c: No symbol

0x850fdd14: No symbol

0x850df1cc: No symbol

0x850fdd14: No symbol

0x851ea128: No symbol

0x850fdd14: No symbol

0x85176bbc: No symbol

0x850fdd14: No symbol

0x8510b274: No symbol

0x8510c7e0: No symbol

0x850fdd14: No symbol

0x851f3db4: No symbol

0x851f32a8: No symbol

0x850cf300: No symbol

0x850fdd14: No symbol

0x850dc67c: No symbol

0x850dc6c0: No symbol

0x850fdd14: No symbol

0x85100804: No symbol

0x850fdd14: No symbol

0x85150a0c: No symbol

0x850fdd14: No symbol

0x85151968: No symbol

0x850ead5c: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x850eb248: No symbol

0x850f65f4: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x850f6750: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x850f6848: No symbol

0x850f69b4: No symbol

0x853c5f48: No symbol

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x94835900 ctr: 0x96b4cfe0

r00: 0x00000000 r01: 0xbfffc760 r02: 0x2370c9f8 r03: 0x2370dbb0

r04: 0x96c0de2c r05: 0x00000000 r06: 0xa1b1c1d3 r07: 0xa1b1c1d3

r08: 0xa1b1c1d3 r09: 0x2370c9e0 r10: 0x00000082 r11: 0x693ede2c

r12: 0xc0000003 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000

r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0xffffffff

r20: 0x00000539 r21: 0xbfffdd28 r22: 0xa0a89ee0 r23: 0x00000001

r24: 0xa0a79ee0 r25: 0x96c0de2c r26: 0x00000000 r27: 0x00000004

r28: 0x2370bea0 r29: 0x00000010 r30: 0x00000004 r31: 0x948357ac

 

Thread 2: (0xb019e83c, 0xb815298f)

0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0

0x9489c668: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 1832

0x90764e40: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio : HALRunLoop::OwnThread(void*) + 216

0x90764c84: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio : CAPThread::Entry(CAPThread*) + 108

0x959e839c: /usr/lib/libSystem.B.dylib : __pthread_body + 40

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x9595d900 ctr: 0x959569d0

r00: 0xffffffe1 r01: 0xf0182550 r02: 0xa093bf48 r03: 0xf0182930

r04: 0x03000006 r05: 0x00000000 r06: 0x00000450 r07: 0x00008e03

r08: 0x00000000 r09: 0x00000000 r10: 0x00000004 r11: 0xa0b165f4

r12: 0x959569d0 r13: 0x00000000 r14: 0xa0929478 r15: 0x7fffffff

r16: 0xffffffff r17: 0x00000000 r18: 0x00000000 r19: 0x00000000

r20: 0x00000000 r21: 0x00000000 r22: 0xf0182930 r23: 0x00000000

r24: 0xf0182930 r25: 0x00000450 r26: 0x00008e03 r27: 0x00000000

r28: 0x00000000 r29: 0x03000006 r30: 0x03000006 r31: 0x9489bf48

 

Thread 3: (0xb009ae28, 0xb8152ad4)

0x087e1ddc: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _PostOTEvent + 104

0x087e1fb8: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonSelectThreadFunc + 204

0x959e839c: /usr/lib/libSystem.B.dylib : __pthread_body + 40

0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x087dcea0 ctr: 0x959ac9ec

r00: 0x00000000 r01: 0xf0080d60 r02: 0x087fa010 r03: 0x000000e8

r04: 0xf0080e34 r05: 0x00000000 r06: 0x0000395f r07: 0x00000002

r08: 0x182fc080 r09: 0x0cd00a30 r10: 0x000eb008 r11: 0x087fa42c

r12: 0x959ac9ec r13: 0x087fa010 r14: 0x00000000 r15: 0x087fa010

r16: 0x087fa008 r17: 0xf0080e18 r18: 0x08801efc r19: 0xf0080e0c

r20: 0xf0080dfc r21: 0xf0080e08 r22: 0xf0080e34 r23: 0x1823a4ec

r24: 0x08801efc r25: 0x087fa010 r26: 0x00000000 r27: 0xf0080e04

r28: 0xf0080e34 r29: 0x00000000 r30: 0x1823a4b8 r31: 0x087e1efc


Which is mostly greek (geek?) to me but perhaps somebody can glean some useful info from that.

 

Thanks.

Share this post


Link to post
Share on other sites

To recap:

= Retrospect running on Intel XServe

= File Backup Set saved on an iSCSI partiton mounted with GlobalSAN iSCSI

= Configure->BackupSets->YourBackupSet->Configure results in the crash noted above

 

- Does this happen _anytime_ you access this Backup Set from the Configure window?

- Can you create and save new File Backup Sets to the same mounted volume, and access them successfully?

Share this post


Link to post
Share on other sites

Quote:

To recap:

= Retrospect running on Intel XServe

 


Correct.

Quote:

 

= File Backup Set saved on an iSCSI partiton mounted with GlobalSAN iSCSI

 


Correct.

Quote:

 

= Configure->BackupSets->YourBackupSet->Configure results in the crash noted above

 


Correct.

 

Quote:

 

- Does this happen _anytime_ you access this Backup Set from the Configure window?

 


No. After launch, Retrospect runs as expected in all respects for some period of time - 12 to 24 hours I haven't been able to determine exactly how long. All backup scripts execute successfully, and Backup Sets can be configured as per normal. At some point 12-24 hours after launch, as the backup server is running, it suddenly sets the status of all scripts to Media, and writes several "can't open/create startup file" errors to the log. The backup server continues on with this status seemingly indefinitely. If I stop it, and go to configure one of the sets, then the crash happens.

Quote:

 

- Can you create and save new File Backup Sets to the same mounted volume, and access them successfully?

 


No. If I create a new set on the iSCSI volume after the backup server has changed to status: Media, Retrospect crashes in much the same way (sorry I don't have logs of that one...)

All the while, the iSCSI volume is mounted in the Finder and is accessible. There are no iSCSI errors noted in the system logs, nor do I get any errors from my iSCSI target (Open-E, for the record)

 

Basically, this means I cant leave this to run unattended - kind of a problem for a systems that supposed to run headless in a basement three buildings away!

Share this post


Link to post
Share on other sites

Quote:

If I create a new set on the iSCSI volume after the backup server has changed to status: Media, Retrospect crashes...

 


 

Then the critical question becomes, if you create a new Backup Set on a directly attached volume (such as the boot volume) after the backup server has changed to status: Media, will Retrospect crash?

 

Dave

Share this post


Link to post
Share on other sites

Okay it just did it again... that was a pretty good run it had there (still not acceptable imho, but better) So I tested creating a new set on the local storage when its in its "media" failure mode, and on touching the "New..." button when creating a file storage set it crashes, which now that I recall is exactly where it crashed when I intended to save to the iSCSI volume so it doesn't even let me get far enough to choose where its going to go.

 

Interestingly, I was resetting the LOM on this server just before it went into "media" failure. Not sure is that's relevant or not. There have been some LOM issues on this one but I put them down to operator error. For the person that asked, yes, it is on a UPS along with the iSCSI server which has been up since July07. As usual, nothing in the Retrospect log on the crash. Crash dump follows:

 

Code:



Process: Retrospect [8185]

Path: /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect

Identifier: Retrospect

Version: ??? (???)

Code Type: PPC (Translated)

Parent Process: launchd [1]

 

Date/Time: 2008-02-19 17:34:01.722 -0800

OS Version: Mac OS X Server 10.5.2 (9C31)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000d0b2ffbf

Crashed Thread: 0

 

Thread 0 Crashed:

0 ??? 0x816b50bf 0 + 2171293887

 

Thread 1:

0 ??? 0x800bb9e6 0 + 2148252134

1 ??? 0x800c31dc 0 + 2148282844

2 translate 0xb818b6ea CallPPCFunctionAtAddressInt + 202802

3 ??? 0x800ecc55 0 + 2148453461

4 ??? 0x800ecb12 0 + 2148453138

 

Thread 2:

0 translate 0xb8152b88 spin_lock_wrapper + 91256

1 translate 0xb8167dec CallPPCFunctionAtAddressInt + 57140

2 translate 0xb80dfb5f 0xb8000000 + 916319

 

Thread 3:

0 translate 0xb8152c78 spin_lock_wrapper + 91496

1 translate 0xb816c843 CallPPCFunctionAtAddressInt + 76171

2 translate 0xb80bdbdf 0xb8000000 + 777183

3 translate 0xb80b705b 0xb8000000 + 749659

4 translate 0xb80d4a14 0xb8000000 + 870932

5 translate 0xb813d7b3 spin_lock_wrapper + 4259

 

Thread 4:

0 translate 0xb8152a43 spin_lock_wrapper + 90931

1 translate 0xb8183653 CallPPCFunctionAtAddressInt + 169883

2 translate 0xb81861e4 CallPPCFunctionAtAddressInt + 181036

3 translate 0xb80dfb5f 0xb8000000 + 916319

 

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0xd0b2ffbf ebx: 0xb813d020 ecx: 0xd0b2ffbf edx: 0x00000000

edi: 0xb81d8794 esi: 0xb81d8770 ebp: 0x8080d180 esp: 0xb7fffacc

ss: 0x0000001f efl: 0x00010282 eip: 0x816b50bf cs: 0x00000017

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

cr2: 0xd0b2ffbf

 

Binary Images:

0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate

 

Translated Code Information:

Rosetta Version: 21.01

Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect

Exception: EXC_BAD_ACCESS (0x0001)

 

Thread 0: (0xb011cd38, 0xb8152c78)

0x902a1e00: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260

0x087de04c: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonOperationThreadFunc + 136

0x902f03ac: /usr/lib/libSystem.B.dylib : __pthread_body + 40

0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x902a1f44 ctr: 0x90269c7c

r00: 0x0000014e r01: 0xf0101a50 r02: 0xf0101a90 r03: 0x00005f03

r04: 0x00006003 r05: 0x00000000 r06: 0x00000000 r07: 0x00000000

r08: 0x00000000 r09: 0x00000001 r10: 0xffffff1f r11: 0xa008e898

r12: 0x90269c7c r13: 0xf0101b28 r14: 0xf0101b24 r15: 0xf0101b20

r16: 0xf0101b1c r17: 0xf0101b18 r18: 0xf0101ce8 r19: 0x00000000

r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000

r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0xa0091928

r28: 0x00176810 r29: 0x0086c200 r30: 0x001767b8 r31: 0x902a1928

 

Thread 1: Crashed (0xb7fffacc, 0x816b50bf)

0x90bb3e34: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : __NSNavCreateChooseFolderDialog + 484

0x951f18e0: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices : _NavCreateChooseFolderDialog + 96

0x8511f8b4: No symbol

0x85160970: No symbol

0x850fdd14: No symbol

0x851ddef0: No symbol

0x850cf300: No symbol

0x850fdd14: No symbol

0x850dc67c: No symbol

0x850dc6c0: No symbol

0x850fdd14: No symbol

0x85100804: No symbol

0x850fdd14: No symbol

0x85150a0c: No symbol

0x850fdd14: No symbol

0x85151968: No symbol

0x850ead5c: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x850eb248: No symbol

0x851511b4: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x85151370: No symbol

0x851dec20: No symbol

0x850fdd14: No symbol

0x85161504: No symbol

0x850fdd14: No symbol

0x851f3274: No symbol

0x850cf300: No symbol

0x850fdd14: No symbol

0x850dc67c: No symbol

0x850dc6c0: No symbol

0x850fdd14: No symbol

0x85100804: No symbol

0x850fdd14: No symbol

0x85150a0c: No symbol

0x850fdd14: No symbol

0x85151968: No symbol

0x850ead5c: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x850eb248: No symbol

0x851511b4: No symbol

0x851238a4: No symbol

0x85123aa0: No symbol

0x85151370: No symbol

0x851f4034: No symbol

0x850fdd14: No symbol

0x85164f30: No symbol

0x850fdd14: No symbol

0x85165f2c: No symbol

0x850cf300: No symbol

0x850fdd14: No symbol

0x850dc67c: No symbol

0x850dc6c0: No symbol

0x850fdd14: No symbol

0x85100804: No symbol

0x850fdd14: No symbol

0x85150a0c: No symbol

0x850fdd14: No symbol

0x85151968: No symbol

0x850ead5c: No symbol

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x90bb3e5c ctr: 0x9025fd10

r00: 0x00000000 r01: 0xbfff9d20 r02: 0xbfffa210 r03: 0xd0b2ffbf

r04: 0x93f72b2c r05: 0x00000001 r06: 0x0000ba12 r07: 0x00000007

r08: 0x0a1fc080 r09: 0x00000001 r10: 0x90d1af70 r11: 0x6c092b2c

r12: 0x9025fd10 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000

r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0xffffffff

r20: 0x00000001 r21: 0x00000000 r22: 0xbfffc550 r23: 0x00000001

r24: 0x53506d74 r25: 0x00000000 r26: 0xbfffa210 r27: 0x00000000

r28: 0x00000000 r29: 0xbfff9d5c r30: 0x001430d0 r31: 0x90bb3c5c

 

Thread 2: (0xb019e83c, 0xb8152a43)

0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0

0x9655561c: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 1832

0x949d4e40: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio : HALRunLoop::OwnThread(void*) + 216

0x949d4c84: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio : CAPThread::Entry(CAPThread*) + 108

0x902f03ac: /usr/lib/libSystem.B.dylib : __pthread_body + 40

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x902658a0 ctr: 0x9025e970

r00: 0xffffffe1 r01: 0xf0182550 r02: 0xa0c64efc r03: 0xf0182930

r04: 0x03000006 r05: 0x00000000 r06: 0x00000450 r07: 0x00008e03

r08: 0x00000000 r09: 0x00000000 r10: 0x00000004 r11: 0xa008e5f4

r12: 0x9025e970 r13: 0x00000000 r14: 0xa0c52478 r15: 0x7fffffff

r16: 0xffffffff r17: 0x00000000 r18: 0x00000000 r19: 0x00000000

r20: 0x00000000 r21: 0x00000000 r22: 0xf0182930 r23: 0x00000000

r24: 0xf0182930 r25: 0x00000450 r26: 0x00008e03 r27: 0x00000000

r28: 0x00000000 r29: 0x03000006 r30: 0x03000006 r31: 0x96554efc

 

Thread 3: (0xb009ae28, 0xb8152b88)

0x087e1ddc: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _PostOTEvent + 104

0x087e1fb8: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonSelectThreadFunc + 204

0x902f03ac: /usr/lib/libSystem.B.dylib : __pthread_body + 40

0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0

 

PPC Thread State

srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000

cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x087dcea0 ctr: 0x902b498c

r00: 0x00000000 r01: 0xf0080d60 r02: 0x087fa010 r03: 0x000000e8

r04: 0xf0080e34 r05: 0x00000000 r06: 0x000050b3 r07: 0x00000002

r08: 0x0a3fc080 r09: 0x003a7150 r10: 0x000eb008 r11: 0x087fa42c

r12: 0x902b498c r13: 0x087fa010 r14: 0x00000000 r15: 0x087fa010

r16: 0x087fa008 r17: 0xf0080e18 r18: 0x08801efc r19: 0xf0080e0c

r20: 0xf0080dfc r21: 0xf0080e08 r22: 0xf0080e34 r23: 0x0a40769c

r24: 0x08801efc r25: 0x087fa010 r26: 0x00000000 r27: 0xf0080e04

r28: 0xf0080e34 r29: 0x00000000 r30: 0x0a407668 r31: 0x087e1efc

 

 


Share this post


Link to post
Share on other sites

Quote:

I tested creating a new set on the local storage when its in its "media" failure mode, and on touching the "New..." button when creating a file storage set it crashes, which now that I recall is exactly where it crashed when I intended to save to the iSCSI volume so it doesn't even let me get far enough to choose where its going to go.

 


 

 

So to be clear:

Configure->Backup Sets->New...->"Backup set type: File" "Name: Backup Set Foo"->New...

 

Retrospect crashes before it can display the "Choose a Folder" Mac OS X window (subtitled: Creating backup set file "Backup Set Foo")?

 

As you stated, at this point you have not selected what volume the File Backup Set is gong to be stored on. But Mac OS X needs to make all available volumes available to the program that is requesting them (note if you had a CD in the drive that had spun down, it would likely spin backup at this point).

 

- Is it possible to unmount the iSCSI volumes from this machine before trying to create a new File Backup Set?

 

- Is the iSCSI software all up to date?

 

- Has this been tested with a fresh version of Retrospect's preference file?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×