Is there a way to restart AIMesh without rebooting the router?

[nsayer]

AIMesh has been just a continuing headache, but I just can't bring myself to permanently abandon it instead of just separate APs.

Is there a way, when it's misbehaving, to log into the router with ssh (I've already enabled this) and restart whatever process is in charge of AIMesh? It'd be a lot less hassle to reboot the nodes and restart the AIMesh process on the router as I'd still be able to keep Ethernet connectivity to the Internet that way.

 

[aex.perez]

SSH into the node, from the comand line on the node, reboot
or from the Router GUI under AiMesh, select a node and select "Reboot Node"

Not to invite opening a can of Worms, but curious what headaches are you dealing with?

 

[nsayer]

SSH into the node, from the comand line on the node, reboot

Right. I know that. What about restarting the AIMesh process on the main router?

 

[nsayer]

SSH into the node, from the comand line on the node, reboot
or from the Router GUI under AiMesh, select a node and select "Reboot Node"

View attachment 65489

Not to invite opening a can of Worms, but curious what headaches are you dealing with?

That's to reboot the node. I want to also restart the AIMesh process on the main router without rebooting it.

Well, at the moment, all of the nodes are blinking blue and show as offline in the web UI. Restarting the nodes doesn't help. This is the third incidence of this _today_. I'd like to be able to bounce whatever it is on the main router that will fix this without having to lose the Internet for 5 minutes.

Other things that I've seen are that the nodes will often show as offline in the web UI despite being perfectly pingable AND hosting WiFi clients perfectly well. In addition, sometimes merely loading the AIMesh page on the web UI will cause the main router to just spontaneously reboot.

 

[aex.perez]

Right. I know that. What about restarting the AIMesh process on the main router?

Don't know the process, but I figure starting it on the router, if you could, would likely restart and disrupt other things for a bit. Probably easier to restart the node and have it rejoin the Mesh.

 

[nsayer]

Don't know the process, but I figure starting it on the router, if you could, would likely restart and disrupt other things for a bit. Probably easier to restart the node and have it rejoin the Mesh.

Restarting the node just makes it blink blue forever after it's done rebooting.

 

[nsayer]

I rebooted the main router and everything came back... for now... but I'd really, really like to be able to do something at the command line to get the main router to accept the nodes without having to reboot the entire thing.

For the record, all of the nodes are connected via 10 GBE switches that are working just fine. Two are BQ16s and one is a BD5 (it's connected at 2.5G, obviously).

 

[degrub]

Are the switches VLAN compatible ? Are they "managed" switches ?
2.5G ports/switch chips can have some compatibility issues between different manufacturers.

 

[nsayer]

Are the switches VLAN compatible ? Are they "managed" switches ?
2.5G ports/switch chips can have some compatibility issues between different manufacturers.

They are all dumb-as-rocks unmanaged switches.

 

[degrub]

And they are smart enough to leave vlan tags on ? Some do strip the tagging.

 

[nsayer]

Not sure how to find that out.

In any event, this isn't something constant. Like, right now everything is working perfectly. I would posit that if the switches were doing something wrong, AIMesh would never work.

 

[ColinTaylor]

I rebooted the main router and everything came back... for now... but I'd really, really like to be able to do something at the command line to get the main router to accept the nodes without having to reboot the entire thing.

For the record, all of the nodes are connected via 10 GBE switches that are working just fine. Two are BQ16s and one is a BD5 (it's connected at 2.5G, obviously).

What is the model number of the primary router?

Try this (just a guess):

service restart_cfgsync

 

[nsayer]

Perfect example. All of these nodes and clients are pingable.

 

[nsayer]

What is the model number of the primary router?

A BQ16

Try this (just a guess):

service restart_cfgsync

Hmm... That seemed to do something very interesting. The AIMesh UI page cleared out, then repopulated over the course of a few seconds. The Mesh node in front of me went from white to blue-blink, then back to white and now the page looks normal.

So I think we have a winner!

 

[aurizn]

Seems like cfg_server process on your AiMesh system got stuck

Do you mind to share the output of this command whenever this happens?

netstat -tnap | grep cfg_server

BTW, you can perform a soft restart of AiMesh via this command, only works on the main unit

It will force to resync wireless configuration to all nodes and restart the WiFi radio

killall cfg_server