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

Similar Messages

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

How do you monitor Xserve 2009 with Mountain?

So, messing around a bit with Mountain Lion on my 2009 Xserve.
How do I monitor the hardware? Server Monitor appears to be gone and trying to use the version from Lion is a no go.
This unit has Lights Out Management. Aside from the IPMITool, how can I modify/configure LOM?
It would be nice to be able to monitor the hardware.
Boy, it is like Apple doesn't want to have servers or something..................................................
Um, so where is ipmitool? Not in /usr/bin and not in the Server.app app bundle.

Just a note about Apple documents; It's important to reccognize that what Apple doesn't say is just as important as what it does say. For instance, in that article it simiply states "To administer OS X Server on Mountain Lion, use Server app version 2 or later on OS X Mountain Lion."
Not only does that statement say what you use to administer, it also says what you can't use. (Any other version of any other management software.)
This seems counter-intuitive to anyone who has used RAC or LOM on other Intel hardware because they understand that RAC/LOM is a firmware or hardware feature and really has very little to do with the OS. Dell, for instance, has a completely seperate PCI card that serves this function with its own network interface, power supply, etc. These methods of remote access simply don't care about the host OS or whether or not the host even has an OS.
This seems to be the case with Apple Xserves, though the NIC is shared, of course; there is apparently a third-party tool that will get to the LOM features of the Xserve, though I've never used it myself. (See above) So the defficiency in this case appears to be the management software itself. The "Server Monitor" app isn't compatible in some way with Mountain Lion and they didn't integrate that functionality into the "Server" app so it's broken.
Though if that were the case, you would be able to use Server Monitor on a Snow Leopard machine to access the LOM on an Xserve running Mountain Lion Server but you can't. So the Host OS must be doing something hinky there. (I vaguely remember an issue with NIC binding in Lion... I think it had something to do with LCAP?)
Anyway, it's just not working right now... I upgraded some workstations to Lion but haven't pulled the trigger on Mountain Lion yet and I won't be upgrading the servers past Snow Leopard Server any time soon... In fact I need to track down a few serial numbers before they're all gone!

Does Server Monitor software work with Mac Pros?

Last time we were purchasing a new server we noticed that Server Monitor doesn't work with Power Macs. Is this still the case with the latest Intel-based Mac Pros?

Hi again Christiaan-
Just to clarify, are you saying that OSX Server is running on the Power Mac and you are using another computer to connect?
If so, which version of each software and which Power Mac?
I am curious as I've had no problem with said configuration.
Luck-
-DaddyPaycheck

Running Windows 2003 Server on Xserve Intel with BootCamp?

Well...
This sounds like awfully bad idea, but one of our clients needs to run Windows 2003 Server for a certain project in their organisation. Fundings for the new hardware is available. Windows-compatible hardware!
The idea here is to get fundings for a new Xserve, run it with Windows 2003 Server in the project and then keep the delicious hardware for free when the project ends. A PC-server would be thrown out of a window in this 100% Mac-centric department.
Windows 2003 Server runs smoothly on a MacPro with Boot Camp and Parallels Desktop. What about the XServe Intel?

Schuckert-
Greetings.
Are you in a position to test the configuration for a while? If so then I vote do it. If not, you could buy a copy of OSX Server and install it on a Mac Pro and try running your software on the XServe platform.
However, depending on your relationship with this client, I would have them sign a release based upon the beta-ness of the software.
A lot of us here are not in a position to give such things a try-just yet. Too busy trying to make things transition smoothly on the accepted configurations.
Although I will say that I suppose a client will eventually pose the question to me (:>)
Luck-
-DaddyPaycheck

Does the Server Monitor work on PowerPC based machine (w/o LOM)?

I tried using the Server Monitor locally on a PowerPC G4 machine which has 10.5.1 server installed. I always get a "Failed to connect to server" error message, except if I try 127.0.0.1 with the original local admin, then I would get a "User and or Password" error.
Strangely, the username of the admin is M999, but if i type in "M999" as username, I would still get a "Failed to connect to server" error, while if I use "m999" as username, I get a user name password error. Either way, I couldn't use Server Monitor.
So I am wondering whether Server Monitor support machines w/o LOM at all? Is there an trick I should know about?
Thanks
Kenneth

Hi
There is no trick you need to know. Its really quite simple, Server Monitor only works with XServes. Apple added LOM capability when they rolled out the Intel XServe.
http://docs.info.apple.com/article.html?artnum=304870
http://docs.info.apple.com/article.html?artnum=304896
http://docs.info.apple.com/article.html?artnum=304897
For more informaiton. Hope this helps, Tony

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.

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.

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

Server Monitoring with clustered instances

Anyone using the server monitor or multiserver monitor with
clustered instances of coldfusion? In CF 8.0.1 on Solaris, enabling
monitoring produces a vast number of repeated errors of the form
included below. This occurs on the both clustered instances as the
instances are setup to replicate session data using J2EE session
variables. The monitoring appears to work but the frequency of the
errors produced in the ouput log of *BOTH* of the cluster instances
is extensive. These errors do not occur when monitoring the
"cfusion" admin instance. Is this a product issue or a
configuration issue?
MM/DD HH:MM:SS error Setup of session replication failed.
[2]java.io.StreamCorruptedException: unexpected end of block
data
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at java.util.Hashtable.readObject(Hashtable.java:859)
...

Dear Jan,
Already I have added the plugin but while adding the target i am getting below error. Can u please give some idea on this
Test Connection failed: [_WinAuthDLLToLoadDynamicProp;em_error=DLL file 'D:\12c_agent\plugins\oracle.em.smss.agent.plugin_12.1.0.2.0\scripts\emx\microsoft_sqlserver_database..\..\..\..\dependencies\oracle.em.smss\jdbcdriver\sqljdbc_auth.dll' is found missing or not was never copied manually. Please copy amd64 version of sqljdbc_auth.dll at the above location and re-try, MSSQL_NumClusterNodes;Can't resolve a non-optional query descriptor property [dllFile] (dllFile), WbemRemote_Determination_DynamicProperty;Can't resolve a non-optional query descriptor property [dllFile] (dllFile), MSSQLInstance_TestMetric_DynamicProperty;Can't resolve a non-optional query descriptor property [dllFile] (dllFile), OSType_TargetHost_DynamicProperty;Can't resolve a non-optional query descriptor property [STDINWBEM_HOST] (ms_sqlserver_host), MSSQL_NumClusterNodes;Can't resolve a non-optional query descriptor property [dllFile] (dllFile)]

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.

Server Monitor on Xserve running Client OS

I have an Xserve running the regular client OSX (Filemaker Server, didn't see the point in installing the full Server OS). Is there any way to get Server Monitor running? I would like to be able to keep an eye on the hardware functions.

Is there any way other than loading Mac OS X Server, you mean? Not directly.
You could enable and use the [SNMP daemon within the Leopard Mac OS X client|http://www.bynkii.com/archives/2007/12/aprimer_to_snmp_on_mac_os_x1.html], but that won't give you the Server Monitor interface.
Or you could see if the [Lithium software|http://lithiumcorp.com] is sufficient for your needs.
Or you could load the 10-client Mac OS X Server distribution, which has the monitoring stuff baked in.

HOW TO: Relay/Send email from websites, Server Monitor in OS 10.5 Server

If you don't want to run your own mail server or configure DNS on your Xserve, but you still want your website or applications like Server Monitor to send email notifications; this is what you need to do:
Scenario: Mac OS 10.5.2 Leopard - Advanced Configuration - Setup is for strictly sending emails through SMTP, routed through your ISP or another provider. This is not for receiving emails.
-Open up Server Admin
If you have yet to add in a server to admin, you need to do so. Resource PDFs on setting up OS X Server are available at Apple http://www.apple.com/server/macosx/resources/ and there are video tutorials at http://movielibrary.lynda.com/html/modPage.asp?ID=373
-Click on your server, then choose the Settings button
-Then choose Services from the Tabs/Buttons below
-Select the Mail checkbox and then hit Save
-Now choose the newly added Mail service in the left pane, then click the Settings button up top
-Start with the Advanced tab. Under Security, un-check everything and don't use SSL unless you want to. You don't need to mess with the other sub-tabs here.
-Next choose the Logging Tab. Under SMTP log level, choose debug so you will be able to see what goes on in the log.
-Mailing List, Quotas and Filters tabs can go untouched. You can mess with them later if you want.
-Click the Relay tab. It is a good idea to only accept relays from your local machine. If you uncheck this, I believe it leaves you with an open relay that anybody can access.
-Now for the General Tab. Under Domain Name put anything you want. Any made up name and extension is fine.
Under Host Name, again put anything you want.
Un-check Enable POP, Un-check Enable IMAP - Basically un-check everything
Check or leave checked Enable SMTP
Now check Relay outgoing mail through host:
Then enter your hosts SMTP server. ex. smtpout.secureserver.net
Now check Authenticate to relay with user name: and enter your username and password
-Now hit the Save button
-Now we need to take a look at the main.cf file and add a few things
-If you aren't showing all files in Finder already, open up Terminal.app
Now type in: defaults write com.apple.Finder AppleShowAllFiles True
Hit enter
Now type in: killall Finder
Now Finder should reset and all files should be visible - To hide all files, do the same thing but type False
-Now open Macintosh HD and navigate to /private/etc/postfix/main.cf (Note: you won't be able to open and edit this in TextEdit. I recommend a program like TextWrangler http://www.barebones.com/products/textwrangler/download.shtml )
-Once you have main.cf open, all your settings should be together at the bottom of the doc. Scroll down. You will need to add in a few lines and verify all the settings are exactly as below (except of course your own names and SMTP server):
readme_directory = /usr/share/doc/postfix
mydomain_fallback = anything.anyting
messagesizelimit = 0
myhostname = anything.anything
mailbox_transport = cyrus
mydomain = anything.anything
mailboxsizelimit = 0
enableserveroptions = yes
inet_interfaces = all
relayhost = smtpout.secureserver.net
smtpsasl_passwordmaps = hash:/etc/postfix/sasl/passwd
smtpsasl_authenable = yes
smtpdsasl_authenable = no
smtpsasl_securityoptions =
smtpduse_pwserver = no
smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
smtpdpw_server_securityoptions = none
-Now save the main.cf document
-Now go back to Macintosh HD and navigate to /private/etc/postfix/sasl/passwd
Open passwd with TextWrangler or you editing app, and verify that your SMTP server, username and password are correct. It should look something like this:
smtpout.secureserver.net [email protected]:password
-This should be what you entered in Server Admin when you first started. If all is well, quit your editing app.
-Now, while you are still at /private/etc/postfix/sasl/passwd you need to edit permissions for passwd
You can chmod in Terminal.app or secondary click on passwd and "Get Info"
Click the lock and enter your password to unlock the settings
Next click the + button and add yourself and Admin
-Now you can close out of everything and go back to Server Admin
-Hit the Reload (twisty arrow) button at the bottom and once everything is reloaded, hit Start Mail
-Now type localhost in your browser to see if your website can send email. You can also open up other apps such as Server Monitor and do something to change the status to have it send an email.
-You can click on Mail in the Server Admin and then view the SMTP log. As long as emails are being sent and then removed from the queue, you are in good shape. If you are getting an SASL error or mechanism error, open up main.cf and verify your settings and/or check permissions on passwd file

Don't you need the Mail service running to have apps like Server Monitor send email notifications? - Also for hosted sites that use the sendmail function you need a service running to get the emails sent.
Really you are not hosting a Mail server. It is open, but there is no incoming and if you only accept SMTP relays from the local machine, there should be no issues.

Server Monitor no longer working between 10.5 client & 10.4 servers?

I've been running Server Monitor 1.5f6 under 10.4.x on my desktop machine to monitor a dozen or so Apple Xserves running 10.4.x Server for ages (3 years?). Upon upgrading my desktop machine to Leopard the Server Monitor application no longer connects to any of the remote Xserves. They simply state "waiting for connection". I tried every "expert" diagnostic I can think of including deleting prefs, caches, adding & removing server entries, firewall off (on the server), etc. I also observed that upon quitting the application, it often produces a crash message instead.
So I tried what I thought would be the obvious fix of upgrading to the latest Server Admin Tools suite (downloaded from Apple, also v10.5) on my desktop which includes Server Monitor 1.5.1-- only to discover it does not work either.
If I boot back into 10.4, everything works again so I am 110% sure the problem is related to Leopard. The 10.4 servers can also monitor each other fine (as a test).
Now I've seen some similar reports in this forum about problems with the admin tools after 10.4.11 and such. But none of them clearly described IMHO the exact problem of using Server Monitor under a remote Leopard client to monitor a 10.4 Xserve.
Can anyone else confirm this problem? Am I missing something?

Wow, thanks for the article reference. Some times no amount of searching will uncover the hidden treasures.
So... not to be too dramatic but... what is Apple trying to do? PUNISH users that have not purchased any copies of 10.5 server? Why wouldn't they release a stand-alone Server Admin Tools installer like they have in the past? (They "forgot"???)
As it appears someone attempted the package extract approach (and it didn't work), can someone offer another solution?
p.s. Where is that number for my Apple rep... >:-( UNHAPPY!

Server Monitor - XServe G5 with OS X 10.4.10 client

Similar Messages

Maybe you are looking for