CodeQL now has consant Failed to clean up database cluster directory warnings

[flagrant99]

Select Topic Area

Question

Body

I keep getting this since last update. Anybody know how I can make them stop?

[2024-08-09 00:40:41Z INFO ExecutionContext] Publish step telemetry for current step {
"action": "github/codeql-action/init",
"ref": "v3",
"type": "node20",
"stage": "Post",
"stepId": "c6f1699a-205a-466a-875a-c18e8078df1c",
"result": "succeeded",
"errorMessages": [
"Failed to clean up database cluster directory D:\actions-runner\_work\_temp\codeql_databases. Details: Error: EBUSY: resource busy or locked, unlink 'D:\actions-runner\_work\_temp\codeql_databases\log\build-tracer.log'"
],
"executionTimeInSeconds": 4,
"startTime": "2024-08-09T00:40:37.910391Z",
"finishTime": "2024-08-09T00:40:41.3459658Z"
}.

[rabbitbrother91031]

Hello, @flagrant99

Please consider the following recommendations:

1. Verify Active Processes: Ensure that no other processes or instances of CodeQL are currently accessing the database directory. Concurrent access can lead to file locking issues.

2. Restart the GitHub Actions Runner: If utilizing a self-hosted runner, restarting it may help clear any locks on resources that could be causing the warnings.

3. Manually Clean Temporary Files: Consider manually deleting any temporary files or directories located in the D:\actions-runner\_work_temp\codeql_databases\ path. Exercise caution to ensure only safe-to-remove files are deleted.

4. Update CodeQL Action: Confirm that you are using the latest version of the CodeQL GitHub Action, as updates often include fixes for known issues.

5. Enhance Resource Availability: If multiple workflows are executing simultaneously, consider increasing the resources allocated to your runner to mitigate potential resource contention.

6. Review Permissions: Ensure that the user account executing the GitHub Actions has the necessary permissions to access and modify the relevant directories and files.

[flagrant99]

This does not happen with @v2 on node 16. Only happens with @V3 on node 20. This happens on two different servers consistently. Both do have some new antivirus on them .Will check to see if I can get exclusions for Antivirus. Thx.

[flagrant99]

So it seems this folder is already excluded from antivirus. The file is never there when ever I look so I guess the only thing I can try is add some delay. It seems to be happening in Post Init for CodeQL. Where can I put Delay?

# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
  uses: github/codeql-action/init@v3
  with:
    languages: ${{ matrix.language }}

# We must compile CSharp for CodeQL to analyze it
- name: 👟Write GitHub Runner Context
  working-directory: ${{env.GITHUB_WORKSPACE}}
  env:
    GITHUB_CONTEXT: ${{ toJson(github) }}
  run: |
    Write-Output $env:GITHUB_CONTEXT | Out-File -FilePath .\github_context.json -Force;
    
   
- name: 🔨 BuildQL
  working-directory: ${{env.GITHUB_WORKSPACE}}
  run: pwsh .\.github\ois\codeql\DoCodeQLBuild.ps1
 
  
- name: Perform CodeQL Analysis
  id: analyze
  uses: github/codeql-action/analyze@v3
  with:
    category: "/language:${{matrix.language}}" 

[flagrant99]

I am on GitHub Enterprise Server 3.12.4

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