How to check health status of Domoticz processes (e.g. webserver) after problem

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post

Please mark your topic as Solved when the problem is solved.
Post Reply
ArnoutZ
Posts: 16
Joined: Monday 30 November 2015 18:39
Target OS: Raspberry Pi
Domoticz version:
Contact:

How to check health status of Domoticz processes (e.g. webserver) after problem

Post by ArnoutZ » Friday 17 August 2018 15:52

Version: 4.9700
Platform: Raspberry Pi 3B with Raspbian Stretch
Plugin/Hardware: Original Power Supply, RFXCOM-E USB and Aeon Labs Aeotec Gen 5 Z-Wave USB Interface.
Description:

I was on vacation for the last week and after three days on my destination I suddenly was not able to get remote access to Domoticz anymore.
I also use the Pilot App on my phone which could also not get in touch with my Pi running Domoticz.
By using the IP camera software I could see that all scripts and timers were and are still running.

This is not the first time that I after a few days of remote access, it suddenly is not possible anymore to access Domoticz.
I have returned home now and I am sure that after a reboot everything is fine, but before doing that I would like to know the cause.
At this moment I cannot access the webinterface, but the system is running as timers and scripts execute normally.

As I can use Putty, can anyone point out which checks I can do on my Domoticz configuration to see the health of the different processes?
I am not a Raspbian expert so I would appreciate some command hints to see what went wrong.
Last edited by ArnoutZ on Friday 17 August 2018 21:33, edited 2 times in total.

SweetPants
Posts: 2255
Joined: Friday 12 July 2013 21:24
Target OS: Linux
Domoticz version: V4.10007
Location: The Netherlands
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by SweetPants » Friday 17 August 2018 17:47

First of all, did you follow the RED forum rules? You have to supply more information, it is a wild guess now.
There is only one process that is called domoticz. Search the forum for how to (re)start it if it fails.
Ubuntu 16.04.3 LTS, Intel NUC, MySensors 2.3.0-alpha, Pro Mini 3.3/8M RFM69(HW), ESP8266 (SDK2.2.0), Sonoff, RFLink, RFXcom, MQTT, NodeRed, Domoticz Beta (from source)

ArnoutZ
Posts: 16
Joined: Monday 30 November 2015 18:39
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by ArnoutZ » Friday 17 August 2018 21:33

Extended the original question with the required hardware and OS info.

ArnoutZ
Posts: 16
Joined: Monday 30 November 2015 18:39
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by ArnoutZ » Saturday 18 August 2018 11:44

If I do a sudo netstat -an I get the following:

Code: Select all

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0    192 192.168.2.98:22         192.168.2.31:50060      ESTABLISHED
tcp6     129      0 :::8080                 :::*                    LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 :::443                  :::*                    LISTEN
tcp6       0      0 :::6144                 :::*                    LISTEN
tcp6     544      0 192.168.2.98:8080       84.28.6.30:61268        CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       223.72.60.230:2074      CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       109.94.227.162:32822    CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       181.124.114.235:59345   CLOSE_WAIT
tcp6      39      0 192.168.2.98:8080       74.82.47.5:62104        CLOSE_WAIT
tcp6     534      0 192.168.2.98:8080       84.28.6.30:55994        CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       187.57.92.132:42019     CLOSE_WAIT
tcp6      27      0 192.168.2.98:8080       175.42.0.68:36490       CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       45.237.156.11:55966     CLOSE_WAIT
tcp6      92      0 192.168.2.98:8080       175.42.0.68:35930       ESTABLISHED
tcp6     187      0 192.168.2.98:8080       180.150.93.230:52172    CLOSE_WAIT
tcp6     434      0 192.168.2.98:8080       84.28.6.30:61259        CLOSE_WAIT
tcp6     544      0 192.168.2.98:8080       84.28.6.30:61264        CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       189.69.13.122:48302     CLOSE_WAIT
tcp6     535      0 192.168.2.98:8080       84.28.6.30:56040        CLOSE_WAIT
tcp6     534      0 192.168.2.98:8080       84.28.6.30:56012        CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       80.248.71.12:34346      CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       177.188.229.125:49797   CLOSE_WAIT
tcp6     535      0 192.168.2.98:8080       84.28.6.30:57394        CLOSE_WAIT
tcp6      89      0 192.168.2.98:8080       175.42.0.68:41854       CLOSE_WAIT
tcp6     536      0 192.168.2.98:8080       84.28.6.30:56041        CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       200.120.133.85:51451    CLOSE_WAIT
tcp6     545      0 192.168.2.98:8080       84.28.6.30:61265        CLOSE_WAIT
tcp6     536      0 192.168.2.98:8080       84.28.6.30:55996        CLOSE_WAIT
tcp6      10      0 192.168.2.98:8080       5.188.210.12:25121      CLOSE_WAIT
tcp6      81      0 192.168.2.98:8080       175.42.0.68:56900       CLOSE_WAIT
tcp6       4      0 192.168.2.98:8080       5.188.210.12:38305      CLOSE_WAIT
tcp6     425      0 192.168.2.98:8080       84.28.6.30:57392        CLOSE_WAIT
tcp6     542      0 192.168.2.98:8080       84.28.6.30:61266        CLOSE_WAIT
tcp6     425      0 192.168.2.98:8080       84.28.6.30:55991        CLOSE_WAIT
tcp6      39      0 192.168.2.98:8080       184.105.247.252:43310   CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       81.183.210.192:44740    CLOSE_WAIT
tcp6     545      0 192.168.2.98:8080       31.161.157.238:48596    CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       86.100.76.139:58288     CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       177.103.42.182:53512    CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       201.105.110.235:48103   CLOSE_WAIT
tcp6      50      0 192.168.2.98:8080       101.201.227.46:56314    CLOSE_WAIT
tcp6       4      0 192.168.2.98:8080       5.188.210.12:52633      CLOSE_WAIT
tcp6     278      0 192.168.2.98:8080       5.188.210.12:21141      CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       190.110.217.70:53855    CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       138.118.103.3:44456     CLOSE_WAIT
tcp6     278      0 192.168.2.98:8080       5.188.210.12:54444      CLOSE_WAIT
tcp6      10      0 192.168.2.98:8080       5.188.210.12:55897      CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       187.56.167.11:58692     CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       152.231.58.127:52193    CLOSE_WAIT
tcp6     544      0 192.168.2.98:8080       31.161.157.238:48504    CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       5.226.50.9:41072        CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       164.77.220.50:33209     CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       91.207.185.90:55642     CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       81.215.8.228:59322      CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       200.187.87.155:57386    CLOSE_WAIT
tcp6      10      0 192.168.2.98:8080       5.188.210.12:42712      CLOSE_WAIT
tcp6     533      0 192.168.2.98:8080       84.28.6.30:56042        CLOSE_WAIT
tcp6     545      0 192.168.2.98:8080       84.28.6.30:61269        CLOSE_WAIT
tcp6     425      0 192.168.2.98:8080       84.28.6.30:56008        CLOSE_WAIT
tcp6     536      0 192.168.2.98:8080       84.28.6.30:57395        CLOSE_WAIT
tcp6       1      0 192.168.2.98:8080       175.42.0.68:36046       CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       114.141.94.131:56058    CLOSE_WAIT
tcp6     543      0 192.168.2.98:8080       84.28.6.30:61262        CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       201.13.84.231:56496     CLOSE_WAIT
tcp6       4      0 192.168.2.98:8080       5.188.210.12:19058      CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       191.17.212.234:53576    CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       103.79.228.228:58715    CLOSE_WAIT
tcp6     535      0 192.168.2.98:8080       84.28.6.30:55995        CLOSE_WAIT
tcp6     534      0 192.168.2.98:8080       84.28.6.30:57393        CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       201.27.239.112:47258    CLOSE_WAIT
tcp6     209      0 192.168.2.98:8080       191.100.11.7:57800      CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       190.110.208.150:45613   CLOSE_WAIT
tcp6     186      0 192.168.2.98:8080       212.66.122.33:57216     CLOSE_WAIT
tcp6     533      0 192.168.2.98:8080       84.28.6.30:55997        CLOSE_WAIT
tcp6     177      0 192.168.2.98:8080       60.191.38.77:22432      CLOSE_WAIT
tcp6     241      0 192.168.2.98:8080       81.17.25.29:46280       CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       168.194.242.16:36700    CLOSE_WAIT
tcp6      82      0 192.168.2.98:8080       121.116.26.120:58809    CLOSE_WAIT
tcp6      44      0 192.168.2.98:8080       45.246.28.162:45106     CLOSE_WAIT
tcp6      71      0 192.168.2.98:8080       175.42.0.68:46626       CLOSE_WAIT
tcp6      82      0 192.168.2.98:8080       121.116.26.120:58706    CLOSE_WAIT
tcp6     533      0 192.168.2.98:8080       84.28.6.30:57397        CLOSE_WAIT
tcp6     215      0 192.168.2.98:8080       162.221.185.58:50067    CLOSE_WAIT
tcp6     193      0 192.168.2.98:8080       191.242.171.65:37572    CLOSE_WAIT
tcp6      81      0 192.168.2.98:8080       175.42.0.68:50938       CLOSE_WAIT
tcp6     278      0 192.168.2.98:8080       5.188.210.12:45104      CLOSE_WAIT
tcp6     187      0 192.168.2.98:8080       188.253.43.179:51509    CLOSE_WAIT
tcp6     535      0 192.168.2.98:8080       84.28.6.30:55999        CLOSE_WAIT
udp        0      0 0.0.0.0:39313           0.0.0.0:*
udp        0      0 0.0.0.0:68              0.0.0.0:*
udp        0      0 0.0.0.0:5353            0.0.0.0:*
udp6       0      0 :::35847                :::*
udp6       0      0 :::546                  :::*
udp6       0      0 :::5353                 :::*
raw6       0      0 :::58                   :::*                    7
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  3      [ ]         DGRAM                    7434     /run/systemd/notify
unix  2      [ ]         DGRAM                    7436     /run/systemd/cgroups-                                agent
unix  2      [ ACC ]     STREAM     LISTENING     7440     /run/systemd/private
unix  2      [ ACC ]     SEQPACKET  LISTENING     7453     /run/udev/control
unix  2      [ ]         DGRAM                    7456     /run/systemd/journal/                                syslog
unix  2      [ ACC ]     STREAM     LISTENING     1835     /run/systemd/fsck.pro                                gress
unix  10     [ ]         DGRAM                    7468     /run/systemd/journal/                                dev-log
unix  2      [ ACC ]     STREAM     LISTENING     7471     /run/systemd/journal/                                stdout
unix  7      [ ]         DGRAM                    7473     /run/systemd/journal/                                socket
unix  2      [ ACC ]     STREAM     LISTENING     9020     /run/thd.socket
unix  2      [ ACC ]     STREAM     LISTENING     12349    /var/run/dhcpcd.sock
unix  2      [ ACC ]     STREAM     LISTENING     12351    /var/run/dhcpcd.unpri                                v.sock
unix  2      [ ACC ]     STREAM     LISTENING     9024     /var/run/avahi-daemon                                /socket
unix  2      [ ACC ]     STREAM     LISTENING     9027     /var/run/dbus/system_                                bus_socket
unix  2      [ ]         DGRAM                    140386   /run/user/1000/system                                d/notify
unix  2      [ ACC ]     STREAM     LISTENING     140390   /run/user/1000/system                                d/private
unix  2      [ ACC ]     STREAM     LISTENING     140395   /run/user/1000/gnupg/                                S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     140398   /run/user/1000/gnupg/                                S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     140400   /run/user/1000/gnupg/                                S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     140402   /run/user/1000/gnupg/                                S.gpg-agent
unix  2      [ ]         DGRAM                    11483    /var/run/wpa_supplica                                nt/wlan0
unix  2      [ ]         DGRAM                    11488    /var/run/wpa_supplica                                nt/p2p-dev-wlan0
unix  3      [ ]         DGRAM                    10094
unix  2      [ ]         DGRAM                    12354
unix  3      [ ]         STREAM     CONNECTED     12387
unix  3      [ ]         STREAM     CONNECTED     12388
unix  2      [ ]         DGRAM                    12393
unix  3      [ ]         DGRAM                    10095
unix  2      [ ]         DGRAM                    1937
unix  3      [ ]         DGRAM                    10093
unix  2      [ ]         DGRAM                    138901
unix  2      [ ]         DGRAM                    10087
unix  3      [ ]         STREAM     CONNECTED     10387    /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     8080     /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     12330
unix  3      [ ]         STREAM     CONNECTED     10146
unix  2      [ ]         STREAM     CONNECTED     138898
unix  2      [ ]         DGRAM                    12569
unix  3      [ ]         STREAM     CONNECTED     12566
unix  3      [ ]         DGRAM                    10096
unix  3      [ ]         STREAM     CONNECTED     13337    /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     139706   /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     12390    /var/run/dbus/system_                                bus_socket
unix  3      [ ]         STREAM     CONNECTED     10532    /var/run/dbus/system_                                bus_socket
unix  3      [ ]         STREAM     CONNECTED     140367
unix  3      [ ]         STREAM     CONNECTED     10422
unix  3      [ ]         STREAM     CONNECTED     12391    /var/run/dbus/system_                                bus_socket
unix  2      [ ]         DGRAM                    10412
unix  3      [ ]         STREAM     CONNECTED     12389    /var/run/dbus/system_                                bus_socket
unix  3      [ ]         STREAM     CONNECTED     10395
unix  3      [ ]         STREAM     CONNECTED     10416
unix  3      [ ]         STREAM     CONNECTED     10336
unix  3      [ ]         DGRAM                    140389
unix  2      [ ]         DGRAM                    10329
unix  3      [ ]         DGRAM                    140388
unix  2      [ ]         DGRAM                    140374
unix  2      [ ]         DGRAM                    140371
unix  3      [ ]         STREAM     CONNECTED     10281
unix  3      [ ]         STREAM     CONNECTED     8082     /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     10415
unix  3      [ ]         STREAM     CONNECTED     10531
unix  2      [ ]         DGRAM                    11416
unix  3      [ ]         STREAM     CONNECTED     8977
unix  3      [ ]         DGRAM                    7439
unix  3      [ ]         DGRAM                    7438
unix  3      [ ]         STREAM     CONNECTED     141356
unix  3      [ ]         STREAM     CONNECTED     334      /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     10079    /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     10393    /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     141355
unix  2      [ ]         DGRAM                    7669
unix  3      [ ]         STREAM     CONNECTED     10934
unix  3      [ ]         STREAM     CONNECTED     13496    /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     9186
unix  3      [ ]         STREAM     CONNECTED     10391    /run/systemd/journal/                                stdout
unix  3      [ ]         STREAM     CONNECTED     9093
unix  2      [ ]         DGRAM                    139703
unix  2      [ ]         DGRAM                    7555
unix  3      [ ]         DGRAM                    7725
unix  2      [ ]         DGRAM                    10938
unix  3      [ ]         DGRAM                    7724
unix  3      [ ]         STREAM     CONNECTED     7667
I see 83 connections on "CLOSE_WAIT". Is that normal? Are there too many sessions and is that why I run out of something?

Neuvidor2307
Posts: 7
Joined: Wednesday 07 March 2018 23:41
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Neuvidor2307 » Saturday 18 August 2018 14:09

Dear ArnoutZ,

Maybe we have the same issue : Webserver and Android App are not working even if domoticz.sh service is running properly
I have opened a specific topic on this issue.

Version: 4.9700
Platform: RASPBIAN STRETCH LITE June 2018
Plugin/Hardware: Raspberry pi 3 model B
Description: Domoticz server not available by Webserver (Domoticz Offline message) and Android App (empty box)

I checked the domoticz status by SSH and I always get "Domoticz is Running..."

Code: Select all

pi@raspberrypi:~ $ sudo service domoticz.sh status
● domoticz.service - LSB: Home Automation System
   Loaded: loaded (/etc/init.d/domoticz.sh; generated; vendor preset: enabled)
   Active: active (exited) since Sat 2018-08-18 08:17:11 CEST; 4h 38min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 570 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/domoticz.service
août 18 08:17:10 raspberrypi systemd[1]: Starting LSB: Home Automation System...
août 18 08:17:11 raspberrypi domoticz.sh[570]: 2018-08-18 08:17:11.281  Status: Domoticz V4.9700 (c)2012-2018 GizMoCuz
août 18 08:17:11 raspberrypi domoticz.sh[570]: 2018-08-18 08:17:11.290  Status: Build Hash: a3a45906, Date: 2018-06-23 16:24:51
août 18 08:17:11 raspberrypi domoticz.sh[570]: 2018-08-18 08:17:11.297  Status: Startup Path: /home/pi/domoticz/
août 18 08:17:11 raspberrypi domoticz.sh[570]: domoticz: Domoticz is starting up....
août 18 08:17:11 raspberrypi domoticz[586]: Domoticz is starting up....
août 18 08:17:11 raspberrypi domoticz[590]: Domoticz running...
août 18 08:17:11 raspberrypi systemd[1]: Started LSB: Home Automation System.
If I simply restart the domoticz service, everything works again (webserver + Android App).

Code: Select all

pi@raspberrypi:~ $ sudo service domoticz.sh stop
pi@raspberrypi:~ $ sudo service domoticz.sh start
pi@raspberrypi:~ $ sudo service domoticz.sh status
● domoticz.service - LSB: Home Automation System
   Loaded: loaded (/etc/init.d/domoticz.sh; generated; vendor preset: enabled)
   Active: active (running) since Sat 2018-08-18 12:56:38 CEST; 6s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5486 ExecStop=/etc/init.d/domoticz.sh stop (code=exited, status=0/SUCCESS)
  Process: 5527 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/domoticz.service
           └─5534 /home/pi/domoticz/domoticz -daemon -www 8080 -sslwww 443
août 18 12:56:38 raspberrypi systemd[1]: Starting LSB: Home Automation System...
août 18 12:56:38 raspberrypi domoticz.sh[5527]: 2018-08-18 12:56:38.324  Status: Domoticz V4.9700 (c)2012-2018 GizMoCuz
août 18 12:56:38 raspberrypi domoticz.sh[5527]: 2018-08-18 12:56:38.324  Status: Build Hash: a3a45906, Date: 2018-06-23 16:24:51
août 18 12:56:38 raspberrypi domoticz.sh[5527]: 2018-08-18 12:56:38.324  Status: Startup Path: /home/pi/domoticz/
août 18 12:56:38 raspberrypi domoticz.sh[5527]: domoticz: Domoticz is starting up....
août 18 12:56:38 raspberrypi domoticz[5534]: Domoticz running...
août 18 12:56:38 raspberrypi systemd[1]: Started LSB: Home Automation System.
I have changed the SD-card by a new one (Sandisk 16Gb Ultra), completly new RASPBIAN STRETCH LITE and Domoticz v4.9700 installation but I get the same behavior.

Do you have any idea about this issue ?

Because the raspberry is located into my mother house, the best way is to solve the issue by SSH.

ArnoutZ
Posts: 16
Joined: Monday 30 November 2015 18:39
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by ArnoutZ » Saturday 18 August 2018 23:23

Yes, it seems that it is the same problem.
Neuvidor2307 wrote:
Saturday 18 August 2018 14:09
Because the raspberry is located into my mother house, the best way is to solve the issue by SSH.
So you also forwarded the port (22?) in your router so you can use Putty to restart the service?

Richard
Posts: 5
Joined: Friday 18 September 2015 22:06
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Richard » Sunday 19 August 2018 14:18

Hi, ArnoutZ,

I have also experienced the same problems recently. I've tried everything, reset modem, restored older image, performed new installation etc. Domoticz works every time after startup, but after a short period the website is no longer accessible. I have no idea what the reason could be. The solutions mentioned on the forum have not yet led to a working solution. I don' t understand why it does not work anymore.

Anyone have an idea?

Version: 4.9700
Platform: Raspberry Pi 3B with Raspbian Stretch version 9
Plugin/Hardware: RFXCOM-E.

Neuvidor2307
Posts: 7
Joined: Wednesday 07 March 2018 23:41
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Neuvidor2307 » Sunday 19 August 2018 17:13

ArnoutZ wrote:
Saturday 18 August 2018 23:23
So you also forwarded the port (22?) in your router so you can use Putty to restart the service?
Yes I'm using a DDNS from www.noip.com and I have forwarded the raspberry port 22 in my mother's livebox (NAT/PAT rules).
This configuration allow me to have a permanent Putty connexion from my house.

We are now 3 persons who have the same domoticz v4.9700 behavior even if it's the stable version.
From my side, I totally use the same hardware at home and it works perfectly. Strange !!!

Is anyone have found a solution to our issue ?

edwin1234
Posts: 108
Joined: Sunday 09 October 2016 20:20
Target OS: Windows
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by edwin1234 » Monday 20 August 2018 15:29

I have problems also,
I have a ethernet cable connected the pi and my ssh connection also failes and then i cant open domoticz either
When i disconnect the power from the pi i can connect with ssh an domoticz for a while and then suddenly it stops again, tried it for 5 times and behaviour is the same.
Someone knows a solution or where to look for?
Thanks

User avatar
Derik
Posts: 2150
Joined: Friday 18 October 2013 23:33
Target OS: Raspberry Pi
Domoticz version: BETA
Location: Arnhem/Nijmegen Nederland
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Derik » Monday 20 August 2018 23:28

When u see this:

Code: Select all

Active: active (exited)
Login with winscp
Remove the plugins u use[ in the plugin section ]
restart
En then ?
Xu4: Beta Extreme antenna RFXcomE,WU Fi Ping ip P1 Gen5 PVOutput Harmony HUE SolarmanPv OTG Winddelen Alive ESP Buienradar MySensors WOL Winddelen counting RPi: Beta SMAspot RFlinkTest Domoticz ...Different backups

Neuvidor2307
Posts: 7
Joined: Wednesday 07 March 2018 23:41
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Neuvidor2307 » Monday 20 August 2018 23:29

edwin1234 wrote:
Monday 20 August 2018 15:29
I have problems also,
I have a ethernet cable connected the pi and my ssh connection also failes and then i cant open domoticz either
When i disconnect the power from the pi i can connect with ssh an domoticz for a while and then suddenly it stops again, tried it for 5 times and behaviour is the same.
Someone knows a solution or where to look for?
Thanks
Dear,

I think that your raspberry behavior is different than us, we only have a webserver issue, not SSH.
Unfortunalety I can't help you regarding this issue. I advise you to open a specific topic if you don't find an existing.

digdilem
Posts: 10
Joined: Sunday 14 January 2018 15:31
Target OS: Linux
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by digdilem » Tuesday 21 August 2018 6:44

There's online web checkers that can check a site for you - uptimerobot.com is one I use (free for personal)

It'll email you when it can't load a page. It won't need login information since it's just checking that a 200 code is returned from a web request and that *something* is responding to web requests.

User avatar
Egregius
Posts: 2715
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: Beta
Location: Beitem, BE
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Egregius » Tuesday 21 August 2018 7:40

For the lose of network connection you could try this script, execute it every minute by cron. Change the ip address to ping to the one of your gateway and change wlan0 to probably eth0 for wired connection.

If three pings to the gateway fails the network interface if brought down and then back up.
You can safely remove the telegram line.

Code: Select all

#!/bin/bash
sudo ping -c1 192.168.2.254 > /dev/null
if [ $? != 0 ]
then
	sleep 2
	sudo ping -c1 192.168.2.254 > /dev/null
	if [ $? != 0 ]
	then
		sleep 2
		sudo ping -c1 192.168.2.254 > /dev/null
		if [ $? != 0 ]
		then
			echo "No network connection, restarting wlan0"
			sudo /sbin/ifdown 'wlan0'
			sleep 2
			sudo /sbin/ifup --force 'wlan0'
			sleep 2
			curl -s --data-urlencode "text=PiCam1 WIFI Restored" --data "silent=true" http://192.168.2.203/secure/telegram.php
		fi
	fi
fi

edwin1234
Posts: 108
Joined: Sunday 09 October 2016 20:20
Target OS: Windows
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by edwin1234 » Tuesday 21 August 2018 9:11

Thx i will try that

ArnoutZ
Posts: 16
Joined: Monday 30 November 2015 18:39
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by ArnoutZ » Thursday 23 August 2018 19:12

Thank you for the script. Seems like a good solution. Will try it out as soon as I know how to use scripts in Domoticz. (I currently only use blocky)

User avatar
Egregius
Posts: 2715
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: Beta
Location: Beitem, BE
Contact:

Re: How to check health status of Domoticz processes (e.g. webserver) after problem

Post by Egregius » Thursday 23 August 2018 19:22

It's a bash script that you have to execute from cron.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest