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 1, 2  Next
 
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: Sat Sep 23, 2017 11:41 am    Post subject: Ads

Back to top
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Mon Jan 25, 2010 8:26 am    Post subject: r268X dashboard connection problems Reply with quote

Hi all

I've got one node (r2686) that not reporting to the dashboard but I can still SSH into that node and the assumption is that it is still working correctly


Only registered users can see links on this forum!
Register or Login on forum!



Code:
Jan 25 00:59:59 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:00:03 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:04:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #316
Jan 25 01:05:04 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:05:04 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:05:07 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:09:50 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #317
Jan 25 01:10:00 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:10:00 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:10:03 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:14:01 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 01:14:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #318
Jan 25 01:15:00 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:15:00 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:15:03 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:19:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #319
Jan 25 01:19:59 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:19:59 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:20:02 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:24:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #320
Jan 25 01:24:59 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:24:59 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:25:02 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:29:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #321
Jan 25 01:30:02 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:30:02 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:30:05 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:34:02 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 01:34:50 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #322
Jan 25 01:35:00 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:35:00 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:35:03 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:39:52 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #323
Jan 25 01:40:03 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:40:03 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:40:06 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:44:48 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #324
Jan 25 01:44:59 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:44:59 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:45:02 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:49:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #325
Jan 25 01:50:04 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:50:04 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:50:08 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:54:01 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 01:54:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #326
Jan 25 01:55:00 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 01:55:00 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 01:55:03 Node2_MR3201a user.notice rc.httpd: started
Jan 25 01:59:49 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #327
Jan 25 01:59:59 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:00:00 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:00:03 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:04:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #328
Jan 25 02:04:53 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:04:53 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:04:57 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:09:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #329
Jan 25 02:09:55 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:09:55 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:09:59 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:14:02 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 02:14:44 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #330
Jan 25 02:14:54 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:14:55 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:14:58 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:19:47 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #331
Jan 25 02:19:57 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:19:57 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:20:01 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:24:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #332
Jan 25 02:24:53 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:24:53 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:24:57 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:29:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #333
Jan 25 02:29:55 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:29:55 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:29:59 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:34:01 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 02:34:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #334
Jan 25 02:34:54 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:34:54 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:34:57 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:39:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #335
Jan 25 02:39:53 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:39:53 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:39:57 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:44:43 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #336
Jan 25 02:44:53 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:44:53 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:44:57 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:46:18 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #337
Jan 25 02:46:29 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:46:29 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:46:32 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:51:19 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #338
Jan 25 02:51:32 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:51:32 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:51:35 Node2_MR3201a user.notice rc.httpd: started
Jan 25 02:54:01 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 02:56:19 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #339
Jan 25 02:56:30 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 02:56:30 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 02:56:33 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:01:20 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #340
Jan 25 03:01:30 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:01:30 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:01:33 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:06:19 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #341
Jan 25 03:06:29 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:06:30 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:06:33 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:11:23 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #342
Jan 25 03:11:35 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:11:35 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:11:39 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:14:02 Node2_MR3201a user.notice tts-check.sh: cumulative message: last                                              10 checks were ok
Jan 25 03:16:20 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #343
Jan 25 03:16:30 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:16:30 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:16:34 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:21:19 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #344
Jan 25 03:21:29 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:21:30 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:21:33 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:26:19 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #345
Jan 25 03:26:29 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:26:29 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:26:33 Node2_MR3201a user.notice rc.httpd: started
Jan 25 03:31:19 Node2_MR3201a user.notice update: dashboard updated successfully                                             : checkin #346
Jan 25 03:31:33 Node2_MR3201a auth.info passwd: Password for root changed by roo                                             t
Jan 25 03:31:33 Node2_MR3201a user.notice rc.httpd: stopped
Jan 25 03:31:36 Node2_MR3201a user.notice rc.httpd: started
Jan 25 05:51:25 Node2_MR3201a daemon.info uhdcp: configuring  eth0
Jan 25 05:51:25 Node2_MR3201a daemon.info uhdcp: adding dns 192.168.0.1
Jan 25 05:51:25 Node2_MR3201a daemon.info uhdcp: adding dns 208.67.222.222
Jan 25 05:51:25 Node2_MR3201a daemon.info uhdcp: adding dns 208.67.220.220
Jan 25 05:51:25 Node2_MR3201a daemon.info uhdcp: adding dns 203.109.129.67
Jan 25 06:23:59 Node2_MR3201a authpriv.info dropbear[26471]: exit after auth (ro                                             ot): Exited normally
Jan 25 17:51:25 Node2_MR3201a daemon.info uhdcp: configuring  eth0
Jan 25 17:51:26 Node2_MR3201a daemon.info uhdcp: adding dns 192.168.0.1
Jan 25 17:51:26 Node2_MR3201a daemon.info uhdcp: adding dns 208.67.222.222
Jan 25 17:51:26 Node2_MR3201a daemon.info uhdcp: adding dns 208.67.220.220
Jan 25 17:51:26 Node2_MR3201a daemon.info uhdcp: adding dns 203.109.129.67
Jan 25 20:14:08 Node2_MR3201a authpriv.info dropbear[17682]: Child connection fr                                             om 192.168.0.109:50060
Jan 25 20:14:14 Node2_MR3201a authpriv.notice dropbear[17682]: password auth suc                                             ceeded for 'root' from 192.168.0.109:50060
Jan 25 20:14:58 Node2_MR3201a authpriv.info dropbear[17694]: Child connection fr                                             om 192.168.0.109:59602
Jan 25 20:15:04 Node2_MR3201a authpriv.notice dropbear[17694]: password auth suc                                             ceeded for 'root' from 192.168.0.109:59602
root@Node2_MR3201a:~#

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

!
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Wed Jan 27, 2010 9:44 am    Post subject: Reply with quote

I've had more nodes disconnect for the dashboard

It appears that r2686 is not a good build Sad

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

!
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: Wed Jan 27, 2010 11:17 am    Post subject: Reply with quote

wait
hmm... why I see a lot of "dashboard updated successfully" ?
I'd need to look at the checkin string sent by the node (/etc/update/update.arg) and "detailed" view of the node list from dashboard.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
sedatkaan
Skilled User
Skilled User


Joined: 30 Jan 2009
Posts: 217

PostPosted: Fri Jan 29, 2010 1:40 am    Post subject: r2686 upgrade Reply with quote

if nodes r2686 and click on dashboard use test verison upgrade again upgrade again because
Only registered users can see links on this forum!
Register or Login on forum!


version:r2686_olsrd-0.5.6-r8

nodes etc\robin_version:r2686

dou you understand me?
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Fri Jan 29, 2010 2:37 am    Post subject: Reply with quote

@sedatkaan

Are you saying that my problems are related to my using Antonio's upgrade script?

or

Are you saying that i'm using a incorrect ROBIN version?

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

!
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: Fri Jan 29, 2010 12:17 pm    Post subject: Reply with quote

@sedatkaan

looking at the logread output (the one that you sent me) it appears that the node does checkin fine every 5 minutes:

Code:
Jan 28 23:30:27  update: dashboard updated successfully: checkin #807
Jan 28 23:35:22  update: dashboard updated successfully: checkin #808
Jan 28 23:40:23  update: dashboard updated successfully: checkin #809
Jan 28 23:45:22  update: dashboard updated successfully: checkin #810
Jan 28 23:50:24  update: dashboard updated successfully: checkin #811
Jan 28 23:55:26  update: dashboard updated successfully: checkin #812
Jan 29 00:00:22  update: dashboard updated successfully: checkin #813
Jan 29 00:05:22  update: dashboard updated successfully: checkin #814
Jan 29 00:10:26  update: dashboard updated successfully: checkin #815
Jan 29 00:15:22  update: dashboard updated successfully: checkin #816
Jan 29 00:20:21  update: dashboard updated successfully: checkin #817
Jan 29 00:25:22  update: dashboard updated successfully: checkin #818
Jan 29 00:30:22  update: dashboard updated successfully: checkin #819
Jan 29 00:35:22  update: dashboard updated successfully: checkin #820
Jan 29 00:40:22  update: dashboard updated successfully: checkin #821
Jan 29 00:45:23  update: dashboard updated successfully: checkin #822
Jan 29 00:50:23  update: dashboard updated successfully: checkin #823
Jan 29 00:55:22  update: dashboard updated successfully: checkin #824
Jan 29 01:00:26  update: dashboard updated successfully: checkin #825
Jan 29 01:05:22  update: dashboard updated successfully: checkin #826
Jan 29 01:10:25  update: dashboard updated successfully: checkin #827
Jan 29 01:15:26  update: dashboard updated successfully: checkin #828


The only reason that makes sense is that the MAC address sent by the node and the MAC address stored in the dashboard do no match hence the dashboard does not recognize the checkin as a valid one and the node is shown as "down".

To figure out what's happening there you should send the files: /etc/config/node and /etc/update/update.arg, these files could help us to find a possible mismatch.
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: Fri Jan 29, 2010 12:35 pm    Post subject: Reply with quote

Quote:
The only reason that makes sense is that the MAC address sent by the node and the MAC address stored in the dashboard do no match hence the dashboard does not recognize the checkin as a valid one and the node is shown as "down".


My Nodes do checkin and report correctly on the dashboard... ... for awhile, then stop showing up on dashboard. Otherwise they work fine.. The MAC ID on dashboard is the same as the ID for the Node and in the files...

If I simply run "Update" on the affected Node.. it reports fine or even reboot sometimes in necessary
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: Fri Jan 29, 2010 12:39 pm    Post subject: Reply with quote

Quote:
...for awhile, then stop showing up on dashboard

ok, when it happens, does logread continue to show "dashboard updated successfully" messages at every 5 minutes?
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: Fri Jan 29, 2010 12:44 pm    Post subject: Reply with quote

Antonio (isleman) wrote:
Quote:
...for awhile, then stop showing up on dashboard

ok, when it happens, does logread continue to show "dashboard updated successfully" messages at every 5 minutes?


no.. it shows

Code:
Jan 29 09:48:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 09:53:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 09:58:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:03:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:08:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:13:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:18:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:23:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:28:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:30:05 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:30:08 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:33:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:38:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:43:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:45:05 Lightwave-QU01 local6.err coova-chilli[2953]: options.c: 821: Rereading configuration file and doing DNS lookup


Until I ssh into it and reboot it
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: Fri Jan 29, 2010 12:53 pm    Post subject: Reply with quote

that's interesting.
So we know that "something" breaks dnsmasq or at least br-lan configuration...
Does wificpa sends some executable code?
I say that 'cos we also know that the bug happens with wificpa as captive portal.
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: Fri Jan 29, 2010 12:59 pm    Post subject: Reply with quote

mtlowes wrote:
Antonio (isleman) wrote:
Quote:
...for awhile, then stop showing up on dashboard

ok, when it happens, does logread continue to show "dashboard updated successfully" messages at every 5 minutes?


no.. it shows

Code:
Jan 29 09:48:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 09:53:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 09:58:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:03:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:08:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:13:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:18:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:23:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:28:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:30:05 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:30:08 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:33:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:38:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:43:43 Lightwave-QU01 daemon.warn dnsmasq[2744]: no address range available for DHCP request via br-lan
Jan 29 10:45:05 Lightwave-QU01 local6.err coova-chilli[2953]: options.c: 821: Rereading configuration file and doing DNS lookup


Until I ssh into it and reboot it


... that logread output is filtered, send me the whole output and tell me where it stops to checkin.

thanks!
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: Fri Jan 29, 2010 6:45 pm    Post subject: Reply with quote

I'll provide entire dumps of all the recorded files (logread included) once it stops reporting again!.
Back to top
View user's profile Send private message
mtlowes
Moderator
Moderator


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

PostPosted: Fri Jan 29, 2010 7:45 pm    Post subject: Reply with quote

mtlowes wrote:
I'll provide entire dumps of all the recorded files (logread included) once it stops reporting again!.


OK.. it stopped reporting again, or at least one of them did.. this is 43minutes of no checking in with Dashboard (Open-Mesh) although node and internet access continue working just fine for access.

Curious about this line in the logread file though.. Wonder where the MAC ID is coming from:
local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=60-FB-42-0E-D7-CE





MAC ID reported on Open-Mesh Dashboard: 00:02:6F:68:DA:DC

etc-update-update.arg
Code:

ip=5.104.218.220&mac=00:02:6F:68:DA:DC&robin=R2686-26/cO&batman=0.5.6-r8&memfree=8708&ssid=Lightwave-TM01&pssid=lhcnet&RR=0&users=1&kbup=3&kbdown=4&top_users


/etc/config/node
Code:

config 'node' 'general'
        option 'profile' 'default'
        option 'ethPorts' '1'
        option 'wanPort' 'eth0'
        option 'lanPort' 'eth0'
        option 'switch' 'none'
        option 'myMAC' '00:02:6F:68:DA:DC'
        option 'board' 'EOC'
        option 'hw_watchdog' '0'
        option 'kernel' '26'
        option 'ath_hal' '2009-05-08'
        option 'changeset' '2663'
        option 'routing' 'O'
        option 'role' '0'
        option 'net' 'lhcnet'
        option 'IP_mesh' '5.104.218.220'
        option 'ap_ssid' 'open-mesh_220'
        option 'IP_ap' '101.218.220.1/24'
        option 'IP_Myap' '102.218.220.1/24'
        option 'wlanMAC' '00:02:6F:68:DA:DD'


logread
Code:

root@Lightwave-TM01:~# logread
Jan 29 15:57:28 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #751
Jan 29 15:57:40 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 15:57:40 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 15:57:43 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:02:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:02:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 8388 Kbps
Jan 29 16:02:28 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #752
Jan 29 16:02:38 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:02:38 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:02:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:04:01 Lightwave-TM01 user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 29 16:06:14 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 16:06:14 Lightwave-TM01 local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=60-FB-42-0E-D                                     7-CE
Jan 29 16:06:15 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 16:06:16 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 16:07:03 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:07:22 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 8323 Kbps
Jan 29 16:07:28 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #753
Jan 29 16:07:40 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:07:41 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:07:44 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:12:03 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:12:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 6264 Kbps
Jan 29 16:12:29 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #754
Jan 29 16:12:39 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:12:39 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:12:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:16:25 Lightwave-TM01 local6.info coova-chilli[2971]: chilli.c: 2954: DHCP addr released by MAC=60-FB-42-0E-D7-                                     CE IP=101.218.220.32
Jan 29 16:17:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:17:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 7297 Kbps
Jan 29 16:17:28 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #755
Jan 29 16:17:38 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:17:38 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:17:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:21:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:21:13 Lightwave-TM01 user.notice speed-test: current bandwidth [0] 25164 Kbps
Jan 29 16:21:22 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #756
Jan 29 16:21:32 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:21:32 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:21:35 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:24:01 Lightwave-TM01 user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 29 16:26:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:26:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 8273 Kbps
Jan 29 16:26:28 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #757
Jan 29 16:26:38 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:26:39 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:26:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:31:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:31:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 6715 Kbps
Jan 29 16:31:29 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #758
Jan 29 16:31:39 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:31:39 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:31:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:36:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:36:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 3681 Kbps
Jan 29 16:36:24 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 16:36:24 Lightwave-TM01 local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=60-FB-42-0E-D                                     7-CE
Jan 29 16:36:26 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 16:36:27 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 16:36:29 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #759
Jan 29 16:36:39 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:36:39 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:36:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:42:26 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:42:46 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 500 Kbps
Jan 29 16:42:51 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #760
Jan 29 16:42:59 Lightwave-TM01 local6.err coova-chilli[2971]: options.c: 821: Rereading configuration file and doing DNS                                      lookup
Jan 29 16:43:02 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:43:02 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:43:05 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:44:02 Lightwave-TM01 user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 29 16:46:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:46:24 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 1213 Kbps
Jan 29 16:46:30 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #761
Jan 29 16:46:36 Lightwave-TM01 local6.info coova-chilli[2971]: chilli.c: 2954: DHCP addr released by MAC=60-FB-42-0E-D7-                                     CE IP=101.218.220.33
Jan 29 16:46:40 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:46:40 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:46:43 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:51:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:51:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 7109 Kbps
Jan 29 16:51:29 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #762
Jan 29 16:51:44 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:51:44 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:51:48 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 16:56:04 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 16:56:23 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 1541 Kbps
Jan 29 16:56:28 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #763
Jan 29 16:56:39 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 16:56:39 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 16:56:42 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:02:38 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:02:57 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 5198 Kbps
Jan 29 17:03:02 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #764
Jan 29 17:03:13 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:03:13 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:03:16 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:04:01 Lightwave-TM01 user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 29 17:06:34 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 17:06:34 Lightwave-TM01 local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=60-FB-42-0E-D                                     7-CE
Jan 29 17:06:36 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 17:06:37 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 17:07:38 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:07:58 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 5592 Kbps
Jan 29 17:08:04 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #765
Jan 29 17:08:14 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:08:14 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:08:17 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:12:39 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:12:58 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 8027 Kbps
Jan 29 17:13:04 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #766
Jan 29 17:13:17 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:13:17 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:13:21 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:16:46 Lightwave-TM01 local6.info coova-chilli[2971]: chilli.c: 2954: DHCP addr released by MAC=60-FB-42-0E-D7-                                     CE IP=101.218.220.34
Jan 29 17:17:38 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:17:57 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 5256 Kbps
Jan 29 17:18:03 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #767
Jan 29 17:18:13 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:18:13 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:18:17 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:22:28 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:22:47 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 6092 Kbps
Jan 29 17:23:03 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #768
Jan 29 17:23:13 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:23:13 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:23:17 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:24:02 Lightwave-TM01 user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 29 17:27:38 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:27:57 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 5157 Kbps
Jan 29 17:28:03 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #769
Jan 29 17:28:15 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:28:16 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:28:19 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:32:39 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:32:57 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 6502 Kbps
Jan 29 17:33:03 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #770
Jan 29 17:33:13 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:33:13 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:33:17 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:36:44 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 17:36:44 Lightwave-TM01 local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=60-FB-42-0E-D                                     7-CE
Jan 29 17:36:45 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 17:36:46 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 17:37:39 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:37:58 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 1516 Kbps
Jan 29 17:38:04 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #771
Jan 29 17:38:14 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:38:15 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:38:18 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:40:27 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:40:49 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 8388 Kbps
Jan 29 17:40:56 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #772
Jan 29 17:41:06 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:41:07 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:41:10 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:42:59 Lightwave-TM01 local6.err coova-chilli[2971]: options.c: 821: Rereading configuration file and doing DNS                                      lookup
Jan 29 17:44:01 Lightwave-TM01 user.notice tts-check.sh: cumulative message: last 10 checks were ok
Jan 29 17:45:26 Lightwave-TM01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 17:45:46 Lightwave-TM01 user.notice speed-test: current bandwidth [5.102.158.173] 8388 Kbps
Jan 29 17:45:51 Lightwave-TM01 user.notice update: dashboard updated successfully: checkin #773
Jan 29 17:46:02 Lightwave-TM01 auth.info passwd: Password for root changed by root
Jan 29 17:46:02 Lightwave-TM01 user.notice rc.httpd: stopped
Jan 29 17:46:05 Lightwave-TM01 user.notice rc.httpd: started
Jan 29 17:46:55 Lightwave-TM01 local6.info coova-chilli[2971]: chilli.c: 2954: DHCP addr released by MAC=60-FB-42-0E-D7-                                     CE IP=101.218.220.35
Jan 29 18:01:27 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:01:27 Lightwave-TM01 local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=00-23-76-3E-E                                     9-86
Jan 29 18:01:28 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:01:28 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:01:28 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:06:54 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:06:54 Lightwave-TM01 local6.notice coova-chilli[2971]: chilli.c: 2822: New DHCP request from MAC=60-FB-42-0E-D                                     7-CE
Jan 29 18:06:55 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:06:56 Lightwave-TM01 daemon.warn dnsmasq[2762]: no address range available for DHCP request via br-lan
Jan 29 18:11:34 Lightwave-TM01 local6.info coova-chilli[2971]: chilli.c: 2954: DHCP addr released by MAC=00-23-76-3E-E9-                                     86 IP=101.218.220.36
Jan 29 18:17:05 Lightwave-TM01 local6.info coova-chilli[2971]: chilli.c: 2954: DHCP addr released by MAC=60-FB-42-0E-D7-                                     CE IP=101.218.220.37
Jan 29 18:30:07 Lightwave-TM01 authpriv.info dropbear[16067]: Child connection from 5.102.158.173:36938
Jan 29 18:30:15 Lightwave-TM01 authpriv.notice dropbear[16067]: password auth succeeded for 'root' from 5.102.158.173:36                                     938
root@Lightwave-TM01:~#
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Fri Jan 29, 2010 7:51 pm    Post subject: Reply with quote

In another thread a user has complained that the dashboard is changing the MAC address, I don't know if this problem is connected?

Only registered users can see links on this forum!
Register or Login on forum!


_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

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


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

PostPosted: Fri Jan 29, 2010 7:52 pm    Post subject: Reply with quote

ispyisail wrote:
In another thread a user has complained that the dashboard is changing the MAC address, I don't know if this problem is connected?

Only registered users can see links on this forum!
Register or Login on forum!



This has only started once nodes are upgraded to 2686 with olsr r8. Didn't happen with olsr 7 or 2683. But who knows...

Anyone know if attempted fixes were applied to the 2688 release I see is now available today??
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: Fri Jan 29, 2010 9:49 pm    Post subject: Reply with quote

great work!

I've filtered the output to find checkins:
[code]
15:57:28 dashboard updated successfully: checkin #751
16:02:28 dashboard updated successfully: checkin #752
16:07:28 dashboard updated successfully: checkin #753
16:12:29 dashboard updated successfully: checkin #754
16:17:28 dashboard updated successfully: checkin #755
16:21:22 dashboard updated successfully: checkin #756
16:26:28 dashboard updated successfully: checkin #757
16:31:29 dashboard updated successfully: checkin #758
16:36:29 dashboard updated successfully: checkin #759
16:42:51 dashboard updated successfully: checkin #760
16:46:30 dashboard updated successfully: checkin #761
16:51:29 dashboard updated successfully: checkin #762
16:56:28 dashboard updated successfully: checkin #763
17:03:02 dashboard updated successfully: checkin #764
17:08:04 dashboard updated successfully: checkin #765
17:13:04 dashboard updated successfully: checkin #766
17:18:03 dashboard updated successfully: checkin #767
17:23:03 dashboard updated successfully: checkin #768
17:28:03 dashboard updated successfully: checkin #769
17:33:03 dashboard updated successfully: checkin #770
17:38:04 dashboard updated successfully: checkin #771
17:40:56 dashboard updated successfully: checkin #772
17:45:51 dashboard updated successfully: checkin #773
[/quote]
which - as you can see - are ok but in fact are fakes.
I have a doubt... can you tell me the content of the files /etc/update/received and /etc/update/received.old ?
I fear that the node checkins to another URL (because of a redirect), it (w)gets something and so it goes on (we do not have a semantic check on the reply).
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: Fri Jan 29, 2010 9:55 pm    Post subject: Reply with quote

Antonio (isleman) wrote:
I have a doubt... can you tell me the content of the files /etc/update/received and /etc/update/received.old ?
I fear that the node checkins to another URL (because of a redirect), it (w)gets something and so it goes on (we do not have a semantic check on the reply).


/etc/update/received is empty, nothing in it.

/etc/update/received.old
Code:

#@#config general
services.base_beta
Only registered users can see links on this forum!
Register or Login on forum!


services.base_test

Only registered users can see links on this forum!
Register or Login on forum!


services.upgd_srv

Only registered users can see links on this forum!
Register or Login on forum!


services.ntpd_srv tick.greyware.com
services.upstream 0
services.name_srv
services.cstm_srv

Only registered users can see links on this forum!
Register or Login on forum!


#@#config madwifi
priv.rate AUTO
#@#config node
general.net lhcnet
#@#config nodes
R 5.104.181.232 Lightwave-QU01 00:02:6F:68:B5:e9
R 5.102.158.167 Lightwave-HA01 00:02:6F:66:9E:a8
G 5.102.164.97 Lightwave-GW02 00:02:6F:66:A4:62
G 5.102.158.173 Lightwave-GW03 00:02:6F:66:9E:ae
G 5.100.224.109 Lightwave-GW01 00:02:6F:64:E0:6e
R 5.104.181.230 Lightwave-MO01 00:02:6F:68:B5:e7
R 5.102.164.89 Lightwave-TM03 00:02:6F:66:A4:5a
R 5.102.158.169 Lightwave-MI01 00:02:6F:66:9E:aa
R 5.104.218.220 Lightwave-TM01 00:02:6F:68:DA:dd
R 5.104.181.236 Lightwave-JU01 00:02:6F:68:B5:ed
#@#config management
enable.base trunk
enable.rootpwd xxxxxxxxxxx  [i](x/d out the password)[/i]
enable.defessid 0
enable.custom_update 0
enable.freeze_version 0
enable.ap2hidden 1
enable.sm 0
enable.gmt_offset -5
enable.https 0
enable.local_domain
#@#config mesh
ap.up 1
Myap.up 1
ap.psk 0
#@#config ra_switch


Hope it helps.. Also of note, the GMT offset is correct in this file, but doesn't work.. times reflected in files are all out by 5 hours
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: Fri Jan 29, 2010 10:08 pm    Post subject: Reply with quote

hmm... can you copy the following file to /usr/sbin/update-chilli.sh ? I think it should fix our problem

Code:

#!/bin/sh

CALLER=$1
CALLER="${CALLER:-1}"
CONF=chilli
WDIR=/etc/update
k_restart=0

wifi_CPA=0
[ 4 -eq "$(uci get cp_switch.main.which_handler)" ] && wifi_CPA=1

format_value() {
   local str="$*"
   echo -n "$str" | tr -d '\n\r\v'
}

skip() { return; }

echo "processing UCI file: $CONF"
while read riga ; do
        SECTION_OPTION=$(echo $riga | awk '{print $1}')
        option="${CONF}.${SECTION_OPTION}"
        VALUE=$(echo $riga | awk '{print $2}') ; VALUE=$(format_value "$VALUE")
      old_value=$(uci get ${option})
       
   case $SECTION_OPTION in
      'agent.uamurlextras'|'agent.uamurl')
         if [ "$old_value" != "$VALUE" ] ; then
            uci set $option="${VALUE}"
            uci commit chilli
            k_restart=1
            [ 1 -eq "$wifi_CPA" ] && k_restart=0
         fi
         ;;

      *)
         if [ "$old_value" != "$VALUE" ] ; then
            uci set $option="${VALUE}"
            uci commit chilli
            k_restart=1
         fi
      ;;
   esac
done < $WDIR/chilli

[ 1 -eq "$CALLER" ] && {
   if [ "$k_restart" -eq 1 ] ; then
        uci set flags.restart.cps="1"
        uci commit flags
   fi
}
#


thanks !
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: Sat Jan 30, 2010 12:02 am    Post subject: Reply with quote

OK..
Replaced contents of the file...
Updated node.

Here is feedback:
Code:

root@Lightwave-MO01:~# update
sending heartbeat...
: WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
get node status...
check dashboard...
update: dashboard updated successfully: checkin #766
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
Changing password for root
New password:
Bad password: too weak
Retype password:
Password for root changed by root
rc.httpd: stopped
rc.httpd: started
processing UCI file: node
processing UCI file: radio
5
/usr/sbin/update-chilli.sh: line 2: copy: not found
/usr/sbin/update-chilli.sh: line 4: -------------------------------------------: not found
processing UCI file: chilli
root@Lightwave-MO01:~#


and of course the logread file shortly after

Code:
root@Lightwave-MO01:~# logread
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x35
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3d
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3c
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x39
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x35
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3d
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3c
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x39
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x35
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3d
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3c
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x39
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x35
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3d
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3c
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x39
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x35
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3d
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3c
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x39
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x35
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3d
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x3c
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adding option 0x39
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter index 2
Jan  1 00:01:17 Lightwave-MO01 user.info : ### adapter hardware address 00:02:6f:68:b5:e6
Jan  1 00:01:17 Lightwave-MO01 user.info : ### Waiting on select...
Jan  1 00:01:17 Lightwave-MO01 user.info : ### vfork'ing and execle'ing /usr/share/udhcpc/robin.script
Jan  1 00:01:17 Lightwave-MO01 user.info : No lease, failing
Jan  1 00:01:17 Lightwave-MO01 user.info : killall: udhcpc: no process killed
Jan  1 00:01:17 Lightwave-MO01 user.info : processing UCI file: mesh, part 1
Jan  1 00:01:18 Lightwave-MO01 user.info : processing UCI file: mesh, part 2
Jan  1 00:01:18 Lightwave-MO01 user.info : processing UCI file: general
Jan  1 00:01:19 Lightwave-MO01 user.info : processing UCI file: acl
Jan  1 00:01:19 Lightwave-MO01 user.info : processing UCI file: iprules
Jan  1 00:01:20 Lightwave-MO01 user.info : processing UCI file: madwifi
Jan  1 00:01:20 Lightwave-MO01 user.info : processing UCI file: management
Jan  1 00:01:20 Lightwave-MO01 user.info : Changing password for root
Jan  1 00:01:20 Lightwave-MO01 user.info : New password:
Jan  1 00:01:20 Lightwave-MO01 user.info : Bad password: too weak
Jan  1 00:01:21 Lightwave-MO01 user.info : Retype password:
Jan  1 00:01:21 Lightwave-MO01 auth.info passwd: Password for root changed by root
Jan  1 00:01:21 Lightwave-MO01 user.info : Password for root changed by root
Jan  1 00:01:21 Lightwave-MO01 user.info : killall: httpd: no process killed
Jan  1 00:01:21 Lightwave-MO01 user.info : rc.httpd: stopped
Jan  1 00:01:21 Lightwave-MO01 user.notice rc.httpd: stopped
Jan  1 00:01:25 Lightwave-MO01 user.info : rc.httpd: started
Jan  1 00:01:25 Lightwave-MO01 user.notice rc.httpd: started
Jan  1 00:01:25 Lightwave-MO01 user.info : processing UCI file: node
Jan  1 00:01:26 Lightwave-MO01 user.info : processing UCI file: radio
Jan  1 00:01:26 Lightwave-MO01 user.info : processing UCI file: ra_switch
Jan  1 00:01:26 Lightwave-MO01 user.info : processing UCI file: cp_switch
Jan  1 00:01:26 Lightwave-MO01 user.info : processing UCI file: chilli
Jan  1 00:01:37 Lightwave-MO01 user.info : brctl: invalid argument '0' to 'timespec'
Jan  1 00:01:37 Lightwave-MO01 user.info kernel: device ath1 entered promiscuous mode
Jan  1 00:01:37 Lightwave-MO01 user.info kernel: br-lan: port 1(ath1) entering learning state
Jan  1 00:01:37 Lightwave-MO01 user.info kernel: br-lan: starting userspace STP failed, starting kernel STP
Jan  1 00:01:45 Lightwave-MO01 authpriv.info dropbear[1709]: Running in background
Jan  1 00:01:47 Lightwave-MO01 user.info kernel: br-lan: port 1(ath1) entering disabled state
Jan  1 00:01:47 Lightwave-MO01 user.info kernel: device ath1 left promiscuous mode
Jan  1 00:01:47 Lightwave-MO01 user.info kernel: br-lan: port 1(ath1) entering disabled state
Jan  1 00:01:56 Lightwave-MO01 user.info kernel: device eth0 entered promiscuous mode
Jan  1 00:01:56 Lightwave-MO01 user.info kernel: br-lan: port 1(eth0) entering learning state
Jan  1 00:01:56 Lightwave-MO01 user.info kernel: br-lan: starting userspace STP failed, starting kernel STP
Jan  1 00:02:11 Lightwave-MO01 user.info kernel: br-lan: topology change detected, propagating
Jan  1 00:02:11 Lightwave-MO01 user.info kernel: br-lan: port 1(eth0) entering forwarding state
Jan  1 00:02:11 Lightwave-MO01 user.info kernel: device ath1 entered promiscuous mode
Jan  1 00:02:11 Lightwave-MO01 user.info kernel: br-lan: port 2(ath1) entering listening state
Jan  1 00:02:12 Lightwave-MO01 user.info kernel: device ath1 left promiscuous mode
Jan  1 00:02:12 Lightwave-MO01 user.info kernel: br-lan: port 2(ath1) entering disabled state
Jan  1 00:02:17 Lightwave-MO01 user.info kernel: device ath1 entered promiscuous mode
Jan  1 00:02:17 Lightwave-MO01 user.info kernel: br-lan: port 2(ath1) entering listening state
Jan  1 00:02:18 Lightwave-MO01 user.info : ath0
Jan  1 00:02:21 Lightwave-MO01 user.info : using gpio pin 4
Jan  1 00:02:21 Lightwave-MO01 user.info : using gpio pin 6
Jan  1 00:02:21 Lightwave-MO01 user.info : using gpio pin 7
Jan  1 00:02:22 Lightwave-MO01 user.info : Parsing file: "/etc/olsrd.conf"
Jan  1 00:02:22 Lightwave-MO01 daemon.info olsrd[2708]: Writing "0" to /proc/sys/net/ipv4/conf/all/send_redirects
Jan  1 00:02:22 Lightwave-MO01 daemon.info olsrd[2708]: Writing "0" to /proc/sys/net/ipv4/conf/ath0/rp_filter
Jan  1 00:02:22 Lightwave-MO01 daemon.info olsrd[2708]: Writing "0" to /proc/sys/net/ipv4/conf/ath0/send_redirects
Jan  1 00:02:22 Lightwave-MO01 daemon.info olsrd[2708]: Adding interface ath0
Jan  1 00:02:22 Lightwave-MO01 daemon.info olsrd[2708]: New main address: 5.104.181.230
Jan  1 00:02:22 Lightwave-MO01 daemon.info olsrd[2708]: olsr.org - 0.5.6-r8 successfully started
Jan  1 00:02:32 Lightwave-MO01 user.info kernel: br-lan: port 2(ath1) entering learning state
Jan  1 00:02:43 Lightwave-MO01 user.info : uci: Entry not found
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: started, version 2.47 cachesize 150
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: compile time options: IPv6 GNU-getopt no-DBus no-I18N TFTP
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: DHCP, IP range 102.181.230.10 -- 102.181.230.250, lease time 2h
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: reading /etc/resolv.conf
Jan  1 00:02:44 Lightwave-MO01 daemon.warn dnsmasq[2753]: ignoring nameserver 127.0.0.1 - local interface
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: using nameserver 208.67.220.220#53
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: using nameserver 208.67.222.222#53
Jan  1 00:02:44 Lightwave-MO01 daemon.info dnsmasq[2753]: read /etc/hosts - 2 addresses
Jan  1 00:02:47 Lightwave-MO01 user.info : flushing ipfilter rules...
Jan  1 00:02:47 Lightwave-MO01 user.info : starting preUp script: chilli
Jan  1 00:02:47 Lightwave-MO01 user.info kernel: br-lan: topology change detected, propagating
Jan  1 00:02:47 Lightwave-MO01 user.info kernel: br-lan: port 2(ath1) entering forwarding state
Jan  1 00:02:47 Lightwave-MO01 user.info : Setting wificpa_enterprise - Repeater settings
Jan  1 00:02:50 Lightwave-MO01 user.info : chilli: Starting...
Jan  1 00:02:50 Lightwave-MO01 user.notice chilli: Starting...
Jan  1 00:02:52 Lightwave-MO01 local6.info coova-chilli[2965]: CoovaChilli(ChilliSpot) 1.0.13. Copyright 2002-2005 Mondru AB. Licensed under GPL. Copyright 2006-2008 David Bird <dbird@acm.org>. Licensed under GPL. See http://coova.org/ for details.
Jan  1 00:02:52 Lightwave-MO01 user.info : chilli: started
Jan  1 00:02:52 Lightwave-MO01 user.notice chilli: started
Jan  1 00:02:52 Lightwave-MO01 local6.notice coova-chilli[2965]: tun.c: 515: TX queue length set to 100
Jan  1 00:02:53 Lightwave-MO01 user.info : iprules.sh: public-AP iface is tun0
Jan  1 00:02:53 Lightwave-MO01 user.notice iprules.sh: public-AP iface is tun0
Jan  1 00:02:54 Lightwave-MO01 user.info : iprules.sh: applying input rules...
Jan  1 00:02:54 Lightwave-MO01 user.notice iprules.sh: applying input rules...
Jan  1 00:02:55 Lightwave-MO01 user.info : iprules.sh: applying AP isolation...
Jan  1 00:02:55 Lightwave-MO01 user.notice iprules.sh: applying AP isolation...
Jan  1 00:02:55 Lightwave-MO01 user.info : iprules.sh: set MTU to auto
Jan  1 00:02:55 Lightwave-MO01 user.notice iprules.sh: set MTU to auto
Jan  1 00:02:55 Lightwave-MO01 user.notice iprules.sh: postrouting and masquerading...
Jan  1 00:02:55 Lightwave-MO01 user.info : iprules.sh: postrouting and masquerading...
Jan  1 00:02:56 Lightwave-MO01 user.info : httpd: bind: Address already in use
Jan  1 00:02:56 Lightwave-MO01 user.info : rc.httpd: started
Jan  1 00:02:56 Lightwave-MO01 user.notice rc.httpd: started
Jan  1 00:02:56 Lightwave-MO01 user.info : iwpriv-mesh.sh: set ath0 mcast_rate to 5500
Jan  1 00:02:56 Lightwave-MO01 user.notice iwpriv-mesh.sh: set ath0 mcast_rate to 5500
Jan  1 00:02:56 Lightwave-MO01 user.notice iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1 ath2
Jan  1 00:02:56 Lightwave-MO01 user.info : iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1 ath2
Jan  1 00:02:56 Lightwave-MO01 user.info : iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1
Jan  1 00:02:56 Lightwave-MO01 user.notice iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1
Jan  1 00:02:56 Lightwave-MO01 user.notice iwpriv-mesh.sh: set abolt=0 and doth=0 for ath2
Jan  1 00:02:56 Lightwave-MO01 user.info : iwpriv-mesh.sh: set abolt=0 and doth=0 for ath2
Jan  1 00:02:57 Lightwave-MO01 user.notice iwpriv-mesh.sh: set ath1 bintval to 100
Jan  1 00:02:57 Lightwave-MO01 user.info : iwpriv-mesh.sh: set ath1 bintval to 100
Jan 29 23:04:30 Lightwave-MO01 local6.err coova-chilli[2965]: options.c: 821: Rereading configuration file and doing DNS lookup
Jan 29 23:04:32 Lightwave-MO01 user.info : kernel.panic_on_oops = 1
Jan 29 23:04:47 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:04:47 Lightwave-MO01 local6.notice coova-chilli[2965]: chilli.c: 2822: New DHCP request from MAC=00-23-8B-0D-27-4A
Jan 29 23:04:50 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 574 Kbps
Jan 29 23:04:50 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 574 Kbps
Jan 29 23:05:07 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:05:07 Lightwave-MO01 local6.notice coova-chilli[2965]: chilli.c: 2822: New DHCP request from MAC=00-14-A5-B8-02-FB
Jan 29 23:05:15 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:05:15 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:05:37 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 6281 Kbps
Jan 29 23:05:37 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 6281 Kbps
Jan 29 23:05:51 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:05:52 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:05:52 Lightwave-MO01 authpriv.info dropbear[3396]: Child connection from 5.100.224.109:58515
Jan 29 23:05:58 Lightwave-MO01 authpriv.notice dropbear[3396]: password auth succeeded for 'root' from 5.100.224.109:58515
Jan 29 23:06:12 Lightwave-MO01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 23:06:21 Lightwave-MO01 user.notice update: dashboard updated successfully: checkin #765
Jan 29 23:06:28 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 5461 Kbps
Jan 29 23:06:28 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 5461 Kbps
Jan 29 23:06:34 Lightwave-MO01 auth.info passwd: Password for root changed by root
Jan 29 23:06:34 Lightwave-MO01 user.notice rc.httpd: stopped
Jan 29 23:06:37 Lightwave-MO01 user.notice rc.httpd: started
Jan 29 23:07:20 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 7092 Kbps
Jan 29 23:07:20 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 7092 Kbps
Jan 29 23:07:34 Lightwave-MO01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 23:07:41 Lightwave-MO01 user.notice update: dashboard updated successfully: checkin #766
Jan 29 23:07:52 Lightwave-MO01 auth.info passwd: Password for root changed by root
Jan 29 23:07:52 Lightwave-MO01 user.notice rc.httpd: stopped
Jan 29 23:07:56 Lightwave-MO01 user.notice rc.httpd: started
Jan 29 23:08:11 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 7732 Kbps
Jan 29 23:08:11 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 7732 Kbps
Jan 29 23:08:58 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 4682 Kbps
Jan 29 23:08:58 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 4682 Kbps
Jan 29 23:09:51 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 6584 Kbps
Jan 29 23:09:51 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 6584 Kbps
Jan 29 23:10:38 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 4756 Kbps
Jan 29 23:10:38 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 4756 Kbps
Jan 29 23:10:53 Lightwave-MO01 daemon.warn dnsmasq[2753]: no address range available for DHCP request via br-lan
Jan 29 23:11:10 Lightwave-MO01 user.notice : WiFi-CPA Heartbeat - Sent to Enterprise Server as Client
Jan 29 23:11:18 Lightwave-MO01 user.notice update: dashboard updated successfully: checkin #767
Jan 29 23:11:31 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 6264 Kbps
Jan 29 23:11:31 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 6264 Kbps
Jan 29 23:11:32 Lightwave-MO01 auth.info passwd: Password for root changed by root
Jan 29 23:11:32 Lightwave-MO01 user.notice rc.httpd: stopped
Jan 29 23:11:35 Lightwave-MO01 user.notice rc.httpd: started
Jan 29 23:12:18 Lightwave-MO01 user.info : speed-test: current bandwidth [5.102.158.173] 8052 Kbps
Jan 29 23:12:18 Lightwave-MO01 user.notice speed-test: current bandwidth [5.102.158.173] 8052 Kbps
root@Lightwave-MO01:~#
Back to top
View user's profile Send private message
mtlowes
Moderator
Moderator


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

PostPosted: Sat Jan 30, 2010 12:38 am    Post subject: Reply with quote

OK, Updated 3 of my most problematic nodes with the new "update-chilli.sh".

See how it goes for a bit..
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Sat Jan 30, 2010 8:39 am    Post subject: Reply with quote

My network running r2686 has completely stopped running except my OM1P which I think kept running because of the watchdog timer

I have now upgraded my whole network to r2688 and we will see what happens this time

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

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


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

PostPosted: Sat Jan 30, 2010 11:45 am    Post subject: Reply with quote

Was that before or after you applied the "update-chilli.sh" update??
Back to top
View user's profile Send private message
mtlowes
Moderator
Moderator


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

PostPosted: Sat Jan 30, 2010 12:52 pm    Post subject: Reply with quote

Upgrading 2 gateways and 2 repeaters to 2688 to see how they perform
Back to top
View user's profile Send private message
sedatkaan
Skilled User
Skilled User


Joined: 30 Jan 2009
Posts: 217

PostPosted: Sat Jan 30, 2010 2:14 pm    Post subject: hi Reply with quote

im upgrade 2688 but same problem continue 8-10 nodes.
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: Sat Jan 30, 2010 3:32 pm    Post subject: Re: hi Reply with quote

@sedatkaan and others
Quote:
im upgrade 2688 but same problem continue 8-10 nodes.


check the timestamps of the files:

/etc/update/received
/etc/update/received.old
/etc/update/last_checkin


(you have simply to issue te command ls -l /etc/update/ an read the time data). Check also the timestamp of the last message "dashboard updated successfully: checkin #NNNN" in logread output.

They all MUST BE IN SYNC, ie they should have, more or less, the same time indication. These checks must be done just for 15-20 minutes WHILE the node you are connected to is shown as "down" or "late" in dashboard.
This is important because it will indicate that the node sends its checkin data and receives the dashboard reply w/out failures.

In such scenario (the node and the dashboard establish a valid communication and this fact is verified) why the dashboard should not mark that node as "alive" ?


Last edited by Antonio (isleman) on Sat Jan 30, 2010 7:10 pm; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail Visit poster's website
sedatkaan
Skilled User
Skilled User


Joined: 30 Jan 2009
Posts: 217

PostPosted: Sat Jan 30, 2010 5:21 pm    Post subject: hi Reply with quote

root@Wi-Kablosuz-Internet-006:~# ls -l /etc/update/
-rw-r--r-- 1 root root 15 Jan 30 15:47 acl
-rw-r--r-- 1 root root 19 Jan 30 15:47 batm an
-rw-r--r-- 1 root root 456 Jan 30 15:47 chil li
-rw-r--r-- 1 root root 21 Jan 30 15:47 cp_s witch
-rw-r--r-- 1 root root 310 Jan 30 15:47 gene ral
-rw-r--r-- 1 root root 95 Jan 30 15:47 ipru les
-rw-r--r-- 1 root root 33 Jan 30 15:47 last _checkin
-rw-r--r-- 1 root root 15 Jan 30 15:47 madw ifi
-rw-r--r-- 1 root root 193 Jan 30 15:47 mana gement
-rw-r--r-- 1 root root 27 Jan 30 15:47 mesh
-rw-r--r-- 1 root root 22 Jan 30 15:47 node
-rw-r--r-- 1 root root 3962 Jan 30 15:47 node s
lrwxrwxrwx 1 root root 17 Jan 30 01:15 nodo gsplash -> /etc/update/nodog
-rw-r--r-- 1 root root 21 Jan 30 15:47 ra_s witch
-rw-r--r-- 1 root root 20 Jan 30 15:47 radi o
-rw-r--r-- 1 root root 0 Jan 30 15:47 rece ived
-rw-r--r-- 1 root root 5570 Jan 30 04:37 rece ived.old
-rw-r--r-- 1 root root 46 Jan 30 15:47 seco ndary
-rw-r--r-- 1 root root 668 Jan 30 15:47 upda te.arg
-rw-r--r-- 1 root root 80 Jan 30 15:47 wire less
root@Wi-Kablosuz-Internet-006:~#
Back to top
View user's profile Send private message
sedatkaan
Skilled User
Skilled User


Joined: 30 Jan 2009
Posts: 217

PostPosted: Sat Jan 30, 2010 5:22 pm    Post subject: hi Reply with quote

root@Wi-Kablosuz-Internet-006:~# ls -l /etc/update/received
-rw-r--r-- 1 root root 0 Jan 30 15:47 /etc/update/received
root@Wi-Kablosuz-Internet-006:~#

root@Wi-Kablosuz-Internet-006:~# ls -l /etc/update/received.old
-rw-r--r-- 1 root root 5570 Jan 30 04:37 /etc/update/received.old
root@Wi-Kablosuz-Internet-006:~#

root@Wi-Kablosuz-Internet-006:~# ls -l /etc/update/last_checkin
-rw-r--r-- 1 root root 33 Jan 30 15:47 /etc/update/last_checkin
root@Wi-Kablosuz-Internet-006:~#

this node status offline dashboard 24 minutes.
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: Sat Jan 30, 2010 7:21 pm    Post subject: Reply with quote

hmm... I'm pretty convinced that this commit will fix the problem:
Only registered users can see links on this forum!
Register or Login on forum!



despite our discussions (see my previous post) it seems that if upgrade process fails then it does not properly restart the cron daemon hence all the scheduled tasks... sleep (and checkin wont be raised).

Now I have a big doubt about the logread outputs posted here: are they right? Inspecting a broken node I do not see any "dashboard succesully upgraded".

Thanks to Sedatkaan for the opportunity to log to a broken node and giving me the canche to (hopefully) fix the problem.

I have commited also robin-mesh SVN with the patched version of sysupdate.sh and hope thet Mike will update ASAP the open-mesh upgrade server.

Let's go on and watch if the bug is gone.
Thanks for your time and help.
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: Sat Jan 30, 2010 8:23 pm    Post subject: Reply with quote

Antonio (isleman) wrote:
hmm... I'm pretty convinced that this commit will fix the problem:
Only registered users can see links on this forum!
Register or Login on forum!



despite our discussions (see my previous post) it seems that if upgrade process fails then it does not properly restart the cron daemon hence all the scheduled tasks... sleep (and checkin wont be raised).

Now I have a big doubt about the logread outputs posted here: are they right? Inspecting a broken node I do not see any "dashboard succesully upgraded".

Thanks to Sedatkaan for the opportunity to log to a broken node and giving me the canche to (hopefully) fix the problem.

I have commited also robin-mesh SVN with the patched version of sysupdate.sh and hope thet Mike will update ASAP the open-mesh upgrade server.

Let's go on and watch if the bug is gone.
Thanks for your time and help.

Upgrading now!
Let you know.. thank

EDIT: Is this still r2688? thats how my updates are reading.. Just doublechecking
Back to top
View user's profile Send private message
sedatkaan
Skilled User
Skilled User


Joined: 30 Jan 2009
Posts: 217

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

im sorry antoni but im dowgrade all nodes 2683 sam problem continue,this problem your firmware or open-mesh dasboard wich?
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 1, 2  Next
Page 1 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.6