-
Notifications
You must be signed in to change notification settings - Fork 103
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
Resource temporarily unavailable (os error 35) #2742
Comments
Hi @aantn ! |
Hi @aviramha,
|
Any chance it happens when you're on a breakpoint for a while? |
Nope!
…On Fri, Sep 6, 2024, 21:50 Aviram Hassan ***@***.***> wrote:
Any chance it happens when you're on a breakpoint for a while?
#2652 <#2652>
—
Reply to this email directly, view it on GitHub
<#2742 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADYUBZQUVZXLIUE6EGWOGTZVH2PHAVCNFSM6AAAAABNYYEU5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGYZTINRRHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Can you please add this to your configuration? {
"internal_proxy": {
"log_destination": "/tmp/mirrord.log",
"log_level": "mirrord=trace"
}
} Run, then attach the output log when the issue occurs? Make sure to retract sensitive information |
Done. I've sent you the log privately on linkedin after redaction.
…On Sat, Sep 7, 2024 at 10:38 AM Aviram Hassan ***@***.***> wrote:
Can you please add this to your configuration?
{
"internal_proxy": {
"log_destination": "/tmp/mirrord.log",
"log_level": "mirrord=trace"
}
}
Run, then attach the output log when the issue occurs? Make sure to
retract sensitive information
—
Reply to this email directly, view it on GitHub
<#2742 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADYUB43ZIO7JXELJTYWUDTZVKUQ3AVCNFSM6AAAAABNYYEU5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZVGEYDKNJVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I believe this is related to this - #1898 |
User added that it seems to happens when another container it's connected to (Prometheus) is OOM |
Bug Description
Randomly getting this bug:
mirrod then exits
Steps to Reproduce
I don't understand how or why this happens, but it happens regularly.
Backtrace
No response
Relevant Logs
No response
Your operating system and version
Mac OS
Local process
robusta
Local process version
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: