Sponsored Content
Operating Systems Solaris Server shutdown based on temperature Post 302752973 by DustinT on Monday 7th of January 2013 10:18:50 PM
Old 01-07-2013
If this server is in a temperature controlled room, all the cooling fans and psu fans are working and the vents aren't clogged with dust there should be no reason why you'd have temperature problems.

If one of the above isn't true, I'd address that before I started to look for a software solution to something that's a hardware problem.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Server shutdown Troubleshooting

SCO Unixware 7.1.1 Hi friends, At 11:30pm last night mymain Unix Server hung or rebooted (Unaware which one), and was bot available for 10 minutes. Is there a log file somewhere which will tell me what happened ? I have looked ad /var/adm/syslog, but cannot make head nor tail of it. ... (1 Reply)
Discussion started by: sureshy
1 Replies

2. UNIX for Advanced & Expert Users

shutdown a unix server

Hi, how to shutdown a unix machine ? We are on SunOS server15.8 Generic_108528-24 sun4u sparc SUNW,Ultra-Enterprise Many thanks. (2 Replies)
Discussion started by: big123456
2 Replies

3. UNIX for Advanced & Expert Users

Mysterious Server Shutdown

Virtually no UNIX admin experience. Any admin duties are shared by several folks with no special training. Today we had our Sun v880 server, running Solaris 5.8, shutdown for no apparent reason. When we checked on server we found it completely powered down, yet still connected to a fully... (6 Replies)
Discussion started by: buechler66
6 Replies

4. AIX

server is getting shutdown

Hi Guys, Please help in this...when we start HACMP services ..server is getting shutdon. Error mesg from cluster.log. Apr 14 08:43:27 bascop17 snmpd: NOTICE: SMUX trap: (0 0) (127.0.0.1+46302+1) Apr 14 08:43:33 bascop17 topsvcs: (Recorded using libct_ffdc.a cv 2):::Error ID:... (1 Reply)
Discussion started by: b_manu78
1 Replies

5. UNIX for Advanced & Expert Users

RHEL 4 U5 - Server immediate shutdown

Dear all, My server has shutdown frequently. It is AMD64, OS is RHEL 4 U5. I've seen the system log, before the shutdown occured: Jul 29 04:28:56 localhost kernel: EDAC k8 MC0: general bus error: participating processor(local node response), time-out(no timeout) memory transaction... (2 Replies)
Discussion started by: mr_bold
2 Replies

6. Shell Programming and Scripting

How to shutdown client machine from the server

I have a unix server through which some ten client machines are connected. I want to shutdown/restart all the machine from the server through the shell script during the particular time of the day. I welcome your suggestions. Thanks in advance. With regards Victor (1 Reply)
Discussion started by: mvictorvijayan
1 Replies

7. Solaris

Server Shutdown Problem

I have a sparc T1 server (I know its old) running Solaris 8, which we use for testing. It has been very slow in response- prompt takes couple of minutes to come up, so I decided to reboot the server but I can reboot it, it is giving following errors when I try to shutdown it down. root@deva:/#... (3 Replies)
Discussion started by: Tirmazi
3 Replies

8. Solaris

Startup and shutdown a server

Are rc scripts executed serially or all at the same time. Is there a way to see this happen? A log file or the syslogd? This is Solaris 10. (2 Replies)
Discussion started by: djehresmann
2 Replies

9. UNIX for Advanced & Expert Users

Shutdown the Linux server if no one is using the server

Hi All, I want to shutdown the server if no one is actualy using it. Its a linux server. I thought of sending a msg on users terminal for those who all are logged in and expecting a input from them. If they will reply system should not get shutdown else it should not. Can any one... (2 Replies)
Discussion started by: Sadhana
2 Replies

10. AIX

Server Shutdown

Hi, is it possible to find out ip address of user who has shutdown or rebooted the server , I have used the command errpt -a , in that it is showing server rebooted but it is not showing ip address who has shutdown the serve, even I have used command last reboot. Please suggest. Regards, ... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
FANCONTROL(8)						      System Manager's Manual						     FANCONTROL(8)

