Jump to content
offthewall

Retro Client 6.2.229 not visible on network

Recommended Posts

Installed Retro Client 6.2.229 on a MacBook Pro running 10.5.4. Client worked for one backup then retrospect 6.1.230 in backup server mode no longer sees the client. It is turned on. Going to configure client from the server, it initially sees the client then errors with a client not visible on the network.

 

I have tried uninstalling the client. Forgetting it. Re-installing. Again it works for one backup then repeats the same pattern described above.

Share this post


Link to post
Share on other sites

Is this a wired or wireless network?

 

What is the backup speed of the one backup?

 

Is the OS X firewall on?

Share this post


Link to post
Share on other sites
Is this a wired or wireless network?

 

What is the backup speed of the one backup?

 

Is the OS X firewall on?

 

Wireless N network.

 

55.9MB/min

 

No firewall.

Share this post


Link to post
Share on other sites

I would suggest a wired connection and compare the results. This seems slow for a N connection.

Share this post


Link to post
Share on other sites

The speed is not the issue, it is the client becoming non-functional after a backup. BTW. I discovered that re-booting the MacBook will fix it as well.

 

Retrospect has always had "issues" with wireless clients so changing connection is only going to possibly eliminate the problem not solve it. This is a laptop so having a wired connection defeats the portability of it. :)

Share this post


Link to post
Share on other sites

I have found when facing similar issues that assigning a DHCP address (that is, using a DHCP reservation) and then adding the client by IP address will allow this to work. I have seen that problem with earlier client/server combinations, and that is the best workaround I have found. It lets the user continue to connect and not need to worry about switching location profiles, so it can be pretty useful.

Share this post


Link to post
Share on other sites

I had exactly the same thing happen. I've been using Retro and the Client software for many years and tried everything I know to get the Client to work. Result = nada. Could not get it to work. Retro could see it, but could not find to configure it.

 

Solution... trash the Client update (v. 6.2.229) and reinstall the previous version (6.1.139). This immediately worked for me.

 

I don't know what is wrong with the Client software, but it did not work on my MacBook Pro.

 

Mac

Share this post


Link to post
Share on other sites

Yes, that is what I have done. Reverted to the older non-universal binary client. Works fine. EMC apparently doesn't understand or care about this issue. If they would allow users to contact them to report bugs without charging them, maybe some of this stuff would get fixed.

Share this post


Link to post
Share on other sites

Customers can always call EMC for technical support. If an issue is identified as a bug, your support costs will be refunded.

 

Share this post


Link to post
Share on other sites
EMC apparently doesn't understand or care about this issue

Why on earth would you say that?

 

Mayoff ran a public beta period for this universal client, where he responded to each and every issue immediately; his Blackberry must have been burning a hole in his pocket!

 

Users identified some bugs during that program that were addressed before release; EMC showed itself to have cared a great deal about fixing them.

 

Certainly the two reports in this thread are not complete enough for anyone to identify it as a software defect. The fact that a re-install of the old version works does not prove that the new version is faulty (it would take more thorough testing to reach that conclusion).

 

There _was_ a problem with a defective .RCU file, so users who "pushed" the update from a machine running Retrospect to a machine running an older client version might have ended up with a faulty client install. That's been corrected, and the .RCU file available now works as intended.

 

(I) tried everything I know to get the Client to work. Result = nada

Such as?

 

Dave

Edited by Guest
fixed a typo

Share this post


Link to post
Share on other sites
EMC apparently doesn't understand or care about this issue

Why on earth would you say that?

 

 

Dave

 

Because of the nature of the initial replies (lack of understanding of the issue) and there has been no reply for a week (lack of interest). I can reproduce the problem at will on several laptops on two different networks/retrospect installations. Another user has claimed to be experiencing the exact same issue. Uninstalling the new client and re-installing the old client fixes the problem. Re-installing the new client re-introduces the problem. I'm available for testing fixes in my own interest but have not had any contact from EMC. I am not willing to pay for support then chase a refund if EMC so decides that it is a bug.

