Server Monitor on Intel XServe Problem

2 weeks ago - our new XServe Intel arrived. It is our 3rd, one G4 XServe running 10.3.1 sind 2003, one DualG5 XServe running 10.4.8 since 2005 - nonstop uptime.
So both machines run well.
With the Intel XServe I installed the new AdminTools like ServerMonitor on a Powerbook G4 and a old G4-466 - both running 10.4.8
But now I have 2 Problems:
First: With Intel XServes Server Monitor I can access the 10.3 Server, but I cant see the little icons and check things like van rpm or CPU temperature - it just shows nothing. Using the G5s 10.4 ServerMonitorversion it works.
Second: I am unable to connect to the Intel XServe via Server Monitor - it always tells me "Auf Antwort warten" in English like "Waiting for response", not even with the G5 Softwareversion.
I already checked the com.apple.hwmond.plist file and startet the hwmondSetup in the Terminal - nothing works.
Even not, when I start the application on the XServe itself.
ServerAdmin and the rest of bundled software is running well.
Anybody knows?
ChB
XServe 2.0 XEON 4 GIGRam Mac OS X (10.4.8) 4 GigByte Ram, RAID Boot Volume, SCSI RAID attached

Check out this link:
http://docs.info.apple.com/article.html?artnum=304833

Similar Messages

Server monitor not working (hardware monitor)

Just finnished installing my brand new maxed out Intel Xserves. And the Server monitor isn't working.
This thread:
http://discussions.apple.com/thread.jspa?messageID=643361
Didn't solve my problem. hwmond is running on the Xserves but each server line just says "Waiting for response". My /System/Library/ServerSetup/SetupExtras file doesn't even HAVE a Disabled key. It has Label, OnDemand, Program, ProgramArguments and ServiceIPC keys, but no Disabled. And the hwmonds is running anyway.
I have opened server monitor on the xserve itself and tried to open it to itself with no luck. I have configured Lights out management by choosing Server->Configure local Machine and added another IP there with different login, but I can't connect to either IP. Firewalls are all turned off.
Running /System/Library/ServerSetup/SetupExtras/hwmondSetup just says "already loaded"
Server Admin works, I can log in and edit services. Workgroup manager also works.
When i run the hwmond as root on the server, it says "Failed to communicate with the front panel" which could be due to hwmond already running, but I can't turn off the process since launchd (?) launches it again.
When I choose "Configure local Machine" the password I entered is always blank, but maybe that's by design.
Since these servers aren't installed yet I have them in my office and their IP's are temporary, so I read this:
http://docs.info.apple.com/article.html?artnum=106830
And it says that for this environment I should set the hostname to "localhost" in /etc/hostconfig. Done. Nothing changed.
I've googled this and searched here but found nothing. I'm running out of options... What should I do?

I set the server on a desk and do a fresh install off a DVD with the "erase HD" option. Then I install and configure the software I need (Software update, Sophos, power options, etc.) I did not configure LOM at that point, because I wasn't sure how to do it, and I needed to deploy the server. (luckily LOM was easy enough to set up after it was deployed.) Once the server is ready, I connect a FireWire HD to it, which has OS installed on it and boot from that.
That way my server is just an attached disk, and I use Disk Utility to create an image of it, which I then deploy on other servers.
I've had an issue with the G5 XServes where such a method required relatively simple modification before the server monitor would work:
http://docs.info.apple.com/article.html?artnum=301046
But, I've not had to do that with the Intel XServes.

How can Server Monitor report status if LOM isn't configured?

I'm now managing a large number of Xserves (PPC & Intel, 10.4/5/6) and the organisation has not before relied on LOM or central reporting of faults.
I predict most of my issues are firewall related (many remote sites) but there are some remote machines that do appear and function in my Server Monitor running on my macbook... but when checking the LOM config on that server it turns out there's nothing configured... how is this so?
Does LOM have to be fully configured to allow Server Monitor to function? or only to allow for 'remote hands' when the server is flaky, and Server Montior will function just as long as LOM is enabled?

bpwell wrote:
I'm now managing a large number of Xserves (PPC & Intel, 10.4/5/6) and the organisation has not before relied on LOM or central reporting of faults.
I predict most of my issues are firewall related (many remote sites) but there are some remote machines that do appear and function in my Server Monitor running on my macbook... but when checking the LOM config on that server it turns out there's nothing configured... how is this so?
Does LOM have to be fully configured to allow Server Monitor to function? or only to allow for 'remote hands' when the server is flaky, and Server Montior will function just as long as LOM is enabled?
It may depend on the model of XServe. Older models did not have LOM so obviously LOM is not needed for those (e.g. an old G5 XServe). I also found that if your running Server Monitor on the XServe itself then it can locally monitor without LOM, but for other XServes I found I did need to configure LOM.

Server Monitor Version 1.6.1 (2) won't send email notification

I am running Server Monitor Version 1.6.1 (2) on a Mac Pro 10.5.8. It is monitoring an Intel XServe 10.5.8 and a Dual G5 XServe 10.4.11.
I had a bad UPS and Server Monitor only emailed notification of the 10.4.11 XServe going down but not about the 10.5.8 Intel XServe going down. I checked the log for the Intel XServe and it says, "Email notification could not be sent to ..."
The email notification settings are the same for both Servers.
Any ideas how to get email notification working for the Intel XServe.

A little more info...
Also, the G5 XServe uses it's actual IP address while the Intel XServe uses a different IP because of LOM.
The G5 Xserve requires password authentication to change email settings while the Intel XServe does not.
ANY suggestions here???
Thanks!

Intel Xserve not contactable via Server Monitor

I simply cannot get our new Intel Xserve to show up in Server Monitor. The app just sits there saying "waiting for a response". Our old G5 Xserve shows up, in 10.4 Server Admin and 10.5 Server admin, on either box. Apart from this, the server is functioning normally, no errors, Open Directory, Home Directories, Apache etc. But it's really annoying as in their current environment I need to keep an eye on the core temp etc. Can anyone suggest a way to find out what is wrong?
Thanks for your time - it's much appreciated.

Connect onto the Xserve box (on the console or ARD or such) and follow the instructions to set up the LOM port with a unique IP address, and ensure you're on the same LAN and subnet as the LOM port.
[Here's the basic LOM configuration sequence|http://support.apple.com/kb/HT2773].
The initial configuration is (often) via Server Monitor invoked directly on the local box and connected directly to the local host.
Use a unique IP for the LOM on each NIC it is active on.
And remember to power-cycle (and unplug) the box when you make significant changes to the LOM.
It's possible to do this via ipmitool if you don't have graphics console access to the box, but (for the sake of brevity) that access is being assumed here.

Intel Xserve power problems

As of recently, I just started noticing a issue with powering on a new intel xserve. If the machine is running, using LOM and shut down works beautifully. After I shut it down, using LOM and the button works beautifully. If i attempt to turn it back on a few min later, it works fine.
If I leave it off for a day or so, even though the lights are on on the front of hte machine, LOM can see the server, but "power on" doesnt do anything, and hitting the front power button doesn't do anything. I have to unplug it from the UPS and replug it in for it to turn on.

Hi Forum folks.
I've had a 6-month (ish) Xserve doing the same thing. Every day, at least once a day, I'd get an email / SMS, saying the power supply or blower was having a momentary problem.
After shutting down the server, I pulled out the Power Supply Units, and checked them out.
Turns out, one of them had a slightly damaged heat sink (damage visible without opening the PSU). So, I swapped it for a spare I'd purchased. And then got the damaged unit (damaged internally at factory by the look of it) replaced by my Apple Reseller.
Note: the newer Intel XServes (early 2008) have a 750w PSU, compared to a 650w PSU, in the 2006 Intel XServes. The older PSUs fit in the newer Xserves, but they DO NOT function. (You'll get an error in Server monitor).
Hope that helps,
Cheers,
Derek

Intel Xserve with Leopard Server 10.5.5 won't let me in via login

A power outage appears to have created some issues with my intel Xserve, running Leopard server 10.5.5
The System identifier light was blinking, so I booted up from the Leopard disk and found out that my mirrored internal array needed to be rebuilt. No problem, 4 hours later, I repair permissions on the mirrored internal array, everything gets "repaired". Change bootup disk to the internal 10.5.5 mirrored array and reboot. System Identifier light stopped blinking, things were looking good.
The login screen comes up and when I put in the admin username and password, the screen does the shake of the wrong login.
What's weird is, on my laptop I can use Server Admin, Workgroup Manager, and the screen sharing for the server....with the admin username and password.
So, I figure, perhaps the mirror rebuild requires me to reset the admin password. So, boot back up from the Leopard Server install DVD, run the password utility. and reset the main account password.
I change the boot drive back to the internal mirror, same thing. I'm stuck. I can't get past the login screen on the actually server....or via the screen sharing...and Server Monitor appears to be stuck at 'waiting for response'. I can, again, use Server Admin and Workgroup Manager on my laptop and make changes to the X server software....but I can't log into the X serve.
My webpage, wiki, etc....are all serving fine. But, I'd like to be able to figure out what I'm doing wrong...log back in and run super duper, etc.
Help...please...

Spent all day with apple support. They said it sounded like the LADP database was corrupted. They had me try to login as root, via an opendir account, etc. No luck.
So, they suggested I do a fresh install of the Leopard server on an external drive. Did that. They then suggested I use my laptop and the workgroup manager app to log in to the xserver, export users, groups and computers....and to copy over the library/collaboration folder to the external "clean install" of Leopard server.
Did that and followed the instructions to "relink" the metadata.plist files in each group, to the GUID to the groups in workgroup manager. First issue, they weren't different GUID strings.
Well, that didn't work...kept getting file not found error. When trying to access the domain.com/groups/groupname...it should've asked for authentication. And let me into that wiki...but no, apache error page.
So, they had me create a new "test" group....added a user. Start and stopped the web...etc. This didn't create a new wiki entry (when we replaced my custom index.html to the default index where groups/wikis/blogs populate automatically at the main). And, there's no new "test" folder in the library/collaboration files.
They then said "well, it must be because you don't have reverse DNS configured right, that's why the new wikis won't set up". I've contacted dyndns.com...but I don't think that's the problem.
So, I've rebooted my xserver to the internal drive. The wiki and blog is still there, still accessible the way I like....I still can't login to the xserver.
So, I'm wondering, if anyone knows a way I can boot up my xserve in the target drive mode, hook up my laptop and replace / swap whatever admin files so that when I boot up my xserve, I can login again.
There has to be a way to hard fix a hidden file? Replace a DB? Some awesome terminal command to get me in and fix the admin account / password....
Or, does anyone know if the reverse DNS issue applecare cites is legit? Doesn't make sense how, the same public ip and domain name, that's worked for some time...suddenly doesn't???
I'm hoping someone can help me.

XServe + Server Monitor = "Waiting for response"

I have 5 Xserves. All are running 10.4.6 Server. One of them I am able to connect to via Server Monitor. I have done a bit of searching the forums and can't find anyone with a similar problem. What can I look for to start troubleshooting this?
Thanks!

Thank you for the response.
XServes are on different subnets. The one I am able to connect with I can connect with no matter what subnet I am on. I cannot talk with any of the others regardless of which subnet I am on.
Admin tools are a fresh installation (recently reinstalled system) MacBook Pro, fully updated.
I am trying to connect to the servers via >server>add server and entering their IP addresses in. I can connect to the servers via Remote Desktop, as well as with AFP shares. The servers are working correctly, with the exception of my inability to use the Server Monitor.
I also cannot seem to use the Server monitor locally on the machine. If I run Server Monitor and try to connect to the server via 127.0.0.1 or via it's internal IP address, I get the same "Waiting for response" message.

Monitor Tiger Xserve from Server Monitor on Leopard machine?

I can't get my G5 Xserve 10.4.11 to show up in Server Monitor 1.6.1 (2) running on my Mac Pro.
My Intel Xserve 10.5.6 shows up just fine.
In fact the G5 Xserve even shows up in Server Admin but I just get 'Waiting for response' from Server Monitor.
I recently rebuilt the G5 Xserve 10.4.11. I wonder if there is something I forgot to reconfigure after the rebuild?

Sorry, somehow got into the regular 10.5.6 forum was looking at the 10.5.6 Server forum earlier. I will repost.
If there were an admin, I'd ask to have the post moved

Problems with server monitor

Hi all,
2 days ago, I cant connect to my xserve via Server Monitor ... and I dont know why. Via server admin I dont have any problem. The message is the following:
"Waiting for response" ....
I see the following web:
http://www.afp548.com/article.php?story=20070211101829496&query=lights%2Bout%2Bm anagement
Is useful this command?
Is there any manner to restart the LOM Interface without power off the xserve?

I've seen that happen once or twice, when the Xserve LOM got confused and/or the daemon became confused.
In the immortal words of the IT Crowd — "Have You Tried Turning It Off And On Again?" I've cleared that by shutting down Xserve entirely, removing grid power for 30+ seconds — it's that power removal which triggers the complete LOM reset, the physical disconnection of Xserve from the grid power — and then re-connecting and re-powering and rebooting the Xserve. If Xserve isn't physically disconnected from grid power, the LOM retains power.
Here are the LOM setup details. There are a couple of related threads around, as well; here's one.
You may alread be aware of this, but if you're using Server Monitor directly from the local Xserve system, you must use the local connection path and not the network path, too.

Intel xserve Server Admin

For some reason, even after installing the new server admin tools off the CD that came with the new intel xserve, I simply get a "waiting for response" in server monitor and the CPU graphs are dead in server admin.
Also, this isnt due to the server, cause when I ARD to the server itself and check out the server monitor, it does work... No firewall or anything either.

Quick Update:
A firmware update came up in my software update on my intel mini that would supposedly fix the issue... it didn't and my g5 tower still doesn't see anything either.

Xserve RAID: Server Monitor says degraded, disk utility says mirror FAILED.

Xserve Quad Intel 4x2GH
4096 GB RAM
OS X Server 10.4.11
Xserve RAID 7TB 14x 500 GB ADM via dual fiber channel, Mirrored, 3.5 TB array.
Flashing yellow indicator light on Xserve this morning. Investigated and found that RAID Admin says everything is OK, all 14 drives normal.
RAID Admin log says :"4000 1 Wed Apr 08 09:37:59 EDT 2009 Disk 2 Failed To Respond. Retrying. RETRY COUNT:0 LBA:0x1C700"
Under the RAID tab, Disk utility says: "Mirrored RAID Set: Degraded" and "Disc2s3: FAILED"
All LED's are solid green across the front of the ADMs.
Since all my drives are reporting OK, could this be a problem with the Fiber Channel interfaces?
Should I just backup (again), shut down and rebuild the mirror using Disk Utility?

Hi Kappy<
I am trying to migrate user data from a RAID - 1 slice from my old PowerMac G4 running OS X 10.4.11 to my new MacBook Pro running OS X 10.5.4 by reading a mirror RAID slice from my old Mac that is mounted in an external drive enclosure and connected by FireWire.
The problem is that the new Mac cannot read the old Mac disk, it never shows up on the desktop, or comes up as available when trying to use Migration Assistant. Then, if I go into Disk Utility, the external RAID slice shows up briefly with a locked yellow padlock beside it, then I suddenly get the window shade of death, and have to hold down the power button to reset/restart my MacBook.
Why can my new computer not read my old computers disk, and how can I change permissions, or make the old drive readable by the new mac.
Regrettably I am away from the original Desktop, and cannot load the old drive back into it, connect the two machines and migrate that way. My only option for reaching my necessary data is to retrieve it off the drive I have with me.
Thanks in advance for any help you can offer.

2 Intel Xserves, both running fast and both unable to connect to Server Mon

Hey guys -
Since this is happening to two identical machines, I'm wondering if I'm just not doing something right.
I have two Xserves, both essentially functioning as metadata controllers for an Xsan volume. They don't do anything else but they both run fullblast at all times.
When I initially set them up, I disabled LOM on them. However, I can't connect to either of them using the Server Monitor. This is being done locally through a belkin KVM switch, so it's nothing to do with firewall issues. They're both on two networks, a private one (for the Xsan metadata) and a public one that operates through proxy servers. Currently, neither of them can physically connect to the internet (owing to an error in the proxy settings I'm guessing), both other machines in the local network and see them and connect to them.
They're both the same configuration, with 2GB of RAM, and operating at 10.4.8. They have dual power supplies and are running into two separate UPSs for power redundancy.
I was wondering if updating to 10.4.10 would have an effect on them, or if there was a procedure to reset the PMU (or SMU or SMC or whatever they call it these days) on them.
I've been searching these forums for similar issues, but most of them seem to be related to intel xserves which actually HAD LOM turned on, and these guys do not.
If it isn't any of these issues, how would I go about thermally recalibrating both of them?

well, I done fixed it.
After I got LOM up and running (127.0.0.1 was the way to go), I was able to see that the CPU intake fans were all blowing at a strong 16K rpm. Not a good sign, even though there were no warning lights going off and everything was reported as green and normal. Since this SAN lived in a hushrack (two servers and two RAIDs all told), I first tried to isolate airflow out of the equation by removing the back enclosure and opening the front door. Even after the heat dissipated, it ran at top speed. I ran all software updates possible, installed the OS onto an empty hard drive, and still got the same thing. I yanked one of the systems out of the rack it was in and swapped the fibre card from slot 1 to slot 2. I started it back up before returning it to the rack and, goodness me, it topped off between 5K-6K. I was so happy with myself that I tossed it back into the rack, patched it all back in, and fired it up. Boom. After about a minute of being on, it rocketed upwards straight to 16K rpm.
So now it was a matter of playing the isolation game. I pulled fibre cables, I tested the power cables in both the UPS and straight into the wall, I pulled the KVM switch out and just stood by listening for any changes.
It turned out to be two bad ethernet cables, of all things. I'd plug the cable in and the fans would start their best jet engine impression. The primary metadata controller had a bad metadata cable, and the open directory master had a bad public ethernet cable.

Why does Server Monitor not work with non-Xserves?

Does anyone know why Server Monitor does not work with non-Xserve computers? We acquired a Power Mac for a server, based on there being no apparent difference except for the obvious. Turns out there are some differences after all.
Do Power Macs lack some hardware components or is this just a software thing?

God question, unfortunitly I dont have the answer but I would also like to know why the software only works for X-Serve....Is there any 3rd Party Software that is similar to "Server Monitor"?
Thanks

Server Monitor - XServe G5 with OS X 10.4.10 client

Hello,
We run here multiple XServe G5. When purchased, they came with OS X Server 10.3.x
We have configured one of the servers with OS X 10.4.10 Client! because of some of the features of OS X 10.4.x. We are running newer versions of MySQL, PHP and Apache, as well as a third-party FTP server, and didn't want to be bothered with buying and extra license of OS X Server 10.4, now that 10.5 is around the corner. Anyhow...
The OS X 10.4 client does not implement the hardware monitoring System, Server Monitor. My understanding is that Server Monitor is a GUI front-end for hwmond and relies on 3 files:
/usr/sbin/hwmond (Hardware Monitor Daemon)
/System/Library/LaunchDaemons/com.apple.hwmond.plist
/System/Library/ServerSetup/SetupExtras/hwmondSetup
I have copied these files from another XServe G5 (this one running the real thing, i.e. OS X Server 10.4.10) to the respective locations on our XServe with OS X client. I have restarted the server, but things didn't work out.
What did I miss?
Thanks for anyone who can help

You can still use iCloud eMail though, if that helps...
I understand .mac mail will still come through. Do not delete the old account yet.
You cannot use .mac or MobileMe as type of Account, you have to choose IMAP when setting up, otherwise Mail is hard coded to change imap.mail.me.com to mail.me.com & smtp.mail.me.com to smtp.me.com, no matter what you try to enter.
iCloud Mail setup, do not choose .mac or MobileMe as type, but choose IMAP...
On second step where it asks "Description", it has to be a unique name, but you can still use your email address.
IMAP (Incoming Mail Server) information:
• Server name: imap.mail.me.com
• SSL Required: Yes
• Port: 993
• Username: [email protected] (use your @me.com address from your iCloud account)
• Password: Your iCloud password
SMTP (outgoing mail server) information:
• Server name: smtp.mail.me.com
• SSL Required: Yes
• Port: 587
• SMTP Authentication Required: Yes
• Username: [email protected] (use your @me.com address from your iCloud account)
• Password: Your iCloud password

Server Monitor on Intel XServe Problem

Similar Messages

Maybe you are looking for