Seeing error below :
"upstream connect error or disconnect/reset before headers. reset reason: connection failure" when tried with below steps:
have created AKS cluster and deployed ASP.NET core docker container. Have installed Istio as per instructions below:
https://learn.microsoft.com/en-us/azure/aks/servicemesh-istio-install?pivots=client-operating-system-windows
Have deployed ASP.NET core docker container in default namespace with istio-injection enabled. Here below is the virtual service and gateway yaml files.
After all this when trying to access http://52.224.26.59/Home/View where 52.224.26.59 is external ip of istio-ingressgateway getting error as "upstream connect error or disconnect/reset before headers. reset reason: connection failure".
I have resolved this issue.
It's because of an issue with an older version of .NET Core version.
Once I updated with .NET Core 3.1, I was able to deploy and access .NET Core WebAPI.
Regarding other issues, there are more challenges and road is not clear with Istio and .NET core combination.
Related
I am using GKE for Jupyterhub deployment. I followed the step given in Documentation but I am facing kernel connection issue.
I am using Helm Chart version 1.2.
Jupyterhub version 1.5
I saw a similar issue posted here: https://github.com/jupyter/notebook/issues/2664, I changed the tornado version but issue still persist.
In the console when I checked It was showing Websocket connection Failure
I strictly follow the instruction on the Play framework and Boxfuse website when deploying the 2.8.x version of the the PLAY SCALA HELLO WORLD TUTORIAL application at https://developer.lightbend.com/start/?group=play&project=play-samples-play-scala-hello-world-tutorial.
When I deployed, I encountered the error "JVM exited with status 255".I was using Openjdk 1.8, Scala Sdk 2.3.14, and Play framework version 2.8.7.
WARNING: Run failed: Time out: Payload of Instance I-############# failed to come up within 300 seconds at http://:9000/
=> ensure your application responds with an HTTP 200 at / on port 9000
=> check the logs for I-############# in prod
=> ensure the healthcheck configuration (healthcheck.port, healthcheck.path, healthcheck.timeout) matches your application
You might have to go to your AWS account and check security and open up your IP ranges
I've installed Istio v1.1.1 and Kiali v0.14 is up running. Per kiali document, Spring boot monitoring is available since v0.16. I'm trying to upgrade the kiali to latest(v0.17) by editing the kiali's deployment file(simply editting image: docker.io/kiali/kiali:v0.14 to v0.17). When I try to login again, the web UI complains "The Kiali secret is missing". See the below screen shot. Actually the secret is already there.
Have you tried the 0.17 deployment descriptor too ?
https://github.com/kiali/kiali/blob/v0.17.0/deploy/kubernetes/deployment.yaml
Note that between versions config might be changed, so just upgrading the image could be not enough.
I have created a standard Windows cluster in AWS Elastic Container Services (ECS) and am trying to deploy an ASP.Net docker image (microsoft/aspnet:4.7.1-windowsservercore-1709) to it and get the following error
Status reason CannotPullContainerError: a Windows version
10.0.16299-based image is incompatible with a 10.0.14393 host
My application is a ASP.Net WebAPI application using .Net Framework 4.6.1.
My docker file is
FROM microsoft/aspnet:4.7.1-windowsservercore-1709
ARG source
WORKDIR /inetpub/wwwroot
COPY ${source:-obj/Docker/publish} .
Can anyone suggest what image I could deploy?
Thanks
Change your FROM to aspnet:4.7.1-windowsservercore-ltsc2016 and it should resolve your issue. Keep in mind the image size for this tag is considerably larger than 1709.
We also got the following message when using AWS ECS:
CannotPullContainerError: a Windows version 10.0.16299-based image is incompatible with a 10.0.14393 host
After a lot of trial and error we found that we were using .NetCore SDK 2.2 and AWS ECS wants 2.1. The developer made changes in Visual Studio 2017 and to the Dockerfile to reference 2.1 instead of 2.2. Once that was done ECS was able to consume it and we had a running state.
Unfortunately the error was not as descriptive and we went down the rabbit hole before discovering what really was our problem.
I have followed this Tutorial to Create simple Java EE 7 Webservices using Netbean 7.3.1. I have Glassfish 4.0 running with Netbeans. I ran project successfully without any problem.
Next Step is to Deploy Webservice project on standalone version of GlassFish 4.0 webserver. So I can run it without Netbeans.
Using Glassfish web interface on http://localhost:4848, and navigating
Common Taks -> Applications -> Deploy
I browse using ("packaged file to be uploaded to the server") and Select the CustomerDB.war file from my project's sub directory /dist/
I have created the war file by running project in Netbean.
But Deployment Failed with following Error.
Error occurred during deployment: Exception while preparing the app : Invalid resource Please see server.log for more details.
When I checked Server Log C:\glassfish4\glassfish\domains\domain1\logs\server.log
It says
[2013-08-20T16:15:07.633+0100] [glassfish 4.0] [INFO] [] [org.glassfish.admingui] [tid: _ThreadID=33 _ThreadName=admin-listener(2)] [timeMillis: 1377011707633] [levelValue: 800] [[
Exception Occurred :Error occurred during deployment: Exception while preparing the app : Invalid resource ]]
UPDATE:
OK I find the solution of above problem as I forget to add the connection.
I just added Connection pool and connection resrouces.
Added JDBC connection pool by navigating Common Tasks -> Resources -> JDBC -> JDBC Connection Pools.
Added the connection Resources by navigating Common Tasks -> Resources -> JDBC -> JDBC Resources
But I am still getting error. This time it is different.
Error occurred during deployment: Exception while deploying the app [CustomerDB] : Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.0.v20130507-3faac2b): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.mysql.jdbc.jdbc2.optional.MysqlDataSource Error Code: 0. Please see server.log for more details.
Any Idea what I am missing?
To Fix First problem, open your glassfish-resource.xml file from your project, it will look something like this.
if you don't have glassfish-resource.xml in server-configuration folder you can also check the these details by clicking on services tab in netbeans and furhter clicking on connection pools as shown in this screenshot.
Based on the information in it, and using Glassfish 4.0 web interface http://localhost:4848
Firstly Create new JDBC connection pool by navigating
Common Tasks -> Resources -> JDBC -> JDBC Connection Pools.
It will look something like this.
Then Secondly create Connection resource by navigating
Common Tasks -> Resources -> JDBC -> JDBC Resources
It will look somehting like this.
First Problem is sorted. you can test it using Ping button in connection pools
For Second problem. (if your ping is not successful do following)
Search mysql-connector-java-5.1.23-bin.jar file in Netbeans installation folder and copy it to Glassfish library folder
C:\glassfish4\glassfish\lib
After copying stop & start server by running following commands in folder C:\glassfish4\glassfish\bin
asadmin.bat stop-domain domain1
asadmin.bat start-domain domain1
After above, deploy the application again and it will successfully deployed and you can access it using test interface
http://localhost:8080/CustomerDB/test-resbeans.html exactly the way as in netbeans.