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

How to debug an infinite loop? #10841

Open
1 task done
amir-ziaei opened this issue May 16, 2024 · 2 comments
Open
1 task done

How to debug an infinite loop? #10841

amir-ziaei opened this issue May 16, 2024 · 2 comments
Labels
area: configuration Configuring LocalStack status: response required Waiting for a response from the reporter type: bug Bug report

Comments

@amir-ziaei
Copy link

amir-ziaei commented May 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When I run Localstack, it goes into an infinite loop. I'd like to get insights on why this is the case and how I should approach debugging it.
It's most likely due to my init script. I don't know what exactly I'm doing wrong there. Ideally, I want Localstack to tell me I'm doing something wrong and error out. However, little information is shown in the console and I have to basically rely on guess and luck to find the source of the problem.

The log I keep seeing in the loop is:

2024-05-16T13:34:19.531 DEBUG --- [et.reactor-6] rolo.gateway.wsgi          : POST localhost:4566/

It keeps printing this into the console in a loop and eats all my machine's resources. How can I debug this issue?

Expected Behavior

  • Give better log insights and instruments to debug
  • Perhaps prevent looping, and just kill the process or something

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

I can't share my init file because it's a proprietary project.

Environment

- OS:
- LocalStack:
  LocalStack version:
  LocalStack Docker image sha:
  LocalStack build date:
  LocalStack build git hash:

https://hub.docker.com/layers/localstack/localstack/latest/images/sha256-c79f44d73da47789652d38168c96d0f1f7926ea608c390e36e85de022e3e4841?context=explore

Anything else?

No response

@amir-ziaei amir-ziaei added status: triage needed Requires evaluation by maintainers type: bug Bug report labels May 16, 2024
@localstack-bot
Copy link
Collaborator

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

@Anze1508 Anze1508 added area: configuration Configuring LocalStack status: backlog Triaged but not yet being worked on and removed status: triage needed Requires evaluation by maintainers labels May 17, 2024
@thrau
Copy link
Member

thrau commented May 19, 2024

to increase the log level you can set LS_LOG=trace-internal, which should give you more indication of where requests are coming from

@thrau thrau added status: response required Waiting for a response from the reporter and removed status: backlog Triaged but not yet being worked on labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: configuration Configuring LocalStack status: response required Waiting for a response from the reporter type: bug Bug report
Projects
None yet
Development

No branches or pull requests

4 participants