Error 1067 during windows service stop #81274

Activity

1. ghost added

   area-Extensions-Hosting

   on Jan 27, 2023
2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jan 27, 2023
4. jgasiorowski commented on Jan 27, 2023

   

   jgasiorowski

   on Jan 27, 2023

   Last edited by jgasiorowski

   Author

   More actions

   Just an update:
   I wanted to try if error 1067 occurs on clean net6 worker service. All I did is I've created a project from template

   dotnet new worker -n TestWorkerFromTemplate --use-program-main true -f net6.0
   

   added package

   dotnet add TestWorkerFromTemplate package Microsoft.Extensions.Hosting.WindowsServices -v 6.0.1
   

   Added UseWindowsService() call on IHostBuilder in Program.cs

   installed windows service with sc.exe create command
   and runned a powershell script to start, stop and check status of that service like:

   $found = $false;
   $count = 0;
   while ($found -eq $false){
       Start-Service AATestWorker
       Start-Sleep -Seconds 1
       Stop-Service AATestWorker
       Start-Sleep -Seconds 1
       $status = & sc.exe query AATestWorker
   
       foreach ($t in $status){
           if ($t -match 'WIN32_EXIT_CODE' -And $t -match '1067'){
               
               echo $status
               $found = $true;
               break;
           }
       };
       $count++;
       echo "Finished attempt #$count"
   }

   I know it might look crazy but I would expect this to be reliable especially that on net core 3.1 we did not have that error ever.
   I've runned this test 3 times. I was waiting for the first time for about 20 minutes to get that error. On second and third attempt I received result quicker (25 and 27 iterations) :

   Finished attempt #18
   Finished attempt #19
   Finished attempt #20
   Finished attempt #21
   Finished attempt #22
   Finished attempt #23
   Finished attempt #24
   
   SERVICE_NAME: AATestWorker
           TYPE               : 10  WIN32_OWN_PROCESS
           STATE              : 1  STOPPED
           WIN32_EXIT_CODE    : 1067  (0x42b)
           SERVICE_EXIT_CODE  : 0  (0x0)
           CHECKPOINT         : 0x0
           WAIT_HINT          : 0x0
   Finished attempt #25
   

   With empty worker it happens less often - but when using our normal service which is using more libraries like Serilog, MassTransit which are using resources mostly from Azure it happens much more frequently

   View from EventViewer
   
5. ericstj commented on Feb 14, 2023

   

   ericstj

   on Feb 14, 2023

   Member

   More actions

   I believe this is the same race condition we found in #62579.

   👍React with 👍1Reacted by Buyaa Namnan
6. jgasiorowski commented on Feb 15, 2023

   

   jgasiorowski

   on Feb 15, 2023

   Author

   More actions

   Thanks @ericstj I think you are right. But I don't know really what is the status of the referenced issue? It is still open but you already found the issue. It is also assigned to Future milestone. Does it mean that there is no plan to fix it for .net 7 or even 8?
7. ericstj commented on Feb 16, 2023

   

   ericstj

   on Feb 16, 2023

   Member

   More actions

   It's a bit of a fundamental design challenge with Windows Services + Hosting that's always been present in some form. It needs folks who own hosting to debate if there is a way to make the models work together.

   As a workaround you can try adding a delay to your main routine after the call to Run() to see if that can help in the short term until the Hosting owners can determine a fix.
8. jgasiorowski commented on Feb 16, 2023

   

   jgasiorowski

   on Feb 16, 2023

   Author

   More actions

   Thanks @ericstj for suggestion. We are also planning to modify our script used for stoping the service to disable it as well - that way we will make sure that service will not start unexpectedly
9. ericstj commented on Feb 16, 2023

   

   ericstj

   on Feb 16, 2023

   Member

   More actions

   If you have a chance to try the delay and report back here, it would be a useful data point to the team. It would confirm we're seeing the same issue.

   👍React with 👍1Reacted by Buyaa Namnan
10. buyaa-n

    added this to the Future milestone on Feb 17, 2023
11. ghost removed

    untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

    on Feb 17, 2023
12. buyaa-n

    added

    needs-author-actionAn issue or pull request that requires more info or actions from the author.An issue or pull request that requires more info or actions from the author.

    on Feb 17, 2023
14. ghost added

    no-recent-activity

    on Mar 3, 2023
17. ghost closed this as completedon Mar 18, 2023
18. ghost locked as resolved and limited conversation to collaborators on Apr 17, 2023