Easy fix fan/temp OS6 issues on x86 legacy #no support

ATCIS wrote:
find / -name syslog --> Yields nothing :( It would appear that syslog is M.I.A.

Check the process list:

ps -A | grep syslogd

That should return something like "1234 ? 00:00:01 syslogd". If it returns nothing at all, syslogd isn't even running.

Tracking down WHY it isn't running might be an interesting exercise. Could be something as simple as an old lockfile preventing it from starting (to check, look in /var/run for a file called "syslogd.pid"; if you see it there even though syslogd isn't running, delete it and restart).

fastfwd wrote:

ATCIS wrote: find / -name syslog --> Yields nothing :( It would appear that syslog is M.I.A. Check the process list: ps -A | grep syslogd That should return something like "1234 ? 00:00:01 syslogd". If it returns nothing at all, syslogd isn't even running. Tracking down WHY it isn't running might be an interesting exercise. Could be something as simple as an old lockfile preventing it from starting (to check, look in /var/run for a file called "syslogd.pid"; if you see it there even though syslogd isn't running, delete it and restart).

I edited the crap out of my original post above. . . Check it out :)
I have to go to bed now. I have to get back up in less than 5 hours. A special THANK YOU" to fastfwd for all your guidance.
I'll catch up with you guys later. . .

ATCIS wrote:
When I did the - /sys/devices/platform/it87.2576# cat temp1_input I got 57 When I - sys/devices/platform/it87.2576# cat temp2_input I got 31 and when I - /sys/devices/platform/it87.2576# cat temp3_input I got -128 (so I assumed that was erroneous) I wound up using the temp1_input as the ambient room temperature is a about 85 degrees F and 87.8 degrees F for temp2_input seemed too low to me.

The -128 is certainly erroneous. The temp3 input is clearly not being used.

The 57-degree SYS temperature is probably right; is that how hot your Ultra4 ran when you were using RAIDiator 4.2.23?

ATCIS wrote:

My resulting script looks like this: #!/bin/sh ####################################################### Coretemp="/sys/devices/platform/coretemp.0/temp2_input" Systemp="/sys/devices/platform/it87.2576/temp1_input" Ct=`cat $Coretemp` C=`expr $Ct / 1000` St=`cat $Systemp` S=`expr $St / 1` rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:$C:$S So do I need to do anything to make it GO? My temperature graph is still quite empty. . .

You stil need to modify your crontab, as described by Iridabike, in order to make the script automatically execute every minute.

ATCIS wrote:
Any chance that the file in there named "systemd" is important?

Not to the syslog mystery, no. Unfortunately, I don't run OS6 so I can't suggest anything further. With luck, someone who does run OS6 will be able to tell you how to get syslogd running again.

fastfwd wrote:
The -128 is certainly erroneous. The temp3 input is clearly not being used. The 57-degree SYS temperature is probably right; is that how hot your Ultra4 ran when you were using RAIDiator 4.2.23?

Probably not, but I honestly don't remember without a shadow of a doubt. I may switch it to temp2_input even though 31 degrees C seems too low. On the GUI I have three thermometers: AUX = 40 C / 104 F, CPU = 43 C / 109 F, and System = 40 C / 104 F. Which leads me to believe that those graphical indications are also erroneous or I'm CAT'ing the wrong files. Wouldn't you agree that for a device residing in an 80 to 85 degree ambient environment that a System temperature of 134.6 F seems kind of high when the CPU temperature is only 109.4 F?

I've changed the script accordingly. It now looks like this:

#!/bin/sh
#######################################################
Coretemp="/sys/devices/platform/coretemp.0/temp2_input"
Systemp="/sys/devices/platform/it87.2576/temp2_input"
Ct=`cat $Coretemp`
C=`expr $Ct / 1000`
St=`cat $Systemp`
S=`expr $St / 1`
rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:$C:$S

Additionally, my /etc/crontab file now looks like this (perhaps my script file is okay, I just dorked up the crontab):

# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user	command
17 *	* * *	root    cd / && run-parts --report /etc/cron.hourly
25 6	* * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6	* * 7	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6	1 * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )

# Delete the lines below if things get wacky.  They are supposed to enable 
# temperature graphing in the Frontview GUI.  Good luck!
*/1 *	* * *	root	/usr/local/etc/scripts/UpdateTempGraph.cron

You thoughts?
Thanks again!

Are you running 6.0.8? Netgear changed some stuff around and you need to patch readynasd to make it work correctly.

To start with is this file present on your machine:

/run/readynasd/stats/temperature_int_deg.rrd ?

If it is then try entering this command about 10-15 times over a couple of minutes and see what happens in the graph:

rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:25:50

Iridabike wrote:
Are you running 6.0.8? Netgear changed some stuff around and you need to patch readynasd to make it work correctly.

YES. EDIT: When you say "patch readynasd" could you be more specific? Details please, THANK YOU!

Iridabike wrote:
To start with is this file present on your machine: /run/readynasd/stats/temperature_int_deg.rrd ?

YES

Iridabike wrote:
If it is then try entering this command about 10-15 times over a couple of minutes and see what happens in the graph: rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:25:50

Trying that now. I will report back in 30 minutes. . .
EDIT: YES! I'm seeing stuff on the graph now. So what must I do to automate this process? I assume the crontab entry is supposed to do that. . .

You should see some data in the graph although I suspect it will not be a two straight lines at 25 and 50 as readynasd is also writing to the file every minute with some false temperatures.

If you are now seeing some data in the graph then the problem may be your script. Try running your script from the command line a few times and check that it logs something.

When you have it logging something by itself you will need to fix the problem readynasd corrupting your data. I have patched the readynasd elf to update a copy of the file rather than corrupt the data. To do this you need a hex editor to mod readynasd. Look for this text in the file:

/usr/bin/rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:%lld:%lld
.
and change it to something like:

/usr/bin/rrdtool update /run/readynasd/stats/temperature_int_deg.bak N:%lld:%lld

Note there are similar lines in the file but only one matches exactly

At startup I use another script to copy the .rrd to .bak just to give readynasd something to write to. It needs to be done at every startup as the files in this folder are deleted.

You may want to backup your readynasd first just incase something goes wrong. Also please be aware this could mess things up if you get things wrong so please only do this if you are confident and are happy to take the risk.

Iridabike wrote:
You should see some data in the graph although I suspect it will not be a two straight lines at 25 and 50 as readynasd is also writing to the file every minute with some false temperatures.

You are correct sir.

Iridabike wrote:
If you are now seeing some data in the graph then the problem may be your script

I have no doubt. . . :cry:

Iridabike wrote:
To do this you need a hex editor to mod readynasd. Look for this text in the file:

Yeah, see my post above RE: "Linux Idiot" I think I should abandon this effort right here. I've done the hex editing thing in the past, sometimes it goes okay, sometimes not so much.

Iridabike wrote:
Also please be aware this could mess things up if you get things wrong so please only do this if you are confident and are happy to take the risk.

Yeah, not so much. . . Even though I would love to get the temperature graph working, it's not important enough to risk screwing things up entirely. I appreciate your and fastfwd's help on this, but I have to be realistic about my limitations in this area. I'm primarily a WinDoze guy, I just tinker with Linux stuff from time to time for fun and education.
Perhaps one day down the road, some ambitious person will compile a preconfigured patch or binary package that fixes some of these non-functional aspects of running OS6 on legacy ReadyNAS devices. . . :naskiller:

Thanks again for trying to lend a hand!

P.S: When you said "Try running your script from the command line a few times and check that it logs something." For educational purposes could you give me an example of what the proper syntax for such a command would be?

To run your script:

1) cd to the directory where your script lives
2) enter the name of your script preceded by ./

Eg.

./myscript

This can be handy when debugging a script as errors are returned on screen.

Iridabike wrote:
To run your script: 1) cd to the directory where your script lives 2) enter the name of your script preceded by ./ Eg. ./myscript This can be handy when debugging a script as errors are returned on screen.

Excellent! Thank you so much for holding the hand of this Linux neophyte. . . :oops:

One more question: What do you know about this?

fastfwd wrote:

ATCIS wrote: find / -name syslog --> Yields nothing :( It would appear that syslog is M.I.A. Check the process list: ps -A | grep syslogd That should return something like "1234 ? 00:00:01 syslogd". If it returns nothing at all, syslogd isn't even running. Tracking down WHY it isn't running might be an interesting exercise. Could be something as simple as an old lockfile preventing it from starting (to check, look in /var/run for a file called "syslogd.pid"; if you see it there even though syslogd isn't running, delete it and restart).

Any chance you could shed some light on how to watch the ReadyNAS OS6 syslog?