HaKuNa
(Remo M)
December 30, 2020, 4:12am
39
If you really have the same issue as described in the 1st post, you have three options. If not, open a new thread as this one here is marked as solved.
Option 1) Use the marked solution (I know it’s a workaround)
I enabled now a workaround using ser2net service
dnf install ser2net
vi /etc/ser2net.conf
deleted the whole content and added only this line
3001:telnet:0:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT remctl
systemctl enable ser2net
systemctl start ser2net
Port configuration:
rfc2217://127.0.0.1:3001
Option 2) use this workaround (I have not yet tried it)
Ok @HaKuNa and @chris I think I figured out what’s wrong. It appears that openHAB 3.0 requires access to /var/lock. On ArchLinux, this is symlinked to /run/lock, which has permissions set to 755 root root so the openhab user cannot access. /run/lock is considered a temp directory and is configured via /usr/lib/tmpfiles.d/legacy.conf, which Systemd uses to create /run/lock in volatile memory at system boot with those permissions. To override these permissions, I was able to copy legacy.conf to /e…
Option 3) Wait and hope someone will fix it permanently.
This is all handled in the nrjavaserial bundle. OH3 uses a newer version and I seem to recall some changes to fix some issues with locking on some variants of linux.
1 Like