-
Notifications
You must be signed in to change notification settings - Fork 269
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
doesn't work in background mode #3
Comments
What do you get in the logfile? Check for the path in your config.yml. Absent that, check for a clihelper exception file in /tmp and paste the backtrace from that. |
ok it works now. turns out there was a .pid.lock file that was still there and it for some reason made the rest of the script not work. Removed it and it works now. |
I seem to run into the same scenario. May I know which lock file are you guys refering to? Also I don't see anything process running in the background via ps -ef |
Sure. Try erasing all the files that the agent created and boot it again.
|
These files does not exist even though I have run the command. |
Did you run the command using sudo? |
I'm already running it as the root user. Do I have to use sudo even already root? |
No. Well can't help you then ;( In my case, once I had erased all three files and made sure it wasn't already running (doing a ps -ef | grep agent), then it would work normally. |
Is there a file in /tmp named something like clihelper-exceptions? if so, can you paste the output? |
Make sure that /var/run/newrelic exists and that it is writable |
Ah... now I see it is running in the background.. |
this works and does indeed send data to rpm
this doesn't generate anything, even though i can see it running in ps -ef
The text was updated successfully, but these errors were encountered: