Netonix Manager / Control Software

[sirhc]

Where do I report errors ?

On Windows 7 I sometimes has to restart the service. It's like the program hangs....

When can we expect new version ?

Here is where you report problems.
Maybe describe your server, OS version, and check and see if there is anything in the WINDOWS logs

Maybe post up what you have it doing

[jjonsson]

Sorry,

I have it running on both Windows 7 and Windows 2012 R2 server. After some days, a couple of weeks or something like that, it just stop answering on the port. Restart the service and it runs again....

Nothing to see in any log. Only that NSSM is stopped/started.....

[PBX-Tech]

This tool is a great idea, thanks for creating it. I find it very useful. Scheduled firmware updates is working great.

Feature requests:
1 )Auto GUI login on the Web UI button - I see someone already made the suggesting and its due on a future release. Thanks.
2) Option to send Logs to remote/local server

[sirhc]

This tool is a great idea, thanks for creating it. I find it very useful. Scheduled firmware updates is working great.

Thanks, work in progress.

1 )Auto GUI login on the Web UI button - I see someone already made the suggesting and its due on a future release.

You have to load v1.4.0rc9 firmware on the switch then it will Auto Log In to Switches

2) Option to send Logs to remote/local server

I guess we could add SYS LOG but this software is on a server and thus can have very long logs. I was thinking of making it so all the switches could dumped their logs here to preserve logs after reboots and you could view the logs from the manager and have it auto prune the switch logs based on number of days old?

[PBX-Tech]

You have to load v1.4.0rc9 firmware on the switch then it will Auto Log In to Switches

I now have rc10 and auto gui login is working great.

I guess we could add SYS LOG but this software is on a server and thus can have very long logs. I was thinking of making it so all the switches could dumped their logs here to preserve logs after reboots and you could view the logs from the manager and have it auto prune the switch logs based on number of days old?

This would work too. Definitely prune/logrotate either by day or size.

[ryanm]

This deployed very easily on a win2012r2 box. Doing some switch upgrade testing now. Is it bad that I have enough switches to justify having this deployed?

[sirhc]

Eric will soon be releasing an upgrade for Manager.

It should update itself if it has access to the net and you let it do the upgrade.

[aurelien personnaz]

Great tool!
Clean, simple, and working perfectly.
The only "bug" I have seen is the Test SMTP feature in the configuration which did not work at first.
I had entered my settings, the test failed, double checked and tested again, failed again. So I gave up and upgraded a switch. Then I tried again and it worked... Really not a big deal anyway.

I was going to ask for a batch upgrade feature... but it's already there :)

[aurelien personnaz]

We have scheduled a batch upgrade for tonight that failed.
Here are the logs :

22/4/2016 11:11:21 Version 1.0.0rc5 starting up
22/4/2016 11:11:22 Starting scheduled upgrade
22/4/2016 11:11:22 Not upgrading 172.17.0.17, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.100, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.34, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.60, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.20, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.80, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.32, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.120, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.150, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.160, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.10, device is not available
22/4/2016 11:11:22 Not upgrading 172.17.0.220, device is not available
22/4/2016 11:11:22 Not upgrading 172.18.190.254, device is not available
22/4/2016 11:11:22 Scheduled upgrade complete, 0 of 13 devices successfully upgraded

I'm in France and the network in California so the time is actually 02:11:22 AM :)

So, the first thing is that the app had crashed (the node app.js process was dead) when the upgrade was originally scheduled (01:35 AM). And the upgrade started as soon as I restarted the app. That could be an issue if the process is restarted in the middle of the day and it triggers some downtime for the users.

As for the reason of the crash, it may be because I have finally installed it on a CentOS server. I did not manage (not much time to spend on that) to turn it into a nice systemd service so I've just edited the init script you provided to run the start.sh and stop.sh scripts. And it happened a few times that the app.js process died (not the bootstrap.js though).
The server runs node 4.4.3
Do you have an idea why it would crash? Turning it into a systemd service would make sure that both processes are restarted on a crash, but the crashes would happen anyway.

We had another minor issue. After the above crash and recovery, one of the switch was always marked as down, even though all the others were ok, and the switch itself was working fine. I tried to remove it from the list and add it back and it finally showed up. This one is a WS-6-MINI.

One minor improvement would also be to display the system time on the main screen to help scheduling the upgrades.

[yahel]

Also - sort by uptime does not work well when the display is mixed between days and no days...