Keypad stuck in "please wait loading" msg

[jeffwu]

Recently the keypad in WebApp kept hanging. On the screen, it displays "please wait loading".. the "ready" or "arm" icon buttons was grey too.

Physical keypad still works and the rest of config menu in WebApp also functions. My workaround was to reboot pi.

I use the out of box pi image download from your site.

What are the troubleshooting steps you'd suggest.

P.s. one recent change I made was to create custom notification for sending all zone faults to a web server with GET. When keypad hung, it stopped sending this custom notification too.

[kevin]

Rebooting fixed the issue?

Maybe the logs will show something around the time it happened.

[jeffwu]

I rebooted 3 times this week already and would like to trace the root cause.

Where the log to check? It wasn't much in access log or syslog.

[kevin]

There are several logs to check

/var/log/gunicorn.d/*.log
/opt/alarmdecoder-webapp/instance/logs/*.log
/var/log/daemon.log
/var/log/syslog

Definitely seems like something is causing the code to lock up, perhaps to do with your notification.

[jeffwu]

Hi Kevin,

the app had problems again. here were the log messages from info.log file. did they give useful info to indicate what the cause could be?




2017-10-03 23:17:22,587 INFO: AlarmDecoder Webapp booting up - v0.7.6-0-g82282c8 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:214]
2017-10-03 23:17:22,681 INFO: Discovery running: loc=10.10.0.7:5000, uuid=a2abcfa8-2623-11e7-9493-b827ebbd5cba [in /opt/alarmdecoder-webapp/ad2web/discovery.py:69]
2017-10-03 23:17:22,685 INFO: Attempting to reconnect to the AlarmDecoder [in /opt/alarmdecoder-webapp/ad2web/decoder.py:481]
2017-10-03 23:17:22,874 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:339]
2017-10-03 23:25:35,003 INFO: AlarmDecoder Webapp booting up - v0.7.6-0-g82282c8 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:214]
2017-10-03 23:25:35,096 INFO: Discovery running: loc=10.10.0.7:5000, uuid=a2abcfa8-2623-11e7-9493-b827ebbd5cba [in /opt/alarmdecoder-webapp/ad2web/discovery.py:69]
2017-10-03 23:25:35,099 INFO: Attempting to reconnect to the AlarmDecoder [in /opt/alarmdecoder-webapp/ad2web/decoder.py:481]
2017-10-03 23:25:35,288 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:339]
2017-10-03 23:33:19,887 INFO: Event: The alarm system has been armed [STAY]. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-04 00:57:35,955 INFO: Event: The alarm system has been disarmed. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-04 00:58:14,527 INFO: Event: The alarm system has been armed [STAY]. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-04 06:03:11,547 INFO: AlarmDecoder Webapp booting up - v0.7.6-0-g82282c8 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:214]
2017-10-04 06:03:18,612 INFO: Discovery running: loc=10.10.0.7:5000, uuid=a2abcfa8-2623-11e7-9493-b827ebbd5cba [in /opt/alarmdecoder-webapp/ad2web/discovery.py:69]
2017-10-04 06:03:18,615 INFO: Attempting to reconnect to the AlarmDecoder [in /opt/alarmdecoder-webapp/ad2web/decoder.py:481]
2017-10-04 06:03:18,813 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:339]
2017-10-04 06:06:22,346 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:08:05,215 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:09:48,094 ERROR: Error sending notification for motion: [Errno
104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:11:30,979 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:13:19,040 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:15:06,976 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:16:54,975 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:18:42,975 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:20:25,855 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:20:27,284 INFO: Event: The alarm system has been disarmed. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-04 06:22:10,018 ERROR: Error sending notification for motion: [Errno 104] Connection reset by peer [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 06:48:14,682 INFO: AlarmDecoder device was closed. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:351]
2017-10-04 06:48:14,706 INFO: Attempting to reconnect to the AlarmDecoder [in /opt/alarmdecoder-webapp/ad2web/decoder.py:481]
2017-10-04 06:48:14,850 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:339]
2017-10-04 17:30:01,459 ERROR: Error sending notification for motion: '' [in /opt/alarmdecoder-webapp/ad2web/decoder.py:399]
2017-10-04 22:59:51,296 INFO: Event: The alarm system has been armed [STAY]. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-04 23:20:51,865 INFO: Event: The alarm system has been disarmed. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-04 23:42:53,840 INFO: Event: The alarm system has been armed [STAY]. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-05 06:03:02,659 INFO: Event: The alarm system has been disarmed. [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:275]
2017-10-05 15:17:23,776 INFO: AlarmDecoder Webapp booting up - v0.7.6-0-g82282c8 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:214]
2017-10-05 15:17:23,866 ERROR: Error [in /opt/alarmdecoder-webapp/ad2web/app.py:175]
Traceback (most recent call last):
File "/opt/alarmdecoder-webapp/ad2web/app.py", line 168, in init_app
app.decoder.init()
File "/opt/alarmdecoder-webapp/ad2web/decoder.py", line 234, in init
self._discovery_thread = DiscoveryServer(self)
File "/opt/alarmdecoder-webapp/ad2web/discovery.py", line 59, in __init__
sock.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, mreq)
File "<string>", line 1, in setsockopt
error: [Errno 19] No such device

[kevin]

It would appear that it is not detecting your alarmdecoder device once in a while - do you have power issues? which device do you have? Ad2pi? Ad2usb?

[jeffwu]

it is AP2PI. the pi was running at that time so the pwr was on. I issued "sudo reboot" in cmd line, Pi came back up and the web app functioned again. this has been going on for a few days.

[kevin]

Looking at it closer, it appears the discovery thread is dying for some reason - maybe a problem with ethernet? The

Code: Select all

File "/opt/alarmdecoder-webapp/ad2web/discovery.py", line 59, in __init__
sock.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, mreq)
File "<string>", line 1, in setsockopt
error: [Errno 19] No such device


is suspect

[jeffwu]

There was a short power outage in the morning around 08:13 AM. AD2PI booted up after the power came back on. however, the web app was stuck in "please wait loading" error again. after checking info.log and syslog, it appeared Webapp booting up with "no such device" error.

I hope webapp could have recovered automatically after a success pi reboot. any suggestion?

Jeff



1) web-app info.log
pi@alarmdecoder:~ $ cat /opt/alarmdecoder-webapp/instance/logs/info.log
2017-10-16 08:17:23,504 INFO: AlarmDecoder Webapp booting up - v0.7.6-0-g82282c8 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:214]
2017-10-16 08:17:23,590 ERROR: Error [in /opt/alarmdecoder-webapp/ad2web/app.py:175]
Traceback (most recent call last):
File "/opt/alarmdecoder-webapp/ad2web/app.py", line 168, in init_app
app.decoder.init()
File "/opt/alarmdecoder-webapp/ad2web/decoder.py", line 234, in init
self._discovery_thread = DiscoveryServer(self)
File "/opt/alarmdecoder-webapp/ad2web/discovery.py", line 59, in __init__
sock.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, mreq)
File "<string>", line 1, in setsockopt
error: [Errno 19] No such device


2) sys.log after boot up. the Pi got eth connection before web-app booting up.

Oct 16 08:17:05 alarmdecoder dhcpcd[387]: DUID 00:01:00:01:1e:7e:76:00:b8:27:eb:
87:c6:80
Oct 16 08:17:05 alarmdecoder dhcpcd[387]: eth0: IAID eb:bd:5c:ba
Oct 16 08:17:05 alarmdecoder avahi-daemon[397]: Service "alarmdecoder" (/service
s/alarmdecoder.service) successfully established.
Oct 16 08:17:05 alarmdecoder dhcpcd[387]: eth0: rebinding lease of 10.10.0.7
Oct 16 08:17:05 alarmdecoder dhcpcd[387]: eth0: soliciting an IPv6 router

[kevin]

Make sure your ad2usb/ad2pi/ad2serial is not malfunctioning.

If it is an ad2usb, hook it up to a PC and see if symptoms persist while running keypad software.

If ad2pi, stop webapp, stop ser2sock, and attach to the pi with a serial program of your choice - see if the device goes away ever.