So you have reinstalled or installed Apple OS X 10.4 server. And you have noticed that no matter what you do you can’t get the Apple OS X Server to talk to your Server Monitor application all that you see is “Waiting for response” where you should be seeing other info like the Drives Temperatures Fan Speeds etc.
I have only noticed this on a 10.4 Server where I installed the Server in Target Disk Mode using Firewire. The Xserve is a G5 dual with no graphics card (also called a headless server) The server was installed via a G4 Powerbook.
Anyway When the system installs it seems to check the hardware now because you have mounted the OS X Server Hard drive onto your other Mac (non Xserve) my guess is that it does not / can not probe the correct hardware, and since the Apple Powerbook is not a G5 Xserve it can not configure the hardware monitor properly.
Anyway to get around this, first make sure that you are in fact connected to the IP address of the Apple Xserve and you don’t have and username password issues. So make sure that servermgrd is running you can open Apple’s Server Monitor and check to see that you can login and see to correct information listed there. Also you can check that the server is listening on port 311 a simple lsof – i | grep server
And you should see something like this in your Terminal
servermgr 656 root 16u IPv4 0x05776f98 0t0 TCP *:asip-webadmin (LISTEN)
servermgr 656 root 17u IPv4 0x0577677c 0t0 TCP *:asipregistry (LISTEN)
servermgr 664 root 16u IPv4 0x05776f98 0t0 TCP *:asip-webadmin (LISTEN)
servermgr 664 root 17u IPv4 0x0577677c 0t0 TCP *:asipregistry (LISTEN)
Now if all this is in place and you still get the “Waiting for response” in Apples Server Monitor you can simply sudo (or su to root but that’s not suggested) /System/Library/ServerSetup/SetupExtras/hwmondSetup
And then check your Server Monitor again.
You should now see all the data you would expect to.
As far as I know hwmondSetup is only available in 10.4 and I would guess 10.5 not that I have a 10.5 Server to play with. but from what I can tell hwmondSetup is not a part of 10.3 or below.
I have only noticed this on a 10.4 Server where I installed the Server in Target Disk Mode using Firewire. The Xserve is a G5 dual with no graphics card (also called a headless server) The server was installed via a G4 Powerbook.
Anyway When the system installs it seems to check the hardware now because you have mounted the OS X Server Hard drive onto your other Mac (non Xserve) my guess is that it does not / can not probe the correct hardware, and since the Apple Powerbook is not a G5 Xserve it can not configure the hardware monitor properly.
Anyway to get around this, first make sure that you are in fact connected to the IP address of the Apple Xserve and you don’t have and username password issues. So make sure that servermgrd is running you can open Apple’s Server Monitor and check to see that you can login and see to correct information listed there. Also you can check that the server is listening on port 311 a simple lsof – i | grep server
And you should see something like this in your Terminal
servermgr 656 root 16u IPv4 0x05776f98 0t0 TCP *:asip-webadmin (LISTEN)
servermgr 656 root 17u IPv4 0x0577677c 0t0 TCP *:asipregistry (LISTEN)
servermgr 664 root 16u IPv4 0x05776f98 0t0 TCP *:asip-webadmin (LISTEN)
servermgr 664 root 17u IPv4 0x0577677c 0t0 TCP *:asipregistry (LISTEN)
Now if all this is in place and you still get the “Waiting for response” in Apples Server Monitor you can simply sudo (or su to root but that’s not suggested) /System/Library/ServerSetup/SetupExtras/hwmondSetup
And then check your Server Monitor again.
You should now see all the data you would expect to.
As far as I know hwmondSetup is only available in 10.4 and I would guess 10.5 not that I have a 10.5 Server to play with. but from what I can tell hwmondSetup is not a part of 10.3 or below.
Comments
servermgr 656 root 17u IPv4 0x0577677c 0t0 TCP *:asipregistry (LISTEN)
servermgr 664 root 16u IPv4 0x05776f98 0t0 TCP *:asip-webadmin (LISTEN)
servermgr 664 root 17u IPv4 0x0577677c 0t0 TCP *:asipregistry (LISTEN)" how would I get that to show up? Granted I have different services running on my server, but are those services that pop up a nesscisary to make server monitor work correctly?
Thanks,
Mack
Dont't expect the same results exactly.
What you are looking for at lease in OSX 10.4 and 10.5 is servermgr TCP *:asip*