You are here

Home » Forums » General discussion

OLSR not running error sometimes 3.16.1.0b02

9 posts / 0 new
Topic locked
Last post
Thu, 04/14/2016 - 21:29
#1
KA7HAK
KA7HAK's picture
OLSR not running error sometimes 3.16.1.0b02

I get the following message when going to mesh status. It has only happened a couple of times. Goes away when I power cycle the node.

Whoops! OLSR is not running, try again later.

 

 node: KA7HAK-ROUTER
model: Ubiquiti AirRouter

!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xe4a2
Device has not been tested. Please file a ticket with your experiences.

eth0   6A:72:51:49:2D:04
eth0.0 6A:72:51:49:2D:04
eth0.2 6A:72:51:49:2D:04
eth1   68:72:51:49:2D:04
wlan0  68:72:51:48:2D:04
wlan0-1 68-72-51-48-2D-04-00-44-00-00-00-00-00-00-00-00

/proc/cpuinfo
system type		: Atheros AR7241 rev 1
machine			: Ubiquiti AirRouter
processor		: 0
cpu model		: MIPS 24Kc V7.4
BogoMIPS		: 259.27
wait instruction	: yes
microsecond timers	: yes
tlb_entries		: 16
extra interrupt vector	: yes
hardware watchpoint	: yes, count: 4, address/irw mask: [0x0000, 0x0ff8, 0x0ff8, 0x0ff8]
isa			: mips1 mips2 mips32r1 mips32r2
ASEs implemented	: mips16
shadow register sets	: 1
kscratch registers	: 0
core			: 0
VCED exceptions		: not available
VCEI exceptions		: not available


nvram
hsmmmesh.settings=settings
hsmmmesh.settings.wifimac=68:72:51:48:2d:04
hsmmmesh.settings.mac2=72.45.4
hsmmmesh.settings.dtdmac=73.45.4
hsmmmesh.settings.config=mesh
hsmmmesh.settings.node=KA7HAK-ROUTER
Top
Thu, 04/14/2016 - 22:30
KG6JEI
Please attach a supportdata
Please attach a supportdata file from a time where the issue occurs.
Top
Thu, 04/14/2016 - 22:32
K5DLQ
K5DLQ's picture
Can you attach a supportdata
Can you attach a supportdata dump?   Setup - > (login) -> Administration -> at the bottom.. "Downloads Support Data"
Top
Thu, 08/25/2016 - 00:06
N2MH
N2MH's picture
Just happened to me

I saw the same thing after rebooting my tunnel node. Running 3.16.1.0 on a Nano M2. Support file attached.

Support File Attachments: 
File supportdata-N2MH-FieldTun0-201608250359.tgz
Top
Fri, 08/26/2016 - 00:41
(Reply to #4)
AE6XE
AE6XE's picture
N2MH,   Did you do the minor
N2MH,   Did you do the minor surgery-edit of the tunnel config to turn off compression over the tunnel?  With 6 tunnels on this client, out-of-memory issues are a good possibility.    I don't see anything in the support data, other than OLSR restarted 3 times in rapid succession, then was gone.    OOM issues are difficult to detect in this data, however, OLSR is at the top of the selection list for the kernel to kill, so there's a strong smell here.   With this tunnel config change, the memory consumption of 6 client connections frees up ~3M of RAM (with only 32M in a NS).
Top
Fri, 08/26/2016 - 01:45
(Reply to #5)
k1ky
k1ky's picture
Help for Tunnel "Clients"?
Does this memory release modification help units that are only connecting as a Tunnel Client?  I've just modified my Tunnel Servers only so far.
 
Top
Fri, 08/26/2016 - 10:42
(Reply to #6)
AE6XE
AE6XE's picture
It is a config change on the
It is a config change on the tunnel 'server'.  Compress settings are set by the server and the clients follow suit.
Top
Wed, 12/28/2016 - 22:23
W8XG
OSLR not running

I just put in a couple of IP reservations into my NSM2 and when checking Mesh Status, got the OSLR not running. I booted with no change. Then I deleted the reserved IP's, and It's "fixed". Not sure what the problem is??

Top
Wed, 12/28/2016 - 22:40
(Reply to #8)
KG6JEI
3.16.1.0b02 was a beta
3.16.1.0b02 was a beta release for 3.16.1.0 and it has been superceeded by the official release of 3.16.1.0. Being a beta build that has been superceeded by an official release the beta is no longer supported.

If this is still an issue in a current version and you can duplicate it  you would likely want to open a ticket in the bug tracker ( http://bloodhound.aredn.org ) along with a support data file.
Top
Topic locked

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer