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 

Complelling reason to go standalone..

 
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:20 pm    Post subject: Ads

Back to top
mtlowes
Moderator
Moderator


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

PostPosted: Wed Feb 17, 2010 10:15 am    Post subject: Complelling reason to go standalone.. Reply with quote

Open Mesh is down.....without any prior notice...for DATABASE MAINTENANCE??.

All my gateways and repeaters updated to 2690 during the night and my system is explicitly set to NOT UPDATE or use TEST FIRMWARE!!!!!!

JUST ANOTHER REASON NOT TO USE THE OPENMESH DASHBOARD AND GO STANDALONE.

Now, why would everything upgrade itself??.. my EOC-2610's hate 2690 so I keep them at 2688 which has been working perfectly and without issues!!

Can someone tell me what 2690 is all about since I am now updated to a version I did not want to be at??
Back to top
View user's profile Send private message
Sully
Intermediate User
Intermediate User


Joined: 05 Jun 2009
Posts: 105

PostPosted: Wed Feb 17, 2010 10:26 am    Post subject: Reply with quote

Test FW still shows r2688:

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



As of this post all my nodes are reporting in "Late!", although they are operating normally and taking logins at the splash page. I'll see what version they check-in with when the database maintenance is complete and hope they have not upgraded.

Mine too are set to "NOT UPDATE" or use "TEST FIRMWARE".

My production network was hit hard by an update in mid September.

EDIT:
Nodes are set to:
Disable Automatic Upgrades

Sully


Last edited by Sully on Wed Feb 17, 2010 11:03 am; edited 2 times in total
Back to top
View user's profile Send private message
quarbe
Intermediate User
Intermediate User


Joined: 26 Apr 2009
Posts: 97

PostPosted: Wed Feb 17, 2010 10:26 am    Post subject: Reply with quote

I dont know, my network is also down!!
Back to top
View user's profile Send private message MSN Messenger
koelneruwe
Intermediate User
Intermediate User


Joined: 09 Aug 2008
Posts: 97
Location: Cologne, Neubrandenburg

PostPosted: Wed Feb 17, 2010 10:27 am    Post subject: Reply with quote

I am down too, but without upgrading from 2683
Back to top
View user's profile Send private message Visit poster's website
koelneruwe
Intermediate User
Intermediate User


Joined: 09 Aug 2008
Posts: 97
Location: Cologne, Neubrandenburg

PostPosted: Wed Feb 17, 2010 10:38 am    Post subject: Reply with quote

The server is up again.
Back to top
View user's profile Send private message Visit poster's website
mtlowes
Moderator
Moderator


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

PostPosted: Wed Feb 17, 2010 10:46 am    Post subject: Reply with quote

Sully wrote:
Test FW still shows r2688:

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



As of this post all my nodes are reporting in "Late!", although they are operating normally and taking logins at the splash page. I'll see what version they check-in with when the database maintenance is complete and hope they have not upgraded.

Mine too are set to "NOT UPDATE" or use "TEST FIRMWARE".

My production network was hit hard by an update in mid September.

Sully

Thanks.. I know test firmware is set to 2688. I'm curious as to why I am now at 2690?

Really dislike things happening "automatically" and without any control on my part... I am uncertain if I keep them at 2690 or roll them back somehow ..............again

What I am certain of is that I will have my staff begin focused energies to bring a dedicated standalone dashboard and server online as quick as possible. No more playing around..

Am intending to keep a portion of my service offerings in open-mesh at this point so time to get serious and build in-house management and control.
Back to top
View user's profile Send private message
Sully
Intermediate User
Intermediate User


Joined: 05 Jun 2009
Posts: 105

PostPosted: Wed Feb 17, 2010 10:53 am    Post subject: Reply with quote

Quote:
Really dislike things happening "automatically" and without any control on my part... I am uncertain if I keep them at 2690 or roll them back somehow ..............again

Yup... see your point!

My nodes are all checking in now without an upgrade. The only issue I had was the need to power cycle one of the P2HP, it was acting as the Gateway.

EDIT:
I am curious to why yours upgraded...
After checking a little closer, my network is set to:
Disable Automatic Upgrades: Checked
Use Test Firmware: Unchecked

It is a test network, so I am making changes and logging results all the time. These units are about to be deployed soon.

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


Joined: 30 Jan 2009
Posts: 217

PostPosted: Wed Feb 17, 2010 11:02 am    Post subject: hi Reply with quote

my all nodes neighbor empety why?
Back to top
View user's profile Send private message
Sully
Intermediate User
Intermediate User


Joined: 05 Jun 2009
Posts: 105

PostPosted: Wed Feb 17, 2010 11:08 am    Post subject: Reply with quote

Quote:
my all nodes neighbor empety why?


Don't know... give it sometime to settle and check them.
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 17, 2010 11:16 am    Post subject: Reply with quote

Sully wrote:

EDIT:
I am curious to why yours upgraded...
After checking a little closer, my network is set to:
Disable Automatic Upgrades: Checked
Use Test Firmware: Unchecked

It is a test network, so I am making changes and logging results all the time. These units are about to be deployed soon.

Sully


I'd like to know too!.
I have 3 Mesh networks running, two I consider production networks and they are quite profitable.. 1 is a production/test network with patient and adventurous customers that I do development/experimentation on.

Test Network 0: 5 Gateways, 14 repeaters
Prod Network 1: 7 Gateways, 33 repeaters
Prod Network 2: 5 Gateways, 40 repeaters

This is tied in with my mainline WISP services and all gateways tap into and off of my 5.8ghz backbone threaded throughout the community and fed with 3 independent back-hauls to 3 different internet taps.

I don't need 87 units all updating themselves without my consent and to a test revision that is not even in the "test firmware" area to get at...

However, so far its running with the exception of 1 unit which is stuck for some reason with 2690.. so I'll keep a close eye on it and see what happens... Previous tests with r2690 on EOC-2610's didn't go well as the 2610's didn't seem to like the 2690 rev.
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 Feb 17, 2010 11:38 am    Post subject: Reply with quote

these are the changes from 2688 to 2690

Quote:
r2690
- fix bug in logging the traffic generated by users
- extend channel range to channels 12, 13 and 14
- nodes do not auto-upgrade by default
- upgrade server URLs are default to blank and only provided by the user’s dashboard

r2689
- STP support in br-lan bridge is now disabled per default


the only change that could be "hateful" to the EOC-2610 is the extended set of the available channels... but it seems pretty odd.
Maybe tha lack of STP support in the bridge?

What kind of failures are you experiencing in EOC-2610?
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: Wed Feb 17, 2010 12:08 pm    Post subject: Reply with quote

Here is an excerpt from the logread following an EOC-2610 firmware upgrade to 2690 (magically and all by itself!)

Code:
Feb 17 06:12:22 Lightwave-GW02 user.warn kernel: ------------[ cut here ]------------
Feb 17 06:12:22 Lightwave-GW02 user.warn kernel: WARNING: at net/sched/sch_generic.c:223 ()
Feb 17 06:12:22 Lightwave-GW02 user.warn kernel: Modules linked in: ath_ahb wlan_xauth wlan_wep wlan_tkip wlan_ccmp wlan_acl ath_rate_minstrel ath_hal(P) wlan_scan_sta wlan_scan_ap wlan ipt_TTL xt_MARK ipt_ECN xt_CLASSIFY ipt_ttl xt_time xt_tcpmss xt_statistic xt_mark xt_leng
Feb 17 06:12:22 Lightwave-GW02 user.warn kernel: Call Trace:[<80048588>][<80048588>][<8006106c>][<c00ed2b4>][<c00fabb4>][<c017fb24>][<c017f7c8>][<c00f0fb4>][<c017e480>][<c018aaf0>][<c018aa7c>][<80061f5c>][<8018da88>][<80197dd4>][<80197db8>][<80197d10>][<8006ba58>][<8006ba58>]
Feb 17 06:12:22 Lightwave-GW02 user.warn kernel: ---[ end trace 80b77945da098bd6 ]---
Feb 17 06:14:22 Lightwave-GW02 user.info kernel: NETDEV WATCHDOG: wifi0: transmit timed out


After which the unit will lockup and not checkin anymore... This error also occured in the 2 Bullet2HP's I experiment with as Gateways.
However, this morning they seem to be operating... for now.. so see how it goes.
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 Feb 17, 2010 12:14 pm    Post subject: Reply with quote

ok, thanks for reporting.
let us wait and see if that was just an occasional problem.
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: Wed Feb 17, 2010 2:10 pm    Post subject: hi Reply with quote

my all nodes this problem:

root@W:~# update
sending heartbeat...
: WiFi-CPA Heartbeat - Sent to Enterprise Server as Gateway
get node status...
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
grep: /etc/update/nodes: No such file or directory
check dashboard...
update: dashboard updated successfully: checkin #3121
pre-process reply...
root@W:~#

my all nodes neighboar empety why?
this problem only today i see
nodes r2688
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 Feb 17, 2010 2:54 pm    Post subject: Reply with quote

I've just checked your -006 node and seems that it did not receive a correct reply. I forced the dashboard to send a complete reply and now that node has the whole list of the network nodes.

I see that almost your nodes in you network #3 are up from few hours... maybe a power off ?

== UPDATE ==
that's a dashboard problem: the reply contains "cant' connect", ie httpd daemon (Apache ?) could not connect to (MySQL?) db.
I'll write a patch to avoid such "fake" replies.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
jalanmac
Skilled User
Skilled User


Joined: 24 Apr 2008
Posts: 165

PostPosted: Wed Feb 17, 2010 5:00 pm    Post subject: Reply with quote

I have 2 networks and they both behaved as I had expected - 1 upgraded to 2690 and the other one stayed at 2671. The settings I had were:

Network that Upgraded Fine from 2683 (13 working nodes - 4 EOC2610s, 4 EOC1650s, 3OM1Ps, 2 MR3201s)

Disable Automatic Upgrades - unchecked
Use Test Firmware - checked

Network that Didn't Change from 2671 (6 working nodes - 1 EOC1650, 2 OM1ps, 3 MR3201s)

Disable Automatic Upgrades - checked
Use Test Firmware - unchecked
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
Page 1 of 1

 
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.114