Hi everyone,
The new 4.10717 version of Domoticz will be available in contribs-testing for ClearOS7 in about 1 hour. A new version of libopenzwave is also found in contribs-testing.
My original plan was to use the fresh libopenzwave version 1.6 that has a wide amount of improvements. However, it is not complete yet and a number of interoperability issues with domoticz still needs to be solved. The 4.10717 release of Domoticz was a rather painful excercise with several attempts upstream before everything was ok. My plan is to have both these new version of domoticz and libopezwave sitting in contribs-testing for at least a couple of weeks to be sure it is fully functioning before moving them to the contribs repo.
Heads up: Domoticz upstream is likely to release yet another version soon that will require libopenzwave version 1.6 . Given the status right now + the fact that version 1.6 configuration files are incompatible with the current version, I am a bit hesitant around the introduction in ClearOS7. I really do not want to push out a new release that will cause any existing installation to fail, forcing the user to reconfigure all the z-wave related stuff in his/her network. Any comments?
/Fred
The new 4.10717 version of Domoticz will be available in contribs-testing for ClearOS7 in about 1 hour. A new version of libopenzwave is also found in contribs-testing.
My original plan was to use the fresh libopenzwave version 1.6 that has a wide amount of improvements. However, it is not complete yet and a number of interoperability issues with domoticz still needs to be solved. The 4.10717 release of Domoticz was a rather painful excercise with several attempts upstream before everything was ok. My plan is to have both these new version of domoticz and libopezwave sitting in contribs-testing for at least a couple of weeks to be sure it is fully functioning before moving them to the contribs repo.
Heads up: Domoticz upstream is likely to release yet another version soon that will require libopenzwave version 1.6 . Given the status right now + the fact that version 1.6 configuration files are incompatible with the current version, I am a bit hesitant around the introduction in ClearOS7. I really do not want to push out a new release that will cause any existing installation to fail, forcing the user to reconfigure all the z-wave related stuff in his/her network. Any comments?
/Fred
Share this post:
Responses (10)
-
Accepted Answer
Fredrik Fornstad wrote:
Ok,
It turns out that fail2ban have changed behaviour a bit and I therefore need to adjust the way app-domoticz detects if it is running or not. I just tested another way to do it and it seems to work. Expect a number of days (a week?) before the update is released as it needs to go through a few steps with the clearos-team first.
You can safely use domoticz as it is right now. The domoticz warning message about the "attack-detector not running" is always on, but you can see the true status at the attack-detector web page. No "real" functionality is affected.
/Fred
Fred
Thanks for the quick fix -
Accepted Answer
ClearOS has a function in /usr/clearos/apps/base/libraries/Daemon.php called get_running_state(). I think that is what the webconfig uses, but I'm not sure. It also seems to use pidof but the status in the Attack Detector app shows correctly. The systemd way of doing things seems to be:
Optionally you can use the "-q" switch and check the return code.systemctl is-active fail2ban -
Accepted Answer
Nick Howitt wrote:
@Fredrik, I'd be interested to know what you find has changed in f2b. It recently updated from 0.10.4 to 0.10.5 and I did not notice anything significant with the ClearOS filters I run. There was quite a change when it went from 0.9.7 to 0.10.4 and I had to rework some of the ClearOS approach. Now we do not do any edits to jail.conf. Instead, put any changes in jail.local. The same goes for any changes to filters or actions. Use a local file to override the conf file settings. You can do what you want in /etc/fail2ban/jail.d.
Not sure if this happened now or was introduced with 0.10.4... But I was using the "pidof fail2ban-server" command to check if it was running in 0.9.7 and that worked. In 0.10.5 the "pidof" command returns nothing unless you query for python... so now modifying it to use "pgrep f2b" instead and that works in 0.10.5. I would say that changes like this should probably not be allowed within a major Centos release, just between them... (but maybe it had been marked depreciated already, I do not know).
Anyway, I have built a new version and sent a message to Ben asking him to release it.
/Fred -
Accepted Answer
@Fredrik, I'd be interested to know what you find has changed in f2b. It recently updated from 0.10.4 to 0.10.5 and I did not notice anything significant with the ClearOS filters I run. There was quite a change when it went from 0.9.7 to 0.10.4 and I had to rework some of the ClearOS approach. Now we do not do any edits to jail.conf. Instead, put any changes in jail.local. The same goes for any changes to filters or actions. Use a local file to override the conf file settings. You can do what you want in /etc/fail2ban/jail.d. -
Accepted Answer
Ok,
It turns out that fail2ban have changed behaviour a bit and I therefore need to adjust the way app-domoticz detects if it is running or not. I just tested another way to do it and it seems to work. Expect a number of days (a week?) before the update is released as it needs to go through a few steps with the clearos-team first.
You can safely use domoticz as it is right now. The domoticz warning message about the "attack-detector not running" is always on, but you can see the true status at the attack-detector web page. No "real" functionality is affected.
/Fred -
Accepted Answer
Patrick de Brabander wrote:
Hi fred,
I getting a message in the webconfig menu of domoticz
Warning
Attack Detector for Domoticz is enabled but the Attack Detector service is not running.
Nothing has been changed and the services are running.
Maybe some update of fail2ban has to do with it ? This was on 19th februari
Yes, you are probably righ about the fail2ban updatet. I am a bit busy right now, but will investigate in a couple of days.
/Fred -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Hi Fred,
Good choice to make an update to 4.10717 and wait until everything is settled with libopenzwave 1.6.
Depending on the development of libopenzwave and Domoticz we will see what happens.
If eventually it is needed to reconfigure, it means we have no choice then to reconfigure or never can update......
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »