Capt.Insano

Anyone?!

Thanks for this, great tool and I am looking forward to Fan Control! A quick question about my IPMI setup: Motherboard: Intel S5500WB CPUs: Intel Xeon CPU L5630 (x2) output of "/usr/bin/ipmitool -vc sdr": root@Tower:~# /usr/bin/ipmitool -vc sdr Running Get PICMG Properties my_addr 0x20, transit 0, target 0 Error Response 0xc1 from Get PICMG Properities No PICMG Extenstion discovered BB +1.1V IOH,1.084,Volts,ok,7.1,System Board,Voltage,1.102,1.067,1.133,,1.177,1.146,,1.027,1.054,0.068,1.190 BB +1.1V P1 Vccp,0.921,Volts,ok,7.1,System Board,Voltage,1.098,0.714,1.482,,1.543,1.501,,0.683,0.708,0.006,1.562 BB +1.5V P1 DDR3,,,ns,7.1,System Board,Voltage,1.492,1.420,1.570,,1.635,1.589,,1.362,1.401,-0.003,1.654 BB +1.8V AUX,1.781,Volts,ok,7.1,System Board,Voltage,1.797,1.743,1.851,,1.927,1.874,,1.673,1.720,-0.013,1.951 BB +3.3V,3.296,Volts,ok,7.1,System Board,Voltage,3.296,3.125,3.454,,3.625,3.525,,2.982,3.067,0.022,3.668 BB +3.3V STBY,3.239,Volts,ok,7.1,System Board,Voltage,3.296,3.125,3.454,,3.625,3.525,,2.982,3.067,0.022,3.668 BB +3.3V Vbat,2.997,Volts,ok,7.1,System Board,Voltage,2.997,2.542,3.139,,3.283,3.192,,2.178,2.502,0.007,3.322 BB +5.0V,4.994,Volts,ok,7.1,System Board,Voltage,4.994,4.744,5.243,,5.538,5.380,,4.471,4.630,-0.182,5.607 BB +5.0V STBY,4.972,Volts,ok,7.1,System Board,Voltage,4.908,4.672,5.143,,5.421,5.272,,4.416,4.565,0.029,5.486 BB +12.0V,12.247,Volts,ok,7.1,System Board,Voltage,11.987,11.363,12.559,,13.287,12.923,,10.739,11.103,0.183,13.443 BB +1.35v P1 MEM,1.378,Volts,ok,7.1,System Board,Voltage,1.354,1.289,1.425,,1.484,1.443,,1.236,1.271,-0.003,1.502 Baseboard Temp,25,degrees C,ok,66.1,Baseboard/Main System Board,Temperature,38.000,20.000,55.000,,66.000,61.000,,5.000,10.000,-128.000,127.000 IOH Therm Margin,-40,degrees C,ok,7.1,System Board,Temperature,-20.000,-40.000,0.000,,10.000,5.000,,,,-128.000,127.000 Mem P1 Thrm Mrgn,-47,degrees C,ok,7.1,System Board,Temperature,-20.000,-40.000,0.000,,10.000,5.000,,,,-128.000,127.000 Processor 1 Fan,3136,RPM,ok,29.1,Fan Device,Fan,8640.000,960.000,16320.000,,,,,640.000,768.000,0.000,16320.000 Processor 1A Fan,640,RPM,Lower Critical,29.2,Fan Device,Fan,8640.000,960.000,16320.000,,,,,640.000,768.000,0.000,16320.000 Processor 2 Fan,3136,RPM,ok,29.5,Fan Device,Fan,8640.000,960.000,16320.000,,,,,640.000,768.000,0.000,16320.000 P1 Therm Margin,-47,degrees C,ok,65.1,Processor,Temperature,-15.000,-70.000,0.000,,,,,,,-128.000,127.000 P1 Therm Ctrl %,0,percent,ok,3.1,Processor,Temperature,0.000,0.000,7.800,,19.500,11.700,,,,0.000,39.000 Pwr Unit Status,01h,ok,21.1, IPMI Watchdog,03h,ok,7.1, Physical Scrty,04h,ok,23.1, FP NMI Diag Int,05h,ok,7.1, SMI Timeout,06h,ok,7.1, System Event Log,07h,ok,7.1, System Event,08h,ok,7.1, P1 Status,60h,ok,3.1,Presence detected P1 VRD Hot,66h,ok,3.1, CATERR,68h,ok,3.1, CPU Missing,69h,ok,3.1, IOH Therm Trip,6Ah,ok,7.1, NM Capabilities,1Ah,ok,46.1, In the IMPI settings page I only get the following options for CPU temp (see attachment): Is there anything I should be doing to enable CPU temp? Thanks again!

