Netonix Manager / Control Software

[Stephen]

Well, it would definitely be some work, but the manager allows you to pick the ssh and http port for each switch.
So technically you could accomplish this.

[uberdome]

I went to try this tool, and am having issues (I haven't even started checking switches yet).

Specifically, CPU cycles are maxed, and I cannot access the web interface.

This is a container in Proxmox. It was given 1 CPU and 1 GB RAM.

Procedure:

1. Install Ubuntu 16.04
2. Update 16.04
3. Install Node.js

Code: Select all

apt-get install nodejs



4. Download netonix-manager

Code: Select all

wget https://forum.netonix.com/netonix-manager/netonix-manager_1.0.11_all.deb



5. Install netonix-manager

Code: Select all

dpkg -i netonix-manager_1.0.11_all.deb



6. Attempt to connect at https://10.1.1.5:3443

I cannot connect over the https connection.

The container is running at 99% CPU. If I stop netonix-manager, the CPU usage goes back to 0%.

What step should I take next? [Also, should this be in its own thread?]

[uberdome]

I went to try this tool, and am having issues (I haven't even started checking switches yet).

Specifically, CPU cycles are maxed, and I cannot access the web interface...

I was using Ubuntu 16.04 LTS as that is what we have for the majority of our containers in Proxmox.

I tried Ubuntu 18.04 LTS with the same steps as above, and it worked just fine. Things are working well for me now. If you need help troubleshooting a 16.04 issue, I'm willing to offer that.

[Stephen]

Can you check to see what version of nodejs you are using on 16.04 vs 18.04?

They might be getting different versions and the Netonix Manager is built from nodejs lts v8 (but later versions should still work)

[uberdome]

Can you check to see what version of nodejs you are using on 16.04 vs 18.04?

I ran "nodejs -v" on each.

Ubuntu 18.04 is running nodejs v8.10.0.

Ubuntu 16.04 is running nodejs v4.2.6.


It looks like there is a default repository difference between the two. The version manager or manual installation are both options for 16.04. I'll just stick to 18.04 since it is already up and running.

[Stephen]

That's what I suspected.

If for whatever reason you need to use 16.04 you could still do it by following these instructions:
https://www.digitalocean.com/community/ ... untu-16-04
Go to the section that says "How to install Using a PPA" and it should help you get the latest.

[tomnbb]

The readme for other OS seems to forget a few steps, I changed my tar command to drop it in root because it seems to want to use ./opt/netonix-manager indicating it wants to be in /opt desperately. I did that thinking it might help with its issues with bson but it did not.

Code: Select all

[root@xms netonix-manager]# tar -zxvf netonix-manager-1.0.14.tar.gz --no-same-owner -C /


Code: Select all

 [root@xms netonix-manager]# node bootloader.js
starting child process
{ Error: Cannot find module '../build/Release/bson'
 at Function.Module._resolveFilename (module.js:548:15)
 at Function.Module._load (module.js:475:25)
 at Module.require (module.js:597:17)
 at require (internal/module.js:11:18)
 at Object.<anonymous> (/opt/netonix-manager/node_modules/bson/ext/index.js:15:10)
 at Module._compile (module.js:653:30)
 at Object.Module._extensions..js (module.js:664:10)
 at Module.load (module.js:566:32)
 at tryModuleLoad (module.js:506:12)
 at Function.Module._load (module.js:498:3) code: 'MODULE_NOT_FOUND' }
Express server listening on port 3000
{ Error: ENOENT: no such file or directory, open '/opt/netonix-manager/storage/configs'
 errno: -2,
 code: 'ENOENT',
 syscall: 'open',
 path: '/opt/netonix-manager/storage/configs' }
^C
[root@xms netonix-manager]# mkdir storage
[root@xms netonix-manager]# node bootloader.js
starting child process
{ Error: Cannot find module '../build/Release/bson'
 at Function.Module._resolveFilename (module.js:548:15)
 at Function.Module._load (module.js:475:25)
 at Module.require (module.js:597:17)
 at require (internal/module.js:11:18)
 at Object.<anonymous> (/opt/netonix-manager/node_modules/bson/ext/index.js:15:10)
 at Module._compile (module.js:653:30)
 at Object.Module._extensions..js (module.js:664:10)
 at Module.load (module.js:566:32)
 at tryModuleLoad (module.js:506:12)
 at Function.Module._load (module.js:498:3) code: 'MODULE_NOT_FOUND' }
Express server listening on port 3000

I'm on the latest v8 LTS

Code: Select all

[root@xms netonix-manager]# node -v
v8.16.0

If I do an NPM update it helps but it just loops.

Code: Select all

[root@xms netonix-manager]# npm update
npm WARN deprecated mongodb@1.4.12: Please upgrade to 2.2.19 or higher

> kerberos@0.0.4 install /opt/netonix-manager/node_modules/mongoose/node_modules/kerberos
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory `/opt/netonix-manager/node_modules/mongoose/node_modules/kerberos/build'
  SOLINK_MODULE(target) Release/obj.target/kerberos.node
make: Leaving directory `/opt/netonix-manager/node_modules/mongoose/node_modules/kerberos/build'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/opt/netonix-manager/package.json'
npm WARN netonix-manager No description
npm WARN netonix-manager No repository field.
npm WARN netonix-manager No README data
npm WARN netonix-manager No license field.

+ ejs@2.6.1
+ multer@1.4.1
+ cookie-parser@1.4.4
+ @types/knockout.mapping@2.0.34
+ express@4.17.1
+ morgan@1.9.1
+ request-promise-native@1.0.7
+ node-gyp@3.8.0
+ mongoose@3.9.7
+ ssh2shell@1.9.1
added 42 packages from 87 contributors, removed 1 package, updated 13 packages and audited 1324 packages in 6.295s
found 29 vulnerabilities (4 low, 16 moderate, 9 high)
  run `npm audit fix` to fix them, or `npm audit` for details
[root@xms netonix-manager]# npm audit fix
npm ERR! code EAUDITNOPJSON
npm ERR! audit No package.json found: Cannot audit a project without a package.json

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-06-15T01_43_41_777Z-debug.log
[root@xms netonix-manager]# node bootloader.js
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1

[Stephen]

Try running the following

Code: Select all

export NODE_ENV=production
node bootloader.js


and see if that works, if the first statement isn't executed, the server starts in development mode and doesn't work correctly in a production environment.

[tomnbb]

Code: Select all

[root@xms ~]# cd /opt/netonix-manager/
[root@xms netonix-manager]# export NODE_ENV=production
[root@xms netonix-manager]# node bootloader.js
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1
starting child process
process exit code 1

[Stephen]

Are you executing those statements as root?

Once we isolate what this is I'll update the instructions.