Soundworks UK Posted February 19, 2007 Report Share Posted February 19, 2007 Putting together a Mac OSX server, 2 x 2ghz Intel, 2gb Ram 7TB XServe Raid striped raid 50 (I think), Mac OSX 10.4.8, all latest updates, Retrospect server v 6.1.126 Device Access version 1.0.107 Driver update version 6.1 9.102 Running with a new Quantum HH Ultrium LTO2 SCSI tape drive with an Atto dual channel SCSI controller wit the latest driver update. Retrospect sees the tape drive, but when I set an immediate backup, as soon as it scans one of the Raids, it just quits. This is before it has asked for a tape etc. Any suggestions greatly appreciated. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 19, 2007 Report Share Posted February 19, 2007 You need a special version of Retrospect with a workaround hack to let it work on Intel Macs. KnowledgeBase article is here with download and instructions: Retrospect hack for Intel Macs Hope this helps, Russ Quote Link to comment Share on other sites More sharing options...
Soundworks UK Posted February 19, 2007 Author Report Share Posted February 19, 2007 Brilliant, thanks very much. Quote Link to comment Share on other sites More sharing options...
hjenkins75 Posted February 20, 2007 Report Share Posted February 20, 2007 This is still an issue for me. I am running an Xserve with 5GB RAM, 2x2 Dual Core Intel. Using Retrospect 6.1.126 with no ACL patch and I cannot get the application to launch it just quits as soon as I launch it with no error. Below are the results of my console. Please advise as I'm unable to run any scheduled backup. Command: RetroRunSL Path: /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/RetroRunSL.app/Contents/MacOS/RetroRunSL Parent: WindowServer [8104] Rosetta: Yes Version: 1.0.0 () PID: 8112 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x00000000 Thread 0 Crashed: 0 com.dantz.RetroRunSL 0xb811d5ad spin_lock_try_wrapper + 911 1 com.dantz.RetroRunSL 0xb8126ab4 spin_lock_wrapper + 37992 2 com.dantz.RetroRunSL 0xb81210b3 spin_lock_wrapper + 14951 3 com.dantz.RetroRunSL 0xb8125a78 spin_lock_wrapper + 33836 4 com.dantz.RetroRunSL 0xb812a1a6 spin_lock_wrapper + 52058 5 com.dantz.RetroRunSL 0xb812ba23 spin_lock_wrapper + 58327 6 com.dantz.RetroRunSL 0xb808a92d 0xb8000000 + 567597 7 com.dantz.RetroRunSL 0xb8139192 spin_lock_wrapper + 113478 8 com.dantz.RetroRunSL 0xb813936f spin_lock_wrapper + 113955 9 com.dantz.RetroRunSL 0xb8138351 spin_lock_wrapper + 109829 10 com.dantz.RetroRunSL 0xb807c36b 0xb8000000 + 508779 11 com.dantz.RetroRunSL 0xb807c48b 0xb8000000 + 509067 12 com.dantz.RetroRunSL 0xb811e179 spin_lock_wrapper + 2861 13 com.dantz.RetroRunSL 0xb811e433 spin_lock_wrapper + 3559 14 com.dantz.RetroRunSL 0xb81369a0 spin_lock_wrapper + 103252 15 com.dantz.RetroRunSL 0xb80050f7 0xb8000000 + 20727 16 com.dantz.RetroRunSL 0xb8137d58 spin_lock_wrapper + 108300 17 com.dantz.RetroRunSL 0xb811dba3 spin_lock_wrapper + 1367 18 com.dantz.RetroRunSL 0xb80038f2 0xb8000000 + 14578 19 com.dantz.RetroRunSL 0xb8003819 0xb8000000 + 14361 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0xb811d594 ecx: 0x00000000 edx: 0x00000d03 edi: 0x00000000 esi: 0x00000d03 ebp: 0xb7fff6d8 esp: 0xb7fff690 ss: 0x0000001f efl: 0x00010246 eip: 0xb811d5ad cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 Binary Images Description: 0x8fc00000 - 0x8fc50fff dyld 46.1 /usr/lib/dyld 0x8fe00000 - 0x8fe49fff dyld 46.1 /usr/lib/dyld 0xb8000000 - 0xb82d9fff com.dantz.RetroRunSL 1.0.0 () /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/RetroRunSL.app/Contents/MacOS/RetroRunSL Translated Code Information: NO CRASH REPORT ********** Host Name: server Date/Time: 2007-02-20 15:41:15.009 +0000 OS Version: 10.4.8 (Build 8N1215) Report Version: 4 Command: RetroRunSL Path: /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/RetroRunSL.app/Contents/MacOS/RetroRunSL Parent: WindowServer [8171] Rosetta: Yes Version: 1.0.0 () PID: 8177 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x00000000 Thread 0 Crashed: 0 com.dantz.RetroRunSL 0xb811d5ad spin_lock_try_wrapper + 911 1 com.dantz.RetroRunSL 0xb8126ab4 spin_lock_wrapper + 37992 2 com.dantz.RetroRunSL 0xb81210b3 spin_lock_wrapper + 14951 3 com.dantz.RetroRunSL 0xb8125a78 spin_lock_wrapper + 33836 4 com.dantz.RetroRunSL 0xb812a1a6 spin_lock_wrapper + 52058 5 com.dantz.RetroRunSL 0xb812ba23 spin_lock_wrapper + 58327 6 com.dantz.RetroRunSL 0xb808a92d 0xb8000000 + 567597 7 com.dantz.RetroRunSL 0xb8139192 spin_lock_wrapper + 113478 8 com.dantz.RetroRunSL 0xb813936f spin_lock_wrapper + 113955 9 com.dantz.RetroRunSL 0xb8138351 spin_lock_wrapper + 109829 10 com.dantz.RetroRunSL 0xb807c36b 0xb8000000 + 508779 11 com.dantz.RetroRunSL 0xb807c48b 0xb8000000 + 509067 12 com.dantz.RetroRunSL 0xb811e179 spin_lock_wrapper + 2861 13 com.dantz.RetroRunSL 0xb811e433 spin_lock_wrapper + 3559 14 com.dantz.RetroRunSL 0xb81369a0 spin_lock_wrapper + 103252 15 com.dantz.RetroRunSL 0xb80050f7 0xb8000000 + 20727 16 com.dantz.RetroRunSL 0xb8137d58 spin_lock_wrapper + 108300 17 com.dantz.RetroRunSL 0xb811dba3 spin_lock_wrapper + 1367 18 com.dantz.RetroRunSL 0xb80038f2 0xb8000000 + 14578 19 com.dantz.RetroRunSL 0xb8003819 0xb8000000 + 14361 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0xb811d594 ecx: 0x00000000 edx: 0x00000d03 edi: 0x00000000 esi: 0x00000d03 ebp: 0xb7fff6d8 esp: 0xb7fff690 ss: 0x0000001f efl: 0x00010246 eip: 0xb811d5ad cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 Binary Images Description: 0x8fc00000 - 0x8fc50fff dyld 46.1 /usr/lib/dyld 0x8fe00000 - 0x8fe49fff dyld 46.1 /usr/lib/dyld 0xb8000000 - 0xb82d9fff com.dantz.RetroRunSL 1.0.0 () /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/RetroRunSL.app/Contents/MacOS/RetroRunSL Translated Code Information: NO CRASH REPORT Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 20, 2007 Report Share Posted February 20, 2007 Quote: Using Retrospect 6.1.126 with no ACL patch... Is there a reason that you are not using the fix linked to in this thead? Or is the above a typo...? Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 20, 2007 Report Share Posted February 20, 2007 Quote: Using Retrospect 6.1.126 with no ACL patch Then you are seeing the expected behavior (crash). Note that you also have to follow the instructions in the KnowledgeBase article (to uncheck the ACL usage). Russ Quote Link to comment Share on other sites More sharing options...
hjenkins75 Posted February 20, 2007 Report Share Posted February 20, 2007 I don't understand? I have downloaded the file from the link supplied in the above discussion: http://download.dantz.com/archives/retro-aclpatch.dmg And I use it To launch Retrospect? But it won't launch? Sorry, if I'm being really slow here..? Quote Link to comment Share on other sites More sharing options...
RonaldL Posted February 21, 2007 Report Share Posted February 21, 2007 Did you go to Special>Preferences>OS X and turn on the option to not copy ACLs during backup? Quote Link to comment Share on other sites More sharing options...
hjenkins75 Posted February 21, 2007 Report Share Posted February 21, 2007 Did you go to Special>Preferences>OS X and turn on the option to not copy ACLs during backup? I'm unable to launch Retrospect to set this preference. A re-install won's solve it either? Quote Link to comment Share on other sites More sharing options...
hjenkins75 Posted February 21, 2007 Report Share Posted February 21, 2007 Where are the preference files for Retrospect kept? Perhaps I can manualy edit the files to reflect Not to Copy ACL's using pico? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 21, 2007 Report Share Posted February 21, 2007 The file linked to above is not a patch, but is a build of Retrospect that is supposed to get around an apparent bug in OS X on Intel hardware. But the ACL issue occurs during backup operation, not just on launch, so your crash of RetroRunSL may be entirely unrelated to the the issue that began this thread. I'd suggest trying to launch the patched version (6.1.131), and if that doesn't work try dragging your preferences to the Desktop (and no, you can't edit the Retro.Config file in a text editor) and try again. - Has Retrospect ever launched for you on this machine? Dave Quote Link to comment Share on other sites More sharing options...
nulldev Posted February 23, 2007 Report Share Posted February 23, 2007 I've encountered the same problem on an Intel Xserve. I've trashed all the preferences and no fix. So far, the only way I know to fix this is to restart the server. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 23, 2007 Report Share Posted February 23, 2007 Huw Jenkins: When you get this crash, do you see the Authentication screen for Retrospect or does Retrospect crash before it asks for a password? Does a Restart of the computer make this issue go away? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 23, 2007 Report Share Posted February 23, 2007 Quote: I've encountered the same problem on an Intel Xserve. Sigh. - Did you read the entire thread above? - Did you attempt to take advantage of the fixes suggested? - What "same problem" are you seeing? The crash when backup starts, as described in the original post by Soundworks UK that began the thread, or the RetroRunSL crash from Huw Jenkins' thread hijack (who also described his experience as "this" even though it was not). - What version of Retrospect are you running? I see Mayoff's attention to reported problems with Intel OS X Server as an indication that they are taking this issue seriously and want to provide a fix to their customers. It would be really, really helpful if people experiencing problems with this configuration provide as much information as they can when they post. "Me too" posts are simply a waste of everyone's time. Dave Quote Link to comment Share on other sites More sharing options...
nulldev Posted February 23, 2007 Report Share Posted February 23, 2007 Dave, If your going to rip apart people on the forums, why should I bother posting? I did a quick scan of the forum and noticed the exact same problem I was having with not suggestions to fix it. I posted the way I did because I forgot there was 2 different problems being discussed in the same thread. I was respond to Huw Jenkins. To answer your questions... - Did you read the entire thread above? Read above - Did you attempt to take advantage of the fixes suggested? There was no suggestion relating to my problem - What "same problem" are you seeing? The crash when backup starts, as described in the original post by Soundworks UK that began the thread, or the RetroRunSL crash from Huw Jenkins' thread hijack (who also described his experience as "this" even though it was not). Retrospect not starting after you authenticate with no log entries. - What version of Retrospect are you running? What ever is the lastest version (I think 6.1.126) I called and talked to support for today about the issue and direct him to this thread. That is why Mayoff is paying attention to this thread. Eric Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 23, 2007 Report Share Posted February 23, 2007 Quote: If your going to rip apart people on the forums, why should I bother posting? Because you're having an issue, and posting to the community Forum is one way to learn and to help others to learn. > There was no suggestion relating to my problem In response to Huw I wrote "I'd suggest trying to launch the patched version (6.1.131)..." It may not make any difference, but it was indeed a suggestion. > Retrospect not starting after you authenticate with no log entries. - I assume you mean no Operations Log entries; are you getting the same RetroRunSL crash log that Huw pasted in above? Quote Link to comment Share on other sites More sharing options...
nulldev Posted February 24, 2007 Report Share Posted February 24, 2007 The RetroRunSL crash log that I get is similar but it is dated from about a week ago. Syslogd has crashed which I'm assuming is why I don't have any current logs. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 24, 2007 Report Share Posted February 24, 2007 Quote: Syslogd has crashed which I'm assuming is why I don't have any current logs. Does that concern you? Even on my OS X 10.4.8 (not-server), killing syslogd will result in the process coming instantly back alive. To have syslogd not running on OS X 10.4 IntelServer sounds like an indication of some system-wide problem. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 24, 2007 Report Share Posted February 24, 2007 I spoke with Eric on the phone and we both agreed that the Syslog issue is a system problem which could be adding extra stability issues, but I am hoping we can try to see if the original poster is having some of the same symptoms. Eric's server is in production and rebuilding the system will be really hard to do. Quote Link to comment Share on other sites More sharing options...
nulldev Posted February 26, 2007 Report Share Posted February 26, 2007 Quote: Does that concern you? Even on my OS X 10.4.8 (not-server), killing syslogd will result in the process coming instantly back alive. To have syslogd not running on OS X 10.4 IntelServer sounds like an indication of some system-wide problem. That does concern me. I'm trying to figure out why it's crashing and also UserNotificationCenter crashed. Eric Quote Link to comment Share on other sites More sharing options...
nulldev Posted February 28, 2007 Report Share Posted February 28, 2007 Quote: Quote: I'm trying to figure out why it's crashing and also UserNotificationCenter crashed. Eric As an update to the issue I'm having. I've moved the hard drives to an identical Xserve to rule out if it is a hardware problem. Will keep you updated on what I find. Eric Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.