Skip to content
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

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

Open
hwangwenchao opened this issue Sep 20, 2024 · 2 comments
Labels
community all incoming issues triage all incoming issues in triage

Comments

@hwangwenchao
Copy link

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

  • Version used (sidekick version): v7.0.2
  • Environment name and version (e.g. nginx 1.9.1):
  • Server type and version: Windows Server 2016 amd64
  • Operating System and version (uname -a): Windows Server 2016
  • Link to your project:
@hwangwenchao hwangwenchao added community all incoming issues triage all incoming issues in triage labels Sep 20, 2024
@jiuker
Copy link
Contributor

jiuker commented Sep 20, 2024

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

@hwangwenchao
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community all incoming issues triage all incoming issues in triage
Projects
None yet
Development

No branches or pull requests

2 participants