Error: RFXCom: Error opening serial port!

[Doler]

After some retries I succesfully migrated to beta build 17277 and converted to systemd control. Since that time my RFXCom won't start anymore stating that the serial port cannot be opened. The serial port is identified by serial/by-id and present in the harware configuration.
Is there a relation to the (many) latest changes? Are there ways to discover the cause of the problem?

[Doler]

Returned to beta 17252 and RFXCom is not giving a problem anymore. Sure it has something to do with changes to 17277. Will investigate this further.

I also noticed that beta 17277 forced reboots of the system. It happens muliple times per day with unknown frequency. I will (on my test system) disable all hardware and see what happens.

[Tukker]

KIS
Don't fuzz with beta if you want to stay out of trouble.

[claude2666]

Are you running monit to monitor domoticz?
If so, you may have to adapt your /etc/monit/monitrc file.
With the latest betas, domoticz has been migrated to use systemd and there is no longer a PID file created, causing monit checks to fail and causing boots. You can check /var/log/monit.log

I have changed my monitrc file from
CHECK PROCESS domoticz WITH PIDFILE /var/run/domoticz.pid
START PROGRAM = "/etc/init.d/domoticz.sh start"
STOP PROGRAM = "/etc/init.d/domoticz.sh stop"

to:

check process domoticz matching "domoticz"
START PROGRAM = "/bin/systemctl start domoticz.service"
STOP PROGRAM = "/bin/systemctl stop domoticz.service"

[Doler]

I'm indeed running monit and didn't think of that. I'll change immediately, thanks for the tip.

[Doler]

I'm indeed running monit and didn't think of that. I'll change immediately, thanks for the tip.

Just saw a new commit the re-introduces a PID:

- Support writing a PID file via -pidfile without requiring -daemon,
allowing process managers like monit to locate the process when
running under systemd Type=simple