-
Notifications
You must be signed in to change notification settings - Fork 186
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
Failure to start .net-5 function dotnet-isolated: grpc error connection refused #518
Comments
I'm sorry @david-peden-q2, im not sure thats relevant; i'm not specifically, as far as i know, trying to use GRPC; I thought this was some internal error related to the runtime? Is Keyvault using GPRC internally? |
@akatakritos that's correct, the error above is about the internal gRPC communication with the workers, so the User Voice item is not related to the issue. We're investigating a similar issue with Linux and VNet, is this your case by chance? If so, unfortunately, the only current workaround until the issue is resolved is to use VNet with the Windows offerings. |
Thank you, we do have some linux & vnets going on, i'll reach out to my cloud engineer and get back to you. I know we've had some trouble with appservice plans related to the networks in some environments too, and he has a ticket open about that as well. |
We're going to try removing the vnets. They were a nice-to-have feature but we'd rather ship :) |
We removed the vnet from the function service plan and it now runs successfully. Thanks for the hint, never would have guessed at that! |
Get the same error. Linux and Docker setup without VNet |
@jincod can you please open a separate issue with the exception and error details of what you're seeing? @akatakritos thank you for confirming. We're investigating the VNet issue and hope to have that resolved soon. Closing this as resolved. |
Can you update here when the vnet issue is resolved? We'd be interested in re-enabling and trying again. |
We are experiencing the same issue (dotnet-isolated + VNet integration breaks stuff), so leaving a comment to hopefully get notified if it gets resolved. |
Hello, I'm having trouble getting my functions app to boot on a .net functions for linux app service plan.
I have a little HTTP health function and a TimerTrigger. Hitting the /health Function i made with the function key spins for a long time before timing out. Luckily we configured Serilog to write to files during app boot, and this is what I'm seeing in the files when I go visit through Kudu.
Using Serilog to write to files, but heres the start up code:
We previously had some issues with a transitive dependency on ASP.NET Core libraries that caused the app to be unable to boot, but I'm pretty sure those are no longer present; besides, that yielded a different error.
What can I be doing to troubleshoot this?
Update
Also getting this sometimes after i commented out my TimerTrigger function
The text was updated successfully, but these errors were encountered: