May 27, 201313 yr Switchblade, The cpu temperature is an issue because you dont have a general cpu temp sensor showing (the one youre trying to read is on the motherboard and those tend to not be very accurate, I know in mine it isnt right, but I have a general CPU temp as part of the first part of sensors so I used that). I dont know if you could just create a new temperature by doing "compute temp5" and then doing an average of temp1-4 for the coretemp-isa-0000 (unlikely this would work), instead you may just set core0 (which is temp1 on that chip) as your CPU temp. It won't be perfect since its just one core youre actually measuring, but normally i think it runs core0 first before turning on others(I think). If theyre all running, they all go up in temperature. So under the coretemp you can just set: label temp1 "CPU Temp" and erase it from the motherboard side For the voltages, did the voltage in bios stay the same all the time? never flipped a tiny bit? if so youre going to need some other ppl to contribute their voltages for the same board so we can find the right conversion factor. I didn't notice any voltages flipping, but I can take another look. It sounds like you are expecting one of the voltage readings to flip back and forth, but which one are you expecting to do this? As for your advice, I'm not clear on what you are suggesting that I change. Here is what I have in my sensors.conf file, # lm-sensors config for Supermicro C2SEA board chip "w83627ehf-isa-0290" label temp1 "CPU Temp" label temp2 "MB Temp" ignore temp3 # chip "coretemp-isa-0000" Thanks for your help. 1) Voltage reading: I would need any and all that switch and what they switch to (or if you know someone else that has the same motherboard what are their numbers). The purpose is that it isn't linear, the voltages shown jump in steps. By identifying the difference from one step to another in the bios, I can figure out the conversion factor (ie if you look in sensors, theyre all under about 3.5v, so you need a conversion to upconvert to the true 12v or 5v reading). This is only important if you want to fix your sensors output to show the correct voltage, if you don't care then no problem and its not even displayed in simplefeatures. 2) For the code, as much as I can tell, the temp1 that you currently have listed as CPU temp may actually be the MB temp. This because in the output it shows 44C and on the bios image it shows 47C. Then again, this may be wrong or some other sensor close to the CPU yet not accurate. You may test by stressing the system again, commenting out the ignore temp 2 and 3 from the sensors config (remember to restart) and watching how the temperatures behave. The MB temperature should be more stable than a CPU temperature. And you will know what the actual CPU temp is because you know the core temperatures, so a CPU sensor on the motherboard should rise with them and stay a few C under them. In any case, I am switching the CPU Temp label over to the actual core sensor. Unfortunately all its going to do is re-label your core0 as CPU temp. This won't be perfectly accurate, since one of the other cores may be higher, but its an actual temperature on the actual CPU, and if other cores are higher, this one will rise as well so you will always be within ~3-4C I would think. In any case, you would normally be looking for a average temperature from all 4 cores that is only an average after all (exceeded by any one or more cores). chip "w83627ehf-isa-0290" label temp1 "MB Temp" ignore temp2 ignore temp3 chip "coretemp-isa-0000" label temp1 "CPU Temp"
May 27, 201313 yr Thanks! I'll go back and look at the voltages. I will also make the changes to the sensors.conf file as you listed above. My only question is that you have label temp1 as MB and then below the chip line, it's listed as CPU. Can you please confirm that the code you listed is what I should change it to? In my existing file, the last chip line is commented out, but in yours it is not.
May 28, 201313 yr Thanks! I'll go back and look at the voltages. I will also make the changes to the sensors.conf file as you listed above. My only question is that you have label temp1 as MB and then below the chip line, it's listed as CPU. Can you please confirm that the code you listed is what I should change it to? In my existing file, the last chip line is commented out, but in yours it is not. That label command is just to change the name. By changing it to CPU Temp or MB Temp, simplefeatures can recognize it and display it. I moved the sensor that is displaying as CPU Temp down to the sensors on the actual core's on the chip (specifically core 0), it needs to be un-commented so that the system recognizes that you're changing the name on the first temperature on the other chip. If you need anything else please let me know, do read up what I said on MB temperature (pevious post), I have no guarantee that its the correct sensor for it so youll have to try and test it out (may be better to comment out those ignore lines to see all the outputs to figure out the correct one for the motherboard, if there is one that is right).
May 30, 201313 yr Not sure if this temp sensor thread is the right place to ask, but was the issue of Simple Features going out to lunch because of too frequent SMART polling (at least I think that was it) ever resolved?
May 30, 201313 yr Is there any new version of SF planned, just wondering what's in the pipeline and what future holds
May 30, 201313 yr Is there any new version of SF planned, just wondering what's in the pipeline and what future holds I hope that a solution to the sloooow parity checks when the web interface is open is included.
May 30, 201313 yr In regards to the Web Server Plugin... Ive installed the plugin, and if I just go stratight to the settings and click ENABLE, and then navigate to IPOFTOWER:81 i get a message telling me to move the root directory to a permant location. So i go back to the settings, and change the Web Root Directory to: /mnt/cache/www and click APPLY, i notice in the upper right, it says DISABLED...I rebooted the tower, same thing. I have a SHARE called WWW on my CACHE drive Ive also tried: /mnt/cache/appdata/web as appdata is where SAB/CP/SB/AirVideo/Plex are all installed and work perfectly, but same thing...cant get the plugin to go to ENABLED. Any thoughts? Im sure whatever it is im missing is simple. Many Thanks!
May 30, 201313 yr Author Is there any new version of SF planned, just wondering what's in the pipeline and what future holds I hope that a solution to the sloooow parity checks when the web interface is open is included. I'm working through this one with Tom, as it technically shouldn't be possible. However, it's quite obvious he has a lot of work on at the moment, and it's likely to be tested after a new unRAID release.
May 30, 201313 yr Hello guyz, I installed Simple Features plugin on my unRAID 5.0-rc12a, everything seems fine, except for the web server.. The icon is showed in Settings but when i enable it, it still says Status: Stopped. Also when i press the icon and go to the web server settings it gives me the following message: "Warning: parse_ini_file(/var/local/emhttp/simpleFeatures.web.server.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/simpleFeatures.webServer/WEBsettings.php on line 1" What could be wrong? Thank you
May 30, 201313 yr I have 2 servers. On my tower 2 simplefeatures just stopped repsonding alltogether. Usually after 10-15 mins. I have tried installing multiple times and I cannot get it working on my tower2. I can still telnet or ssh in and my sabnzb and transmission are all available by the web but simplefeatures just stops working. Anyway to troubleshoot?? On tower it is working perfectly.
May 30, 201313 yr Author I have 2 servers. On my tower 2 simplefeatures just stopped repsonding alltogether. Usually after 10-15 mins. I have tried installing multiple times and I cannot get it working on my tower2. I can still telnet or ssh in and my sabnzb and transmission are all available by the web but simplefeatures just stops working. Anyway to troubleshoot?? On tower it is working perfectly. What differences are there, in terms of software and hardware, between the two servers? Cheers
May 30, 201313 yr Same software exactly except one is intel based (the working one) and the non working one is amd.
May 31, 201313 yr to fix zone error Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Thu May 30 04:12:48 2013 MDT (yesterday), finding 5 errors un zip and replace in plogin simpleFeatures.web.server-1.0.11-noarch-1.plg.zip
May 31, 201313 yr Author Same software exactly except one is intel based (the working one) and the non working one is amd. Bizarre - I'm running an AMD server as my main unRAID server - not a problem. Do you get this issue without simpleFeatures installed on that server?
May 31, 201313 yr No it works fine without simplefeatures. Since simplefeatures is still crashed I installed unmenu and that is working fine. Not sure the issue. Same software exactly except one is intel based (the working one) and the non working one is amd. Bizarre - I'm running an AMD server as my main unRAID server - not a problem. Do you get this issue without simpleFeatures installed on that server?
June 1, 201313 yr Author No it works fine without simplefeatures. Since simplefeatures is still crashed I installed unmenu and that is working fine. Not sure the issue. Same software exactly except one is intel based (the working one) and the non working one is amd. Bizarre - I'm running an AMD server as my main unRAID server - not a problem. Do you get this issue without simpleFeatures installed on that server? Can you send through a syslog when it crashes? Thanks
June 4, 201313 yr No it works fine without simplefeatures. Since simplefeatures is still crashed I installed unmenu and that is working fine. Not sure the issue. Does this work? As in you can still access some sort of webui? the problem with losing the webUI is that you wont know if something fails, etc. Can SimpleFeatures and UnMenu work side by side without a fight?
June 4, 201313 yr Can SimpleFeatures and UnMenu work side by side without a fight? yes. Joe to the rescue! thanks. heading over there now.... !
June 4, 201313 yr I'm running both now because SF just stops responding sometimes and I've haven't wanted to spend the time to troubleshoot and send syslogs, post and deal with it. Unmenu has always worked great for me. It's nice when SF webgui dies and the only way to fix it is to reboot (this is a known issue for may SF users), I can use Unmenu to stop my array, stop samba, and then powerdown, all with a nice gui. I think at the end of the day, it's nice having both SF and Unmenu and all the features they both bring to the table at your fingertips. Both solutions fill different gaps for native Unraid (with some overlap).
June 4, 201313 yr I'm running both now because SF just stops responding sometimes and I've haven't wanted to spend the time to troubleshoot and send syslogs, post and deal with it. Unmenu has always worked great for me. It's nice when SF webgui dies and the only way to fix it is to reboot (this is a known issue for may SF users), I can use Unmenu to stop my array, stop samba, and then powerdown, all with a nice gui. I think at the end of the day, it's nice having both SF and Unmenu and all the features they both bring to the table at your fingertips. Both solutions fill different gaps for native Unraid (with some overlap). Agree... I love that unMenu can be restarted via the console. +1000 points on that. And that the stock UI is still accessible when needed.
Archived
This topic is now archived and is closed to further replies.