Can't connect to AD2USB after updating Raspberry Pi

General Discussion

Can't connect to AD2USB after updating Raspberry Pi

Postby nbrining » Fri Sep 22, 2017 7:52 pm

I am running the Alarm Decoder Webapp on an old raspberry pi with a AD2USB. I decided to update my pi using apt-get update and apt-get upgrade. After I rebooted, the webapp can no longer connect to the AD2USB. I've spent 2 hours trying to troubleshoot with no luck. Any help is appreciated. Thank you.
nbrining
newt
newt
 
Posts: 4
Joined: Fri Sep 22, 2017 7:42 pm

Re: Can't connect to AD2USB after updating Raspberry Pi

Postby kevin » Fri Sep 22, 2017 8:14 pm

Please check logs
Please check versions of required packages (nginx, gunicorn, python, etc)
kevin
Site Admin
Site Admin
 
Posts: 845
Joined: Fri Aug 16, 2013 10:10 am

Re: Can't connect to AD2USB after updating Raspberry Pi

Postby nbrining » Sat Sep 23, 2017 5:37 am

In the syslog I see a couple things that pop out to me:

Error opening pid file /var/run/ser2sock.pid
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Exceeded CRDA call max attemps. Not calling CRDA
unable to qualify my own domain name (alarmdecoder) -- using short name

Current versions are:
nginx 1.2.1
gunicorn 19.3.0
python 2.7.3
sendmail 8.14.4
libffi 3.0.10
build-essential 11.5
libssl 1.0.1
curl 7.26.0
libpcre3 1:8.31
libpcre++ 0.9.5
zlib1g 1:1.2.7
libcurl4-openssl-dev 7.26.0
minicom 2.6.1
telnet 0.17
python2.7 2.7.3
autoconf 2.69
automake 1:1.11.6
avahi-daemon 0.6.31
screen 4.1.0
locales 2.13
dosfstools 3.0.13
vim 2:7.3.547
sqlite3 3.7.13
nbrining
newt
newt
 
Posts: 4
Joined: Fri Sep 22, 2017 7:42 pm

Re: Can't connect to AD2USB after updating Raspberry Pi

Postby nbrining » Sat Sep 23, 2017 7:36 am

I have fixed the pid error and the CRDA error but still having the domain name error.
Here is the last 50 entries in syslog:
Code: Select all
Sep 23 11:22:54 alarmdecoder /usr/sbin/cron[2007]: (CRON) STARTUP (fork ok)
Sep 23 11:22:54 alarmdecoder /usr/sbin/cron[2007]: (CRON) INFO (Running @reboot jobs)
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Found user 'avahi' (UID 103) and group 'avahi' (GID 105).
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Successfully dropped root privileges.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: avahi-daemon 0.6.31 starting up.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Successfully called chroot().
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Successfully dropped remaining capabilities.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Loading service file /services/alarmdecoder.service.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Loading service file /services/udisks.service.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: socket() failed: Address family not supported by protocol
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Failed to create IPv6 socket, proceeding in IPv4 only mode
Sep 23 11:22:56 alarmdecoder kernel: [   29.545067] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: socket() failed: Address family not supported by protocol
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Network interface enumeration completed.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Registering HINFO record with values 'ARMV6L'/'LINUX'.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Server startup complete. Host name is alarmdecoder.local. Local service cookie is 1134205678.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Service "alarmdecoder" (/services/udisks.service) successfully established.
Sep 23 11:22:56 alarmdecoder avahi-daemon[2078]: Service "alarmdecoder" (/services/alarmdecoder.service) successfully established.
Sep 23 11:22:57 alarmdecoder ntpd[2121]: ntpd 4.2.6p5@1.2349-o Fri Jul 22 22:29:05 UTC 2016 (1)
Sep 23 11:22:57 alarmdecoder dhcpcd[1870]: eth0: leased 192.168.1.211 for 86400 seconds
Sep 23 11:22:57 alarmdecoder avahi-daemon[2078]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.211.
Sep 23 11:22:57 alarmdecoder avahi-daemon[2078]: New relevant interface eth0.IPv4 for mDNS.
Sep 23 11:22:57 alarmdecoder avahi-daemon[2078]: Registering new address record for 192.168.1.211 on eth0.IPv4.
Sep 23 11:22:57 alarmdecoder ntpd[2122]: proto: precision = 1.000 usec
Sep 23 11:22:57 alarmdecoder ntpd[2122]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Sep 23 11:22:57 alarmdecoder ntpd[2122]: Listen normally on 1 lo 127.0.0.1 UDP 123
Sep 23 11:22:57 alarmdecoder ntpd[2122]: Listen normally on 2 eth0 192.168.1.211 UDP 123
Sep 23 11:22:57 alarmdecoder ntpd[2122]: peers refreshed
Sep 23 11:22:57 alarmdecoder ntpd[2122]: Listening on routing socket on fd #19 for interface updates
Sep 23 11:22:57 alarmdecoder dhcpcd[1870]: eth0: adding route to 192.168.1.0/24
Sep 23 11:22:57 alarmdecoder dhcpcd[1870]: eth0: adding default route via 192.168.1.1
Sep 23 11:22:57 alarmdecoder ntpd[2122]: restrict: error in address '::' on line 38. Ignoring...
Sep 23 11:22:57 alarmdecoder ntpd[2122]: restrict: error in address '::1' on line 42. Ignoring...
Sep 23 11:22:58 alarmdecoder dhcpcd[1870]: forked to background, child pid 2190
Sep 23 11:22:59 alarmdecoder ser2sock[2213]: [✔] Using config file: /etc/ser2sock/ser2sock.conf
Sep 23 11:22:59 alarmdecoder ser2sock[2213]: [✔] Serial 2 Socket Relay version V1.5.2 starting
Sep 23 11:22:59 alarmdecoder ser2sock[2213]: [✔] Listening socket created on port 10010
Sep 23 11:22:59 alarmdecoder ser2sock[2213]: [✔] daemonizing the process
Sep 23 11:22:59 alarmdecoder ser2sock[2216]: [✔] Using PID file: /tmp/ser2sock.pid
Sep 23 11:22:59 alarmdecoder ser2sock[2216]: [✔] Seting thread priority to HIGH
Sep 23 11:22:59 alarmdecoder ser2sock[2216]: [✔] Start wait loop using raw communication mode
Sep 23 11:22:59 alarmdecoder ser2sock[2216]: [✔] Opened com port at /dev/ttyUSB0
Sep 23 11:22:59 alarmdecoder ser2sock[2216]: [✔] Setting speed 115200
Sep 23 11:22:59 alarmdecoder ser2sock[2216]: [✔] Set speed successful
Sep 23 11:23:00 alarmdecoder sm-mta[2261]: My unqualified host name (alarmdecoder) unknown; sleeping for retry
Sep 23 11:23:02 alarmdecoder sm-msp-queue[2298]: My unqualified host name (alarmdecoder) unknown; sleeping for retry
Sep 23 11:24:37 alarmdecoder sm-mta[2261]: unable to qualify my own domain name (alarmdecoder) -- using short name
Sep 23 11:24:37 alarmdecoder sm-mta[2301]: starting daemon (8.14.4): SMTP+queueing@00:10:00
Sep 23 11:24:39 alarmdecoder sm-msp-queue[2298]: unable to qualify my own domain name (alarmdecoder) -- using short name
Sep 23 11:26:45 alarmdecoder ser2sock[2216]: [✔] Socket connected slot 2
nbrining
newt
newt
 
Posts: 4
Joined: Fri Sep 22, 2017 7:42 pm

Re: Can't connect to AD2USB after updating Raspberry Pi

Postby kevin » Sat Sep 23, 2017 1:30 pm

Yes, the issue here is that the version of nginx that apt-get installed (we ship compiled from source in our image) does not support websockets.

You need to be 1.7.4 or greater - suggest removing the apt installed nginx and reinstalling nginx from source

Also recommended to be python 2.7.10 or later for proper SSL support
kevin
Site Admin
Site Admin
 
Posts: 845
Joined: Fri Aug 16, 2013 10:10 am


Return to General

Who is online

Users browsing this forum: No registered users and 2 guests

cron