-
Notifications
You must be signed in to change notification settings - Fork 302
Handling of unit names with special characters incorrect #477
Comments
I can't repro with the d_db.service not starting, on both v0.3.2 and HEAD. How big is your cluster? As for the other unit, it looks like we have a URL-encoding issue with the % sign causing it to lose track of the job:
For now, could you choose a different character for your job name? |
I'll also note that systemd itself doesn't support this unit name:
We should obviously fail more gracefully in this case (and prevent you from having submitted the job in the first place); I'll file another ticket for follow up. |
Our cluster size is 3 nodes We use a debian testing with:
starting a.service:
starting d_db.service:
|
Please, we really need help on this issue. |
Could you please clarify what the issue is here exactly? |
As you could not reproduce our issue, we sent you logs of our problem plus informations about software versions. We can starts theses services manually using systemd without problem. Whih other information could be usefull for you ? |
@jonboulle Looks like we might not be serializing dbus paths properly. I used the same unit provided by @tclavier and found this log line:
|
Interesting - is this a bug in systemd? It causes it to completely hang on the machine it seems
|
Yes, systemd hand after this bug. In my logs, systemd seems to be flooded by dbus requests:
|
I have a similar error that appears to occur only if my unit file names have fleetctl version 0.5.0 on my mac; 0.3.3 on core.
|
What version of systemd? I've been really struggling to reproduce this in my own testing. |
We use debian testing :
fleet is the master on github. as a workarround of this bug, we currently encode all our service names in hex string |
Apologies for the confusion and difficulties reproducing this issue. It should now finally be resolved on master and available in the next release! |
Given 3 services files with the same content :
named
When i start service with fleetctl i have 3 outputs :
And fleetctl list-units say :
It's with fleet v0.3.2, with HEAD fleetctl never return for d_db.service, but output of "fleetctl list-units" is the same.
The text was updated successfully, but these errors were encountered: