Mac 6.2.234 Client Still Randomly Turning Off

[macboyrules]

After updating all of my Mac clients to 6.2.234, they are still exhibiting the same problem as the previous client. They are just randomly turing off. If I remote into the client, and restart the client, it will function again for an indeterminate time period. Also, when the machine is restarted, the client never starts properly.

 

Server Version: Windows Multi Server 7.6.111 with Driver Update and Hot Fix Version 7.6.101

 

All clients were updated via the server upgrade, and they were a mixture of 6.1.130 and 6.2.229 clients. They [color:red]all[/color] now exhibit the same problem. All clients are either on Mac OS X 10.5.5 or 10.5.4, and are Intel based.

 

This is becoming very frustrating, and leaving the backup program almost unusable for my Mac clients.

[Mayoff]

I would suggest an uninstall using the client installer itself and then reinstall the client on the computer. A simple permissions problem can cause this and can be fixed with an uninstall and reinstall.

[macboyrules]

I have uninstalled and re-installed locally on a few test machines, and after re-start they are [color:red]still[/color] not showing up on the network. If I ssh into the machine, kill the retroclient, and start it back up again, it shows up. But, after restart, the client is no where to be found. :confused2:

[Mayoff]

What processes show up for the client after the restart?

 

What is the status in the client control panel after the restart? Does it say "on" or "off" or "not running"? Any other details?

 

What error or crash logs appear in the Console for Retrospect Client?

[rhwalker]

Tim,

 

On one of the Mac clients that turn off on restart, could you open the Terminal program (/Applications/Terminal) and enter the following command, and then post the results here:

 

cat /Library/StartupItems/Retro*/*

 

That will show whether the correct client is being started and how.

 

As for Robin's request for the running processes, that can be shown by the following two Terminal commands (open your Terminal window up wide):

 

ps axlwww | fgrep piton

ps axlwww | fgrep retro

 

That's a "pipe" symbol (above the Return key, shifted) between the two commands on each line. The first command should only produce a single line of output (for the fgrep, because there shouldn't be any pitond running) and the second command should produce two lines of output, one for the fgrep and one for retroclient.

 

Post the results. It's easiest to just copy and paste these commands from this post.

 

Russ

[macboyrules]

What processes show up for the client after the restart?

 

root 104 0.0 0.0 604780 968 ?? S 2:07PM 0:07.13 /Applications/Retrospect Client.app/Contents/Resources/retroclient

 

What is the status in the client control panel after the restart? Does it say "on" or "off" or "not running"? Any other details?

 

The client control panel says it's on and waiting for first backup

 

What error or crash logs appear in the Console for Retrospect Client?

 

In the retrospect.log file, I see the following:

 

1226070427: IPNSRegister(1): registered: "E71018792","1a8cf48a58151c2f","0.0.0.0:0"

1226070427: ConnStartListen: starting thread ConnStartListen for 192.xxx.xxx.xxx:0

1226070427: iplud: recvfrom() failed with error 9 for 192.xxx.xxx.xxx:49525

1226070427: bindToValidBootPort: Unable to bind to valid boot port

 

And it just keeps repeating that last line.

[Mayoff]

Is the client on or off when it this state?

[macboyrules]

The client control panel says it's on and waiting for first backup

[macboyrules]

Tim,

 

On one of the Mac clients that turn off on restart, could you open the Terminal program (/Applications/Terminal) and enter the following command, and then post the results here:

 

cat /Library/StartupItems/Retro*/*

 

That will show whether the correct client is being started and how.

#!/bin/sh

##
# Start retroclient (formerly pitond) daemon
#
#	please make sure this is saved with unix line endings
##

. /etc/rc.common

if [ -f "/Library/Preferences/retroclient.state" ] && [ -d "/Applications/Retrospect Client.app" ]; then
ConsoleMessage "Starting Retrospect Client"
/Applications/Retrospect\ Client.app/Contents/Resources/retroclient &
fi
{
 Description     = "retroclient daemon";
 Provides        = ("Network Backup");
 OrderPreference = "Late";
 Messages =
 {
   start = "Starting RetroClient";
   stop  = "Stopping RetroClient";
 };
}

 

 

 

As for Robin's request for the running processes, that can be shown by the following two Terminal commands (open your Terminal window up wide):

 

ps axlwww | fgrep piton

ps axlwww | fgrep retro

 

That's a "pipe" symbol (above the Return key, shifted) between the two commands on each line. The first command should only produce a single line of output (for the fgrep, because there shouldn't be any pitond running) and the second command should produce two lines of output, one for the fgrep and one for retroclient.

 

Post the results. It's easiest to just copy and paste these commands from this post.

 

Russ

 

e71018792:~ admin$ ps axlwww | fgrep piton

501 1053 1042 0 31 0 590472 196 - R+ s000 0:00.00 fgrep piton

 

e71018792:~ admin$ ps axlwww | fgrep retroclient

0 936 1 0 31 0 605300 1052 - S ?? 1:00.91 /Applications/Retrospect Client.app/Contents/Resources/retroclient

501 1055 1042 0 31 0 599700 336 - R+ s000 0:00.00 fgrep retroclient

 

Tim

[Mayoff]

Getting these specific details are really only helpful after the client has turned itself off.

[macboyrules]

Getting these specific details are really only helpful after the client has turned itself off.

 

But that goes to the root of the problem . . . The client says it's on and ready, the proper process is running, but the server doesn't see it, so it doesn't get backed up. :confused2:

 

[Mayoff]

The client is waiting for first access. You need to forget it from the client database and add it again. Maybe try add by address.