Replies: 3 comments
-
Having the same issue on one of 5 machines. on Ubuntu. I've made the user not the |
Beta Was this translation helpful? Give feedback.
-
Try removing PrivateTmp=true
PrivateDevices=true
ProtectHome=true
ProtectSystem=full |
Beta Was this translation helpful? Give feedback.
-
I had the same issue on Debian 12 Bookworm. The file Personally, I added the existing user [Service]
User=prometheus
# CapabilityBoundingSet= |
Beta Was this translation helpful? Give feedback.
-
Hello author,
I'm a newcomer to operations, and I've encountered some issues while using your software. I'm eager to receive your guidance.
Firstly, let me explain my use case:
I have configured syslog on an Nginx server, which sends logs to an exporter. This exporter then provides the data to Prometheus. The exporter is deployed on a CentOS 7 server. When I start the service using the command "prometheus-nginxlog-exporter -config-file /path/to/config.hcl", the service starts successfully, and Prometheus successfully retrieves the data.
Next, I wanted to deploy the exporter as a systemd service, and this is where I encountered an issue. When I check the system's message log, I can see the following content:
This seems to suggest a permission issue, but I should have already set the permissions to root. Here is my "prometheus-nginxlog-exporter.service" file:
Could you please help me identify the issue? Thank you for your assistance!
Beta Was this translation helpful? Give feedback.
All reactions