twindux Posted January 4, 2007 Report Share Posted January 4, 2007 I have Retrospect Client 6.1.130 on my MB Pro 2.33/2G/120G. After a backup is run, Activity Monitor shows the pitind process taking 99%+ of cpu cycles. I kill the process, and CPU usage goes back to normal, of course I then need to go back to Retrospect Client and turn it back "on" if I want the backup to run again. I'm using OS X 10.4.8.. Any ideas? I searched the forum and didn't see a similar item, although my search on the words... pitond core2duo mac excess cpu.. returned more than 1,000 results, none of which seemed to fit my circumstance. Any help would be appreciated. Link to comment Share on other sites More sharing options...
rhwalker Posted January 5, 2007 Report Share Posted January 5, 2007 Quote: although my search on the words... pitond core2duo mac excess cpu.. returned more than 1,000 results, none of which seemed to fit my circumstance. Boy, you must be a fast reader. I suspect that you needed instead to search on +pitond +core2duo +mac +excess +cpu (so that all of the words were required; your stated search will find posts with ANY of the words - click on the "Advanced search tips" link on the search page to see the quirky usage). A search on that sequence of keywords, with the "+" prefix for the past couple of years, turns up only this post, not over 1000 results. There's an experimental Google search engine for the forums, too. See: Google Search the forum Pretty cool. Sorry I don't know the solution to your issue. russ Link to comment Share on other sites More sharing options...
RaoulSevier Posted January 5, 2007 Report Share Posted January 5, 2007 This behavior has occured on a CoreDuo MBP three times so far. This condition is generally diagnosed by sluggish performance and very hot operating temperature when resuming use of the laptop. No way to tell how long it had been in that state. Backups take place in between so this is not a consistent pattern. Very discouraging. Latest OS rev, 2GB MBP CoreDuo Link to comment Share on other sites More sharing options...
twindux Posted January 5, 2007 Author Report Share Posted January 5, 2007 Thanks for pointing that out, Russ. I will admit that I skimmed the subject lines of the 1000 responses, and did it over a couple of days...but I did get through all pages of posts. I"ll try a few more search scenarios with the + condition. Link to comment Share on other sites More sharing options...
CallMeDave Posted January 5, 2007 Report Share Posted January 5, 2007 Quote: This condition is generally diagnosed by sluggish performance and very hot operating temperature when resuming use of the laptop I'd suggest a better diagnostic tool would be Activity Monitor, using its floating cpu window and/or its list or active processes. Most telling would be to learn the link between how the Retrospect application's backup behaved and how the pitond process behaves. For example, does the issue arise only after unsuccessful backups? Only after successful backups? That sort of information would be valuable. Dave Link to comment Share on other sites More sharing options...
twindux Posted January 5, 2007 Author Report Share Posted January 5, 2007 Activity Monitor was indeed the tool I was using to determine there was a problem. Well, very unscientifically it seems Dave may have hit on the answer. I just checked the logs and noticed that there had been a volume that Retro was unable to find on the remote machine (my MBP). I cleaned that up, and alas, pitond seems to be behaving. So perhaps it's related to unsuccessful backups only? I'll post back after a few more backups. Not quite ready to declare victory yet, but a big "THANK YOU DAVE" goes out to Dave! Rich Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.