Open gladky opened 7 years ago
danger_shutdown
service installed on every machine.3a. looking at /usr/local/bin/temperature_lib.sh
on a dvbu machine, looking at the shell function GetTemperature()
one can see that the temperature sensor names (e.g. FCB Ambient1
or BB Inlet Temp
) depend on the type of server, so a generic expression like 'server temperature' probably describes it best.
3b. 'everything' in this case is defined as 'everything with the danger_shutdown
installed and properly configured'. After some more reading, I noticed however that there is no ssh involved so the message of the DAQDottoressa refers only to the host it is running on (i.e. it only parses its own log), warning the shifter that the DAQDottoressa may be stopped soon if the temperature watching service triggers a shutdown.
Looking at the code of the original DAQDottoressa, it was only checking the temperature of the machine where the DAQDottoressa was running, not of others.
Our virtual machines (such as the one where the daq expert is running on) do not have the file /var/log/danger_shutdown.sh.log
(the deamon shutting down the machine in case of two high temperature should run on the host system, not on the virtual machine), so currently there is obvious way how to implement this check on the DAQExpert.
I would vote to close this issue.
From the DAQDottoressa temperature monitor:
tail -3 /var/log/danger_shutdown.sh.log | grep -i Temperature
Quote 1:
Quote 2: