openwebnet & crash domoticz every night

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.
Post Reply
raeymeister
Posts: 2
Joined: Sunday 18 February 2018 21:03
Target OS: Raspberry Pi
Domoticz version:
Contact:

openwebnet & crash domoticz every night

Post by raeymeister » Wednesday 21 February 2018 21:01

Hi,

my setup:
- raspberry pi 3
- latest domoticz beta (3.8923)
- bticino myhome (via openwebnet)

Behaviour: every night, domoticz crashes.

________________DOMOTICZ LOG_______________
018-02-20 05:34:51.766 Error: COpenWebNetTCP: Cannot connect to gateway, Unable to connect to specified IP Address on specified Port
2018-02-20 05:34:51.766 COpenWebNetTCP: disconnect
2018-02-20 05:34:51.766 Error: COpenWebNetTCP: Command session ERROR
2018-02-20 05:34:51.767 Error: COpenWebNetTCP: Cannot connect to gateway, Unable to connect to specified IP Address on specified Port
2018-02-20 05:34:51.767 Error: COpenWebNetTCP: Command session ERROR
2018-02-20 05:34:51.767 Error: COpenWebNetTCP: Cannot connect to gateway, Unable to connect to specified IP Address on specified Port
2018-02-20 05:34:51.767 Error: COpenWebNetTCP: Command session ERROR
2018-02-20 05:34:51.767 Error: COpenWebNetTCP: Cannot connect to gateway, Unable to connect to specified IP Address on specified Port
2018-02-20 05:34:51.767 Error: COpenWebNetTCP: Command session ERROR
2018-02-20 05:34:51.802 Error: COpenWebNetTCP: Cannot connect to gateway, Unable to connect to specified IP Address on specified Port
2018-02-20 05:34:51.802 Error: COpenWebNetTCP: Command session ERROR
2018-02-20 05:34:51.802 Error: COpenWebNetTCP: Cannot connect to gateway, Unable to connect to specified IP Address on specified Port
2018-02-20 05:34:51.802 Error: COpenWebNetTCP: Command session ERROR
2018-02-20 05:34:53.201 Error: Domoticz received fatal signal 11 !...
2018-02-20 05:34:53.222 Error: /home/pi/domoticz/domoticz() [0x246a90]
2018-02-20 05:34:53.223 Error: /home/pi/domoticz/domoticz(_Z14signal_handleri+0x4c) [0x246b48]
2018-02-20 05:34:53.223 Error: /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer_v2+0) [0x76c0e180]
2018-02-20 05:34:53.223 Error: /home/pi/domoticz/domoticz(_ZN14COpenWebNetTCP13MonitorFramesEv+0x13c) [0x4b744c]
2018-02-20 05:34:53.223 Error: /home/pi/domoticz/domoticz() [0x7a8d10]
________________DOMOTICZ LOG_______________

at the same time in /var/log/syslog

________________syslog_______________________
Feb 21 02:06:58 raspberrypi ntpd[835]: 85.88.55.5 interface 192.168.1.4 -> (none)
Feb 21 02:06:58 raspberrypi ntpd[835]: 195.200.224.66 interface 192.168.1.4 -> (none)
Feb 21 02:06:58 raspberrypi ntpd[835]: 193.190.147.153 interface 192.168.1.4 -> (none)
Feb 21 02:06:58 raspberrypi ntpd[835]: 193.104.37.238 interface 192.168.1.4 -> (none)
Feb 21 02:06:58 raspberrypi ntpd[835]: peers refreshed
Feb 21 02:07:04 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
Feb 21 02:07:05 raspberrypi wpa_supplicant[581]: wlan0: Trying to associate with 10:bf:48:e6:b6:06 (SSID='bladibla' freq=2442 MHz)
Feb 21 02:07:14 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
Feb 21 02:07:15 raspberrypi wpa_supplicant[581]: wlan0: Trying to associate with 10:bf:48:e6:b6:06 (SSID='bladibla' freq=2442 MHz)
Feb 21 02:07:23 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
Feb 21 02:07:23 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="bladibla" auth_failures=1 duration=10 reason=CONN_FAILED
Feb 21 02:07:43 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="bladibla"
Feb 21 02:07:43 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Wed Feb 21 02:08:43 2018 [try http://www.rsyslog.com/e/2007 ]
Feb 21 02:07:43 raspberrypi wpa_supplicant[581]: wlan0: Trying to associate with 10:bf:48:e6:b6:06 (SSID='bladibla' freq=2442 MHz)
Feb 21 02:07:46 raspberrypi wpa_supplicant[581]: wlan0: Associated with 10:bf:48:e6:b6:06
Feb 21 02:07:46 raspberrypi wpa_supplicant[581]: wlan0: WPA: Key negotiation completed with 10:bf:48:e6:b6:06 [PTK=CCMP GTK=CCMP]
Feb 21 02:07:46 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-CONNECTED - Connection to 10:bf:48:e6:b6:06 completed [id=0 id_str=]
Feb 21 02:07:46 raspberrypi dhcpcd[733]: wlan0: carrier acquired
Feb 21 02:07:46 raspberrypi dhcpcd[733]: wlan0: adding address fe80::5489:b7e4:5b8a:b7e0
Feb 21 02:07:46 raspberrypi dhcpcd[733]: wlan0: IAID eb:27:78:15
Feb 21 02:07:47 raspberrypi dhcpcd[733]: wlan0: using static address 192.168.1.4/24
Feb 21 02:07:47 raspberrypi dhcpcd[733]: wlan0: adding route to 192.168.1.0/24
Feb 21 02:07:47 raspberrypi dhcpcd[733]: wlan0: adding default route via 192.168.1.2
Feb 21 02:07:47 raspberrypi dhcpcd[733]: wlan0: received approval for 192.168.1.4
Feb 21 02:07:47 raspberrypi avahi-daemon[445]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::5489:b7e4:5b8a:b7e0.
Feb 21 02:07:47 raspberrypi avahi-daemon[445]: New relevant interface wlan0.IPv6 for mDNS.
Feb 21 02:07:47 raspberrypi avahi-daemon[445]: Registering new address record for fe80::5489:b7e4:5b8a:b7e0 on wlan0.*.
Feb 21 02:07:49 raspberrypi ntpd[835]: Listen normally on 15 wlan0 fe80::5489:b7e4:5b8a:b7e0 UDP 123
Feb 21 02:07:49 raspberrypi ntpd[835]: peers refreshed
Feb 21 02:08:03 raspberrypi dhcpcd[733]: wlan0: carrier lost
Feb 21 02:08:03 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-DISCONNECTED bssid=10:bf:48:e6:b6:06 reason=0 locally_generated=1
Feb 21 02:08:03 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb 21 02:08:03 raspberrypi wpa_supplicant[581]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Feb 21 02:08:03 raspberrypi dhcpcd[733]: wlan0: deleting address fe80::5489:b7e4:5b8a:b7e0
Feb 21 02:08:03 raspberrypi avahi-daemon[445]: Withdrawing address record for fe80::5489:b7e4:5b8a:b7e0 on wlan0.

________________syslog_______________________

I found some messages online on how raspberry pi wireless is unstable. For normal desktop-use, this is not a problem, but running a server which crashes if wireless is down is,... inconvenient.

Just wanted to share this. I will change to a wired connection to see whether the problem disappears.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 9 guests