Netonix Manager / Control Software

[kakadaudi]

Are you on 1.07 ? That seem to crash a hell of a let less on Ubuntu than it used to.
Restarting the service makes it very unhappy, have to reboot mine too on 16.04.3 LTS.
Yes I'm on 1.07


Have you tried by IP address ?
Didn't matter whether using the IP address or fqdn. It still crashed. I'm not sure who if at all anyone checks this crash report logs.


Unless your FQDN is actually netonix.company.com that doesn't look right to me...
Yes i have all my services with an A record in my NS.


EDIT: forgot to add - my 1.03 (-ish) did not upgrade well to 1.07 so I did an apt-get remove and then cd'd to /var/lib and recursively remove netonix-manager which seemed to help a lot[/quote]
I actually followed your advice and uninstalled the manager, purged the netonix manager dir in var lib and reinstalled it afresh.

Im now stuck trying to discover new devices in the network. I get "Scanning, completed 512 of 65534, found 0 new devices
" for a 10.10.0.0/16 scan.

[kakadaudi]

Are you on 1.07 ? That seem to crash a hell of a let less on Ubuntu than it used to.
Restarting the service makes it very unhappy, have to reboot mine too on 16.04.3 LTS.
Yes I'm on 1.07


Have you tried by IP address ?
Didn't matter whether using the IP address or fqdn. It still crashed. I'm not sure who if at all anyone checks this crash report logs.


Unless your FQDN is actually netonix.company.com that doesn't look right to me...
Yes i have all my services with an A record in my NS.


EDIT: forgot to add - my 1.03 (-ish) did not upgrade well to 1.07 so I did an apt-get remove and then cd'd to /var/lib and recursively remove netonix-manager which seemed to help a lot

I actually followed your advice and uninstalled the manager, purged the netonix manager dir in var lib and reinstalled it afresh.

Im now stuck trying to discover new devices in the network. I get "Scanning, completed 512 of 65534, found 0 new devices
" for a 10.10.0.0/16 scan. [/quote]

A bit impatient on my side, the scan is progressing a couple of devices have been found. I hope the frequent crashes will stop now with the re-install of the manager.

[tonym]

Systemd init script, just place in /etc/systemd/system:

Code: Select all

[Unit]
Description=Netonix Manager
After=network.target

[Service]
Type=simple
Environment=NODE_ENV=production
WorkingDirectory=/opt/netonix-manager
ExecStart=/usr/bin/nodejs bootloader.js
Restart=on-failure

[Install]
WantedBy=multi-user.target


[sakita]

Netonix Manager 1.0.7 is not backing up all our configs.

Tested with a few switches... make a simple change (e.g. port name) and then check the 'configs' tab in the manager to see if a fresh backup shows up.

The ones with 1.4.8 get backed up. Those with 1.4.9 and 1.5.0rc4 do not get backed up.

Also checked between a working switch and non-working switch and didn't see any obvious config page differences.

Is anyone else seeing this issue?

[jakematic]

Just changed a port name on a WS-6 on 1.4.9 and it backed up the config.

I have noticed in the past it was taking more time until I rebooted the box Manager is running on.
Maybe restart Manager or reboot the machine it lives on ?

Code: Select all

Apr 21 05:48:46 UI: Log cleared by Netonix Manager (192.168.0.141)
May 10 11:54:38 UI: Configuration changed by admin (192.168.0.141)
May 10 11:54:38 UI: Port 3 Name: changed from 'Southeast Camera' to 'SouthEast Camera'
May 10 11:59:41 UI: Configuration changed by admin (192.168.0.141)
May 10 11:59:41 UI: Port 3 Name: changed from 'SouthEast Camera' to 'Southeast Camera'


Code: Select all



TimestampMessage



5/10/2018 11:54:42 AM
Backing up configuration for device 192.168.0.36
 


5/10/2018 11:54:45 AM
192.168.0.36: Backed up configuration to 192.168.0.36_WS-6-MINI_ws6b_12.ncfg
 


5/10/2018 11:59:46 AM
Backing up configuration for device 192.168.0.36
 


5/10/2018 11:59:49 AM
192.168.0.36: Backed up configuration to 192.168.0.36_WS-6-MINI_ws6b_13.ncfg





[sakita]

Thanks jakematic! Never underestimate the power of a reboot

It looks like it grabbed the configs for all of the switches I tested as well.

[Eric Stern]

Version 1.0.8 is out. This should work better for people with many switches and scanning large subnets.

[jakematic]

Hi Eric-

I had upgraded from 1.07 to 1.08 via the GUI and everything was working fine, except that dpkg showed 1.07 still.

Today it prompted me to go to 1.09 and I said OK.
It came back up and the log showed v1.08 and asked to upgrade again. Tried again, same.

Downloaded the .deb and installed it and now it crashes.
Once it asked to send a log to you but am not sure it did.

Below is after a reboot of the Ubuntu 16 server it is running on.
When I try to go to Manager in Chrome it says connection refused.

Here is what I'm seeing:

Code: Select all

root@ubu:/etc/init.d# ps -ef | grep bootload
root 763 1 0 11:20 ? 00:00:00 /usr/bin/nodejs bootloader.js
root 4716 3067 0 11:24 pts/0 00:00:00 grep --color=auto bootload
root@ubu:/etc/init.d# service netonix-manager stop
root@ubu:/etc/init.d# service netonix-manager start
root@ubu:/etc/init.d# service netonix-manager --status
Usage: /etc/init.d/netonix-manager {start|stop|restart}
root@ubu:/etc/init.d# service netonix-manager status
● netonix-manager.service - LSB: Start daemon at boot time
 Loaded: loaded (/etc/init.d/netonix-manager; bad; vendor preset: enabled)
 Active: active (running) since Thu 2018-07-12 11:24:44 EDT; 13s ago
 Docs: man:systemd-sysv-generator(8)
 Process: 4816 ExecStop=/etc/init.d/netonix-manager stop (code=exited, status=0
 Process: 4849 ExecStart=/etc/init.d/netonix-manager start (code=exited, status
 CGroup: /system.slice/netonix-manager.service
 ├─4853 /usr/bin/nodejs bootloader.js
 └─4969 nodejs app.js
Jul 12 11:24:44 ubu systemd[1]: Starting LSB: Start daemon at boot time...
Jul 12 11:24:44 ubu systemd[1]: Started LSB: Start daemon at boot time.
root@ubu:/etc/init.d# dpkg -l | grep -i netonix
ii netonix-manager 1.0.9 all Netonix Manager
root@ubu:/etc/init.d#


Let me know if you need anything else. Thanks-Jake

[wirelessblue]

I installed Netonix Manager 1.0.9 as well and the crash log mentions that it cannot find js-bson. That seems to be the core of the problem. I reverted to 1.0.8 which still works fine.

[Eric Stern]

In 1.0.9 I updated some of the libraries and it now requires node v8 or higher. Previously we only required node v4, which is now EOL.

Recommend installing node v8 LTS. I've updated the documentation to reflect this.