Stephen wrote:I can confirm this is happening when I try to replicate the scenario. Keep an eye out for an update to the NM
I was disappointed to see that this bug still wasn't fixed in the 1.0.11 NM release that you guys made a few days ago.
I investigated the problem more deeply and finally found the cause.
It is node_modules/ssh2shell's textColorFilter "feature" which seems to be broken (regexp bug?) and filter out valid data passed to netonix-manager/models/Device.js. This could also interfere with other aspects of NM operation and have important negative side-effects.
The patch below (relative to NM 1.0.11) corrects the issue by disabling the textColorFilter.
Marc
--- netonix-manager/models/Device.js.DIST 2019-04-02 14:29:02.000000000 -0400
+++ netonix-manager/models/Device.js 2019-04-06 16:49:08.101375930 -0400
@@ -94,6 +94,7 @@
// but we have to use SSH initially to get the bootid
if (device.bootid == '' || device.web_protocol == '') {
var host = {
+ disableColorFilter: true,
server: {
host: device.deviceInfo.address,
port: device.deviceInfo.ssh_port,
@@ -380,6 +381,7 @@
var device = this;
util.log("Rebooting device " + device.address);
var host = {
+ disableColorFilter: true,
server: {
host: device.deviceInfo.address,
port: device.deviceInfo.ssh_port,
@@ -466,6 +468,7 @@
var data = "";
util.log("Backing up configuration for device " + device.address);
var host = {
+ disableColorFilter: true,
server: {
host: device.deviceInfo.address,
port: device.deviceInfo.ssh_port,
@@ -534,6 +537,7 @@
Device.prototype.getLogAlerts = function (resultCallback) {
var device = this;
var host = {
+ disableColorFilter: true,
server: {
host: device.deviceInfo.address,
port: device.deviceInfo.ssh_port,