Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSM: Error when running nsm_sensor with --start and --sensor-name #1637

petiepooo opened this issue Sep 10, 2019 · 3 comments


Copy link

@petiepooo petiepooo commented Sep 10, 2019

I can stop just the sensor apps (netsniff-ng through barnyard2) using any of these commands:

nsm --sensor --stop --sensor-name=myhost-eno2
nsm_sensor --stop --sensor-name=myhost-eno2
nsm_sensor_ps-stop --sensor-name=myhost-eno2

These commands leave the sguild server, bro, and elastic apps running, which is what I expected to happen.

When I use the equivalent command to start them:

nsm --sensor --start --sensor-name=myhost-eno2
nsm_sensor --start --sensor-name=myhost-eno2

the right range of apps are started as expected, but there's another call to some script that gives the following error:

OOPS: Unknown option "--sensor-name=myhost-eno2" found!

The NSMnow Administration scripts are designed to easily configure and manage
your NSM installation. Bugs, comments and flames can be directed to the
SXL team at

The NSMnow Administration scripts come with ABSOLUTELY NO WARRANTY.

Usage: /usr/sbin/nsm_sensor [options]

Interestingly, this command works without the error:

sudo nsm_sensor_ps-start --sensor-name=myhost-eno2

@dougburks dougburks transferred this issue from Security-Onion-Solutions/securityonion-nsmnow-admin-scripts Sep 11, 2019
@dougburks dougburks self-assigned this Sep 11, 2019
@dougburks dougburks added this to To do in via automation Sep 11, 2019
@dougburks dougburks changed the title Error when running nsm_sensor with --start and --sensor-name NSM: Error when running nsm_sensor with --start and --sensor-name Sep 11, 2019
dougburks added a commit to Security-Onion-Solutions/securityonion-nsmnow-admin-scripts that referenced this issue Sep 11, 2019

This comment has been minimized.

Copy link

@dougburks dougburks commented Sep 11, 2019

Hi @petiepooo ,

Can you try out Security-Onion-Solutions/securityonion-nsmnow-admin-scripts@5309f5a and see if that resolves the issue for you?

@dougburks dougburks moved this from To do to In progress in Sep 11, 2019
@dougburks dougburks moved this from In progress to In Testing in Sep 12, 2019

This comment has been minimized.

Copy link

@weslambert weslambert commented Oct 18, 2019

Looks good from my testing 👍

@dougburks dougburks moved this from In Testing to Tested in Oct 19, 2019

This comment has been minimized.

@dougburks dougburks closed this Oct 22, 2019 automation moved this from Tested to Done Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.