1st source created; starting fails

[bobmac]

completely new to NA; created a source, defined it in NA; clicking on start does not start it (no, this is not a joke post)

tcpdump at firewall shows flow is making it through

[eloyd]

How did you install NNA?

[bobmac]

The sysadmins install stuff. Notwithstanding, I don't think they know what the hell they're doing, they have to redo it over and over.

I'll do a tcpdump at the cli Monday AM to verify netflow is getting to NNA. I'm sure it is arriving, what might I do as the next step to debug the non-starting behavior?

[lmiltchev]

What is the version of the Nagios Network Analyzer that you are currently running?

Run the following commands and show us the output:

Code: Select all

uname -a
cat /etc/*release
ps aux | grep nfcapd
which rrdtool
sh /usr/local/nagiosna/bin/nagiosna start
tail /var/log/messages
cat /etc/sudoers.d/nna_conf

[bobmac]

Problem was that I'm not a sysadmin. The sysadmins are the only ones authorized to run commands that require root permissions. That includes starting a SOURCE up. Thanks for the responses above.

If there's anyone else in DoD places who has gotten around this conflict (net eng not allowed to run processes owned by root), maybe you can reply. Until I get a linux cert (in my copious free time), this issue literally can cost days in lost time to get a simple task done.

[eloyd]

Even in my DoE days, we had sudo access.

[slansing]

Unfortunately, having root access, or some form of it, is almost a necessity in most cases when it comes to administrating a monitoring solution such as Nagios, if not required, it is extremely helpful. We'll keep this thread open for a bit to see if anyone who has been in the same spot has any good ideas, or tips for you to bring to the table.

[eloyd]

@lmiltchev listed commands that do not require root to run. You should at least try them out so it's easier to help you.

[lmiltchev]

bobmac, were you able to run these commands?