-
Notifications
You must be signed in to change notification settings - Fork 91
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
systemd service cannot start #301
Comments
What version of pgMonitor are you using? We'd seen this error in the past as well when trying to use startup options containing multiple |
|
Can you please share the entire contents of your service startup file? Just to make sure if the changes were applied and so we can test with what you have? |
Also noticed that your service file is named differently than the one pgMonitor provides. How are you installing it? |
Thank you for the info. We'll look into it. |
So I do see the |
@leo-minorui So I've included this change in the PR for the PG15 update. It seems like it may have been trying to escape the user of a dollar here according to systemd rules, but may not be needed in this case?
However, I'm still a bit curious how this is breaking for you if we cannot reproduce this on our Rocky test system, nor any other OS's that we test (RHEL8/7, CenOS7, Ubuntu20/22). Do you have anything else customized with the shell for the user that's running the exporter? Or done anything to the bash interpreter since this is explicitly calling bash? |
What version of systemd are you running? This was from a CentOS7 system I have running now
|
Sorry to reply late. For me, the logic of command( > $(echo $OPT | sed 's/.--extend.query-path=([^\ ].yml).*/\1/')") is to combine multiple file contents into a new file named 'queries.yaml' and in my mind , double dollar signs mean process number in bash.
|
Describe the issue:
systemd service cannot start
Describe the expected behavior:
I think double '$$' not good for me:
i can work when i use one '$'
Tell us about your environment:
The text was updated successfully, but these errors were encountered: