Our server monitor does not require root privileges to operate correctly, but our install instructions assume root privileges. Here’s the easy workaround:
- download the tarball (in the “other linux” instructions here: https://newrelic.com/docs/server/server-monitor-installation-other-linux)
- unpack and copy as suggested in that article. It’s important to use the init script most relevant to your distribution (redhat or debian). The file locations don’t functionally matter except that the init script looks for stuff where it belongs. So, if anything gets changed (say, moving nrsysmond to /usr/local/sbin) then make sure that you replace all occurrences of that path/location in the init script. Adding “set -x” to the init script as the second line may help diagnose files giving trouble
- be sure to set the RUNAS variable (in the defaults file if extant, it should be settable in the init script directly if not) to whatever you’re going to use to run the binary.
- make sure that relevant files have good permissions: newrelic.cfg, logfile directory (/var/log/newrelic by default), and binary (should be executable by RUNAS user).
Snippet of Power
Download the tarball from https://download.newrelic.com/server_monitor/release/.
Note: If the current version is 1.1.X.YYY, the file will be:
newrelic-sysmond-1.1.X.YYY-linux.tar.gz Extract the tarball
tar xvfz newrelic-sysmond-1.1.X.YYY-linux.tar.gz
Copy the appropriate nrsysmond.x86 or nrsysmond.x64 and nrsysmond.cfg files from the extracted tarball to a location you have access to. Rename the nrsysmond.x86 or nrsysmond.x64 file to nrsysmond
Create a log/ subdirectory navigate to the log/ subdirectory and create an nrsysmond.log file.
Edit the nrsysmond.cfg file. Insert your license key and change the path to the log file to match the path to the nrsysmond.log you created in step 3
Start the Server Monitor by issuing the command
/path/to/nrsysmond -c /path/to/nrsysmond.cfg