VeraPlus dead...about to kick it out of the window, then resuscitated

I got the unit back from the dead, summary: started with space issues, then network and after some tweaking of the nameservers it came back from unable to do anything, then to update anything, then a constant reboot.

So I started having issues with the last firmware filling up the space and getting some errors. It was “fixed” by deleting the files suggested by support in other threads. But since saturday I was unable to do anything and have come to the conclusion that the network driver is corrupted.

I can connect to the unit from inside my network, but the unit cannot connect to anything even devices in the same network.
Here are some logs:

01	05/21/18 23:24:04.974	ZWJob_PollNode::Run job job#2 :pollnode #3 dev:141 (0xefa110) N:3 P:100 S:1 Id: 2 ZW_Send_Data to node 3 failed 1 req 0xefa000/1 abort m_iFrameID 0 <0x76d94520>
01	05/21/18 23:24:04.974	ZWJob_PollNode::Run job job#2 :pollnode #3 dev:141 (0xefa110) N:3 P:100 S:1 Id: 2 node 3, NO REPLY FROM NODE <0x76d94520>
01	05/21/18 23:24:06.684	FileUtils::ReadURL 6/resp:0 user: pass: size 1 http://apps.mios.com/get_plugin_version2.php?plugin=3166&accesspoint=XXXXX&platform=mt7621_Luup
&firmware=*1.7.3831*&oem=1 response:  <0x77594520>
01	05/21/18 23:24:06.685	JobHandler_LuaUPnP::GetPluginVersionOnline iPlugin: 3166 buffer empty <0x77594520>
...
01	05/21/18 23:25:36.769	FileUtils::ReadURL 6/resp:0 user: pass: size 1 http://apps.mios.com/get_plugin_version2.php?plugin=6436&accesspoint=XXXXX&platform=mt7621_Luup
&firmware=*1.7.3831*&oem=1 response:  <0x77594520>
01	05/21/18 23:25:36.769	JobHandler_LuaUPnP::GetPluginVersionOnline iPlugin: 6436 buffer empty <0x77594520>
...
01	05/21/18 23:26:02.112	luup_log:16: (MyQGateway::MYQ_API::retrieveSecurityToken): Unsuccessful at connecting with the authorization URL! <0x75b94520>
...
01	05/21/18 23:26:03.332	luup_log:144: OnkyoReceiver: Running Network Attached I_OnkyoReceiver1.xml on 192.XXX.XXX.XXX <0x77594520>
01	05/21/18 23:26:03.333	IOPort::Connect connect -1 192.XXX.XXX.XXX:60128 <0x71af7520>
01	05/21/18 23:26:07.355	IOPort::Connect connect -1 192.XXX.XXX.XXX:60128 <0x71af7520>
01	05/21/18 23:26:11.359	IOPort::Connect connect -1 192.XXX.XXX.XXX:60128 <0x71af7520>
50	05/21/18 23:26:15.451	luup_log:144: OnkyoReceiver: debug: ISCP request: !1PWRQSTN <0x77594520>
50	05/21/18 23:26:15.452	luup_log:144: OnkyoReceiver: debug: ISCP request returned in 0ms <0x77594520>
50	05/21/18 23:26:15.453	luup_log:144: OnkyoReceiver: debug: ISCP request: !1MVLQSTN <0x77594520>
50	05/21/18 23:26:15.453	luup_log:144: OnkyoReceiver: debug: ISCP request returned in 0ms <0x77594520>
50	05/21/18 23:26:15.454	luup_log:144: OnkyoReceiver: debug: ISCP request: !1SLIQSTN <0x77594520>
50	05/21/18 23:26:15.454	luup_log:144: OnkyoReceiver: debug: ISCP request returned in 0ms <0x77594520>
01	05/21/18 23:26:15.454	LuaInterface::CallFunction_Startup device 144 function receiverStartup took 12 seconds <0x77594520>
...
01	05/21/18 23:27:19.434	JobHandler_LuaUPnP::ConfirmUpnpFile can't retrieve http://192.XXX.XXX.XXX:8008//ssdp/notfound basefile notfound <0x72ef7520>
...

It starts not updating the time nor getting the location, so I checked the nameserver configuration and found this:

root@###:/etc# cat resolv.conf
search lan
nameserver 127.0.0.1

then I modified to add the google servers and restarted network, and now I get this on the net troubleshooting:

=== IP Configuration ===
br-wan    Link encap:Ethernet  HWaddr B4:XX:XX:XX:XX:XX  
          inet addr:192.XXX.XXX.XXX  Bcast:192.XXX.XXX.XXX  Mask:255.255.255.0
eth0      Link encap:Ethernet  HWaddr B4:XX:XX:XX:XX:XX  
eth0.1    Link encap:Ethernet  HWaddr B4:XX:XX:XX:XX:XX 
          inet addr:192.XXX.XXX.XXX  Bcast:192.XXX.XXX.XXX  Mask:255.255.255.0
eth0.2    Link encap:Ethernet  HWaddr B4:XX:XX:XX:XX:XX  
          inet addr:127.0.0.1  Mask:255.0.0.0
ra0       Link encap:Ethernet  HWaddr B4:XX:XX:XX:XX:XX 
rai0      Link encap:Ethernet  HWaddr B4:XX:XX:XX:XX:XX 
========================
External IP: 

=== Testing Gateway: 192.XXX.XXX.1 ===
.....
GATEWAY:OK
=== Testing DnsServer: 192.XXX.XXX.1 ===
.....
DNSSERVER1:OK
========================
=== Testing External Servers ===
.....
GOOGLE.COM:FAIL
.....
STA server: FAILED
.....
EVT server: FAILED
TS server tunnel connection: FAILED
.....
FWD server: FAILED
FWD server tunnel connection: FAILED
SSH_TUNNELS:NONE
== DONE ==

After that it was able to send out some notifications, but then started rebooting itself and reverting my changes. While I was trying to set the nameservers back, I started getting Segmentation Faults while connected thru SSH. In each restart I tried to update the nameservers and to check the “troubleshoot network” results. Well, at some point something worked and now I’m able to work with the unit. It connected to the servers and finally is stable enough to be used. Network test is:

[code]=== IP Configuration ===
br-wan Link encap:Ethernet HWaddr B4:XX:XX:XX:XX:XX
inet addr:192.XXX.XXX.XXX Bcast:192.XXX.XXX.XXX Mask:255.255.255.0
eth0 Link encap:Ethernet HWaddr B4:XX:XX:XX:XX:XX
eth0.1 Link encap:Ethernet HWaddr B4:XX:XX:XX:XX:XX
inet addr:192.XXX.XXX.1 Bcast:192.XXX.XXX.XXX Mask:255.255.255.0
eth0.2 Link encap:Ethernet HWaddr B4:XX:XX:XX:XX:XX
inet addr:127.0.0.1 Mask:255.0.0.0
ra0 Link encap:Ethernet HWaddr B4:XX:XX:XX:XX:XX
rai0 Link encap:Ethernet HWaddr B4:XX:XX:XX:XX:XX

External IP: XXX.XXX.XXX.XXX

=== Testing Gateway: 192.XXX.XXX.1 ===

GATEWAY:OK
=== Testing DnsServer: 192.XXX.XXX.1 ===

DNSSERVER1:OK

=== Testing External Servers ===

GOOGLE.COM:OK

STA server: OK

EVT server: OK
TS server tunnel connection: OK

FWD server: OK
FWD server tunnel connection: OK

=== SSH_TUNNELS: ===
Found 1 ssh sessions running
Remote Control Tunnels are running
== DONE ==
[/code]

So, long story short, the culprit seemed to be the unit unable to connect to the servers.

I hope it stays stable enought until I move out of it to openLuup in a raspberry pi.