Dec 9, 08:44 am, Tom, Gordon
data from wvally4 stopped overnight. At the site, the data system up and taking data, yesterday's files had been copied.
/var/log/isfs/kernel had many messages about eth0 down and up.
Power, WAN and WLAN LEDs were on, but not the USB. Modem LED was on solid. Could not ping the router, 192.168.0.1.
Power cycled router with
vio 7 0 vio 7 1
Router came up and the modem connected.
Apparently need to modify the network check scripts. If the viper cannot ping the router, then the router is not power cycled. It is cycled only if the viper can ping the router, but cannot ping google or EOL. This was done so that the modem would not do reconnects if the problem was in the ethernet wiring of the box. Will change the crontab, so that once an hour if the router cannot be pinged, the power will be cycled.
Pulled a drip loop in pyrgeometer data cable. Drip loop on pyranometer is not as good.
Left 8:44 am.
Updated the crontabs on all stations, so that once an hour do a router_check.sh without a net_check.sh:
# Only run router_check.sh if net_check.sh succeeds to avoid power cycling modem # if the problem is with the ethernet connection 15,30,45 * * * * net_check.sh eth0 192.168.0 192.168.0.1 && router_check.sh 7 www.eol.uca # once an hour skip net_check.sh 0 * * * * router_check.sh 7 www.eol.ucar.edu www.google.com