Share this post


Link to post
Share on other sites

Just because EMC has not replied to this exact topic in your thread does not mean the issue is being ignored. While not every post in the forum can receive a reply by EMC, most issues are read and reviewed by us.

 

, it initially sees the client then errors with a client not visible on the network.

 

What is the status of the client when you open the client UI after this problem?

 

When this failure happens, and you run Top in the terminal, what Retrospect and Retrospect Client processes appear? What % of the CPU is being used for these processes.

 

Internally we have fixed at least one situation that can cause the client to "crash". We are investigating another possible client failure that we have reproduced and are debugging.

Edited by Guest

Share this post


Link to post
Share on other sites
Another user has claimed to be experiencing the exact same issue

 

With "claimed" being the operative word. The second poster in the thread provided very limited information, so there's no way to confirm that both issues were the same.

 

 

I discovered that re-booting the MacBook will fix it as well.

 

...

 

there has been no reply for a week

 

One might have read your previous post as suggesting that you had solved the problem, so in the absence of a simple post "bump" it's hard to assign any bad motives for the lack of updates by others.

 

Robin's request for more information is important; if the "retroclient" process is not running, Retrospect won't be able to see the machine. So identifying if/when/how this process might be crashing would be the most helpful feedback EMC could get. You might find crash logs in

/Library/Logs/CrashReporter/

(I have a couple there from March 2008 during the beta cycle)

Share this post


Link to post
Share on other sites
Just because EMC has not replied to this exact topic in your thread does not mean the issue is being ignored. While not every post in the forum can receive a reply by EMC, most issues are read and reviewed by us.

 

, it initially sees the client then errors with a client not visible on the network.

 

What is the status of the client when you open the client UI after this problem?

 

When this failure happens, and you run Top in the terminal, what Retrospect and Retrospect Client processes appear? What % of the CPU is being used for these processes.

 

Internally we have fixed at least one situation that can cause the client to "crash". We are investigating another possible client failure that we have reproduced and are debugging.

 

Thank you. I will run top when I see the issue again. I currently have all laptops reverted to the older client at the moment. When I get some time later in the week, I'll re-install and get more details when it fails.

 

Share this post


Link to post
Share on other sites

I am having a similar problem with the latest Mac client software (6.2.229). What I observe is that the client interface shows that it is off, even though it had been previously set on. It appears that it will stay on for a while, and then turns itself off. This is directly related to upgrading to the latest client software. The host OS is 10.4.11 with latest patches. I was able to perform one immediate backup using the new Retrospect client, but scheduled backups do not work because the client is always turned off when the scheduled backup starts.

 

I have also noticed that the Retrospect client software is no longer able to run from a non-administrator account. I normally run in a non-admin account, but have to switch to an admin account to activate the Retrospect client. Even when leaving the admin account logged in, the client sw turns itself off at some point.

 

I have re-installed the client software directly on this machine from the admin account (and restarted the system). I initially upgraded the client software via the Retrospect server. Prior to the re-install, I could no longer turn on the client at all. The GUI would set the radio button on, and it would immediately switch back to off. After the reinstall, I could at least turn it on, but it won't stay on.

 

Solution for the moment is to fall back to the previous version of the client software.

 

 

Share this post


Link to post
Share on other sites
What I observe is that the client interface shows that it is off, even though it had been previously set on.

 

In addition to the state of the on/off radio buttons, there is a large "status" field in the window. What does the text in that window display?

 

I have also noticed that the Retrospect client software is no longer able to run from a non-administrator account.

 

What does this mean? Are you able to launch the Retrospect Client application?

 

(I) have to switch to an admin account to activate the Retrospect client

 

Since there is something wrong with how the software is running on your machine, "activating" the Retrospect client would not normally be necessary. Solve the underlying problem, and this won't be an issue. Personally, I would expect that a non-administrator user would not be allowed to launch or kill a root process. Sounds like a feature, not a bug.

 

the client sw turns itself off at some point.

 

This would be the underlying issue.

 

In post #3779 above, I suggested looking in /Library/Logs/CrashReporter/ for any retroclient crash logs. Do you have any?

 

I have re-installed the client software directly on this machine

 

But did you un-install first, using the installer program?

 

I initially upgraded the client software via the Retrospect server.

 

This is likely the initial problem, as the .RCU file that was released when the client software went live was faulty. It's fixed now, but EMC is still dealing with the fallout of that mistake.

 

Crash logs might help...

 

 

Dave

Share this post


Link to post
Share on other sites

Just a heads up. I tried re-downloading the latest 6.2.229 client software install dmg, and noted that the Mac_X_Client_Update_6_2_229.rcu file in this download is now dated 7/10/2008. However, the download page still says that the file is for 6/30/2008. If I hadn't seen another posting, I would have had no idea that there was an update for this installer.

 

I am now going through a uninstall followed by a reinstall procedure. I'll see if this corrects the problem, as it appears to be related to having installed from the latest server issued on the 6/30 date.

Share this post


Link to post
Share on other sites
Just because EMC has not replied to this exact topic in your thread does not mean the issue is being ignored. While not every post in the forum can receive a reply by EMC, most issues are read and reviewed by us.

 

, it initially sees the client then errors with a client not visible on the network.

 

What is the status of the client when you open the client UI after this problem?

 

When this failure happens, and you run Top in the terminal, what Retrospect and Retrospect Client processes appear? What % of the CPU is being used for these processes.

 

Internally we have fixed at least one situation that can cause the client to "crash". We are investigating another possible client failure that we have reproduced and are debugging.

 

Client is ON and Status is READY.

 

Processes: 92 total, 3 running, 2 stuck, 87 sleeping... 389 threads 18:15:30

Load Avg: 0.37, 0.45, 0.37 CPU usage: 25.91% user, 7.73% sys, 66.36% idle

SharedLibs: num = 19, resident = 50M code, 4312K data, 3788K linkedit.

MemRegions: num = 15026, resident = 747M + 34M private, 222M shared.

PhysMem: 246M wired, 817M active, 709M inactive, 1777M used, 271M free.

VM: 13G + 375M 139199(0) pageins, 29956(0) pageouts

 

PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE

4628 top 8.2% 0:17.97 1 18 31 2184K 204K 2768K 18M

4617 tcsh 0.0% 0:00.02 1 15 25 592K 192K 1160K 18M

4616 login 0.0% 0:00.03 1 17 56 332K 232K 1104K 19M

4615 Terminal 27.6% 0:04.45 3 100- 212 2108K+ 16M 12M+ 366M

4584 mdworker 0.0% 0:03.60 4 55 61 1484K 5848K 4128K 36M

4580 mdworker 0.0% 0:01.12 4 73 85 2936K 9636K 9064K 40M

4492 rmdb 0.0% 0:00.00 1 8 23 72K 1416K 308K 20M

4491 rmdb 0.0% 0:00.00 1 8 24 24K 1416K 228K 21M

4490 rmdb 0.0% 0:00.01 1 15 24 80K 1404K 1004K 21M

4489 ARDAgent 0.0% 0:00.14 10 104 70 928K 1196K 3548K 286M

4488 Remote Des 18.6% 1:40.56 16 160 353 16M 31M 40M 423M

4485 SecurityAg 0.0% 0:00.82 5 115 241 2196K 15M 8416K 369M

4484 authorizat 0.0% 0:00.02 1 31 36 508K 1904K 1572K 29M

4432 SyncServer 0.0% 0:07.96 2 59 225 28M 5808K 30M 52M

4238 LKDCHelper 0.0% 0:00.01 1 18 26 224K 188K 892K 19M

3872 DashboardC 0.0% 0:04.52 4 150 250 10M 11M 18M 359M

3871 DashboardC 0.0% 0:06.96 4 130 401 27M 19M 45M 388M

3383 launchd 0.0% 0:00.81 3 24 27 168K 300K 508K 18M

2930 AppleSpell 0.0% 0:00.46 1 60 34 720K 5612K 4076K 34M

1081 racoon 0.0% 0:01.20 1 14 28 244K 224K 1044K 18M

1061 VNCPrivile 0.0% 0:00.00 1 16 24 124K 184K 620K 19M

1060 krb5kdc 0.0% 0:00.17 1 17 44 444K 188K 1424K 18M

1059 kdcmond 0.0% 0:04.90 2 25 20 248K 184K 1020K 18M

1058 RFBRegiste 0.0% 0:00.02 1 16 19 196K 184K 1044K 18M

1057 AppleVNCSe 0.0% 0:00.12 2 74 48 648K 4948K 2832K 284M

448 launchd 0.0% 0:06.26 3 24 27 168K 300K 508K 18M

290 Address Bo 0.0% 0:03.10 4 100 335 9476K 16M 20M 373M

289 iCal 0.0% 0:31.31 3 114 301 12M 18M 27M 375M

288 Safari 0.2% 24:45.94 16 361 2640 254M 30M 309M 719M

287 iChatAgent 0.0% 0:12.49 4 74 170 7760K 5964K 10M 297M

286 Mail 0.1% 5:42:35 17 424 749 57M 36M 101M 516M

285 iChat 0.0% 0:31.69 10 417 478 13M 23M 30M 429M

195 dmnotifyd 0.0% 0:00.70 5 72 42 2648K 4176K 3860K 25M

193 usbmuxd 0.0% 0:00.00 2 21 29 184K 188K 668K 19M

192 Missing Sy 0.0% 0:00.86 2 83 177 848K 7564K 3696K 345M

190 Missing Sy 0.1% 4:52.00 8 161 245 11M 11M 15M 369M

189 Spanning S 0.0% 0:00.78 3 85 184 3688K 8696K 7272K 347M

188 Rogue Amoe 0.0% 0:00.22 1 62 48 572K 5928K 2864K 304M

185 Microsoft 0.0% 0:02.57 2 74 106 4536K 1364K 8228K 355M

183 iTunesHelp 0.0% 0:00.16 2 53 57 580K 2760K 2996K 291M

181 XPSLaunche 0.0% 0:00.18 2 62 55 688K 5976K 3016K 304M

158 Finder 0.0% 0:38.93 12 210 499 18M 30M 45M 481M

156 coreaudiod 0.0% 0:01.28 2 302 105 1968K 2872K 3680K 23M

155 SystemUISe 0.0% 6:28.72 10 503 484 10M 14M 18M 370M

154 ATSServer 0.0% 0:06.05 2 118 208 1424K 9108K 7676K 79M

152 pvsnatd 0.0% 0:14.19 3 26 29 176K 184K 1060K 21M

151 pboard 0.0% 0:00.00 1 15 26 168K 188K 576K 19M

148 Dock 0.0% 26:09.78 3 160 429 5000K 22M 14M 374M

146 UserEventA 0.0% 0:00.77 2 308 107 736K 6468K 3192K 33M

145 Spotlight 0.0% 0:00.35 2 80 86 1132K 6684K 4780K 310M

141 AirPort Ba 0.0% 0:00.35 3 87 180 772K 7792K 3572K 343M

140 Folder Act 0.0% 0:00.44 1 59 51 748K 5944K 3264K 304M

137 RetroRunSL 0.0% 0:05.51 1 18 83 2412K 1120K 2724K 78M

118 virusbarri 0.0% 2:19.39 22 91 165 81M 416K 82M 159M

115 virusbarri 0.0% 0:00.00 2 16 25 104K 184K 268K 19M

112 qmasterd 0.0% 0:00.04 2 24 55 116K 2184K 1128K 33M

111 RetroRun 0.0% 0:22.22 1 14 79 380K 1116K 1256K 97M

102 integod 0.0% 0:06.33 2 56 98 48M 512K 49M 68M

100 Missing Sy 0.0% 0:00.13 2 51 115 360K 5344K 1884K 69M

 

 

Share this post


Link to post
Share on other sites

Did you run Top on the backup server or client? We would want to see this info for the client system at the same time the failure is happening.

Share this post


Link to post
Share on other sites
Did you run Top on the backup server or client? We would want to see this info for the client system at the same time the failure is happening.

 

I ran top on the client at the time that the server was unable to see the client.

 

Edited by Guest

Share this post


Link to post
Share on other sites

I didn't see anything for Retroclient or retropds. Clearly the client isn't running correctly, but I do see RetroRun, which I think is normally only see on the backup server.

 

As previously mentioned, any logs in /Library/Logs/CrashReporter/ for Retroclient?

Share this post


Link to post
Share on other sites
I didn't see anything for Retroclient or retropds. Clearly the client isn't running correctly, but I do see RetroRun, which I think is normally only see on the backup server.

 

As previously mentioned, any logs in /Library/Logs/CrashReporter/ for Retroclient?

 

Correct, "Clearly" the client isn't running correctly. You see retro run because this particular laptop in my personal one and also has a copy or Retrospect installed on it.

 

There are no crash reporter logs for retrospect client in the location specified.

 

As I previously stated, a reboot of the client machine will temporarily fix the problem until a backup occurs.

 

Here is top on the client after a reboot and client now visible to server:

 

 

Processes: 85 total, 3 running, 2 stuck, 80 sleeping... 337 threads 20:46:49

Load Avg: 0.24, 0.24, 0.24 CPU usage: 4.00% user, 7.11% sys, 88.89% idle

SharedLibs: num = 19, resident = 76M code, 6272K data, 5004K linkedit.

MemRegions: num = 11811, resident = 571M + 32M private, 247M shared.

PhysMem: 241M wired, 875M active, 396M inactive, 1558M used, 490M free.

VM: 11G + 375M 77169(0) pageins, 0(0) pageouts

 

PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE

663 top 11.1% 0:02.57 1 18 31 1916K 204K 2500K 18M

652 tcsh 0.0% 0:00.02 1 15 24 700K 192K 1160K 18M

651 login 0.0% 0:00.03 1 17 56 332K 232K 1104K 19M

650 Terminal 3.2% 0:01.18 3 100 212 1940K+ 26M 12M+ 366M

645 PubSubAgen 0.0% 0:00.02 2 58 30 480K 8788K 1624K 32M

615 SyncServer 0.0% 0:05.35 2 59 159 26M 8784K 29M 52M

611 mdworker 0.0% 0:01.04 4 73 74 2360K 11M 8536K 39M

521 launchd 0.0% 0:00.28 3 24 26 164K 300K 508K 18M

510 AppleMobil 0.0% 0:04.36 1 43 39 2820K 4832K 4916K 30M

487 iTunes 0.0% 2:31.55 10 274 1072 86M 36M 120M 490M

484 rmdb 0.0% 0:00.00 1 8 22 84K 2084K 308K 20M

483 rmdb 0.0% 0:00.00 1 8 23 36K 2084K 228K 21M

482 rmdb 0.0% 0:00.03 1 15 23 80K 2072K 1004K 21M

481 ARDAgent 0.0% 0:00.20 10 101 67 864K 3156K 3492K 286M

480 Remote Des 0.0% 0:27.37 14 154 340 6752K 34M 20M 399M

450 AppleSpell 0.0% 0:00.09 1 37 31 636K 8504K 2420K 33M

251 iChatAgent 0.0% 0:01.26 5 75 153 9496K 9008K 13M 298M

250 Address Bo 0.0% 0:01.50 4 101 275 9320K 25M 19M 370M

249 iCal 0.0% 0:09.45 3 109 298 11M 29M 26M 374M

248 Safari 0.0% 1:12.69 7 153 708 39M 36M 90M 441M

247 Mail 0.1% 1:10.11 12 323 482 47M 47M 76M 439M

246 iChat 0.1% 0:16.82 9 413 474 31M 39M 48M 428M

239 dmnotifyd 0.0% 0:00.12 5 60 39 2456K 228K 3472K 22M

236 usbmuxd 0.0% 0:03.44 2 22 43 924K 228K 1536K 19M

235 Spanning S 0.0% 0:00.16 1 66 179 2896K 13M 6424K 346M

234 Rogue Amoe 0.0% 0:00.05 1 61 47 600K 8892K 2952K 304M

231 Microsoft 0.0% 0:00.63 2 73 105 4536K 3432K 9724K 355M

229 iTunesHelp 0.0% 0:00.24 2 53 51 804K 7668K 3364K 291M

226 XPSLaunche 0.0% 0:00.08 2 61 54 732K 8940K 3128K 304M

220 racoon 0.0% 0:00.07 1 14 27 228K 224K 1032K 18M

206 Finder 0.0% 0:09.02 6 151 305 5128K 37M 20M 382M

205 SystemUISe 0.0% 0:15.95 9 487 456 6604K 21M 14M 362M

204 coreaudiod 0.0% 0:00.51 2 300 96 2036K 2924K 3940K 23M

202 Dock 0.0% 0:03.56 3 129 400 5116K 42M 19M 373M

201 pboard 0.0% 0:00.00 1 15 25 220K 188K 624K 19M

200 ATSServer 0.0% 0:02.14 2 103 193 1724K 12M 5376K 75M

198 UserEventA 0.0% 0:00.25 2 308 103 816K 5024K 2976K 24M

197 Spotlight 0.0% 0:00.13 2 81 89 1308K 11M 4992K 310M

195 AppleVNCSe 0.0% 0:00.04 2 76 47 532K 6724K 2796K 284M

192 AirPort Ba 0.0% 0:00.08 3 82 175 820K 13M 3648K 343M

191 Folder Act 0.0% 0:00.17 1 59 52 772K 9004K 3292K 304M

189 RetroRunSL 0.0% 0:00.72 1 18 82 3272K 3200K 3492K 78M

177 VNCPrivile 0.0% 0:00.00 1 16 24 148K 188K 624K 19M

168 pvsnatd 0.0% 0:01.41 3 26 28 204K 184K 884K 21M

164 virusbarri 0.0% 1:03.97 22 91 159 78M 404K 79M 157M

161 virusbarri 0.0% 0:00.00 2 16 24 172K 184K 308K 19M

149 launchd 0.0% 0:01.16 3 231 26 280K 300K 596K 18M

140 RetroRun 0.0% 0:02.24 1 14 78 2096K 3196K 2632K 97M

139 qmasterd 0.0% 0:00.04 2 24 54 772K 7240K 4084K 33M

136 integod 0.0% 0:00.97 2 56 97 49M 872K 51M 68M

124 retroclien 0.0% 2:49.32 8 50 37 268K 188K 968K 23M

123 qmasterd 0.0% 0:00.05 1 19 52 704K 7236K 3848K 33M

121 llipd 0.0% 0:02.45 1 8 17 84K 184K 220K 18M

106 intermappe 0.0% 0:00.00 1 14 22 128K 188K 396K 18M

104 WindowServ 1.0% 1:22.98 5 264 1078 6252K- 73M 80M- 412M-

62 krb5kdc 0.0% 0:00.02 1 17 43 480K 188K 1424K 18M

57 coreservic 0.0% 0:01.26 4 219 146 2240K 23M 23M 62M

 

 

Edited by Guest

Share this post


Link to post
Share on other sites

So what it sounds like is Retroclient is crashing. This sounds similar to bugs we are already in the process if trying to fix.

 

What about the crash log?

Share this post


Link to post
Share on other sites
So what it sounds like is Retroclient is crashing. This sounds similar to bugs we are already in the process if trying to fix.

 

What about the crash log?

 

I'm not seeing any crash logs for retro client.

 

Share this post


Link to post
Share on other sites
So what it sounds like is Retroclient is crashing. This sounds similar to bugs we are already in the process if trying to fix.

 

What about the crash log?

 

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

×