Gingersnap155

Ok so I switch to using a JSON and adjusted the docker run command accordingly. Now it works fine. It’s possible I messed up something with my docker run command with a typo and that was the problem. Either way it works perfectly fine now. And I can even edit it in notepad++ and save and it will adjust on the fly.

Yes I read through the documentation. That is why I am here. I created the YAML as instructed, placed it where instructed. So where do I ask for support for this issue then? It’s a separate docker that you provide and is required for the automatic fan control. The documentations talks about a disks.ini but no where to obtain it? It’s in the location mapped in the suggested docker compose command. It appears the log shows disk temperatures so I would assume that means that part is covered and working. I never mentioned that I am using a json the log file is stating it. The docker run command I used came from that page and it’s set to use the YAML. I am not sure what I’m missing in my errors. Or where to get help with something you’ve provided documentation to. I’m fine without a community app and just using the background service and YAML. Just need it to work since following what’s provided did not work for me.

Hello there. I am having an error when starting the openfanservice docker. my .yaml is a copy paste of the provided example and then changes sensors, temperatures, speeds, along with per header assignments made to the profiles. Per yamlchecker it is valid. Totally possible I am missing something super simple. Thank you for your help! Here is the log, Jan 18 2025 14:47:47.357 pid:7 base_logger.py 62 INFO Logging level: DEBUG Jan 18 2025 14:47:47.357 pid:7 start.py 127 INFO ---- Starting OpenFAN UnRAID Service ---- Jan 18 2025 14:47:47.357 pid:7 start.py 128 INFO -- API Host: `192.168.10.25:3000` Jan 18 2025 14:47:47.357 pid:7 start.py 129 INFO -- Sensors: `/mnt/OpenFanService/sensors/disks.ini` Jan 18 2025 14:47:47.357 pid:7 start.py 130 INFO -- Profile: `/mnt/OpenFanService/data/fan_profiles.yaml` Jan 18 2025 14:47:47.357 pid:7 start.py 131 INFO -- LiveReload: `True` Jan 18 2025 14:47:47.357 pid:7 start.py 20 INFO Starting OpenFAN - Unraid fan control app Jan 18 2025 14:47:47.357 pid:7 start.py 22 INFO Loading temperature sensors Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `parity` temperature is `25°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk1` temperature is `24°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk2` temperature is `23°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk3` temperature is `24°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk4` temperature is `24°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk5` temperature is `25°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk6` temperature is `24°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk7` temperature is `29°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk8` temperature is `28°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk9` temperature is `27°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk10` temperature is `28°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk11` temperature is `27°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk12` temperature is `27°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk13` temperature is `39°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk14` temperature is `40°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `disk15` temperature is `32°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `parity2` temperature is `25°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `cache` temperature is `33°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `cache2` temperature is `33°C` Jan 18 2025 14:47:47.361 pid:7 temperature_sensors.py 24 DEBUG Sensor `downloadcache` temperature is `33°C` Jan 18 2025 14:47:47.362 pid:7 temperature_sensors.py 24 DEBUG Sensor `downloadcache2` temperature is `33°C` Jan 18 2025 14:47:47.362 pid:7 temperature_sensors.py 24 DEBUG Sensor `vm` temperature is `33°C` Jan 18 2025 14:47:47.362 pid:7 temperature_sensors.py 24 DEBUG Sensor `vm2` temperature is `27°C` Jan 18 2025 14:47:47.362 pid:7 temperature_sensors.py 24 DEBUG Sensor `vm4tb` temperature is `26°C` Jan 18 2025 14:47:47.362 pid:7 temperature_sensors.py 24 DEBUG Sensor `flash` temperature is `*°C` Jan 18 2025 14:47:47.362 pid:7 start.py 25 INFO Loading fan profiles Jan 18 2025 14:47:47.362 pid:7 fan_configuration.py 23 ERROR Error parsing json file Jan 18 2025 14:47:47.362 pid:7 fan_configuration.py 24 ERROR Error: Expecting value: line 1 column 1 (char 0)

Updated from 6.11.5 to 6.12.4 today and zero issues using macvtap so far. All dockers and shares working properly.

I was reading through the notes about macvtap having some benefits. Is there any downside to using it instead? from my understand staying set to macvlan on the docket network and disabling the bond would enable macvtap? Planning to make the shift to 6.12.4 from 6.11.5 this weekend and have been reading through things to have my ducks in a row.