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

Container is marked as unhealthy when "routePrefix" is empty #8

Open
slyons opened this issue Nov 7, 2022 · 1 comment
Open

Container is marked as unhealthy when "routePrefix" is empty #8

slyons opened this issue Nov 7, 2022 · 1 comment

Comments

@slyons
Copy link

slyons commented Nov 7, 2022

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Follow example of using FastAPI on Azure Functions

Any log messages given by the failure

Container logs:

2022-11-07T05:03:23.905498754Z Starting OpenBSD Secure Shell server: sshd.
2022-11-07T05:03:25.784337592Z Hosting environment: Production
2022-11-07T05:03:25.784372792Z Content root path: /azure-functions-host
2022-11-07T05:03:25.784378492Z Now listening on: http://[::]:80
2022-11-07T05:03:25.784381892Z Application started. Press Ctrl+C to shut down.

Service log:

2022-11-07T05:01:48.563Z INFO  - Initiating warmup request to container <name>-dtest_0_975e4ee4 for site <name>-dtest
2022-11-07T05:02:07.615Z ERROR - Container <name>-dtest_0_975e4ee4 for site <name>-dtest has exited, failing site start
2022-11-07T05:02:07.627Z ERROR - Container <name>-dtest_0_975e4ee4 didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.

Expected/desired behavior

Service would start and would be accessible. It works just fine locally.

OS and Version?

Linux Container with non-consumption App Service Plan

Versions

4.0.4829 local, latest deployed

Mention any other details that might be useful

Once I adjusted the routePrefix to be "api" again it started working, had to re-write a bunch of code to be at a different base URL.

@pamelafox
Copy link
Contributor

I'm unable to replicate this issue, after deploying this repo to Azure Functions, keeping the current routePrefix of empty string. A few questions:

  1. Did you deploy to Azure Functions? Did you do that via VS Code or via a CLI or via Portal?
  2. Did you change the code in any other way? Can you point at the exact code that has the issue? (You could upload it)
  3. Where did you get those logs from? (I want to get the same logs for comparison)

Sorry for delay in responding, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants