Python Running CPU Overtime

Question

Level 1

48 points

Python Running CPU Overtime

iStatMenu shows that every five seconds Python usage of the CPU is at 90 to 99.9%. Then it drops back down, then up again endlessly. This is even whne the computer is sitting idle with no apps at all running. The graph is steep peaks and valleys.

Activity Monitor shows _teamsserver and _devicemgr as the most active users and a parent process being launchd.

I do have Mavericks Server installed, but nothing in it is active since I use it to administer a remote machine. In Safe Mode it doesn't happen so I killed everything set for start up with no change.

The activity keeps my computer running hot and eats up the battery so it's a serious concern.

How do I find out what's doing this and stop it?

MacBook Pro, OS X Mavericks (10.9.2)

Posted on May 28, 2014 6:13 PM

Reply

Answer 1

kelhak1

Level 2

232 points

May 28, 2014 6:51 PM in response to James Cook2

Hi James,

Did you try running Activity Monitor and quitting the process that's doing that?

gl,

kel

Reply

Answer 2

James Cook2 Author

Level 1

48 points

May 29, 2014 7:04 AM in response to kelhak1

I hadn't tried that but have now. Once I Quit the Python activity associated with _teamsserver, activity by collabd went through the roof. I Quit that too and it flat lined for a while but eventually they started up again on their own.

But, all of this lead me to locating a thread on caollabd. It is a Mavericks Server related process and shouldn't be runnign with all servcies shut down. The thread offered a Terminal command that does shut them down when the graphical interface fails to do so:

sudo serveradmin status $service | grep "RUNNING" && sudo serveradmin stop $service

My CPU now shows the lowest level of activity that I've seen in a very long time.

The lingering question is whether or not it will last through restarts.

Reply

Answer 3

Linc Davis

Level 10

209,739 points

May 29, 2014 8:59 AM in response to James Cook2

You set up the machine as a server, which you don't need to do in order to administer another server remotely. Quit the Server app and drag it to the Trash, but don't empty. Confirm that you want to stop all services. Then put the app back where it was and launch it.

Reply

Answer 4

James Cook2 Author

Level 1

48 points

Jun 5, 2014 7:57 AM in response to Linc Davis

You may have something there on the origins of the problem. There was a time when I inadvertently chose "This Machine" when launching Server.app.

Apparently although I never actually started any services and the GUI showed nothing running, something was running. The Terminal commands I used stopped it, possibly your suggested Trashing would do the same. I tried it and got the messages you mentioned. I'll remember it in case I ever encounter the scenario again.

Thanks

Reply