This is great! Thanks!
I've modified it a bit to suit my needs, and have posted my
modifications. It just uses the same method to get the Max Warn Temp
and the Max Fail Temp, and spit those out as well, just so you can get
a feeling for how your server's doing. I've also added Fahrenheit
output to the display and tidied it all up into a table.
A couple caveats:
1.) I've only tested it on our DualG5 XServer (10.3.7)
2.) I've never programmed in Python before
3.) My programming skills in general are very rudimentary
As such, it may not work, or I might have done in 50 lines that which
would take 3 with an experienced programmer. It's not efficient, but
I've tried to make it as tidy as I could.
You can see the script here:
http://divinity.acadiau.ca/~ahankins/servertemps.txt
Let me know how you like it.
Andrew
On Tue, 22 Feb 2005 15:50:17 -0800, Todd Dailey <email@hidden> wrote:
> FYI, I updated this script today to be more robust. Linked here
> (instructions are here too for the Python novice):
> http://todd.dailey.info/archives/2005/02/22/xserve-temperature-logging/
>
> Or just get the script here.
> http://todd.dailey.info/files/xserveg5logger
>
> Also, if you want to see what serveradmin is capable of monitoring,
> this command:
> sudo serveradmin command xserve:command = status | egrep
> "(location|current-value|type)"
> is a little easier to read than slogging through all the other text.
>
> Please let me know if you have errors running the script on an Xserve
> G5. Note that the script currently won't run on an single cpu Xserve
> G5, but you could make it work just by commenting out the CPU 2
> sections.
>
> - Todd
>
>
> On Feb 22, 2005, at 9:36 AM, Todd Dailey wrote:
>
> > Andrew Hankinson wrote:
> >>
> >> Is there any information about the normal operating range temperatures
> >> of the XServe? I would like to make sure that our XServe is cool
> >> enough, but can't seem to find anything. Currently, our XServe is
> >> running at the following:
> >>
> >>
> >> Between the Processors : 32.00 C
> >> CPU 2 Ambient : 30.00 C
> >> CPU 2 Internal : 40.36 C
> >> Behind the DIMMs : 53.00 C
> >> PCI Slots : 48.00 C
> >> CPU 1 Internal : 47.93 C
> >> System Controller Ambient : 40.00 C
> >> System Controller Internal : 51.38 C
> >> CPU 1 Inlet : 24.00 C
> >> CPU 1 Ambient : 35.75 C
> >> CPU 2 Inlet : 22.50 C
> >> _______________________________________________
> >
> > If you run:
> > sudo serveradmin command xserve:command = status | less
> >
> > You can find the thresholds for each parameter, the units are 1/65536
> > of a C degree.
> >
> > So, for example, for CPU 1 it shows maxWarningThreshold as 5636096,
> > which is 86C, and maxFailureThreshold as 5898240, which is 90C.
> >
> > I wrote a python script to log these temps here:
> >
> > Unfortunately, the sensor numbers appear to change from server to
> > server, so I need to update it to work off the sensor name, not the
> > sensor number. The current script doesn't work quite right on all
> > systems, but you can look at it and get an idea of what I'm doing.
> >
> > - Todd
> >
> >
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macos-x-server mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/macos-x-server/email@hidden
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
