Hi folks
Suddenly Vera has taken it on herself to restart every 15 minutes to an hour. Not the end of the world as things are mostly still working, but slightly worrying especially as I’m about to go on a business trip
Possibly related is that I re-cabled some of my LAN yesterday. Since then the Internet LED remains stubbornly unlit despite the very clear fact that it’s online and fine:
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_req=2 ttl=54 time=19.9 ms
Any ideas where I can look to ascertain the instability?
Hmm it is likely because you have a check network monitor script running which is causing these reboots. Disabling that script is probably also needed. I thought I included all of this in my veramods script it’s been so long, my memory might be failing. Can you check if it is in your crontab?
#This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License. #This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; #without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
exit 0
log “Terminating Start_NetworkMonitor.sh”
log “===END===”
So that was definitely not running, but check_internet is in /etc/init.d so calls that at init time.
Hmm, so was running fine until a Luup reload from editing a scene
That obviously inited check_internet and restarted Network monitor
Issues /etc/init.d/check_internet stop
Killed the Network monitor but didn’t stop it from re-loading which restarted it.
There appears to be an error in the check_internet script:
Here:
# Temporary code: restart dropbear to force it to listen on all interfaces.
log2file “Delete the interface from the dropbear config”
uci del dropbear.@dropbear[-1].Interface 2>>$log_file
uci commit
sync
Gives this in the check internet log:
2019-05-06_15:49:13 -[12042]- Delete the interface from the dropbear config
uci: Entry not found
Dropbear restarts and Network_Monitor logs this:
05/06/19 16:06:36.075 GetIpAddress: LAN NIC NOT FOUND in script response: NIC_NOT_FOUND from:
br-wan Link encap:Ethernet HWaddr B4:A5:EF:E7:46:61
inet addr:192.168.70.6 Bcast:192.168.70.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17863 errors:0 dropped:715 overruns:0 frame:0
TX packets:12661 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3479099 (3.3 MiB) TX bytes:25025412 (23.8 MiB)
Let me look into this. My veramods script is designed to take the vera offline as much as possible but since you are using geofence, I don’t think that’s what you want to do. I may need to create a script to take down the network related luup reloads without disconnecting from the mios servers which as you noted is overkill and not the smartest thing to do since the luup reload or very reboot are unlikely to change the network conditions. @Sorin told me this was getting fixed on the new firmware which is being redone from scratch.
I have looked through what I did in my veramods and I actually killed both the check_internet script in the /etc/init.d folder and the Start_NetworkMonitor.sh in /usr/bin by adding an “exit 0” line at the beginning of these scripts. I also did the same to the CheckForMissingFiles.sh
@rafale77, thanks I’m aware of that however if the node of suc values are wrong, this can cause issues, like one I experienced recently following upgrade to latest firmware, having upgraded from a veralite about 3 years ago, and legacy setup still existing.
When I check my vera now, following factory reset, I now see HouseID/Node: House: f22bedc1 Node 1 Suc 0
however I think my suc was 1 before and that, if I remember correctly, meant that my veraplus wasn’t acting as the primary controller.
This is the best guide I found explaining the three zwave roles: primary, SUC and SIS:
Indeed your vera not being the SUC could be a problem if it is your only controller. I am fairly certain that the firmware upgrade cannot change this because this role is assigned within the zwave network and cannot be changed by the vera firmware (I wish it could) unless you upgraded the zwave firmware in the process. (Ie you upgraded from a ver old firmware which had an older zwave firmware) On my network I use a secondary controller as a tool to assign and control these roles when needed.