Good work! Thank you very much for continuing this. I have added this container as a feature request to linuxserver.io here: http://feathub.com/linuxserver/linuxserver.github.io If people could please upvote it, it would be great to have this container streamlined and follow correct container guidelines. Regards, The Capt

That looks like a connection issue to a folding@home assignment server. Restart the container and check if the server is back up. Otherwise check that ports are open as per the folding@home docker template.

My ISP (Sky Ireland) provide a shite router (SkyHub 2.0) which does not easily provide DNS settings. My Solution: root@tower:# docker exec -it Observium /bin/bash root@300cb02a1ebf:#vi /etc/hosts add ip address and hostname to hostfile and BINGO, Observium resolves host!! hey Cap - thanks for sharing your solution. Quick question. I do have a router (ASUS RT N56-U) and I believe I have DNS configured (I believe) - do I still need to add ip address and hostname to hostfile. Based on that screenshot you will need to, the DNS setting pictured is not the same settings as previously mentioned in this thread.

Also, 2 questions for users of this plugin with observium? 1: Does location work for you? The map on my Observium homepage reports my server as being in Sao Miguel instead of Ireland!! 2: virbr0 appears as a "Port Down" for me, are others getting this error report? I believe it is the the network bridge created by KVM, but why is it appearing as down? My VMs have perfect network/internet access. Thanks!

My ISP (Sky Ireland) provide a shite router (SkyHub 2.0) which does not easily provide DNS settings. My Solution: root@tower:# docker exec -it Observium /bin/bash root@300cb02a1ebf:#vi /etc/hosts add ip address and hostname to hostfile and BINGO, Observium resolves host!!

Each chip has 4 cores. For some reason (documented around the web) coretemp lists the cores of each CPU as: core 0 core 1 core 9 core 10 I could choose 1 core from each CPU as a reference of CPU temp, but being able to show temp of each CPU would allow me monitor for cooling problems on each CPU (Separate Fans). That make sense? Edit: For clarity. The output of sensors: root@Tower:/etc/sensors.d# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +20.0°C (high = +61.0°C, crit = +71.0°C) Core 1: +19.0°C (high = +61.0°C, crit = +71.0°C) Core 9: +19.0°C (high = +61.0°C, crit = +71.0°C) Core 10: +23.0°C (high = +61.0°C, crit = +71.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 0: +24.0°C (high = +61.0°C, crit = +71.0°C) Core 1: +20.0°C (high = +61.0°C, crit = +71.0°C) Core 9: +23.0°C (high = +61.0°C, crit = +71.0°C) Core 10: +20.0°C (high = +61.0°C, crit = +71.0°C) jc42-i2c-0-18 Adapter: SMBus I801 adapter at 3000 temp1: +25.2°C (low = +0.0°C) (high = +0.0°C, hyst = +0.0°C) (crit = +75.0°C, hyst = +75.0°C) jc42-i2c-0-1c Adapter: SMBus I801 adapter at 3000 temp1: +26.0°C (low = +0.0°C) (high = +0.0°C, hyst = +0.0°C) (crit = +75.0°C, hyst = +75.0°C)

Would it be possible in SystemTemp to add the option to show the temp of multiple CPUs if multiple CPUs are installed? The attached image shows my options but I can only choose 1:

I recently got my hands on the S5500WB server motherboard as an upgrade to my unRAID set up: When I am setting up dynamix-systemtemp I run sensors-detect as per: http://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing using the newest version of sensors-detect from: http://lime-technology.com/forum/index.php?topic=36543.msg430371#msg430371 I get the following results: root@Tower:/boot# ./sensors-detect # sensors-detect revision 6279 (2015-03-30 08:43:30 +0200) # System: Intel Corporation S5500WB [....................] # Kernel: 4.1.15-unRAID x86_64 # Processor: Intel(R) Xeon(R) CPU L5630 @ 2.13GHz (6/44/2) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... Success! (driver `i5500_temp') VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Found `IPMI BMC KCS' at 0xca2... Success! (confidence 8, driver `to-be-written') Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10 Next adapter: SMBus I801 adapter at 3000 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x18 Handled by driver `jc42' (already loaded), chip type `jc42' Client found at address 0x1c Handled by driver `jc42' (already loaded), chip type `jc42' Client found at address 0x2e Probing for `Myson MTP008'... No Probing for `National Semiconductor LM78'... No Probing for `National Semiconductor LM79'... No Probing for `National Semiconductor LM80'... No Probing for `National Semiconductor LM96080'... No Probing for `TI / National Semiconductor ADC128D818'... No Probing for `National Semiconductor LM85'... No Probing for `National Semiconductor LM96000 or PC8374L'... No Probing for `Analog Devices ADM1027'... No Probing for `Analog Devices ADT7460 or ADT7463'... No Probing for `SMSC EMC6D100 or EMC6D101'... No Probing for `SMSC EMC6D102'... No Probing for `SMSC EMC6D103'... No Probing for `SMSC EMC6D103S or EMC2300'... No Probing for `SMSC EMC6W201'... No Probing for `Winbond WPCD377I'... No Probing for `Analog Devices ADT7467 or ADT7468'... No Probing for `Analog Devices ADT7470'... No Probing for `Analog Devices ADT7473'... No Probing for `Analog Devices ADT7475'... No Probing for `Analog Devices ADT7476'... No Probing for `Analog Devices ADT7490'... No Probing for `Andigilog aSC7611'... No Probing for `Andigilog aSC7621'... No Probing for `National Semiconductor LM87'... No Probing for `Analog Devices ADM1024'... No Probing for `National Semiconductor LM93'... No Probing for `National Semiconductor LM94 or LM96194'... No Probing for `Winbond W83781D'... No Probing for `Winbond W83782D'... No Probing for `Winbond W83791D'... No Probing for `Winbond W83792D'... No Probing for `Winbond W83793R/G'... No Probing for `Nuvoton W83795G/ADG'... No Probing for `Nuvoton NCT7802Y'... No Probing for `Nuvoton NCT7904D'... No Probing for `Winbond W83627HF'... No Probing for `Winbond W83627EHF'... No Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No Probing for `Asus AS99127F (rev.1)'... No Probing for `Asus AS99127F (rev.2)'... No Probing for `Asus ASB100 Bach'... No Probing for `Winbond W83L786NR/NG/R/G'... No Probing for `Winbond W83L785TS-S'... No Probing for `Analog Devices ADM9240'... No Probing for `Dallas Semiconductor DS1780'... No Probing for `National Semiconductor LM81'... No Probing for `Analog Devices ADM1026'... No Probing for `Analog Devices ADM1025'... No Probing for `Maxim MAX6639'... No Probing for `Texas Instruments AMC6821'... No Probing for `Analog Devices ADM1029'... No Probing for `Analog Devices ADM1030'... No Probing for `Analog Devices ADM1031'... No Probing for `Analog Devices ADM1022'... No Probing for `Texas Instruments THMC50'... No Probing for `Analog Devices ADM1028'... No Probing for `Texas Instruments THMC51'... No Probing for `ITE IT8712F'... No Probing for `SMSC DME1737'... No Probing for `SMSC SCH5027D-NW'... No Probing for `SMSC EMC2103'... No Probing for `Fintek F75373S/SG'... No Probing for `Fintek F75375S/SP'... No Probing for `Fintek F75387SG/RG'... No Probing for `Winbond W83791SD'... No Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca2 Chip `IPMI BMC KCS' (confidence: Driver `i5500_temp': * Chip `Intel 5500/5520/X58 thermal sensor' (confidence: 5) Driver `jc42': * Bus `SMBus I801 adapter at 3000' Busdriver `i2c_i801', I2C address 0x18 Chip `jc42' (confidence: 6) * Bus `SMBus I801 adapter at 3000' Busdriver `i2c_i801', I2C address 0x1c Chip `jc42' (confidence: 6) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp modprobe i5500_temp modprobe jc42 /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. When I test the above with modprobe i5500_temp i get "modprobe: FATAL: Module i5500_temp not found." Any chance the i5500_temp module could be added into the next unRAID release? Thanks, The Capt

