Jump to content
Sign in to follow this  
aethiolas

Engine Crashing...again

Recommended Posts

Ok I'm def in need of some help here. I've been attempting to use retrospect now for about 6 months and I'll be honest, this is the worth software experience I've had in my life. I'm attempting to use 8.2 on a mac mini server. The server connects to a remote AFP share to store all the media. I've got the "multi-server" version and I'm using it to backup about 6 servers. They are a mix of windows, mac and linux. It seems to work fine for about a month but then suddenly the engine just decides to turn off and then not work again. The engine will start and then less than 30 seconds later will just turn off. If I go in and delete all the config files and set all my stuff up again w/ the same media sets, it works fine but I refuse to continue doing this every month. I know this is not enough information to help you guys but if you can tell me what you need I'll be glad to give it to you. I'll be checking this forum all day long as I need to solve this problem. I emailed retrospect support but they tend to take quite a while to respond...

 

Thanks in advance guys!

Share this post


Link to post
Share on other sites

Well, for a start, you could provide version numbers. Mac OS version (10.x.x) on each computer in play. Exact Retrospect version on each computer in play (8.2.x engine, 8.2.x console, x.x.x client).

 

It's unclear whether you are backing up the "6 servers" by mounting their volumes on the Retrospect engine machine, or whether you are running Retrospect client on those "6 servers".

 

It's unclear what the OS are on those "6 servers" (windows? version? linux flavor? version?).

 

Is there any information in the logs? Any crash reports?

 

Is the Retrospect console on the same machine as Retrospect engine?

 

The program is very buggy. Let's at least get some basic information from you.

 

Russ

Share this post


Link to post
Share on other sites

Sure. Let go with the rundown of the version first.

The server:

-Mac OS X 10.6.4(not 10.6.5 yet)

-The retrospect engine is 8.2.x however I don't know how to tell you more than that since I can't get the engine to stay on long enough to run the program to check it!

 

The client versions are a mix of 6.3.029 & 6.3.027

 

My apologies for not explaining myself better but I am running the retrospect client on 6 servers to back them up. The servers are the following

-Windows Server 2003 R2

-Mac OS X 10.6.4

-Windows XP Pro

-Ubuntu Linux

 

For the logs, yes there is a crash report but I can't seem to trace it back. I will follow this post up with the last post in the assert logs. I renamed the file, restarted the engine and let it throw this log again to make sure I got the correct error. If there's anything else you need, let me know.

 

Share this post


Link to post
Share on other sites

Retrospect detected a failure:

 

This report documents an unusual condition detected by Retrospect's

internal integrity checking. This might be caused by a software bug,

but can also be the result of an incompatibility, hardware malfunction,

damaged system software, or other problems. Details on possible causes

can be found on the Retrospect website:

 

http://www.retrospect.com/support

 

 

********************************************************************

 

Mac OS X

OS Type: Darwin

OS Release: 10.4.0

OS Version: Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386

Machine: i386

Model: Macmini3,1

NCPU's: 2

PhysMem: 0x100000000

Application: /, version 8.2.0.399

Exception occurred on 11/15/2010 at 9:08:04 AM

Error info: Assertion failure at "elem.cpp-1124", on threadID 0x4C36000

 

Signal no: 30 Assertion

Error no: 00

Sig Code: 00

Fault Addr: 0x853D82FA -- "mach_msg_trap"

Thread ID: 0x5FBFB390, Name:

 

eax:0x000000000100001f r8:0x0000000000000e03 eip:0x0000000000000e03 cs:0x00007fff853d82fa eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x0000000000000000 rsp:0x0000000000000000 rbp:0x0000000000000270

rcs:0x00007fff5fbfa188 r10:0x00007fff5fbfa1e0 rsi:0x00007fff5fbfa188 fs:0x0000000000000270

rdx:0x00007fff5fbfa200 r11:0x0000000000000003 rdi:0x0000000000000010 gs:0x0000000000000028

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x05442000, Name: DAG Selector Thread

 

eax:0x000000000200014e r8:0x0000000000000000 eip:0x000000010300ac50 cs:0x00007fff85412eb6 eflags:0x000000000000002f

rbx:0x0000000000000246 r9:0x0000000105442000 rsp:0x0000000000000000 rbp:0x000000010300ac08

rcs:0x000000010543fc58 r10:0x000000010543fcd0 rsi:0x000000010543fc58 fs:0x0000000000000000

rdx:0x0000000000000001 r11:0x0000000000002803 rdi:0x0000000000000000 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x0523F000, Name: Execution thread

 

eax:0x000000000200014e r8:0x0000000000000000 eip:0x0000000101e6a700 cs:0x00007fff85412eb6 eflags:0x000000000000002f

rbx:0x0000000000000246 r9:0x000000010523f000 rsp:0x0000000000000000 rbp:0x0000000101e6a730

rcs:0x0000000105223c38 r10:0x0000000105223cb0 rsi:0x0000000105223c38 fs:0x0000000000000000

rdx:0x0000000000000001 r11:0x0000000000002a03 rdi:0x0000000000000010 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x0503C000, Name: DAG Listener Thread

 

eax:0x000000000200001e r8:0x0000000000000004 eip:0x0000000200000001 cs:0x00007fff85455b96 eflags:0x000000000000002f

rbx:0x0000000000000202 r9:0x0000000100c68aca rsp:0x000000010286a400 rbp:0x0000000100741e90

rcs:0x000000010503aca8 r10:0x000000010503ad20 rsi:0x000000010503aca8 fs:0x000000000006de00

rdx:0x0000000000000000 r11:0x000000010503acf0 rdi:0x0000000000000000 gs:0x000000010503acec

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x04E39000, Name: Execution thread

 

eax:0x0000000002000003 r8:0x000000004ce13ec4 eip:0x0000000000000000 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x0000000000000000 rsp:0x0000000104e19aa0 rbp:0x00000001007fffec

rcs:0x0000000104e19ab8 r10:0x0000000104e19af0 rsi:0x0000000104e19ab8 fs:0x000000000000030a

rdx:0x0000000104e1a940 r11:0x0000000104e19adf rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x04C36000, Name: Execution thread

 

eax:0x000000000200014e r8:0x000000000000012c eip:0x0000000104c2b230 cs:0x00007fff85412eb6 eflags:0x000000000000002f

rbx:0x0000000000000246 r9:0x0000000104c2b240 rsp:0x0000000000000000 rbp:0x0000000104c2c250

rcs:0x0000000104c2b1c8 r10:0x0000000104c2b200 rsi:0x0000000104c2b1c8 fs:0x0000000000000001

rdx:0x000000000285c010 r11:0x0000000000000000 rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x04A33000, Name: Execution thread

 

eax:0x0000000002000003 r8:0x000000004ce13ec4 eip:0x0000000100000000 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000202 r9:0x0000000000000000 rsp:0x0000000104a129d0 rbp:0x00000001007fffec

rcs:0x0000000104a129e8 r10:0x0000000104a12a20 rsi:0x0000000104a129e8 fs:0x0000000000000292

rdx:0x0000000104a13870 r11:0x0000000104a12a0f rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x04830000, Name: Execution thread

 

eax:0x0000000002000003 r8:0x000000004ce13ec4 eip:0x8000000100000000 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x0000000000000063 rsp:0x0000000104808160 rbp:0x00000001007fffec

rcs:0x0000000104808178 r10:0x00000001048081b0 rsi:0x0000000104808178 fs:0x00000000000002ff

rdx:0x0000000104809000 r11:0x000000010480819f rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x0442A000, Name: Execution thread

 

eax:0x0000000002000003 r8:0x000000004ce13ec4 eip:0x0000000000000000 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x0000000000000000 rsp:0x00000001043fe8e0 rbp:0x00000001007fffec

rcs:0x00000001043fe8f8 r10:0x00000001043fe930 rsi:0x00000001043fe8f8 fs:0x00000000000002e8

rdx:0x00000001043ff780 r11:0x00000001043fe91f rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x0462D000, Name: RAPI server thread

 

eax:0x0000000000000001 r8:0x000000004ce13ec4 eip:0x000000010462ace0 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x00000001007fd761 rsp:0x0000000104629370 rbp:0x000000010083122e

rcs:0x0000000104629388 r10:0x00000001046293c0 rsi:0x0000000104629388 fs:0x000000000000028d

rdx:0x000000010462a1b0 r11:0x00000001046293af rdi:0x0000000000000010 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x03404000, Name: Poll Callback Thread

 

eax:0x000000000200016b r8:0x0000000000000019 eip:0x0000000000000000 cs:0x00007fff853f108a eflags:0x000000000000002f

rbx:0x0000000000000246 r9:0x0000000103404000 rsp:0x0000000000000000 rbp:0x0000000000002403

rcs:0x0000000103403b78 r10:0x0000000103403ee0 rsi:0x0000000103403b78 fs:0x0000000103403b90

rdx:0x000000010070f8e4 r11:0x0000000000000000 rdi:0x0000000000000010 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x04227000, Name: Sub-thread of Local Mac Volume Tracker

 

eax:0x000000000100001f r8:0x0000000000004003 eip:0x0000000000004003 cs:0x00007fff853d82fa eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x0000000000000000 rsp:0x0000000000000000 rbp:0x0000000000000800

rcs:0x00000001042255e8 r10:0x0000000104225640 rsi:0x00000001042255e8 fs:0x0000000000000800

rdx:0x0000000104225720 r11:0x0000000007000006 rdi:0x0000000000000010 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x04024000, Name: Local Mac Volume Tracker Thread

 

eax:0x0000000000000001 r8:0x000000004ce13ec4 eip:0x0000000104021ba0 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x00000001007fd761 rsp:0x0000000104020230 rbp:0x000000010083122e

rcs:0x0000000104020248 r10:0x0000000104020280 rsi:0x0000000104020248 fs:0x0000000000000287

rdx:0x0000000104021070 r11:0x000000010402026f rdi:0x0000000000000010 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x0380A000, Name: Adding clients

 

eax:0x0000000002000003 r8:0x000000004ce13ec4 eip:0x0000000103808060 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000202 r9:0x00000001007fd761 rsp:0x00000001038066f0 rbp:0x000000010083122e

rcs:0x0000000103806708 r10:0x0000000103806740 rsi:0x0000000103806708 fs:0x00000000000001c7

rdx:0x0000000103807530 r11:0x000000010380672f rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x03CA1000, Name: Controller thread

 

eax:0x0000000000000001 r8:0x000000004ce13ec4 eip:0x0000000103c9eda0 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000206 r9:0x00000001007fd761 rsp:0x0000000103c9d430 rbp:0x000000010083122e

rcs:0x0000000103c9d448 r10:0x0000000103c9d480 rsi:0x0000000103c9d448 fs:0x0000000000000311

rdx:0x0000000103c9e270 r11:0x0000000103c9d46f rdi:0x0000000000000010 gs:0x0000000000000000

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Thread ID: 0x03607000, Name: Server thread

 

eax:0x0000000002000003 r8:0x000000004ce13ec4 eip:0x0000000103605070 cs:0x00007fff853e28e6 eflags:0x000000000000002f

rbx:0x0000000000000202 r9:0x00000001007fd761 rsp:0x0000000103603700 rbp:0x000000010083122e

rcs:0x0000000103603718 r10:0x0000000103603750 rsi:0x0000000103603718 fs:0x0000000000000310

rdx:0x0000000103604540 r11:0x000000010360373f rdi:0x0000000000000010 gs:0x0000000000000001

 

Module Function + offset into function Args

_______________ ________________________________________________ _______________________________________________________________________

 

Share this post


Link to post
Share on other sites
I emailed retrospect support but they tend to take quite a while to respond...

 

How do you know?

 

- Have you had tickets with Roxio (who have owned Retrospect for almost exactly 6 months)?

- What issues did you ask for support regarding? This issue?

- What did they say when the did, after quite a while, respond?

 

I'll be checking this forum all day long as I need to solve this problem

I'll be riding my bicycle and eating lunch.

 

Dave

Share this post


Link to post
Share on other sites
If I go in and delete all the config files and set all my stuff up again w/ the same media sets, it works fine but I refuse to continue doing this every month.

Ok, then you've narrowed it down to some bug that causes your config files to become corrupt, which causes the engine to crash.

 

You've got so many variables in play here that I suggest you start narrowing things down with, say, a single client backup, to see if you can get a reproducible test case.

 

I also suggest that you make periodic copies (whether finder copies, or Retrospect copy) of the config files so that you can restore them from when they were good and get back up and running quickly until the problem can be isolated.

 

The program is known to be buggy and known to corrupt its config files. When that happens, the engine crashes. That's life in the Retrospect world right now.

 

Russ

Share this post


Link to post
Share on other sites

Thanks for the answer. I guess I'll attempt to just make daily copies of my config files so that I can possibly restore them. Is there anyway(without setting them up individually and waiting a month on each as thats how long it seems to take when for it to have an issue) that I can see which configuration is causing the issue and remove that from the file?

Share this post


Link to post
Share on other sites
I emailed retrospect support but they tend to take quite a while to respond...

 

How do you know?

 

- Have you had tickets with Roxio (who have owned Retrospect for almost exactly 6 months)?

 

