Jump to content
Sign in to follow this  
charliektm400exc

Clients not getting backup automaticaly in Tiger

Recommended Posts

I have upgraded to Tiger, as well as the latest version of Retrospect for my backup machine (imac running 10.4.1) and my clients (Powerbook and iBook both running 10.4.1).

 

I have them running as backup server scripts, and Retrospect just doesn't see the machines. On the laptops if I look the client is showing as "off" (I can't remember if this is what it showed prior to Tiger) However if I turn the client on manually and run an immediate backup from the client it works perfectly. I have followed the instructions about installing the upgrade from the server, not on the client machine, that is listed in the knowledge base, but this doesn't seem to have fixed the problem.

 

Does anybody have any ideas on what I should try?

 

Thanks

 

Charlie

Share this post


Link to post
Share on other sites

Quote:

On the laptops if I look the client is showing as "off"

 


 

- When you restart the client machine, what will the Status window on the Retrospect Client application show?

Share this post


Link to post
Share on other sites

Quote:

I'd guess this is a permission error. Restarting should give you a dialog where you can fix it.

 


Not necessarily. Using Activity Monitor, you'll probably find that the pitond daemon is dying on the client machines. It happens to me almost every time I wake up my PowerBook. I was never able to fix it no matter what I tried, so I just created an AppleScript that polls process status periodically to determine whether the pitond daemon is running. If it isn't, the AppleScript will restart it.

Share this post


Link to post
Share on other sites

When I restart it works fine, but after a little while it turns itself off. It seems to me that Alan might be on the right track, but I don't want to get into this sort of issue with AppleScript as I don't really know how to write scripts. The program should work, and Dantz should provide the fix, or help on their web site on how to fix it.

 

If anybody can document a simple fix then I might be able to try that.

 

Thanks for the advice so far.

 

Charlie

Share this post


Link to post
Share on other sites

Quote:

If anybody can document a simple fix then I might be able to try that.

 


 

Documentation of the _problem_ would be worthwhile, too.

 

- What does the Status window of the Retrospect Client application show during various stages of the observed behavior?

Share this post


Link to post
Share on other sites

Also, open up the Console app immediately after seeing this problem (before turning the client back on) and view the retroclient.log (under /var/log, I believe) and see what error was reported, if any. It might be helpful if you'd also post the last several lines of the log file here.

Share this post


Link to post
Share on other sites

Well I had two machines ( 10.4.1 , now 10.4.2 ) that would launch the client, but not have them be on. I put up with this for a while, the decided to uninstall/reinstall the client - Poof!

Both machines now start the client in the correct mode ( ON ) automagically.

Am still backing up from a 10.3.9 machine..

 

jeff

Share this post


Link to post
Share on other sites

Ok, this is the log file just after I wake up the powerbook, and client has turned itself off saying "error during startup"

 

1121498973: PmcOpen: connect() failed with error 61: Connection refused

1121498973: ipludAddMembership: adding membership for 0.0.0.0

1121498973: iplud: bound to address 24.0.0.10

1121498979: IPNSRegister(0): registered: "Charlie's AlBook"/"6520aa31eba11831"

1121498990: IPNSRegister(0): registered: "Charlie's AlBook"/"6520aa31eba11831"

1121498990: bindToValidBootPort: gServerPID has been initialized to 261

1121499193: Connection established by 3.0.0.10:51401

1121499236: ConnReadData: Connection with 3.0.0.10:51401 was reset

1121499239: Connection established by 3.0.0.10:51402

1121499284: ConnReadData: Connection with 3.0.0.10:51402 was reset

1121499495: Connection established by 3.0.0.10:51405

1121499538: ConnReadData: Connection with 3.0.0.10:51405 was reset

1121499541: Connection established by 3.0.0.10:51406

1121499588: ConnReadData: Connection with 3.0.0.10:51406 was reset

1121499795: Connection established by 3.0.0.10:51409

1121499837: ConnReadData: Connection with 3.0.0.10:51409 was reset

1121499843: Connection established by 3.0.0.10:51410

1121499886: ConnReadData: Connection with 3.0.0.10:51410 was reset

1121500097: Connection established by 3.0.0.10:51413

 

 

Charlie

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  

×