NAME
fancontrol - automated software based fan speed regulation SYNOPSIS
fancontrol [configfile] DESCRIPTION
fancontrol is a shell script for use with lm_sensors. It reads its configuration from a file, then calculates fan speeds from temperatures and sets the corresponding PWM outputs to the computed values. WARNING
Please be careful when using the fan control features of your mainboard, in addition to the risk of burning your CPU, at higher tempera- tures there will be a higher wearout of your other hardware components, too. So if you plan to use these components in 50 years, maybe you shouldn't use fancontrol at all. Also please keep in mind most fans aren't designed to be powered by a PWMed voltage. In practice it doesn't seem to be a major issue, the fans will get slightly warmer, just be sure to have a temperature alarm and/or shut- down call, in case some fan fails, because you probably won't hear it anymore ;) CONFIGURATION
For easy configuration, there's a script named pwmconfig(8) which lets you interactively write your configuration file for fancontrol. Alternatively you can write this file yourself using the information from this manpage. Since most of you are going to use pwmconfig(8) script, the config file syntax will be discussed last. First I'm going to describe the var- ious variables available for changing fancontrol's behaviour: INTERVAL This variable defines at which interval in seconds the main loop of fancontrol will be executed DEVPATH Maps hwmon class devices to physical devices. This lets fancontrol check that the configuration file is still up-to-date. DEVNAME Records hwmon class device names. This lets fancontrol check that the configuration file is still up-to-date. FCTEMPS Maps PWM outputs to temperature sensors so fancontrol knows which temperature sensors should be used for calculation of new values for the corresponding PWM outputs. FCFANS Records the association between a PWM output and a fan input. Then fancontrol can check the fan speed and restart it if it stops unexpectedly. MINTEMP The temperature below which the fan gets switched to minimum speed. MAXTEMP The temperature over which the fan gets switched to maximum speed. MINSTART Sets the minimum speed at which the fan begins spinning. You should use a safe value to be sure it works, even when the fan gets old. MINSTOP The minimum speed at which the fan still spins. Use a safe value here, too. MINPWM The PWM value to use when the temperature is below MINTEMP. Typically, this will be either 0 if it is OK for the fan to plain stop, or the same value as MINSTOP if you don't want the fan to ever stop. If this value isn't defined, it defaults to 0 (stopped fan). MAXPWM The PWM value to use when the temperature is over MAXTEMP. If this value isn't defined, it defaults to 255 (full speed). The configuration file format is a bit strange: VARIABLE=chip/pwmdev=value chip/pwmdev2=value2 VARIABLE2=... Each variable has its own line. The variable name is followed by an equal sign and the device=value pairs. These consist of the path to the pwm output for which the value is valid, equal sign followed by the value and are separated by a blank. Path can be absolute or relative (from /sys/bus/i2c/devices or /sys/class/hwmon depending on the kernel version). Example: MINTEMP=hwmon0/device/pwm1=40 hwmon0/device/pwm2=54 You have to play with the temperature values a bit to get happy. For initial setup I recommend using the pwmconfig script. Small changes can be made by editing the config file directly following the rules above. Upon starting, fancontrol will make sure that all referenced devices do exist and match what they were at configuration time, and that all referenced sysfs files do exist. If not, it will quit immediately, upon the assumption that the configuration file may be out-of-sync with the loaded kernel drivers. THE ALGORITHM
fancontrol first reads its configuration, writes it to arrays and loops its main function. This function gets the temperatures and fanspeeds from kernel driver files and calculates new speeds depending on temperature changes, but only if the temp is between MINTEMP and MAXTEMP. After that, the new values are written to the PWM outputs. Currently the speed increases quadratically with rising temperature. This way you won't hear your fans most of the time at best. SEE ALSO
pwmconfig(8), sensors(1). AUTHOR
Marius Reiner <marius.reiner@hdev.de> lm-sensors 3 September 2009 FANCONTROL(8)
All times are GMT -4. The time now is 03:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy