Ok, I found and corrected the problem with the vanishing directory and have issued a new build. Will be released in a day or two.
/Fred

Fredrik Fornstad wrote:

Patrick,
That should not happen... Not sure why.
Please make sure domoticz is stopped and then try this from the command line:

mkdir /var/run/domoticz

chown domoticz:domoticz /var/run/domoticz

Now I think you should be able to start domoticz in the normal way.

/Fred

Hi Fred,

This worked. Strange that is has changed some how.

thanks for the quick support

Patrick,
That should not happen... Not sure why.
Please make sure domoticz is stopped and then try this from the command line:

mkdir /var/run/domoticz

chown domoticz:domoticz /var/run/domoticz

Now I think you should be able to start domoticz in the normal way.

/Fred

Patrick de Brabander wrote:

Patrick de Brabander wrote:

[quote]Dave Loper wrote:

With the service stopped, does the pid file exist?

Hi Dave,

No. no.pid file found on the server.
As mentioned, even the directory doesn't exist.

Maybe this helps:

/etc/cron.daily/update_clearos_cert_in_domoticz:



Job for domoticz.service failed because a configured resource limit was exceeded. See "systemctl status domoticz.service" and "journalctl -xe" for details.

[/quote]

Update:

Running manually by executing : /usr/share/domoticz/run-domoticz is working

Patrick de Brabander wrote:

Dave Loper wrote:

With the service stopped, does the pid file exist?

Hi Dave,

No. no.pid file found on the server.
As mentioned, even the directory doesn't exist.

Maybe this helps:

/etc/cron.daily/update_clearos_cert_in_domoticz:



Job for domoticz.service failed because a configured resource limit was exceeded. See "systemctl status domoticz.service" and "journalctl -xe" for details.

Dave Loper wrote:

With the service stopped, does the pid file exist?

Hi Dave,

No. no.pid file found on the server.
As mentioned, even the directory doesn't exist.

With the service stopped, does the pid file exist?

Hi Fred,

My domoticz server i s not starting any more after a reboot of the ClearOS server
I'm getting the following error

Sep 02 19:00:13 pdebrabander.nl systemd[1]: Unit domoticz.service entered failed state.

Sep 02 19:00:13 pdebrabander.nl systemd[1]: domoticz.service failed.

Sep 02 19:00:29 pdebrabander.nl polkitd[710]: Registered Authentication Agent for unix-process:19335:4071892 (system bus name :1.940 [/usr/bin/pkttyagent --n

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: 2017-09-02 19:00:43.855  Domoticz V3.8153 (c)2012-2017 GizMoCuz

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: 2017-09-02 19:00:43.855  Build Hash: 494fff7, Date: 2017-08-07 20:07:56

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: Domoticz is starting up....

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: 2017-09-02 19:00:43.855  Startup Path: /usr/share/domoticz/

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: 2017-09-02 19:00:43.855  Startup delay... waiting 0 seconds...

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: domoticz: Domoticz is starting up....

Sep 02 19:00:43 pdebrabander.nl domoticz[19359]: domoticz: Could not open PID lock file /var/run/domoticz/domoticz.pid, exiting

Sep 02 19:00:43 pdebrabander.nl domoticz[19360]: Could not open PID lock file /var/run/domoticz/domoticz.pid, exiting

Sep 02 19:00:43 pdebrabander.nl systemd[1]: domoticz.service never wrote its PID file. Failing.

Sep 02 19:00:43 pdebrabander.nl systemd[1]: Failed to start Domoticz Home Automation.

-- Subject: Unit domoticz.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit domoticz.service has failed.

Strange, because the directory " /var/run/domoticz" doesn't exist.

Can you help me with this

Just got a message that the domoticz program (and an updated libopenzwave) has been released to the correct repository. It now takes about 1 hour before it is available at the ClearOS mirrors. After that there should be no dependency errors when updating.

/Fred

Patrick,
No problem, it will "solve itself" in the next 24 hours as one of the packages is still on its way...

Explanation:
The new app-domoticz program require the new base domoticz program. That is; both needs to be released for the update to succeed. Both packages has been built, but the way clearos build system is setup they go into different places with different persons as "release gatekeepers". I have a request for both packages to be released but the request for the base domoticz package to be released has not yet been handled (time zone related...).

If you absolutely can not wait, I think you can from command line issue:

yum update --enablerepo=clearos-contribs-testing libopenzwave domoticz app-domoticz app-domoticz-core

I have not tested it myself, and i may have gotten the name of the repo slighly wrong...

/Fred

Fredrik Fornstad wrote:

Hi everyone,
I am about to release Domoticz 3.8153 within a day or so together with a needed adjustment of app-domoticz. Please note that Domoticz has undergone heavy development and potentially there are some features that have changed behaviour and that you may need to adjust any scripts etc that you have created for the present Domoticz program.

One thing that I do not think can be avoided is that due to the fundamental change of the deamon/PID handling (actually: a bug correction in Domoticz) any running instance of Domoticz will stop at the update and you will have to manually start it again. Sorry for this.

/Fred

Hello Fred,

I'm getting the following error when i try to upgrade:

Resolving Dependencies

--> Running transaction check

---> Package app-domoticz.noarch 1:3.1-4.v7 will be updated

---> Package app-domoticz.noarch 1:3.2-3.v7 will be an update

---> Package app-domoticz-core.noarch 1:3.1-4.v7 will be updated

---> Package app-domoticz-core.noarch 1:3.2-3.v7 will be an update

--> Processing Dependency: domoticz >= 3.8153-1 for package: 1:app-domoticz-core                                                                               -3.2-3.v7.noarch

--> Finished Dependency Resolution

Error: Package: 1:app-domoticz-core-3.2-3.v7.noarch (private-clearcenter-domotic                                                                               z)

           Requires: domoticz >= 3.8153-1

           Installed: domoticz-3.5877-6.v7.x86_64 (@clearos-contribs)

               domoticz = 3.5877-6.v7

 You could try using --skip-broken to work around the problem