Any chance of this feature being added to the DockerMan GUI similar the VM Manager? A list of CPU core checkboxes in the advanced mode would make managing CPU pinning much easier for those who want it.

Great find by aptalca! That command showed that linuxserver/headphones had a log file 2GB big!! Hopefully 6.2 might include some docker updates to include the log rotation. Thanks!

This fixed the excessive usage in mycase: http://lime-technology.com/forum/index.php?topic=45249.0 Great find by aptalca! linuxserver/headphones had a log file 2GB big!!

Is it possible that this is related to the architecture of the Host/Guest: I originally tried all the above in a Vortexbox 2.3 VM (32bit), and when I was having no luck I quickly set up a lubuntu 15.04 VM for testing prior to setting up this topic (lubuntu was also 32bit as I happened to have the iso on my desktop for another reason). I even updated lubuntu last night to 15.10 with the newest 4.0 kernel and still no joy. Today when looking for further answers I learned that Vortexbox 2.4 was released and it is 64bit for the first time, I installed it in a VM and instantly the above worked, it had no problem mounting and viewing through the 9p filesystem!! Since figuring this out I have been looking for ANY mention of a need for the Host and Guest to share the same architecture for 9p to work and I can find nothing!! @saarg: what your ubuntu VM 32 or 64 bit?!

lubuntu was the 2nd OS I tried!! I originally tried in my Vortexbox VM (Fedora based) and exactly the same thing was happening. I'll set up a straight ubuntu VM and test! Do you mind posting your VM .xml and commands used to mount it? Thanks for this help

I changed some of the settings to stop any ambiguity!! I now have the Virtio Tag as unraidtemp: <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Files/Temp/'/> <target dir='unraidtemp'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </filesystem> the target folder is the folder "temp" in the users home directory. I run: sudo mount -t 9p -o trans=virtio,version=9p2000.L,posixacl,cache=loose unraidtemp /home/user/temp As always, same results; /home/user/temp appears empty and if I create a file it instantly disappears but I can view it from unRAID!!

I have also tried the following in my VM setup: changing from /temp to temp as Virtio tag <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Files/Temp/'/> <target dir='temp'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </filesystem> and then sudo mount -t 9p -o trans=virtio temp temp -o version=9p2000.L,posixacl,cache=loose same results as before!!

if you mean: sudo mount -t 9p -o trans=virtio /temp temp -o version=9p2000.L,posixacl,cache=loose I have tried and same results; mounts without error but appears empty!!

No difference with fix!: user@Lubuntu-VM:~$ sudo umount temp/ [sudo] password for user: user@Lubuntu-VM:~$ sudo mount -t 9p -o trans=virtio /temp ./temp -o version=9p2000.L,posixacl,cache=loose user@Lubuntu-VM:~$ cd temp/ user@Lubuntu-VM:~/temp$ ls user@Lubuntu-VM:~/temp$ ls user@Lubuntu-VM:~/temp$ location still contains files: see attachment. Any other suggestions, I am willing to try anything!! (please no suggestions of just use SMB to mount instead of 9p, there is a reason I need 9p to work!)

I am mounting a location in unRAID as follows: In VM xml: <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Files/Temp/'/> <target dir='/temp'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> within this location (/mnt/user/Files/Temp) I have a files called test.txt and test2.txt for testing purposes: test.txt was made by unRaid root user via commandline (root:root) test2.txt was made over SMB share (nobidy:users) If I boot VM (lubuntu 15.04 in this case) I run the following commands: user@Lubuntu-VM:~$ sudo mount -t 9p -o trans=virtio /temp ./temp -oversion=9p2000.L,posixacl,cache=loose user@Lubuntu-VM:~$ ls -la total 116 drwxr-xr-x 22 user user 4096 Jan 9 16:24 . drwxr-xr-x 3 root root 4096 Oct 19 15:47 .. -rw------- 1 user user 2415 Jan 9 15:41 .bash_history -rw-r--r-- 1 user user 220 Oct 19 15:47 .bash_logout -rw-r--r-- 1 user user 3760 Oct 19 15:47 .bashrc drwxrwxr-x 9 user user 4096 Jan 9 16:30 .cache drwx------ 16 user user 4096 Oct 19 16:19 .config drwx------ 3 user user 4096 Oct 19 15:55 .dbus drwxr-xr-x 2 user user 4096 Oct 19 15:55 Desktop drwxr-xr-x 2 user user 4096 Oct 19 15:55 Documents drwxr-xr-x 2 user user 4096 Oct 19 15:55 Downloads drwx------ 5 user user 4096 Jan 9 15:03 .dropbox drwxr-xr-x 3 user user 4096 Oct 19 16:19 .dropbox-dist drwxrwxr-x 3 user user 4096 Oct 19 16:15 dropbox-restore drwx------ 3 user user 4096 Jan 9 16:20 .gconf drwxrwxr-x 3 user user 4096 Oct 19 15:55 .local drwx------ 4 user user 4096 Oct 19 16:14 .mozilla drwxrwxr-x 2 user user 4096 Jan 9 15:25 music drwxr-xr-x 2 user user 4096 Oct 19 15:55 Music drwxr-xr-x 2 user user 4096 Oct 19 15:55 Pictures -rw-r--r-- 1 user user 675 Oct 19 15:47 .profile drwxr-xr-x 2 user user 4096 Oct 19 15:55 Public -rw-r--r-- 1 user user 0 Oct 19 16:07 .sudo_as_admin_successful drwxrwxrwx 1 99 users 6 Jan 9 16:25 temp drwxr-xr-x 2 user user 4096 Oct 19 15:55 Templates drwx------ 4 user user 4096 Jan 9 16:23 .thumbnails drwxr-xr-x 2 user user 4096 Oct 19 15:55 Videos -rw------- 1 user user 55 Jan 9 16:20 .Xauthority -rw-r--r-- 1 user user 14 Oct 22 2012 .xscreensaver -rw------- 1 user user 242 Jan 9 16:20 .xsession-errors -rw------- 1 user user 242 Jan 9 15:38 .xsession-errors.old user@Lubuntu-VM:~$ cd temp/ user@Lubuntu-VM:~/temp$ ls user@Lubuntu-VM:~/temp$ mkdir test user@Lubuntu-VM:~/temp$ ls user@Lubuntu-VM:~/temp$ As you can see the mount command does not give any errors, the location appears mounted but after moving into the directory it's empty and when I create a directory within the mount it instantly disappears. If I then log into my unRAID host machine I CAN see the created directory from above: root@Tower:~# cd /mnt/user/Files/Temp root@Tower:/mnt/user/Files/Temp# ls -la total 4 drwxrwxrwx 1 nobody users 6 Jan 9 16:38 ./ drwxrwxrwx 1 nobody users 4096 Jan 9 16:21 ../ drwxrwxr-x 1 user 1000 6 Jan 9 16:31 test/ -rw-rw-rw- 1 root root 0 Jan 9 16:25 test.txt -rw-rw-rw- 1 nobody users 0 Jan 9 16:27 test2.txt I feel like this is some sort of permissions issue, are there some extra options I should be adding to my initial mount command so that I can view files and folders within the VM on the mount. Any help much appreciated!

Looks perfect! Many thanks!

One small request: Would it be possible to show what action is currently underway above the progress bar? I have a relatively underpowered CPU so I set a task in motion and then check back over the day and I am likely to forget exactly what is running. Attached is a crude representation of what I am suggesting!! Many Thanks, The Capt. EDIT: attachment updated to slightly improve representation of idea. (If single or multiple discs active, show what tasks are running)

Any chance the legend could be put in a floating frame or something similar so that if I am scrolling through the log I don't need to go back up to the top of the page to check the colour legend? Also is there a colour for docker errors? I know Docker was not around in the unMENU days!! Thanks

Thanks!

I updated the plugin today and now I am getting the following error at the top of the speedtest page in the WebUI: Warning: parse_ini_file(/boot/config/plugins/speedtest/speedtest.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/speedtest/include/parse_cfg.php on line 4 I have cleared browser cache but the error remains, any ideas? Thanks!