- What issues did you ask for support regarding? This issue?

- What did they say when the did, after quite a while, respond?

 

I'll be checking this forum all day long as I need to solve this problem

I'll be riding my bicycle and eating lunch.

 

Dave

 

Yes, I've had tickets with Retrospect. I had a simple question regarding open file backup that they did answer quite wonderfully however their reply took over two weeks. Company reorganization and purchasing is a normal procedure and I understand that its not easy however I still think customer service should be a priority.

 

Share this post


Link to post
Share on other sites
Is there anyway(without setting them up individually and waiting a month on each as thats how long it seems to take when for it to have an issue) that I can see which configuration is causing the issue and remove that from the file?

Sadly, no. Many of us are just as perplexed as to the cause of the config file corruption. If it was an easy problem to solve, I believe that the programmer(s) would have solved it already.

 

Remember, the 8.x code branch is new code, quite immature. We (and our data) are the guinea pigs. Sigh.

 

Russ

Share this post


Link to post
Share on other sites

In general...

 

If the engine is crashing "30 seconds" after you restart the engine, then some scripted action is causing the crash (and, as such, retries when you restart the engine, etc...)

 

What I found worked to debug this is to do the following:

 

1) Stop the engine

 

2) Move your catalog files -- or at least perhaps the one that *may* match a time stamp close to when the engine is crashing -- out of their current location to the desktop (or some other folder)

 

3) Restart the engine.

 

At this point, what *usually* happens is that the scripts will fire off -- but pause because they can't find the catalogs.

 

 

This will give you the opportuntity to then launch the Console to see what script was running and use that as a starting point to see what the problem is (or at least pause/modify the scripts so they stops running.)

 

Then you can stop the engine again, put your catalog files back, restart the engine and then be able to go back into the console to do some experimenting (like maybe running one script manually at a time, or doing one client backup at a time, etc...)

Share this post


Link to post
Share on other sites

Very insightful, Steve.

 

The software needs to be robust enough (defensive programming) to handle bad media sets / bad catalogs. If I were on the Retrospect team, I would be trying to capture some of these bad catalogs / bad media sets so that the software weaknesses could be repaired.

 

As long as we spend hours each month trashing media sets, rebuilding catalogs, re-creating preferences, without having these issues addressed, the problem will never get fixed.

 

Russ

Share this post


Link to post
Share on other sites

I understand that when switching to a new company the development really begins to lack however I wish I had realized this before purchasing the program. I ran it in "trial" mode for a month with no problems at all so its a bit upsetting that this happens after purchasing this. Oh well, I set my stuff back up and I started my backups last night and it crashed out during "some" event though I don't know which. I just restarted the engine and I'm going to attempt running each script individually. Thanks for all the help guys.

Share this post


Link to post
Share on other sites
Very insightful, Steve.

 

The software needs to be robust enough (defensive programming) to handle bad media sets / bad catalogs. If I were on the Retrospect team, I would be trying to capture some of these bad catalogs / bad media sets so that the software weaknesses could be repaired.

 

As long as we spend hours each month trashing media sets, rebuilding catalogs, re-creating preferences, without having these issues addressed, the problem will never get fixed.

 

Russ

 

 

 

When I was debugging similar crashes in the past, it wasn't related to bad catalog files/media sets -- it was just some other event that caused a crash.

 

In all of my cases, it was nothing explicitly reproducible, but something that would eventually crash. That said -- they *did* fix my specific crashing bugs.

 

 

But sending them catalog files/media sets would not have helped in my instances -- because it wasn't related to either.

 

 

Share this post


Link to post
Share on other sites

A suggestion from my experience:

 

Retrospect Has been stable for me in the last 2 months, after a period in which I had to keep fixing things regularly due to config corruption and the engine crashing.

 

It crashed last night. Normally I run the console to check on things and then quit it, but this time I left it open. Maybe it it a good habit to quit the console promptly after use to improve stability.

 

The other habit I have gotten into is to give the console a few extra minutes after connecting before I use it to make sure it has all the config info from the server before I modify things.

 

I also do a quick check on the scripts, sources and destinations before modifying anything. Once in a while the config seems to load incorrectly, then I quit the console, then launch it again after waiting a few minutes. For example, this morning, the console claimed that one of my tape backup sets had no members, but contained many files. From my experience, waiting for the console further doesn't correct this particular mis-communication, so I quit the console and it was fine after the next launch.

Edited by Guest

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
Sign in to follow this  

×