Netonix Manager / Control Software

[Eric Stern]

I also just released 1.0.10 to fix a small problem in 1.0.9.

[jakematic]

So... since there is no v8 in the apt repositories, removed nodejs which also removed Manager.

Downloaded the source and spent half an hour compiling node.js 8.11.3 LTS, then tried to re-install and got this:

Code: Select all

root@ubu:/Fedora/Netonix# dpkg -i netonix-manager_1.0.10_all.deb
Selecting previously unselected package netonix-manager.
(Reading database ... 108626 files and directories currently installed.)
Preparing to unpack netonix-manager_1.0.10_all.deb ...
Unpacking netonix-manager (1.0.10) ...
dpkg: dependency problems prevent configuration of netonix-manager:
 netonix-manager depends on nodejs; however:
 Package nodejs is not installed.
dpkg: error processing package netonix-manager (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 netonix-manager
root@ubu:/Fedora/Netonix# dpkg -l | grep -i netonix
iU netonix-manager 1.0.10 all Netonix Manager
root@ubu:/Fedora/Netonix#


Edit: needless to say the service won't start even though it thinks it is sorta installed

[wirelessblue]

Understood. I will try that. I am on Ubuntu 16.04 LTS on this system.

[jakematic]

Understood. I will try that. I am on Ubuntu 16.04 LTS on this system.

Let me know if you have better luck.


For Eric:

Code: Select all

root@ubu:/Fedora/Netonix# which node
/usr/local/bin/node
root@ubu:/Fedora/Netonix# file $(which node)
/usr/local/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=388dfdb03f3d5e08d58f877cb8706d4a27920787, not stripped
root@ubu:/Fedora/Netonix#


[jakematic]

Un-installed the compiled version, and installed v8 with:

Code: Select all

 curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y nodejs

Installed 1.0.10 and it acts like it is working but keeps saying it crashed at the top of the web page.
Do those logs actually get sent to the mothership when we click send ?



Reference: https://nodejs.org/en/download/package- ... tributions


Edit: Tried different browser and cleared all caches, same scenario.
From the log:

Code: Select all




7/12/2018 4:27:03 PM
Version 1.0.10 starting up
 


7/12/2018 4:27:10 PM
Device 'ws6b' (192.168.0.36) changed state to Online
 


7/12/2018 4:27:11 PM
Device 'ws12c' (192.168.0.32) changed state to Online
 


7/12/2018 4:27:12 PM
Device 'ws12b' (192.168.0.31) changed state to Online
 


7/12/2018 4:27:13 PM
Device 'ws12' (192.168.0.30) changed state to Online
 


7/12/2018 4:27:13 PM
Device 'ws6' (192.168.0.35) changed state to Online
 


7/12/2018 4:27:15 PM
Device 'ws12d' (192.168.0.33) changed state to Online
 


7/12/2018 4:27:48 PM
Error in GET /main.html: Error: write EPIPE





[jakematic]

Well I noticed this in the crash log:

Code: Select all


Error: listen EADDRINUSE :::3443
 at Object._errnoException (util.js:992:11)
 at _exceptionWithHostPort (util.js:1014:20)
 at Server.setupListenHandle [as _listen2] (net.js:1355:14)
 at listenInCluster (net.js:1396:12)
 at Server.listen (net.js:1480:7)
 at Object.<anonymous> (/opt/netonix-manager/app.js:729:116)
 at Module._compile (module.js:652:30)
 at Object.Module._extensions..js (module.js:663:10)
 at Module.load (module.js:565:32)
 at tryModuleLoad (module.js:505:12)
 at Function.Module._load (module.js:497:3)
 at Function.Module.runMain (module.js:693:10)
 at startup (bootstrap_node.js:191:16)
 at bootstrap_node.js:612:3
js-bson: Failed to load c++ bson extension, using pure JS version
events.js:183
 throw er; // Unhandled 'error' event
 ^
Error: listen EADDRINUSE :::3443
 at Object._errnoException (util.js:992:11)
 at _exceptionWithHostPort (util.js:1014:20)
 at Server.setupListenHandle [as _listen2] (net.js:1355:14)
 at listenInCluster (net.js:1396:12)
 at Server.listen (net.js:1480:7)
 at Object.<anonymous> (/opt/netonix-manager/app.js:729:116)
 at Module._compile (module.js:652:30)
 at Object.Module._extensions..js (module.js:663:10)
 at Module.load (module.js:565:32)
 at tryModuleLoad (module.js:505:12)
 at Function.Module._load (module.js:497:3)
 at Function.Module.runMain (module.js:693:10)
 at startup (bootstrap_node.js:191:16)
 at bootstrap_node.js:612:3
 


So rebooted, and it claimed it crashed at login, but seems OK now.

Damn... rebooted a Linux SERVER twice today to fix this.... I feel like a Windoze admin

[wirelessblue]

I brought my Ubuntu 16.04 LTS install of nodejs up to 8.11 and Netonix Manager 1.0.9 and I still have the same crash.

Code: Select all


js-bson: Failed to load c++ bson extension, using pure JS version
(node:21241) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:21241) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:21241) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
/opt/netonix-manager/models/Device.js:177
 this.connection.close();
 ^
TypeError: this.connection.close is not a function
 at SSH2Shell.onError (/opt/netonix-manager/models/Device.js:177:37)
 at emitTwo (events.js:126:13)
 at SSH2Shell.emit (events.js:214:7)
 at Client.<anonymous> (/opt/netonix-manager/node_modules/ssh2shell/lib/ssh2shell.js:868:24)
 at emitOne (events.js:116:13)
 at Client.emit (events.js:211:7)
 at Socket.<anonymous> (/opt/netonix-manager/node_modules/ssh2/lib/client.js:300:10)
 at emitOne (events.js:116:13)
 at Socket.emit (events.js:211:7)
 at emitErrorNT (internal/streams/destroy.js:64:8)
 at _combinedTickCallback (internal/process/next_tick.js:138:11)
 at process._tickDomainCallback (internal/process/next_tick.js:218:9)
js-bson: Failed to load c++ bson extension, using pure JS version
/opt/netonix-manager/models/Device.js:177
 this.connection.close();
 ^


[wirelessblue]

I noticed 1.0.10 was just released. I updated to that but kept having crashes (and it said it was running 1.0.8 even though it was supposed to be 1.0.10) so eventually completely removed Netonix Manager and removed the /opt/netonix-manager directory and then reinstalled 1.0.10. That seemed to fix things and I am up and running again. Thank you.

[PeakWiFi]

Thanks for this great management tool!

Would it be possible to add a voltage column to the interface? Most of our units are battery/solar and keeping track of voltages during the winter is critical.

Thanks,
Peak WiFi

[Eric Stern]

Thanks for this great management tool!

Would it be possible to add a voltage column to the interface? Most of our units are battery/solar and keeping track of voltages during the winter is critical.

Thanks,
Peak WiFi

You would probably be better off setting up a real NMS, which would give you alerts, history, graphs, etc. LibreNMS seems to be popular, its free and supports Netonix switches out of the box.