Jump to content
quad

Dynamix Auto Fan Control - Suddenly stopped working

10 posts in this topic Last Reply

Recommended Posts

I was been using the Auto Fan Control plugin for the latest months and it was working like charm.

Suddenly and after upgrading to v6.3.3 it stopped working. It doesn't detect sensors any more.

Few months ago it was installed along with Nerd Tools pack perl version and detected relevant sensors with success.

I also upgraded to the latest perl version but again nothing. (Mobo: ASRock - 970 Pro3 R2.0)

Any ideas?

Thanks in advance.

Share this post


Link to post

I have a situation that might be related related to Dynamix plugins that just stop working.  Upgrade to 6.3.2 or 6.3.3 has the CPU utilization percentages where they stop working shortly after boot.  Look through your logs.  I'm finding maybe related nastiness.  You might try to observe if your seeing anything peculiar or similar.

 


Apr  7 18:33:01 unraid crond[1653]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)
Apr  7 18:38:01 unraid crond[1653]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Apr  7 18:38:26 unraid kernel: br0: port 2(vnet0) entered disabled state
Apr  7 18:38:26 unraid kernel: device vnet0 left promiscuous mode
Apr  7 18:38:26 unraid kernel: br0: port 2(vnet0) entered disabled state
Apr  7 18:38:26 unraid kernel: br0: port 3(vnet1) entered disabled state
Apr  7 18:38:26 unraid kernel: device vnet1 left promiscuous mode
Apr  7 18:38:26 unraid kernel: br0: port 3(vnet1) entered disabled state
Apr  7 18:48:01 unraid crond[1653]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)
Apr  7 19:08:21 unraid sshd[32548]: Accepted password for root from 192.168.199.112 port 4394 ssh2
Apr  7 19:13:03 unraid kernel: br0: port 6(vnet4) entered disabled state
Apr  7 19:13:03 unraid kernel: device vnet4 left promiscuous mode
Apr  7 19:13:03 unraid kernel: br0: port 6(vnet4) entered disabled state
Apr  7 19:27:17 unraid kernel: br0: port 5(vnet3) entered disabled state
Apr  7 19:27:17 unraid kernel: device vnet3 left promiscuous mode
Apr  7 19:27:17 unraid kernel: br0: port 5(vnet3) entered disabled state
Apr  7 19:27:39 unraid kernel: br0: port 2(vnet0) entered blocking state
Apr  7 19:27:39 unraid kernel: br0: port 2(vnet0) entered disabled state
Apr  7 19:27:39 unraid kernel: device vnet0 entered promiscuous mode
Apr  7 19:27:39 unraid kernel: br0: port 2(vnet0) entered blocking state
Apr  7 19:27:39 unraid kernel: br0: port 2(vnet0) entered forwarding state
Apr  7 19:27:39 unraid kernel: br0: port 3(vnet1) entered blocking state
Apr  7 19:27:39 unraid kernel: br0: port 3(vnet1) entered disabled state
Apr  7 19:27:39 unraid kernel: device vnet1 entered promiscuous mode
Apr  7 19:27:39 unraid kernel: br0: port 3(vnet1) entered blocking state
Apr  7 19:27:39 unraid kernel: br0: port 3(vnet1) entered forwarding state
Apr  7 19:27:39 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr  7 19:27:39 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr  7 19:28:22 unraid kernel: br0: port 5(vnet3) entered blocking state
Apr  7 19:28:22 unraid kernel: br0: port 5(vnet3) entered disabled state
Apr  7 19:28:22 unraid kernel: device vnet3 entered promiscuous mode
Apr  7 19:28:22 unraid kernel: br0: port 5(vnet3) entered blocking state
Apr  7 19:28:22 unraid kernel: br0: port 5(vnet3) entered forwarding state
Apr  7 19:28:22 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr  7 19:28:22 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr  7 19:28:36 unraid kernel: br0: port 6(vnet4) entered blocking state
Apr  7 19:28:36 unraid kernel: br0: port 6(vnet4) entered disabled state
Apr  7 19:28:36 unraid kernel: device vnet4 entered promiscuous mode
Apr  7 19:28:36 unraid kernel: br0: port 6(vnet4) entered blocking state
Apr  7 19:28:36 unraid kernel: br0: port 6(vnet4) entered forwarding state
Apr  7 19:28:40 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr  7 19:28:40 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr  7 19:28:50 unraid kernel: ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
Apr  7 19:28:50 unraid kernel: ata5.00: irq_stat 0x00400040, connection status changed
Apr  7 19:28:50 unraid kernel: ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
Apr  7 19:28:50 unraid kernel: ata5.00: failed command: READ DMA EXT
Apr  7 19:28:50 unraid kernel: ata5.00: cmd 25/00:18:10:03:e6/00:00:ae:00:00/e0 tag 21 dma 12288 in
Apr  7 19:28:50 unraid kernel:         res 50/00:00:8f:47:37/00:00:b0:00:00/e0 Emask 0x50 (ATA bus error)
Apr  7 19:28:50 unraid kernel: ata5.00: status: { DRDY }
Apr  7 19:28:50 unraid kernel: ata5: hard resetting link
Apr  7 19:28:56 unraid kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr  7 19:28:56 unraid kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr  7 19:28:56 unraid kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr  7 19:28:56 unraid kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr  7 19:28:56 unraid kernel: ata5.00: NCQ Send/Recv Log not supported
Apr  7 19:28:56 unraid kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr  7 19:28:56 unraid kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr  7 19:28:56 unraid kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr  7 19:28:56 unraid kernel: ata5.00: NCQ Send/Recv Log not supported
Apr  7 19:28:56 unraid kernel: ata5.00: configured for UDMA/133
Apr  7 19:28:56 unraid kernel: ata5: EH complete
Apr  7 19:29:09 unraid kernel: ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
Apr  7 19:29:09 unraid kernel: ata5.00: irq_stat 0x00400040, connection status changed
Apr  7 19:29:09 unraid kernel: ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
Apr  7 19:29:09 unraid kernel: ata5.00: failed command: READ DMA EXT
Apr  7 19:29:09 unraid kernel: ata5.00: cmd 25/00:20:10:4f:39/00:00:b0:00:00/e0 tag 15 dma 16384 in
Apr  7 19:29:09 unraid kernel:         res 50/00:00:97:5f:6a/00:00:af:00:00/e0 Emask 0x50 (ATA bus error)
Apr  7 19:29:09 unraid kernel: ata5.00: status: { DRDY }
Apr  7 19:29:09 unraid kernel: ata5: hard resetting link
Apr  7 19:29:14 unraid kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr  7 19:29:14 unraid kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr  7 19:29:14 unraid kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr  7 19:29:14 unraid kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr  7 19:29:14 unraid kernel: ata5.00: NCQ Send/Recv Log not supported
Apr  7 19:29:14 unraid kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr  7 19:29:14 unraid kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr  7 19:29:14 unraid kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr  7 19:29:14 unraid kernel: ata5.00: NCQ Send/Recv Log not supported
Apr  7 19:29:14 unraid kernel: ata5.00: configured for UDMA/133
Apr  7 19:29:14 unraid kernel: ata5: EH complete
Apr  7 19:29:38 unraid kernel: ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
Apr  7 19:29:38 unraid kernel: ata5.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Apr  7 19:29:38 unraid kernel: ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Apr  7 19:29:38 unraid kernel: ata5.00: failed command: READ DMA EXT
Apr  7 19:29:38 unraid kernel: ata5.00: cmd 25/00:18:20:76:07/00:00:af:00:00/e0 tag 20 dma 12288 in
Apr  7 19:29:38 unraid kernel:         res 50/00:00:ff:18:73/00:00:af:00:00/e0 Emask 0x50 (ATA bus error)
Apr  7 19:29:38 unraid kernel: ata5.00: status: { DRDY }
Apr  7 19:29:38 unraid kernel: ata5: hard resetting link

I'm also having running VM's that just halt.  I haven't caught a log of it yet.  But I'm looking for it.

Edited by joedotmac

Share this post


Link to post

Actually I cannot find anything unusual in logging. However after executing sensors command I only get the following output:

 

root@Tower:~# sensors
fam15h_power-pci-00c4
Adapter: PCI adapter
power1:       42.30 W  (crit =  45.05 W)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +33.8°C  (high = +70.0°C)
                       (crit = +70.0°C, hyst = +67.0°C)

root@Tower:~#

 

 

Moreover after executing the detection process as seen in the below link:

 

http://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing

 

and after copying the sensors.conf file to /etc/sensors.d path: 

cp /boot/config/sensors.conf /etc/sensors.d

When I finally reboot system, the copied conf file under /etc/sensors.d path is somehow disappeared. (?)

 

On the other hand dynamix system temp plugin show the below conf file contents:

 

root@Tower:~# more /boot/config/plugins/dynamix.system.temp/sensors.conf
# sensors
chip "nct6776-isa-0290"
ignore "temp7"
chip "nct6776-isa-0290"
ignore "temp8"
chip "nct6776-isa-0290"
ignore "temp9"
chip "nct6776-isa-0290"
ignore "fan3"
chip "nct6776-isa-0290"
ignore "fan4"
chip "nct6776-isa-0290"
ignore "fan5"
chip "nct6776-isa-0290"
label "temp2" "CPU Temp"
chip "k10temp-pci-00c3"
label "temp1" "MB Temp"
chip "nct6776-isa-0290"
label "fan2" "Array Fan"
 

Again the Auto Fan Control plugin cannot detect any PWM controller

 

Edited by quad

Share this post


Link to post

You and I don't have common symptoms.  Though we seem to share various issues with the Dynamix.  I see numerous dynamix references in the syslog that appear to be related in time with various VM's just abending.  Additionally my dashboard CPU utilization percentage metrics just stop working sometime after boot.  My issues started with 6.3.2 and continue with 6.3.3.  

 

I've ripped out all the Dynamix plugins for fan, temp, stats, information, schedules, streams to see if this changes anything.  

 

I have an ASRock H97M Pro4 MB. Before I ripped out the plugins it was able to find I believe three PWM controllers on my board.

 

I can say with decent certainty that this is related to theC PU percentage utilization counters stopping a short time after boot.

Apr 24 20:43:36 unraid kernel: php[24428]: segfault at 0 ip 00000000005f42ad sp 00007fff9d0501c0 error 4 in php[400000+724000]
Apr 24 20:44:09 unraid kernel: qemu-system-x86 invoked oom-killer: gfp_mask=0x24000c0(GFP_KERNEL), nodemask=0, order=0, oom_score_adj=0
Apr 24 20:44:09 unraid kernel: qemu-system-x86 cpuset=emulator mems_allowed=0
Apr 24 20:44:09 unraid kernel: CPU: 0 PID: 19424 Comm: qemu-system-x86 Not tainted 4.9.19-unRAID #1
Apr 24 20:44:09 unraid kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H97M Pro4, BIOS P1.50 01/15/2015
Apr 24 20:44:09 unraid kernel: ffffc900059a37d8 ffffffff813a3bf2 ffffc900059a39c0 ffffffff8193d07a
Apr 24 20:44:09 unraid kernel: ffffc900059a3858 ffffffff8111ee27 0000000000000000 0000000000000000
Apr 24 20:44:09 unraid kernel: ffffffff810b2041 00000000ffffffff ffffc900059a3830 ffffffff81053fee
Apr 24 20:44:09 unraid kernel: Call Trace:
Apr 24 20:44:09 unraid kernel: [<ffffffff813a3bf2>] dump_stack+0x61/0x7e
Apr 24 20:44:09 unraid kernel: [<ffffffff8111ee27>] dump_header+0x76/0x20e
Apr 24 20:44:09 unraid kernel: [<ffffffff810b2041>] ? delayacct_end+0x51/0x5a
Apr 24 20:44:09 unraid kernel: [<ffffffff81053fee>] ? has_ns_capability_noaudit+0x34/0x3e
Apr 24 20:44:09 unraid kernel: [<ffffffff810c7bf6>] oom_kill_process+0x81/0x377
Apr 24 20:44:09 unraid kernel: [<ffffffff810c83bf>] out_of_memory+0x3aa/0x3e5
Apr 24 20:44:09 unraid kernel: [<ffffffff810cc07a>] __alloc_pages_nodemask+0xb5b/0xc71
Apr 24 20:44:09 unraid kernel: [<ffffffff81102c75>] alloc_pages_current+0xbe/0xe8
Apr 24 20:44:09 unraid kernel: [<ffffffff810c91e4>] __get_free_pages+0x9/0x37
Apr 24 20:44:09 unraid kernel: [<ffffffff81130ce2>] __pollwait+0x59/0xc7
Apr 24 20:44:09 unraid kernel: [<ffffffff81158eb6>] eventfd_poll+0x27/0x50
Apr 24 20:44:09 unraid kernel: [<ffffffff81131e2f>] do_sys_poll+0x243/0x481
Apr 24 20:44:09 unraid kernel: [<ffffffff81130c89>] ? poll_initwait+0x3f/0x3f
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81130eaa>] ? poll_select_copy_remaining+0xfe/0xfe
Apr 24 20:44:09 unraid kernel: [<ffffffff81132226>] SyS_ppoll+0xb9/0x135
Apr 24 20:44:09 unraid kernel: [<ffffffff81132226>] ? SyS_ppoll+0xb9/0x135
Apr 24 20:44:09 unraid kernel: [<ffffffff8167acab>] ? schedule+0x84/0x95
Apr 24 20:44:09 unraid kernel: [<ffffffff8167dfb7>] entry_SYSCALL_64_fastpath+0x1a/0xa9
Apr 24 20:44:09 unraid kernel: Mem-Info:
Apr 24 20:44:09 unraid kernel: active_anon:7983187 inactive_anon:18286 isolated_anon:0
Apr 24 20:44:09 unraid kernel: active_file:2273 inactive_file:3660 isolated_file:0
Apr 24 20:44:09 unraid kernel: unevictable:0 dirty:24 writeback:0 unstable:0
Apr 24 20:44:09 unraid kernel: slab_reclaimable:4167 slab_unreclaimable:10152
Apr 24 20:44:09 unraid kernel: mapped:22547 shmem:121068 pagetables:18754 bounce:0
Apr 24 20:44:09 unraid kernel: free:66578 free_pcp:15 free_cma:0
Apr 24 20:44:09 unraid kernel: Node 0 active_anon:31932748kB inactive_anon:73144kB active_file:9092kB inactive_file:14640kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:90188kB dirty:96kB writeback:0kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 18933760kB anon_thp: 484272kB writeback_tmp:0kB unstable:0kB pages_scanned:41461 all_unreclaimable? yes

 

This is related to the VM's just shutting off. 

Apr 24 19:34:01 unraid crond[1662]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null)
Apr 24 19:50:10 unraid kernel: br0: port 2(vnet0) entered disabled state
Apr 24 19:50:10 unraid kernel: device vnet0 left promiscuous mode
Apr 24 19:50:10 unraid kernel: br0: port 2(vnet0) entered disabled state
Apr 24 19:50:10 unraid kernel: br0: port 3(vnet1) entered disabled state
Apr 24 19:50:10 unraid kernel: device vnet1 left promiscuous mode
Apr 24 19:50:10 unraid kernel: br0: port 3(vnet1) entered disabled state
Apr 24 19:54:01 unraid crond[1662]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null)
Apr 24 19:57:44 unraid emhttp: err: get_temperature: popen /usr/sbin/smartctl -n standby  -A /dev/sde: Cannot allocate memory
Apr 24 19:57:44 unraid emhttp: err: get_temperature: popen /usr/sbin/smartctl -n standby  -A /dev/sdi: Cannot allocate memory
Apr 24 19:57:44 unraid emhttp: err: get_temperature: popen /usr/sbin/smartctl -n standby  -A /dev/sdf: Cannot allocate memory
Apr 24 19:57:44 unraid emhttp: err: get_temperature: popen /usr/sbin/smartctl -n standby  -A /dev/sdg: Cannot allocate memory
Apr 24 19:57:44 unraid emhttp: err: get_temperature: popen /usr/sbin/smartctl -n standby  -A /dev/sdh: Cannot allocate memory
Apr 24 19:57:44 unraid emhttp: err: get_temperature: popen /usr/sbin/smartctl -n standby  -A /dev/sdd: Cannot allocate memory
Apr 24 19:57:44 unraid emhttp: err: emhttp_event: popen /usr/local/sbin/emhttp_event poll_attributes: Cannot allocate memory
Apr 24 20:01:29 unraid kernel: br0: port 4(vnet2) entered disabled state
Apr 24 20:01:29 unraid kernel: device vnet2 left promiscuous mode
Apr 24 20:01:29 unraid kernel: br0: port 4(vnet2) entered disabled state
Apr 24 20:04:13 unraid kernel: br0: port 2(vnet0) entered blocking state
Apr 24 20:04:13 unraid kernel: br0: port 2(vnet0) entered disabled state
Apr 24 20:04:13 unraid kernel: device vnet0 entered promiscuous mode
Apr 24 20:04:13 unraid kernel: br0: port 2(vnet0) entered blocking state
Apr 24 20:04:13 unraid kernel: br0: port 2(vnet0) entered forwarding state
Apr 24 20:04:13 unraid kernel: br0: port 3(vnet1) entered blocking state
Apr 24 20:04:13 unraid kernel: br0: port 3(vnet1) entered disabled state
Apr 24 20:04:13 unraid kernel: device vnet1 entered promiscuous mode
Apr 24 20:04:13 unraid kernel: br0: port 3(vnet1) entered blocking state
Apr 24 20:04:13 unraid kernel: br0: port 3(vnet1) entered forwarding state
Apr 24 20:04:14 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr 24 20:04:14 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound
Apr 24 20:04:17 unraid kernel: br0: port 4(vnet2) entered blocking state
Apr 24 20:04:17 unraid kernel: br0: port 4(vnet2) entered disabled state

 

 

Edited by joedotmac

Share this post


Link to post
On 4/9/2017 at 4:37 PM, quad said:

I was been using the Auto Fan Control plugin for the latest months and it was working like charm.

Suddenly and after upgrading to v6.3.3 it stopped working. It doesn't detect sensors any more.

Few months ago it was installed along with Nerd Tools pack perl version and detected relevant sensors with success.

I also upgraded to the latest perl version but again nothing. (Mobo: ASRock - 970 Pro3 R2.0)

Any ideas?

Thanks in advance.

 

Were you able to make any progress from where you started?  I'm considering the leap back to 6.2.4.

Edited by joedotmac

Share this post


Link to post
On 4/9/2017 at 2:37 PM, quad said:

Any ideas?

 

Please post your diagnostics.zip file as requested here:

 

 

Share this post


Link to post
On 4/26/2017 at 11:58 PM, joedotmac said:

 

Were you able to make any progress from where you started?  I'm considering the leap back to 6.2.4.

 

To be honest during this period I don't have spare hardware to experiment further and as far as the current setup given the fact that I utilize 3 VMs used for my daily tasks I think it is not a good I idea to apply such testing with the current hw.  

Share this post


Link to post

Problem resolved after:

 

a) Upgrading to v6.3.5

b) Uninstalling Nerd Tools

c) Uninstalling Dynamix Auto Fan Control

d) Installing Nerd Tools (for perl package)

e) Installing Dynamix System Temperature

f) and finally installing Dynamix Auto Fan Control

Share this post


Link to post

Is anyone having the issue of when uninstalling the plug in it doesn't get rid of the tile on the dashboard?

image.thumb.png.f608497849d46dadd377db51c9d0374e.png

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.