#139 - Fix Launcher not starting on Systemd & multiple installations

[forsthug]

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

{Summary of the changes}

Description

{Detail}

Fixes #{issue number}

[volllly]

When running the install command twice I get the following error message from systemd
fiskaltrust-161f695b-98f1-47e8-b99d-f8259b009841.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

#139

[volllly]

Ok so systemd started the launcher correctly but the install command never stopped. The last message was Enable service. and then it hung.

I'm thinking that

middleware-launcher/src/fiskaltrust.Launcher/ServiceInstallation/LinuxSystemD.cs

Line 31 in 8b650f8

return (await ProcessHelper.RunProcess("systemctl", new[] { "enable", _serviceName, "-q" })).exitCode;

this command does wait for something in the launcher to signal that it has started up? 🤔

[forsthug]

When running the install command twice I get the following error message from systemd fiskaltrust-161f695b-98f1-47e8-b99d-f8259b009841.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

#139

The service did not start the middleware before, this was fixed with this PR- The problem of multiple install tries will be fixed now.,

[forsthug]

Ok so systemd started the launcher correctly but the install command never stopped. The last message was Enable service. and then it hung.

I'm thinking that

middleware-launcher/src/fiskaltrust.Launcher/ServiceInstallation/LinuxSystemD.cs

Line 31 in 8b650f8

return (await ProcessHelper.RunProcess("systemctl", new[] { "enable", _serviceName, "-q" })).exitCode;

this command does wait for something in the launcher to signal that it has started up? 🤔

This command is not sending a start event. But when you look at the implementation of Backgroundservice, this is not the way they work. That`s way the timeout is 0 for the systemd service. One reasons way the service never started.

[forsthug]

..

[volllly]

/azp run