Netonix Manager / Control Software

[sirhc]

Also - sort by uptime does not work well when the display is mixed between days and no days...
(can't we upload an image/attachment to this forum? Sorry for my ignorance).

viewtopic.php?f=17&t=1593&p=11767&hilit=upload#p11767

viewtopic.php?f=17&t=1546&p=11680&hilit=upload#p11680

viewtopic.php?f=17&t=1467&p=10859&hilit=upload#p10859

[rkelly1]

How do I restart the service? After rebooting a windows pc, the localhost:3443 page doesn't come up. I don't see anything related in services panel to start/restart.
I see the nssm.exe in the Netonix Manager directory but unsure what to put as the service name.

Thanks

[Eric Stern]

The service is called "Netonix Manager". Maybe it didn't install correctly, because it should have started after a reboot, and I'm sure you would have spotted such an obvious name in the services list.

[rkelly1]

Thanks. Definitely not there...if I reinstall will I loose the switch info on 12 switches already setup? Is there a config file I can save?

[rkelly1]

bump

[Eric Stern]

Thanks. Definitely not there...if I reinstall will I loose the switch info on 12 switches already setup? Is there a config file I can save?

You won't lose the config on a reinstall, but if you want to back it up its in C:\Windows\System32\config\systemprofile\AppData\Roaming\Netonix Manager, just back up the whole directory.

[rkelly1]

Worked perfect. Back in action! Thanks!

[aurelien personnaz]

We still have the issue of the app.js process crashing. Do you think it may come from our configuration? (Centos 7, node 4.4.3)

So to restart it automatically I had set up a real systemd service. If someone is interested here is the .service file :

Code: Select all

 

[Unit]
Description=Netonix manager service
[Service]
Type=simple
PIDFile=/var/run/netonix-manager.pid
ExecStart=/usr/bin/node /opt/netonix-manager/app.js
Restart=always
RestartSec=10 # Restart service after 10 seconds if node service crashes
StandardOutput=syslog # Output to syslog
StandardError=syslog # Output to syslog
SyslogIdentifier=netonix-manager
Environment=NODE_ENV=production
WorkingDirectory=/opt/netonix-manager
[Install]
WantedBy=multi-user.target
 

I have not managed to get the bootloader.js running with systemd.
When running the bootloader, if I set the service type to simple it does not monitor the app process, and if I set the service type to forking it awaits for the bootloader to exit on startup, which it does not.

One way to solve my problems would be to terminate the bootloader process if the app process closes. For now you only log the process exit code on a crash, but is there a reason to keep the bootloader process alive if the app process is dead?

Or did I miss a subtlety somewhere?

Thanks for your help.

[Eric Stern]

Have it run app.js directly instead of bootloader.js. It should run, but the self-update function won't work (that functionality is in bootloader.js).

That should help until I figure out why app.js is crashing.

[nriedman]

This is great!! We had been building some scripts to automate a few tasks and this certainly will suffice. Looking forward to the progress.