ROBIN -  Open Source Mesh Network Forum Index ROBIN - Open Source Mesh Network
users community forum
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

r268X dashboard connection problems
Goto page Previous  1, 2
 
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> beta-1.5 Release Candidates
View previous topic :: View next topic  
Author Message
Ads






Posted: Thu Sep 21, 2017 8:19 pm    Post subject: Ads

Back to top
mtlowes
Moderator
Moderator


Joined: 28 Oct 2009
Posts: 577
Location: Lakeshore Ontario Canada

PostPosted: Sun Jan 31, 2010 2:57 pm    Post subject: Reply with quote

Lacking any clear understanding of the differences between the two versions, could this be an OLSR 8 issue?

I don't seem to remember this problem when we were using r7.

Just guessing.
Back to top
View user's profile Send private message
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Sun Jan 31, 2010 6:43 pm    Post subject: Reply with quote

Well, I see that whether sysupdate.sh fails or is killed the cron daemon is not restarted hence the nodes did not checkin so - in my opinion - the bug lives in upgrade-process.
This is why I suggested to check the option Disable Auto Upgrade.

However, I'll go on testing...
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Sun Jan 31, 2010 6:45 pm    Post subject: Re: hi Reply with quote

sedatkaan wrote:
im sorry antoni but im dowgrade all nodes 2683 sam problem continue,this problem your firmware or open-mesh dasboard wich?


So, you have not checked the option Disable Auto Upgrade as I suggested...
Back to top
View user's profile Send private message Send e-mail Visit poster's website
aberam
Skilled User
Skilled User


Joined: 28 Feb 2009
Posts: 169

PostPosted: Sun Jan 31, 2010 7:09 pm    Post subject: Reply with quote

I have checked Disable Automatic Upgrades:

Will monitor and give feedback
Back to top
View user's profile Send private message
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Sun Jan 31, 2010 7:13 pm    Post subject: Reply with quote

aberam

This is the logread output

Jan 31 03:53:32 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 03:53:36 EQ user.notice update: dashboard updated successfully: checkin #96
Jan 31 03:53:51 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 03:58:32 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 03:58:36 EQ user.notice update: dashboard updated successfully: checkin #97
Jan 31 03:58:53 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:00:02 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 04:02:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:02:27 EQ user.notice update: dashboard updated successfully: checkin #98
Jan 31 04:02:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:07:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 7642 Kbps
Jan 31 04:07:27 EQ user.notice update: dashboard updated successfully: checkin #99
Jan 31 04:07:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:12:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 6871 Kbps
Jan 31 04:12:27 EQ user.notice update: dashboard updated successfully: checkin #100
Jan 31 04:12:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:17:22 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:17:26 EQ user.notice update: dashboard updated successfully: checkin #101
Jan 31 04:17:43 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:20:01 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 04:22:22 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8142 Kbps
Jan 31 04:22:27 EQ user.notice update: dashboard updated successfully: checkin #102
Jan 31 04:22:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:27:22 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:27:27 EQ user.notice update: dashboard updated successfully: checkin #103
Jan 31 04:27:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:32:22 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:32:27 EQ user.notice update: dashboard updated successfully: checkin #104
Jan 31 04:32:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:37:22 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:37:27 EQ user.notice update: dashboard updated successfully: checkin #105
Jan 31 04:37:45 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:40:02 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 04:42:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:42:27 EQ user.notice update: dashboard updated successfully: checkin #106
Jan 31 04:42:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:47:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:47:27 EQ user.notice update: dashboard updated successfully: checkin #107
Jan 31 04:47:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:52:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:52:28 EQ user.notice update: dashboard updated successfully: checkin #108
Jan 31 04:52:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 04:57:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:57:51 EQ user.notice update: dashboard updated successfully: checkin #109
Jan 31 04:58:08 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:00:01 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 05:02:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:02:52 EQ user.notice update: dashboard updated successfully: checkin #110
Jan 31 05:03:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:07:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:07:52 EQ user.notice update: dashboard updated successfully: checkin #111
Jan 31 05:08:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:12:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:12:52 EQ user.notice update: dashboard updated successfully: checkin #112
Jan 31 05:13:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:17:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8158 Kbps
Jan 31 05:17:52 EQ user.notice update: dashboard updated successfully: checkin #113
Jan 31 05:18:10 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:20:02 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 05:22:48 EQ user.notice speed-test: current bandwidth [5.201.62.41] 7256 Kbps
Jan 31 05:22:52 EQ user.notice update: dashboard updated successfully: checkin #114
Jan 31 05:23:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:27:48 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:27:52 EQ user.notice update: dashboard updated successfully: checkin #115
Jan 31 05:28:08 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:32:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:32:52 EQ user.notice update: dashboard updated successfully: checkin #116
Jan 31 05:33:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:37:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 3681 Kbps
Jan 31 05:37:52 EQ user.notice update: dashboard updated successfully: checkin #117
Jan 31 05:38:10 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:40:01 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 05:42:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 4657 Kbps
Jan 31 05:42:52 EQ user.notice update: dashboard updated successfully: checkin #118
Jan 31 05:43:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:47:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 3501 Kbps
Jan 31 05:47:52 EQ user.notice update: dashboard updated successfully: checkin #119
Jan 31 05:48:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:51:43 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:51:47 EQ user.notice update: dashboard updated successfully: checkin #120
Jan 31 05:52:05 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 05:59:13 EQ user.notice speed-test: current bandwidth [5.201.62.41] 7806 Kbps
Jan 31 05:59:17 EQ user.notice update: dashboard updated successfully: checkin #121
Jan 31 05:59:32 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewall
Jan 31 08:06:27 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:06:27 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 RADIUS: starting accounting session 0000006F-00000003
Jan 31 08:06:27 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: pairwise key handshake completed (WPA)
Jan 31 08:06:29 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: group key handshake completed (WPA)
Jan 31 08:06:32 EQ daemon.info dnsmasq[2234]: DHCPDISCOVER(br-lan) 00:24:2c:44:fc:f7
Jan 31 08:06:32 EQ daemon.info dnsmasq[2234]: DHCPOFFER(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPDISCOVER(br-lan) 00:24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPOFFER(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPREQUEST(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPACK(br-lan) 101.97.222.10 00:24:2c:44:fc:f7 acer-330bb84976
Jan 31 08:09:26 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: group key handshake completed (WPA)
Jan 31 08:13:18 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:13:21 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: deauthenticated due to local deauth request
Jan 31 08:13:21 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: disassociated
Jan 31 08:18:06 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:18:10 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: deauthenticated due to local deauth request
Jan 31 08:18:10 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: disassociated
Jan 31 08:22:32 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:22:33 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 RADIUS: starting accounting session 0000006F-00000004
Jan 31 08:22:33 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: pairwise key handshake completed (WPA)
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPDISCOVER(br-lan) 00:24:2c:44:fc:f7
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPOFFER(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPREQUEST(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPACK(br-lan) 101.97.222.10 00:24:2c:44:fc:f7 acer-330bb84976
Jan 31 08:22:35 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: group key handshake completed (WPA)
Jan 31 08:26:05 EQ authpriv.info dropbear[20164]: Child connection from 5.201.62.41:58361
Jan 31 08:26:11 EQ authpriv.notice dropbear[20164]: password auth succeeded for 'root' from 5.201.62.41:58361
root@EQ:~#


The node stopped checkin in at 5.59. I associated with the node around 2hrs later and I can get online but the node is not checkin in the dashboard.

I ran a manual update and watch the checkin number resumes at 122.




106
Jan 31 04:42:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 04:47:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:47:27 EQ user.notice update: dashboard updated successfully: checkin # 107
Jan 31 04:47:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 04:52:23 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:52:28 EQ user.notice update: dashboard updated successfully: checkin # 108
Jan 31 04:52:42 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 04:57:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 04:57:51 EQ user.notice update: dashboard updated successfully: checkin # 109
Jan 31 04:58:08 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:00:01 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 05:02:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:02:52 EQ user.notice update: dashboard updated successfully: checkin # 110
Jan 31 05:03:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:07:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:07:52 EQ user.notice update: dashboard updated successfully: checkin # 111
Jan 31 05:08:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:12:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:12:52 EQ user.notice update: dashboard updated successfully: checkin # 112
Jan 31 05:13:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:17:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8158 Kbps
Jan 31 05:17:52 EQ user.notice update: dashboard updated successfully: checkin # 113
Jan 31 05:18:10 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:20:02 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 05:22:48 EQ user.notice speed-test: current bandwidth [5.201.62.41] 7256 Kbps
Jan 31 05:22:52 EQ user.notice update: dashboard updated successfully: checkin # 114
Jan 31 05:23:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:27:48 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:27:52 EQ user.notice update: dashboard updated successfully: checkin # 115
Jan 31 05:28:08 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:32:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:32:52 EQ user.notice update: dashboard updated successfully: checkin # 116
Jan 31 05:33:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:37:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 3681 Kbps
Jan 31 05:37:52 EQ user.notice update: dashboard updated successfully: checkin # 117
Jan 31 05:38:10 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:40:01 EQ user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 31 05:42:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 4657 Kbps
Jan 31 05:42:52 EQ user.notice update: dashboard updated successfully: checkin # 118
Jan 31 05:43:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:47:47 EQ user.notice speed-test: current bandwidth [5.201.62.41] 3501 Kbps
Jan 31 05:47:52 EQ user.notice update: dashboard updated successfully: checkin # 119
Jan 31 05:48:07 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:51:43 EQ user.notice speed-test: current bandwidth [5.201.62.41] 8388 Kbps
Jan 31 05:51:47 EQ user.notice update: dashboard updated successfully: checkin # 120
Jan 31 05:52:05 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 05:59:13 EQ user.notice speed-test: current bandwidth [5.201.62.41] 7806 Kbps
Jan 31 05:59:17 EQ user.notice update: dashboard updated successfully: checkin # 121
Jan 31 05:59:32 EQ user.notice strict-mesh.sh: write strict-mesh rules to firewa ll
Jan 31 08:06:27 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:06:27 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 RADIUS: star ting accounting session 0000006F-00000003
Jan 31 08:06:27 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: pairwis e key handshake completed (WPA)
Jan 31 08:06:29 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: group k ey handshake completed (WPA)
Jan 31 08:06:32 EQ daemon.info dnsmasq[2234]: DHCPDISCOVER(br-lan) 00:24:2c:44:f c:f7
Jan 31 08:06:32 EQ daemon.info dnsmasq[2234]: DHCPOFFER(br-lan) 101.97.222.10 00 :24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPDISCOVER(br-lan) 00:24:2c:44:f c:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPOFFER(br-lan) 101.97.222.10 00 :24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPREQUEST(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:06:33 EQ daemon.info dnsmasq[2234]: DHCPACK(br-lan) 101.97.222.10 00:2 4:2c:44:fc:f7 acer-330bb84976
Jan 31 08:09:26 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: group k ey handshake completed (WPA)
Jan 31 08:13:18 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:13:21 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: deauthenticated due to local deauth request
Jan 31 08:13:21 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: disassociated
Jan 31 08:18:06 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:18:10 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: deauthenticated due to local deauth request
Jan 31 08:18:10 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: disassociated
Jan 31 08:22:32 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 IEEE 802.11: associated
Jan 31 08:22:33 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 RADIUS: star ting accounting session 0000006F-00000004
Jan 31 08:22:33 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: pairwis e key handshake completed (WPA)
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPDISCOVER(br-lan) 00:24:2c:44:f c:f7
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPOFFER(br-lan) 101.97.222.10 00 :24:2c:44:fc:f7
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPREQUEST(br-lan) 101.97.222.10 00:24:2c:44:fc:f7
Jan 31 08:22:35 EQ daemon.info dnsmasq[2234]: DHCPACK(br-lan) 101.97.222.10 00:2 4:2c:44:fc:f7 acer-330bb84976
Jan 31 08:22:35 EQ daemon.info hostapd: ath1: STA 00:24:2c:44:fc:f7 WPA: group k ey handshake completed (WPA)
Jan 31 08:26:05 EQ authpriv.info dropbear[20164]: Child connection from 5.201.62 .41:58361
Jan 31 08:26:11 EQ authpriv.notice dropbear[20164]: password auth succeeded for 'root' from 5.201.62.41:58361
root@EQ:~#
root@EQ:~# update
get node status...
speed-test: current bandwidth [5.201.62.41] 8388 Kbps
check dashboard...
update: dashboard updated successfully: checkin #122
pre-process reply...
processing UCI file: cp_switch
processing UCI file: mesh, part 1
processing UCI file: mesh, part 2
processing UCI file: general
processing UCI file: acl
processing UCI file: iprules
processing UCI file: madwifi
processing UCI file: management
processing UCI file: node
strict-mesh.sh: write strict-mesh rules to firewall
processing UCI file: radio
1
processing nodogsplash configuration file
root@EQ:~#
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Sun Jan 31, 2010 7:15 pm    Post subject: Reply with quote

he "hole" in logread indicates that cron daemon was not running so all the scheduled tasks are not performed.
When you see a not-checking-nodethen - please - ssh to it and inspect the process status issuing a ps command: do you find a line such as crond -l 10 -c /etc/crontabs ?

Moreover, I suggested to not activate auto-upgrade... but it seems to me that the post was not read.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mtlowes
Moderator
Moderator


Joined: 28 Oct 2009
Posts: 577
Location: Lakeshore Ontario Canada

PostPosted: Sun Jan 31, 2010 10:38 pm    Post subject: Reply with quote

I did as instructed yesterday and set to not Upgrade Firmware.. and so far no issues.. all nodes and gateways staying online.

Guess that might be it... give it another day or two and see how it goes.

Thanks again
Back to top
View user's profile Send private message
sedatkaan
Skilled User
Skilled User


Joined: 30 Jan 2009
Posts: 217

PostPosted: Mon Feb 01, 2010 2:23 am    Post subject: hi Reply with quote

my problem maybe fix,3 hours dont any check dash problem see.

my nodes 2683,2686,2688 dont any problem now,i hope continue without problem.
Back to top
View user's profile Send private message
aberam
Skilled User
Skilled User


Joined: 28 Feb 2009
Posts: 169

PostPosted: Mon Feb 01, 2010 1:19 pm    Post subject: Reply with quote

With disable automatic upgrades checked. The checkin issue seems to be solved.
Back to top
View user's profile Send private message
mtlowes
Moderator
Moderator


Joined: 28 Oct 2009
Posts: 577
Location: Lakeshore Ontario Canada

PostPosted: Mon Feb 01, 2010 1:25 pm    Post subject: Reply with quote

Agreed..
Into day 3 now with Upgrades turned off and not a single drop or issue with the network.. running on r2688.

Thanks
Back to top
View user's profile Send private message
mtlowes
Moderator
Moderator


Joined: 28 Oct 2009
Posts: 577
Location: Lakeshore Ontario Canada

PostPosted: Wed Feb 03, 2010 1:04 pm    Post subject: Reply with quote

Everything is running smoothly under 2688 now.. not a single issue I can see.. checkins are working and nodes are staying online (Day5, x my fingers).

So.. Ultimately, whats the fix for the checkin problem besides disabling updates?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> beta-1.5 Release Candidates All times are GMT + 1 Hour
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
c d
e



Powered by phpBB © 2001, 2005 phpBB Group

Abuse - Report Abuse - TOS & Privacy.
Powered by forumup.it free forum, create your free forum! Created by Hyarbor & Qooqoa
Confirmed

Page generation time: 0.578