jsiemon
Members
-
Joined
-
Last visited
-
Just a question regarding an upgrade path from 7.2.6 to 7.3. If I upgrade to 7.3 but for now choose not to use internal boot or TPM, and then I find an issue with 7.3 and my hardware, is it possible to rollback to 7.2.6 or am I forever locked into 7.3+? The wording for the downgrade seems to suggest I would be ok to rollback to 7.2.6 under these circumstances, but I just want to confirm before upgrading.
-
@mandarons, I just started to use the app/docker and I have everything running fine, with no apparent issues, however I do have question regarding the config.yaml. I would like to receive an email notification whenever iCloud requires re-authentication. My question is: does the email password in config.yaml go inside of quotes? The template does not indicate that it does, but I would like to make sure this is correct. Thanks for your help.
-
I’m also having the same issues with the WebGUI crashing on startup. I’m now running the docker TailScale without issue. WebGUI is reachable, all shares can be accessed as can all docker containers so it doesn’t appear to be a server or network setup issue.
-
tower-diagnostics-20230521-1435.zip I’ve been running 12.RC5 and now 12.RC6 as upgraded from 11.5 and I’m experiencing a problem with Mover. For 11.5 I had been running a dedicated mover_cache using a single SSD formatted as XFS. With the move to 12.RC5 I decided to reformat the mover_cache as ZFS. I also reformatted my array drives from XFS to ZFS. Now using 12.RC5/12.RC6 when I save a file, such as an Excel Spreadheet, it is appropriately saved on the ZFS formatted pool mover_cache. When I invoke Mover, the file is then moved to the appropriate share on the ZFS Array Drive as it should. No change in behavior from 11.5 using all XFS drives. However if I try to open the file after it has been moved to the Array ZFS drive it is now seen as Read Only. If I open it while it is on the SSD ZFS mover_cache I can open it without issue, full r/w privileges. Things that work most of the time, at least as temporary fixes, are Stop/Start the array, or reformat the mover_cache as ZFS or XFS, or Reboot the server, then the file can be opened with full r/w privileges. Using an XFS SSD mover_cache is a permanent fix, but not relevant. In this configuration, there is no issue but it kind of defeats my hope of mirroring the cache drives in the future. The only other change I made was to increase the memory available to the ZFS filesystem from 1/8 to ¼. I have 32G of ECC ram and it mostly goes unused so I thought doubling the ZFS ram might be beneficial. Attached is the DIAGNOSTIC immediately after a save that and MOVE resulting in the file being READ ONLY. My client machine is running MacOS 12.6.5. On Unraid, I have tried toggling the SMB MacOS enhancement, auto trim and compression on the mover_cache and ARRAY but it doesn't seem to matter.
-
Just to jump in on this issue, I recently updated to 6.10.3 and today I went to do a manual backup using the plugin but no backup was initiated. I reverted back to 6.10.2 and all is working fine. Before reverting to 6.10.2 I tried using macvlan instead of ipvlan but that made no difference. There is definitely an issue with the plugin and 6.10.3. For now I'll just stay with 6.10.2.
-
SOLVED: The issue is not related to the Docker Template or UnRaid but is unique to OpenHAB. I have a high core count server(32 cores) and Jetty chokes. The solution is to either pin the docker to no more than 4 cores or update the OpenHAB conf/services/runtime.cfg as follows. For future reference: in Openhab 3.0 org.eclipse.smarthome.webclient has changed to org.openhab.webclient. So it becomes: org.eclipse.smarthome.webclient:minThreadsShared=20 org.eclipse.smarthome.webclient:maxThreadsShared=40 org.eclipse.smarthome.webclient:minThreadsCustom=15 org.eclipse.smarthome.webclient:maxThreadsCustom=40 After making these changes OH3 runs without apparent issue. _______________ I've been running OpenHAB 2.5.x for almost 2 years now using the Docker template without much problem. I have also spun up another Docker to evaluate OpenHAB 3.0 and it runs pretty well overall, but I have 1 major problem with OH 3.0 that I do not have OH2.5x, I am unable to connected to OH3.0 from the myopenhab.org website. I can push Notifications from the site but I cannot access my local OH3.0 WebUI from home.myopenhab.org. For 2.5.x I have no issue. Every time I try to access OH3 this way I get an error openHAB connection error: HttpClient@4016d1a5{FAILED} is stopped Any ideas how to fix this? is this a permissions issue or some incompatibility with UnRaid Docker (my suspicion). I am running UnRaid 6.8.2 and have tried 6.8.3 and 6.9.rc2 but it makes no difference. I have also removed and recreated the docker image and docker containers, without a better result. If I switch over to OH2 I immediately am able to access the local OH2 WebUI. I also tried installing OH3 on a MacOS VM hosted on UnRaid using br0 just like my dockers and that worked like a charm without issue, so I know OH3 can run on UnRaid network setup. If it was only UI access I wouldn't be too concerned, but any traffic such as OWNTracks that uses the home.myopenhab.org interface is not able to communicate with my OH3 installation and therefore I have no way to update Presence detection that involves the GPS Tracker/OWNTracks. Any ideas as what might be the problem or what to try next? Any arguments I should be using during the install?
