how to fix file not found issue in Linux Cosmos DB emulator

Question

how to fix file not found issue in Linux Cosmos DB emulator

Ruiqi Liu 35

I started encountering file not found issues when starting the Cosmos DB emulator container (Linux version). The error messages are from the Docker container logs.

It worked well last week.

How to know the file path that's being complaint about? (it's Linux version)

Are you aware of relevant changes? What may be possible causes? e.g. dependencies changes? e.g. any releases of the linux version?

How can I specify a specific linux version to use? Where can I see release notes of the linux version?

Please advise. Thanks.

Unhandled Exception: System.AggregateException: One or more errors occurred. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)    at Microsoft.Azure.Documents.Common.ProcessUtil.Run(String fileName, String args)    at Microsoft.Azure.Documents.Common.EtwManifest.<>c__DisplayClass7_0.<UnInstallEtwManifest>b__0()    at Microsoft.Azure.Documents.BackoffRetryUtility`1.<ExecuteRetryAsync>d__5`2.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying(ExceptionDispatchInfo capturedException)    at Microsoft.Azure.Documents.BackoffRetryUtility`1.<ExecuteRetryAsync>d__5`2.MoveNext()    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)    at Microsoft.Azure.Documents.Common.EtwManifest.UnInstallEtwManifest(String manifestFile)    at Microsoft.Azure.Documents.Common.EtwManifest.InstallEtwManifest(String manifestFile)    at Microsoft.Azure.Documents.Services.StartupEntryPoint.ServiceSetupHelper.InstallRuntimeSourceManifest(String manifestPath)    at Microsoft.Azure.Documents.Services.StartupEntryPoint.GatewayServiceSetupCommand.GatewayInit(CodePackageActivationContext context)    at Microsoft.Azure.Documents.Services.StartupEntryPoint.GatewayServiceSetupCommand.<>c.<AddCommand>b__3_1()    at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)    at Microsoft.Azure.Documents.Services.StartupEntryPoint.ServiceStartupEntryPoint.Main(String[] args) Failed to create CoreCLR, HRESULT: 0x8007000E

first last 80 Reputation points

2023-11-10T18:18:03.37+00:00

I have the same issue after pulling the latest cosmos-emulator image.
SSingh-MSFT 16,371 Reputation points Moderator

2023-11-13T05:29:49.1233333+00:00

Hi
Ruiqi Liu •,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Also refer to @first last • comment if that helps in your case.

Thanks.
Ruiqi Liu 35 Reputation points

2023-11-13T18:36:42.5433333+00:00
Thanks for the answer. Changing the memory from 3GB to 4GB helped resolve the issue for me.

For the wslconfig, does it apply if running the Linux version of Cosmos DB emulator on a Linux machine (not involving Windows at all)?

@SSingh-MSFT I am still curious to know why this starts to happen. Can you help with below questions?

Where can I see release notes of the linux version?

How can I specify a specific linux version to use?
Ruiqi Liu 35 Reputation points

2023-11-13T18:40:05.5233333+00:00
The issue was resolved after I changed the memory limit from 3GB to 4GB.

Thanks for the answer.

@SSingh-MSFT I am still curious to know why this started to happen.

Can you help answer below?

Where can I see release notes of the linux version?

How can I specify a specific linux version to use?

if I am running it on Linux machine (not involving Window at all), does the wslconfig matter? (Unsure how to set that)

Thanks!
Ruiqi Liu 35 Reputation points

2023-11-13T18:41:25.05+00:00

oops, sorry about commenting twice. I did not see my 1st comment after I submitted it, so I submitted something else.
SSingh-MSFT 16,371 Reputation points Moderator

2023-11-14T09:46:51.7666667+00:00

Hi
Ruiqi Liu •,

Glad to know that the issue is solved.

Regarding your other questions, I would recommend you to raise question on GitHub page as mentioned in the Answer so that concerned team could address these.

Thanks. Have a great day!

Accepted answer

1 additional answer

Your answer

first last 80 Reputation points

2023-11-10T18:18:03.37+00:00

I have the same issue after pulling the latest cosmos-emulator image.
SSingh-MSFT 16,371 Reputation points Moderator

2023-11-13T05:29:49.1233333+00:00

Hi
Ruiqi Liu •,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Also refer to @first last • comment if that helps in your case.

Thanks.
Ruiqi Liu 35 Reputation points

2023-11-13T18:36:42.5433333+00:00

Thanks for the answer. Changing the memory from 3GB to 4GB helped resolve the issue for me.

For the wslconfig, does it apply if running the Linux version of Cosmos DB emulator on a Linux machine (not involving Windows at all)?

@SSingh-MSFT I am still curious to know why this starts to happen. Can you help with below questions?

Where can I see release notes of the linux version?

How can I specify a specific linux version to use?
Ruiqi Liu 35 Reputation points

2023-11-13T18:40:05.5233333+00:00

The issue was resolved after I changed the memory limit from 3GB to 4GB.

Thanks for the answer.

@SSingh-MSFT I am still curious to know why this started to happen.

Can you help answer below?

Where can I see release notes of the linux version?

How can I specify a specific linux version to use?

if I am running it on Linux machine (not involving Window at all), does the wslconfig matter? (Unsure how to set that)

Thanks!
Ruiqi Liu 35 Reputation points

2023-11-13T18:41:25.05+00:00

oops, sorry about commenting twice. I did not see my 1st comment after I submitted it, so I submitted something else.
SSingh-MSFT 16,371 Reputation points Moderator

2023-11-14T09:46:51.7666667+00:00

Hi
Ruiqi Liu •,

Glad to know that the issue is solved.

Regarding your other questions, I would recommend you to raise question on GitHub page as mentioned in the Answer so that concerned team could address these.

Thanks. Have a great day!

Answer 1

first last 80

I was able to fix this by changing my docker-compose for cosmosdb to have mem_limit: 4GB adding a C:\Users\<UserName>\.wslconfig file, and restarting docker desktop, then the cosmos emulator container was able to start successfully. The contents of the .wslconfig file should be as listed in this github issue comment https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/77#issuecomment-1798588144.

Answer 2

SSingh-MSFT 16,371 Moderator

Hi
Ruiqi Liu •,

Welcome to Microsoft Q&A.

As I understand, you are getting File not found error in Cosmos DB Linux Emulator.

Possible causes of file not found issues could be:

1). changes to the container image or dependencies,

2). changes to the host environment, or changes to the configuration of the container.

3). It's also possible that the file was deleted or moved since the last time the container was started.

I would recommend you to please file a support ticket for deeper investigation and in case if you don't have a support plan, do let us know here so that we can check on other options to unblock you.

Thanks

Vikas Singh 0 Reputation points Microsoft Employee

2023-12-19T07:40:56.76+00:00

Hi @Ruiqi Liu , can you please share the command line (or docker compose section) which you were using to start Emulator when facing problem. This is to see if this error is due to any large resource allocation. i.e. Partition count etc.

Share via

how to fix file not found issue in Linux Cosmos DB emulator

1 additional answer

Your answer