-
Notifications
You must be signed in to change notification settings - Fork 3
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
Plugin is not running with the Daemon #4
Comments
So after quite a bit of digging and experimentation, I've found this application quite difficult to daemonize properly on ScientificLinux. What technique does a0labs use? |
Hello, You can have different solutions :
Actually I don't really know your OS, ScientificLinux, never heard about it, and every solutions above work on debian, so I'd bet at least the 2 first would on your OS, not sure about the last one. Best, |
I am going to try upstart, nohup isn't an enterprise option and we want it running as a service. I am going to try writing an upstart job for it. Are you guys open to forks and merge-backs? Potentially a ./daemonization directory for different solutions? |
Alright, yes we can do it. I have also some scripts in order to set it up on debian, I just need to comit them |
Upstart has been working absolutely wonderfully
I am working on a few commits and cleaning it up and then will open a PR for you to review and consider. note: upstart should be cross-platform for almost all modern linux systems as well with no dependencies |
Hello,
I have the plugin successfully running when manually called via python on the command line, however it does not appear to be coming on and running with the newrelic-daemon.
Could I be missing something not documented?
The text was updated successfully, but these errors were encountered: