Ecsport108

Hello all, I am having similar issues to Hasown above with a Gigabyte W480 Vision W motherboard with three system fans installed (not including CPU cooler). When the IT87 plugin is not installed, I get three fans listed in both the System Temp and Fan Auto Control plugins appearing as it8792. If I install the IT87 plugin multiple new it8688 entries, including those for fan headers not currently populated, appear just as in the screenshot above. Even with the IT87 plugin installed, System Temp seems to only list speeds next to the it8792 entries anyways so I have uninstalled the IT87 plugin for now. My CPU fan only appears with the IT87 plugin installed, but I don't want to control it with the Fan Auto Control plugin regardless. I have enabled fan control on all three it8792 PWM controllers and the Fan Auto Control plugin is able to detect a fan on each controller, albeit intermittently. However, when I go to detect the minimum PWM value, I hear the fans physically changing speeds but a value never populates the box and the speed control doesn't appear to be working correctly. I have tried putting multiple random numbers in the "Minimum PWM Value" box but it does not seem to affect anything. Here are some lines from my log that show the plugin appearing to adjust the PWM value but the RPMs stay constant. Does anyone have any ideas on how to fix this, I am going deaf from these 80mm server fans and the motherboard's BIOS fan controls only allow me to bring them down to 70% speed. Oct 13 16:25:53 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm) Oct 13 16:25:53 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3229rpm) to: 88 (34% @ 3229rpm) Oct 13 16:26:09 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3040rpm) to: 88 (34% @ 3040rpm) Oct 13 16:26:59 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm) Oct 13 16:26:59 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3245rpm) to: 88 (34% @ 3229rpm) Oct 13 16:28:05 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm) Oct 13 16:28:05 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3245rpm) to: 88 (34% @ 3229rpm) Oct 13 16:29:11 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3125rpm) Oct 13 16:29:11 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3245rpm) to: 88 (34% @ 3229rpm) Oct 13 16:30:17 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm) Oct 13 16:30:17 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3214rpm) to: 88 (34% @ 3229rpm)

Stardew Valley has just had its largest update in a while and this method seems to have been updated very quickly to be compatible. Are you still unwilling to add support for this method? I would really love to host this game for my friend group. There was one outdated line of code that I noticed when looking though the Stardew Multiplayer Docker repository so I forked it to correct the error and sent a pull request to the main repository. Until the developer accepts that pull request, my corrected fork can be found here: https://github.com/Ecsport108/stardew-multiplayer-docker I tried to get this to work with Unraid but I'll be honest, I have absolutely no idea what I am doing. Any help would be greatly appreciated.

Is anyone else having issues running either of these commands. Alternatively, does anyone have any ideas I what I can do to correct this issue. I can still run the commands manually it's just a bit annoying.

Hello. I am running into a slight issue. I just updated from 6.7.2 to 6.8.3 (a little late, I know) and it seems to have broken one of my scripts. Any time I try to run or the done button never appears which leads me to believe the script is hanging. If I open the docker tab of the web ui in another browser tab without closing the script, the docker service appears to have started and works fine. However, closing the script in the original tab causes it to abort leading the docker service to return that it failed to start despite it working fine up until then. I have deleted my docker image to verify that it was not an issue with docker and the issue persists. Executing the same commands from the terminal works fine. Any help would be very appreciated!

The 'ghost' Dockers disappeared from the Auto-Updater plugin after an update to Unraid version 6.5.1-rc6 and a subsequent system reboot. I don't know which of these prompted their removal but I assume it was simply a reboot the whole time. Sorry for the trouble.

Okay, thank you for the info! However, I am still struggling to get these Dockers to go away. They are no longer installed and the images have been removed, I have also run a prune command so there shouldn't be any remaining files/plugin info and yet the Auto-Updater still thinks they are installed and tries to update them every night (unless I manually deselect them). Why are these plugins showing up in the first place and what can I do to prevent them from showing up in the Auto-Updater?

I am also experiencing this issue, specifically with Docker containers that were not installed through Community Applications, but rather manually through commands. I am unsure if this last part is related or just coincidental. Any ideas on how to get these 'ghost' plugins to be properly removed? Unraid Version: 6.5.1-rc2 Plugin Version: 2018.03.02 EDIT: I realized after initially posting that pihole is also a 'ghost' Docker that I removed, I installed that Docker using Community Applications, therefore disproving my initial hypothesis.