Interactive Probe Shell sensor script logs Errors to syslog, that contain just the result, which might be literally the message "empty" - Known Error

Interactive Probe Shell sensor script logs Errors to syslog, that contain just the result, which might be literally the message "empty" Description Interactive Probe Shell sensor script logs Errors to syslog, that contain just the result, which might be literally the message "empty"

Steps to Reproduce

Install Discovery and the Patterns app (which includes the Interactive Probe Shell, that runs when SSH is open in case it might be a Citrix OS Unix for Citrix NetScaler SDX devices) Run Discovery against something with SSH open. Check syslog, or appnode logs for the error messages coming from line 23 of Interactive Probe Shell sensor https:// .service-now.com/discovery_sensor.do?sys_id=7d4d8cbcdbd42010815bd844ca96192e 20: classify: function() { 21: 22: // you can see how the output is logged.. 23: gs.error(JSON.stringify(this.ci_data.output),"output");

If the ecc_queue input looks like this::

empty The app node log looks like this, with no additional explanation. In syslog, there is no clues for what feature it comes from, except maybe the user_id being a MID Server user.

2022-06-10 23:20:09 (157) worker.0 worker.0 txid=adf2ee814744 Discovery: Processing sensor: Interactive Probe Shell (10.x.x.x) 65f2ee814744599ca35d3982e36d43d9 2022-06-10 23:20:09 (168) worker.0 worker.0 txid=adf2ee814744 SEVERE *** ERROR *** *** Script: "empty" 2022-06-10 23:20:09 (239) worker.0 worker.0 txid=adf2ee814744 Discovery: Processed sensors: Interactive Probe Shell (10.x.x.x) in 65f2ee814744599ca35d3982e36d43d9 Workaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.

These errors can be ignored. The don't indicate an error, and the Discovery Status logs, and Device History for the IP, should confirm that the device with SSH enabled did get classified correctly by other Classification probes.