Power Management/Slave Scheduling on Mac OS X

Deadline
1

Hi,

I’d like to use slave scheduling on the Mac and I’m not sure what I need to do to get it working. I’ve checked the documentation and couldn’t see anything. We run a system with two subnets 1 for PCs and 1 for Macs. We run pulse on the Windows server connected to both networks. When I try to restart a slave from the monitor it doesn’t do anything.

Any help or suggestions would be great.

Nick

2

Hey Nick,

The first thing to check is if the Launcher is running on the slaves. The Launcher handles the remote communication, so it would receive the command from the Monitor and then pass it on to the slave.

If it is already running, do you get an error message in the remote command window in the monitor after sending the command?

Cheers,

  • Ryan
3

Hi Ryan,

Yeah the launcher is running. The error I got was “The requested address is not valid in it’s context 255.255.255.255:5042”

I haven’t installed vnc or anything similar on the mac so you can’t remote connect to it…

Nick

4

Hmm… in the slave list in the monitor, is it showing the correct information for the machine’s IP and Mac address?

5

Yeah it’s showing the right IP address and Mac address in the monitor. I am running to named slaves on that machine could that affect it? We have also specified 255.255.255.0 as the subnet mask on the PC, although I’m not really sure why or what I need that for…!

Nick

6

Running two slaves on the machine shouldn’t be an issue. The Launcher on the machine would accept the command and pass it on to the correct slave.

Are you able to ping this machine from the machine you’re running the Monitor on?

7

No, They’re on different subnets that don’t talk to each other. I can do it from the machine that pulse is installed on though.

8

OK, I’ve moved on a step. From a Mac to Mac we have some remote control from the monitor. I can start the slaves but don’t seem to be able to kill them even though it says it’s succeeded. I also scheduled them to turn off using the power management tools and it appears in the power management history but the slaves are still running.

Nick

9

You can check the launcher log on the node you’re trying to stop the slave on to see if it is having problems. You can find the log folder from the Help menu in the Launcher app. It should show it receiving the message to stop the slave, and then if there is an error in doing so, hopefully it will follow in the log. Feel free to post a log and we’ll have a look.

Cheers,

  • Ryan