minio / sidekick

High Performance HTTP Sidecar Load Balancer
GNU Affero General Public License v3.0
546 stars 82 forks source link

Create a sidekick service in Windows Server 2016, but cannot start, error code 1053 is returned #118

Open hwangwenchao opened 1 month ago

hwangwenchao commented 1 month ago

Create a sidekick service in Windows Server 2016, but cannot start, error code 1053 is returned

Expected Behavior

The service can start normally

Current Behavior

In Windows Server2016, I use sc to create a service. The command is as follows: sc create sidekick binPath= "C:\Users\Administrator\Desktop\sidekick\bin\sidekick.exe --insecure --key C:\Users\Administrator\Desktop\sidekick\certs\private.key --cert C:\Users\Administrator\Desktop\sidekick\certs\public.crt --address :44090 --health-path /minio/health/ready https://127.0.0.1:44090" type= own start= auto DisplayName= "sidekick" , the service type is LocalSystem, prompt when starting the service: The service did not respond to the start or control request in time, the error code is 1053

Possible Solution

Steps to Reproduce (for bugs)

  1. check the system event log, Modify the registry ServicesPipeTimeout to 12000ms.

  2. Log in to the machine as administrator, manually execute the service start command, and it can run normally, the command:C:\Users\Administrator\Desktop\sidekick\bin\sidekick.exe --insecure --key C:\Users\Administrator\Desktop\sidekick\certs\private.key --cert C:\Users\Administrator\Desktop\sidekick\certs\public.crt --address :44090 --health-path /minio/health/ready https://127.0.0.1:44090

  3. startup failed like this: sc start sidekick

Context

Regression

Your Environment

jiuker commented 1 month ago

It looks like a file permission issue, can you try to modify the read and write permissions of the file?

hwangwenchao commented 1 month ago

It looks like a file permission issue, can you try to modify the read and write permissions of the file?

the permission like this: Owner : BUILTIN\Administrators Group : WIN-LOAMMITMNHT\None Access : NT AUTHORITY\SYSTEM Allow FullControl BUILTIN\Administrators Allow FullControl WIN-LOAMMITMNHT\Administrator Allow FullControl