BBGW crash

Hi!

I have some Beaglebone running my python script for controlling relays and read sensors. But time to time some beaglebone freeze and I don’t know why.

Here is the log when the beaglebone crash. I think maybe it’s a power problem when the wifi chip try to connect.

For power up the HW I use a Menwell powersupply and two solder wires to the BBGW pinheader (vdd_5v and gnd)

HW: Beaglebone Green Wireless

Kernel: Linux beaglebone 4.4.9-ti-r25

`

Jun 24 21:46:02 beaglebone CRON[3370]: (CRON) info (No MTA installed, discarding output)
Jun 24 21:48:02 beaglebone rsyslogd-2007: action ‘action 17’ suspended, next retry is Sat Jun 24 21:49:32 2017 [try http://www.rsyslog.com/e/2007 ]
Jun 24 21:48:02 beaglebone CRON[3395]: (root) CMD (/root/cloudponics/ota_client.sh)
Jun 24 21:48:03 beaglebone CRON[3394]: (CRON) info (No MTA installed, discarding output)
Jun 24 21:50:01 beaglebone rsyslogd-2007: action ‘action 17’ suspended, next retry is Sat Jun 24 21:51:31 2017 [try http://www.rsyslog.com/e/2007 ]
Jun 24 21:50:01 beaglebone CRON[3420]: (root) CMD (/root/cloudponics/ota_client.sh)
Jun 24 21:50:03 beaglebone CRON[3419]: (CRON) info (No MTA installed, discarding output)
Jun 24 21:50:57 beaglebone rsyslogd: [origin software=“rsyslogd” swVersion=“8.4.2” x-pid=“402” x-info=“http://www.rsyslog.com”] start
Jun 24 21:50:57 beaglebone hdparm[221]: Setting parameters of disc: (none).
Jun 24 21:50:57 beaglebone networking[213]: Configuring network interfaces…done.
Jun 24 21:50:57 beaglebone alsactl[290]: /usr/sbin/alsactl: load_state:1729: No soundcards found…
Jun 24 21:50:57 beaglebone sh[299]: generic-board-startup: [model=TI_AM335x_BeagleBone_Green_Wireless]
Jun 24 21:50:57 beaglebone sh[299]: generic-board-startup: [startup script=/opt/scripts/boot/am335x_evm.sh]
Jun 24 21:50:57 beaglebone cron[324]: (CRON) INFO (pidfile fd = 3)
Jun 24 21:50:57 beaglebone wifidog_server[320]: [6][Sat Jun 24 21:50:56 2017]326 Reading configuration file ‘/etc/wifidog.conf’
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[311]: OpenVPN 2.3.4 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Nov 19 2015
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[311]: library versions: OpenSSL 1.0.1t 3 May 2016, LZO 2.08
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[311]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Jun 24 21:50:57 beaglebone cron[324]: (CRON) INFO (Running @reboot jobs)
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[311]: Socket Buffers: R=[163840->131072] S=[163840->131072]
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[341]: UDPv4 link local: [undef]
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[341]: UDPv4 link remote: [AF_INET]45.79.95.68:1194
Jun 24 21:50:57 beaglebone ovpn-2cf7f1061a1c[341]: write UDPv4: Network is unreachable (code=101)
Jun 24 21:50:57 beaglebone wifidog_server[320]: [6][Sat Jun 24 21:50:56 2017]326 Setting started_time
Jun 24 21:50:57 beaglebone wifidog_server[320]: [3][Sat Jun 24 21:50:56 2017]326 get_iface_mac ioctl(SIOCGIFHWADDR): No such device
Jun 24 21:50:57 beaglebone wifidog_server[320]: [3][Sat Jun 24 21:50:56 2017]326 Could not get MAC address information of SoftAp0, exiting…
Jun 24 21:50:57 beaglebone udhcpd[346]: udhcpd: Disabled. Edit /etc/default/udhcpd to enable it.
Jun 24 21:50:57 beaglebone dnsmasq[336]: dnsmasq: syntax check OK.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Found user ‘avahi’ (UID 105) and group ‘avahi’ (GID 114).
Jun 24 21:50:57 beaglebone wifidog_pre[294]: command failed: No such file or directory (-2)
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Successfully dropped root privileges.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: avahi-daemon 0.6.31 starting up.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Successfully called chroot().
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Successfully dropped remaining capabilities.
Jun 24 21:50:57 beaglebone avahi-daemon[374]: chroot.c: open() failed: No such file or directory
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Failed to open /etc/resolv.conf: Invalid argument
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Loading service file /services/bone101.service.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Loading service file /services/cloud9.service.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Loading service file /services/node-red.service.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Network interface enumeration completed.
Jun 24 21:50:57 beaglebone dbus[359]: [system] Successfully activated service ‘org.freedesktop.systemd1’
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Registering HINFO record with values ‘ARMV7L’/‘LINUX’.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Server startup complete. Host name is beaglebone.local. Local service cookie is 2490854071.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Service “Node-RED for beaglebone” (/services/node-red.service) successfully established.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Service “Cloud9 IDE for beaglebone” (/services/cloud9.service) successfully established.
Jun 24 21:50:57 beaglebone avahi-daemon[352]: Service “BeagleBone 101 Getting Started for beaglebone” (/services/bone101.service) successfully established.
Jun 24 21:50:57 beaglebone bb-wl18xx-wlan0[316]: wlan_0_mac=[2C:F7:F1:06:1A:1C]
Jun 24 21:50:57 beaglebone systemd[1]: wifidog-pre-startup.service: main process exited, code=exited, status=254/n/a
Jun 24 21:50:57 beaglebone systemd[1]: Unit wifidog-pre-startup.service entered failed state.
Jun 24 21:50:57 beaglebone systemd[1]: wifidog-gateway.service: main process exited, code=exited, status=1/FAILURE
Jun 24 21:50:57 beaglebone systemd[1]: Unit wifidog-gateway.service entered failed state.
Jun 24 21:50:57 beaglebone kernel: [ 0.000000] Booting Linux on physical CPU 0x****0
Jun 24 21:50:57 beaglebone kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jun 24 21:50:57 beaglebone kernel: [ 0.000000] Initializing cgroup subsys cpu
Jun 24 21:50:57 beaglebone kernel: [ 0.000000] Initializing cgroup subsys cpuacct

`

Here is one thing to try:

journalctl -u wifidog-gateway

I hope maybe the above will yield a clue as to the specific failure. Good luck.

Greg

Thanks Greg

this command only show me today’s logs, and this happened 4 days ago

It looks possible to make the log persist:

https://manpages.debian.org/jessie/systemd/systemd-journald.service.8.en.html

"r25" is known broken Kernel on the BeagleBone Green Wireless.

It took awhile, but we didn't figure out till mid Oct 2016, that one
of the pin's on the wl1835 module needs to be pulled low on startup.
Otherwise the wl1835 is actually entering a test mode on startup, thus
ending up completely un-usable..

The fix was first pushed on Oct 20, 2016 with "4.4.24-ti-r58"

So either, upgrade your kernel:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh

or grab a newer image:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Stretch_Snapshot_iot

Regards,

btw for up-time "reliability" i've been seeing much better uptime
performance with v4.9.x-ti, most cases they survive a week. (every 7-8
days, i update the board's debian userspace and kernel and reboot)

http://gfnd.rcn-ee.org:81/farm/uptime/

test-bbgw-* are the bbgw's...

sudo ./update_kernel.sh --lts-4_9

Regards,

Thanks Robert, I already updated the kernel v4.9.x-ti to test it on a beaglebone I have here

I hope this also can solve the problem that sometimes the wifi does not work and only after several boot is fixed

and Greg, thanks for the log’s tips

regards,
Sebastián

I’ve got a BBGW bolted to the side of my house exposed to a sub-tropical climate.
I’m running without benefit of a UPS. My home has a “whole” house surge suppressor.
I suppose the little 5V “wall wart” switching power supply is providing some isolation.

The WIFI is solid and quite reliable. I have seen a few instances where I had to reboot the board when the WIFI dropped, however,
with the board in its remote location I am less motivated to analyze the problem.
I reboot by flipping a breaker in the main house panel in the garage.
WIFI has consistently come back up after reboot.

This area is one of the top areas in the world for lightning strikes, and the AC power is often very glitchy.

I’m surprised it has survived this long. I’m totally satisfied with the level of reliability so far.
It will be interesting to see if the BBGW survives the long, hot summer.

The kernel info:

Linux beaglebone 4.4.48-ti-r88 #1 SMP Sun Feb 12 01:06:00 UTC 2017 armv7l GNU/Linux

I think the above is from the March version IOT Debian image at beagleboard.org.

Greg

Good tips Greg, thank you.
I would like to use one of these IOT images but I need wifidog so my users can configure the home wifi.

I tried installing wifidog with these instructions without luck

Https://github.com/Pillar1989/wifidog-server

Is there any alternative to wifidog ?, my users do not know linux how to use connmanctl

Robert, I have another question for you,
Is it convenient to remotely update the kernel on a machine that I do not have physical access, is it possible to block it?

regards,
Sebastián

Good tips Greg, thank you.
I would like to use one of these IOT images but I need wifidog so my users
can configure the home wifi.

I tried installing wifidog with these instructions without luck
Https://github.com/Pillar1989/wifidog-server

sudo apt update
sudo apt install seeed-wificonfig-installer wifidog-gateway

(that's what converts an iot image to a seeed-iot image)

Is there any alternative to wifidog ?, my users do not know linux how to use
connmanctl

I'd like to find a "simpler" nodejs app to talk from a web-browser and connman..

Robert, I have another question for you,
Is it convenient to remotely update the kernel on a machine that I do not
have physical access, is it possible to block it?

I do all the time. :wink:

but i have a network pwr relay i can ping to reset the board's power..

Regards,

Robert,
When converting a seeedstudio image, does it install bone101 or cloud9?
I can not install it because it gives root access to anyone connecting to AP

Please recommend me some network pwr relay ?

Robert,
When converting a seeedstudio image, does it install bone101 or cloud9?
I can not install it because it gives root access to anyone connecting to AP

Yeah, seeed-wificonfig-installer requires bone101...

https://github.com/rcn-ee/repos/blob/master/seeed-wificonfig-installer/suite/jessie/debian/control#L11

so i see what you mean..

ps, in stretch, cloud9 is locked down to the "debian" user.. it's no
longer root..

Please recommend me some network pwr relay ?

this is favorite one:

http://www.robot-electronics.co.uk/eth8020-20-x-16a-ethernet-relay.html

right now, the one i have has 17 bone/bone varients hooked up...

Regards,

ok,

thanks for the answers

Hi Robert, I can’t find wifidog package for Stretch image.

image test: bone-debian-9.0-iot-armhf-2017-06-25-4gb.img

`

debian@beaglebone:~$ sudo apt install seeed-wificonfig-installer wifidog-gateway
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package seeed-wificonfig-installer
E: Unable to locate package wifidog-gateway

`

sudo apt-get update <------- before apt-get install

Williams, I already did the update, apparently it’s just for Jessie

https://github.com/rcn-ee/repos/tree/master/seeed-wificonfig-installer

Well, considering the wireless beaglebone require a 4.4+ kernel, and 4.4+ kernels were not developed for this platform until the Jessie image was used . . . Yes you need to use Jessie. I suppose you could try compiling your own version of of the kernel for Wheezy. . . but god that would be a nightmare.

I haven’t ported it to stretch. My personal opinion, wifi dog is overkill.

Seeed did all the wifidog work in Jessie.

Regards,

yes, I think the same.

I’m going to explore the nodejs world.

thanks you

I found nodejs to be amazing! My opinion: go with the latest and greatest Nodejs v8.0 and try Javascript ES6 + HTML5 + WebSockets.
Javascript is now a reasonable language and a lot of the weirdness of working with it is gone.

I had good luck with this project:

https://www.hackster.io/Greg-R/beaglebone-green-wireless-irrigation-control-ce7c4b

Once I got the BBGW configured to a simple station, it performed perfectly.
If you have a wireless router in your home system, the AP stuff is only going to confuse. Deactivate it.