Netonix Forums

Yes

Try connecting to your Ubuntu OS such that you have access to a bash terminal.

Then run the following commands (as root, don't worry, no need to change anything in here)

Code: Select all

cd /opt/network-manager
find * | grep crash.log


Once you've located the crash log

Code: Select all

cat crash.log


and post the contents here.

EDIT: forgot the period, crash.log not crashlog

Crashlog file was located at /opt/network-manager/crash.log and is large. Here are the last 50 lines (the same thing is repeated over and over):

Code: Select all

 :/opt/netonix-manager# tail -50 crash.log
 at Server.listen (net.js:1492: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:188:16)
 at bootstrap_node.js:609: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:1022:11)
 at _exceptionWithHostPort (util.js:1044:20)
 at Server.setupListenHandle [as _listen2] (net.js:1367:14)
 at listenInCluster (net.js:1408:12)
 at Server.listen (net.js:1492: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:188:16)
 at bootstrap_node.js:609: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:1022:11)
 at _exceptionWithHostPort (util.js:1044:20)
 at Server.setupListenHandle [as _listen2] (net.js:1367:14)
 at listenInCluster (net.js:1408:12)
 at Server.listen (net.js:1492: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:188:16)
 at bootstrap_node.js:609:3

Looks like you have two manager's attempting to run at the same time.

What happens if you run:

Code: Select all

/etc/init.d/netonix-manager stop


(Note, obviously this should shut it off, let's see what happens though)

That appears to stop it entirely. I can no longer view it from the web login.

Alright, try rebooting the VM

If you get access back to the Manager from the web page, then run:

Code: Select all

/etc/init.d/netonix-manager start


After that, is the crashing still occurring?

Reboot brings it back up. Web login works, and it shows all the switches. It also shows the warning.

Running the command you suggested shows this:

Code: Select all

 :~# /etc/init.d/netonix-manager start
/usr/bin/nodejs already running.

I can rebuild this if you would prefer, I would just want to know the steps for keeping the switch connections in place.

Before we go that far, try deleting the crash.log file directly first.
It may not have been removed automatically on the reboot. And the crashes may have stopped.

If that doesn't work. Then the next easiest thing to do would be to just re-install the manager, via the deb file.
Which does not override your current setup:

Code: Select all

wget http://forum.netonix.com/netonix-manager/netonix-manager_1.0.16_all.deb
dpkg -i netonix-manager_1.0.16_all.deb


If you decide to go so far as to rebuild the VM
To keep your configurations, make sure you preserve:

Code: Select all

/lib/netonix-manager


I deleted the crash.log file as suggested and the warning is gone. For now, it appears to be working and I'll leave it alone. If it comes back up, I'll come back here.

Thank you for your help.