[MyDomoAtHome] Support thread

[epierre]

start-stop-daemon: warning: failed to kill 13314: No such process
failed!

so although it is started, it doesn't work (IP:port/devices also doesn't load...)

ok so :

./update-mdah.sh

sudo service MyDomoAtHome.sh check

if nothing then try:

./start2.sh

[patricknooijen]

Hello,

i'm trying to get domoticz and MyDomoAtHome running on an virtualbox ubuntu server.
Domoticz runs fine and returns the devices. MyDomoAtHome runs the webserver, but no devices. When i call that url i get :

Code: Select all

{"devices":[{"id":"S00","type":"DevGenericSensor","name":"Unable to connect to Domoticz","params":[{"key":"Value","unit":"","graphable":"false","value":""}]},{"id":"S01","name":"Please add this gateway in Setup/settings/Local Networks","type":"DevGenericSensor","params":[{"unit":"","graphable":"false","value":"","key":"Value"}]}]}

Added both ip's to domoticz does nothing. Same errors.

Running ./start2.sh gives me :

Code: Select all

domoticz@ubuntu:~/domoticz/MyDomoAtHome$ ./start2.sh
[sudo] password for domoticz:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
environment:development
log:error
logger:file
2015/10/09-18:01:58 Starman::Server (type Net::Server::PreFork) starting! pid(1450)
Resolved [*]:3001 to [::]:3001, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 3001 on host :: with IPv6
Setting gid to "33 33 33"
Starman: Accepting connections at http://*:3001/
Use of uninitialized value in concatenation (.) or string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 382.
Use of uninitialized value $ver in string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 851.
Use of uninitialized value $mpd_host in string ne at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 859.
Use of uninitialized value in concatenation (.) or string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 873.
Use of uninitialized value in concatenation (.) or string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 907.
::ffff:10.50.192.154 - - [09/Oct/2015:18:02:11 +0200] "GET /devices HTTP/1.1" 200 684 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"

anyone can tell me what i'm doing wrong? Reinstalled ubuntu to check if that was the problem. Same thing for domoticz and MyDomoAtHome. Tried on my home network and work network. Same problem.

[DRuw]

start-stop-daemon: warning: failed to kill 13314: No such process
failed!

so although it is started, it doesn't work (IP:port/devices also doesn't load...)

ok so :

./update-mdah.sh

sudo service MyDomoAtHome.sh check

if nothing then try:

./start2.sh

I thought it was working this morning when I did the ./update-mdah.sh
then I received the devices when I hit ip:3001/devices

I could not test it that time with the app but was confident it was fixed.
now however I saw it didn't work in the app so I did the last part as well with this result:

pi@raspberrypi ~/domoticz/MyDomoAtHome $ sudo service MyDomoAtHome.sh check
Usage: /etc/init.d/MyDomoAtHome {start|force-start|stop|force-stop|reload|restart|force-reload}
pi@raspberrypi ~/domoticz/MyDomoAtHome $ ./start2.sh
log directory /home/pi/domoticz/MyDomoAtHome/bin/.. isn't writable/executable and can't chmod it at /usr/share/perl5/Dancer/Logger.pm line 16
log directory /home/pi/domoticz/MyDomoAtHome/bin/.. isn't writable/executable and can't chmod it at /usr/share/perl5/Dancer/Logger.pm line 16
environment:development
log:error
logger:file
log directory /home/pi/domoticz/MyDomoAtHome isn't writable/executable and can't chmod it at /usr/share/perl5/Dancer/Logger.pm line 16
log directory /home/pi/domoticz/MyDomoAtHome isn't writable/executable and can't chmod it at /usr/share/perl5/Dancer/Logger.pm line 16
2015/10/09-18:31:24 Starman::Server (type Net::Server::PreFork) starting! pid(23465)
Resolved [*]:3001 to [0.0.0.0]:3001, IPv4
Host [*] resolved to IPv6 address [::] but IO::Socket::INET6->new fails: Address family not supported by protocol at /usr/share/perl5/Net/Server/Proto.pm line 133.
Binding to TCP port 3001 on host 0.0.0.0 with IPv4
2015/10/09-18:31:24 Can't connect to TCP port 3001 on 0.0.0.0 [Address already in use]
at line 67 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2015/10/09-18:31:24 Received QUIT. Running a graceful shutdown
Use of uninitialized value in subtraction (-) at /usr/share/perl5/Net/Server/PreFork.pm line 355.
Use of uninitialized value in subtraction (-) at /usr/share/perl5/Net/Server/PreFork.pm line 385.
Use of uninitialized value in subtraction (-) at /usr/share/perl5/Net/Server/PreFork.pm line 405.
Use of uninitialized value in subtraction (-) at /usr/share/perl5/Net/Server/PreFork.pm line 413.
2015/10/09-18:31:24 Worker processes cleaned up
2015/10/09-18:31:24 Server closing!
shutdown() on closed socket GEN1 at /usr/lib/perl/5.14/IO/Socket.pm line 294.
pi@raspberrypi ~/domoticz/MyDomoAtHome $ sudo service MyDomoAtHome.sh reload
[....] Reloading plack server: MyDomoAtHomestart-stop-daemon: warning: failed to kill 15042: No such process
start-stop-daemon: warning: failed to kill 15042: No such process
failed!
pi@raspberrypi ~/domoticz/MyDomoAtHome $

so this didn't work either...
Any ideas? I do get the ip:3001/devices printout (and there I can see that temp will go to "room" temp etc so that looks fine...

ps: the line: sudo service MyDomoAtHome.sh check doesn't work since I get the response what the input should be... status is apparently not a valid input...?

[SchattenMann]

Hello,

i'm trying to get domoticz and MyDomoAtHome running on an virtualbox ubuntu server.
Domoticz runs fine and returns the devices. MyDomoAtHome runs the webserver, but no devices. When i call that url i get :

Code: Select all

{"devices":[{"id":"S00","type":"DevGenericSensor","name":"Unable to connect to Domoticz","params":[{"key":"Value","unit":"","graphable":"false","value":""}]},{"id":"S01","name":"Please add this gateway in Setup/settings/Local Networks","type":"DevGenericSensor","params":[{"unit":"","graphable":"false","value":"","key":"Value"}]}]}

Added both ip's to domoticz does nothing. Same errors.

Running ./start2.sh gives me :

Code: Select all

domoticz@ubuntu:~/domoticz/MyDomoAtHome$ ./start2.sh
[sudo] password for domoticz:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
environment:development
log:error
logger:file
2015/10/09-18:01:58 Starman::Server (type Net::Server::PreFork) starting! pid(1450)
Resolved [*]:3001 to [::]:3001, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 3001 on host :: with IPv6
Setting gid to "33 33 33"
Starman: Accepting connections at http://*:3001/
Use of uninitialized value in concatenation (.) or string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 382.
Use of uninitialized value $ver in string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 851.
Use of uninitialized value $mpd_host in string ne at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 859.
Use of uninitialized value in concatenation (.) or string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 873.
Use of uninitialized value in concatenation (.) or string at /home/domoticz/domoticz/MyDomoAtHome/lib/Domo.pm line 907.
::ffff:10.50.192.154 - - [09/Oct/2015:18:02:11 +0200] "GET /devices HTTP/1.1" 200 684 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"

anyone can tell me what i'm doing wrong? Reinstalled ubuntu to check if that was the problem. Same thing for domoticz and MyDomoAtHome. Tried on my home network and work network. Same problem.

I have the exact same problem. Spent the last couple of hours trying to fix this with no success

[patricknooijen]

I think it has to do with a domoticz or mydomoathome update.

[DRuw]

it was working till I updated MyDomoAtHome so I guess thats the cause...

[SchattenMann]

it was working till I updated MyDomoAtHome so I guess thats the cause...

It would be great if we could hear something from support...

[korniza]

Well I had the same issue!
problem solved moving production.yml from subfolder enviroments to root forder of MyDomoAtHome (ex. /home/pi/domoticz/MyDomoAtHome)
it has to be change on wiki also.

[joshimosh]

I have exactly the same problem as DRuw - all f***ed up. Everything was fine until I did an update. Now I get the very same error report DRuw has given in his rather long post above.

The solution korniza proposed did not work for me.

@epierre:
Please please: provide us with a working version or a fix !

[SchattenMann]

Tried that and doesn't make any difference....can't see why production.yml should be tbh...

[korniza]

Tried that and doesn't make any difference....can't see why production.yml should be tbh...

I tried it on a linux pc and on a odroid XU system. both had the same issue. I moved production.yml and config.yml( forgot to mention that) and all worked as it should. To be more clear I had the following issue:

Code: Select all

{"devices":[{"id":"S00","type":"DevGenericSensor","name":"Unable to connect to Domoticz","params":[{"key":"Value","unit":"","graphable":"false","value":""}]},{"id":"S01","name":"Please add this gateway in Setup/settings/Local Networks","type":"DevGenericSensor","params":[{"unit":"","graphable":"false","value":"","key":"Value"}]}]}

[joshimosh]

@korniza:
I'm on a Raspberry PI 2. Moved (and entered my specific ip and port of course) config.yml and production.yml. No change, same error messages as before (as already reported in detail by DRuw above).

I guess that epierre is the only one who is able to fix it ...

Josh

[DRuw]

Yeah my post was a bit long indeed... sorry about that but I am a kinda linux noob and I did not want to forget possibly required info.

I guess epierre has a weekend as well;) hoping to hear from him monday... i the meantime... if it works.. dont update!

[Finnalist]

I am having trouble getting MyDomoAtHome to run. I am confused what to set the MyDomoAtHome.sh file parameter to.
On line 20 what is the option/parameter vale that must be set and what should it be set to? I am taking a guess here
is it --pid 10.xx.xx.xxx:8080 ?

EDIT As A side note I had this running in the past but made some network changes and forgot what was set here before.

[joshimosh]

Yeah my post was a bit long indeed... sorry about that but I am a kinda linux noob and I did not want to forget possibly required info.

I guess epierre has a weekend as well;) hoping to hear from him monday... i the meantime... if it works.. dont update!

@DRuw:
Don't get me wrong: this was not meant as criticism, just a way to point to your posting. I appreciate that you posted the full output of the error message.
That saved me to do it and it showed me that it is unlikely that it is some misconfiguration in my setup.

I also hope that we will get a fix soon.

Cheers
Josh

[epierre]

Hi All,

Well the support+dev can answer you now...

I'm sorry for the mess, I've been working hard to have some automated tests and did some corrections that would enhance support, but since sometimes things are not documented it resulted in a mess... that I hope will be fixed soon, as we are still testing it with two other people. I've also had to make an urgency migration for Domoticz because of the head it generated on a fanless unit...

First the last update should correct most, but is short terms:

- config.yml must be in MDAH root
- development.yml and production.yml must be in environments directory, they will not have to be edited in the future
- logs directory and files must be accessible and be writable by the user launching the gateway, usually www-data

So please move files in the right place and run this for the right rights:

Code: Select all

 sudo chown www-data.www-data logs
 sudo chown www-data.www-data logs/*

Moving files will not be done by the update-mdah.sh, but rights will be enforced each time now to be sure it is right.

From now on, in production we will have logs we did not have previously, thus helping usage analysis.

[joshimosh]

@epierre:
Thank you very much for the fix !
I have adjusted the access rigth for logs and logs/* as described above. To check if everything is ok, I have entered ./start2.sh. Result looked fine. Calling http://<my_ip>:3001/devices resulted in a lengthy list (xml ?) with my sensors - looked fine.
Then I did a reboot for a clean start, but starman then was not running. What did I wrong ?

May I throw in a suggestion here ? I have Domoticz and MDAH installed on a Raspi Pi 2. I write all logs to a /var/log which resides on a ramdisk to avoid wear of the SD-card. In Domoticz, the location of the log can be defined by the user. May I suggest that you add a similar feature to MDAH ? Thank you for your consideration.

Cheers
Josh

[epierre]

@epierre:
Thank you very much for the fix !
I have adjusted the access rigth for logs and logs/* as described above. To check if everything is ok, I have entered ./start2.sh. Result looked fine. Calling http://<my_ip>:3001/devices resulted in a lengthy list (xml ?) with my sensors - looked fine.
Then I did a reboot for a clean start, but starman then was not running. What did I wrong ?

You nothing, but someone else reported this issue so everything is not fixed...

can you do a :
sudo sh -x /etc/init.d/MyDomoAtHome.sh start

and give me the output ?

I'm busy tonight I won't have time to check this back home...

thanks !

May I throw in a suggestion here ? I have Domoticz and MDAH installed on a Raspi Pi 2. I write all logs to a /var/log which resides on a ramdisk to avoid wear of the SD-card. In Domoticz, the location of the log can be defined by the user. May I suggest that you add a similar feature to MDAH ?

Sure, I'll have to fix problems one at the time

[SchattenMann]

@epierre:

May I throw in a suggestion here ? I have Domoticz and MDAH installed on a Raspi Pi 2. I write all logs to a /var/log which resides on a ramdisk to avoid wear of the SD-card. In Domoticz, the location of the log can be defined by the user. May I suggest that you add a similar feature to MDAH ? Thank you for your consideration.

maybe a symlink for logs folder?

[epierre]

@epierre:

May I throw in a suggestion here ? I have Domoticz and MDAH installed on a Raspi Pi 2. I write all logs to a /var/log which resides on a ramdisk to avoid wear of the SD-card. In Domoticz, the location of the log can be defined by the user. May I suggest that you add a similar feature to MDAH ? Thank you for your consideration.

maybe a symlink for logs folder?

in the worse case (or minimalistically) yes