MySQL pod crashes when connecting to it from other pods (minikube problem)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm trying to setup Helm chart with some dependencies like MySQL, RabbitMQ and so on and when my actual microservice is starting, the moment when first connection is established to MySQL from the microservice, both instantly crash.
It works with docker-for-desktop but with minikube it doesn't work.
I tried manually to get inside the pod (of microservice and others also) and to try to login to MySQL server (MySQL pod) and it still crashes without any exception
BUT
strange thing is that if I try to login with wrong credentials for first the time it doesn't crash, it shows me an error that wrong credentials are in question and after it if I try with correct ones, it succeeds!
If I try to login from MySQL pod inside MySQL server it logins correctly.
Curl to MySQL port returns version so it works like it should, only the login to MySQL from external pod is the problem.
Does anyone of you have an idea what's going on here?
kubernetes devops minikube 
kubernetes-helm asked Jan 4 at 13:27
DejanDejan
507
add a comment |
I'm trying to setup Helm chart with some dependencies like MySQL, RabbitMQ and so on and when my actual microservice is starting, the moment when first connection is established to MySQL from the microservice, both instantly crash.
It works with docker-for-desktop but with minikube it doesn't work.
I tried manually to get inside the pod (of microservice and others also) and to try to login to MySQL server (MySQL pod) and it still crashes without any exception
BUT
strange thing is that if I try to login with wrong credentials for first the time it doesn't crash, it shows me an error that wrong credentials are in question and after it if I try with correct ones, it succeeds!
If I try to login from MySQL pod inside MySQL server it logins correctly.
Curl to MySQL port returns version so it works like it should, only the login to MySQL from external pod is the problem.
Does anyone of you have an idea what's going on here?
kubernetes devops minikube kubernetes-helm asked Jan 4 at 13:27
DejanDejan
507
kubectl logsmight tell you something informative.
– David Maze
Jan 4 at 14:44
MySQL pod literally nothing but Microservice pod returns me an general exception "java.io.EOFException" but the problem is not with Microservice pod/app, the problem is when I try to login with MySQL Client and it crashes. I think if we solve the basic one problem, microservice as more general should work too.
– Dejan
Jan 4 at 14:52
add a comment |
I'm trying to setup Helm chart with some dependencies like MySQL, RabbitMQ and so on and when my actual microservice is starting, the moment when first connection is established to MySQL from the microservice, both instantly crash.
It works with docker-for-desktop but with minikube it doesn't work.
I tried manually to get inside the pod (of microservice and others also) and to try to login to MySQL server (MySQL pod) and it still crashes without any exception
BUT
strange thing is that if I try to login with wrong credentials for first the time it doesn't crash, it shows me an error that wrong credentials are in question and after it if I try with correct ones, it succeeds!
If I try to login from MySQL pod inside MySQL server it logins correctly.
Curl to MySQL port returns version so it works like it should, only the login to MySQL from external pod is the problem.
Does anyone of you have an idea what's going on here?
kubernetes devops minikube kubernetes-helm asked Jan 4 at 13:27
DejanDejan
507
I'm trying to setup Helm chart with some dependencies like MySQL, RabbitMQ and so on and when my actual microservice is starting, the moment when first connection is established to MySQL from the microservice, both instantly crash.
It works with docker-for-desktop but with minikube it doesn't work.
I tried manually to get inside the pod (of microservice and others also) and to try to login to MySQL server (MySQL pod) and it still crashes without any exception
BUT
strange thing is that if I try to login with wrong credentials for first the time it doesn't crash, it shows me an error that wrong credentials are in question and after it if I try with correct ones, it succeeds!
If I try to login from MySQL pod inside MySQL server it logins correctly.
Curl to MySQL port returns version so it works like it should, only the login to MySQL from external pod is the problem.
Does anyone of you have an idea what's going on here?
kubernetes devops minikube kubernetes-helm kubernetes devops minikube kubernetes-helm asked Jan 4 at 13:27
DejanDejan
507
asked Jan 4 at 13:27
DejanDejan
507
edited Jan 4 at 15:15
Dejan
asked Jan 4 at 13:27
DejanDejan
507
asked Jan 4 at 13:27
DejanDejan
507
asked Jan 4 at 13:27
DejanDejan
507
507
kubectl logsmight tell you something informative.
– David Maze
Jan 4 at 14:44
MySQL pod literally nothing but Microservice pod returns me an general exception "java.io.EOFException" but the problem is not with Microservice pod/app, the problem is when I try to login with MySQL Client and it crashes. I think if we solve the basic one problem, microservice as more general should work too.
– Dejan
Jan 4 at 14:52
add a comment |
kubectl logsmight tell you something informative.
– David Maze
Jan 4 at 14:44
MySQL pod literally nothing but Microservice pod returns me an general exception "java.io.EOFException" but the problem is not with Microservice pod/app, the problem is when I try to login with MySQL Client and it crashes. I think if we solve the basic one problem, microservice as more general should work too.
– Dejan
Jan 4 at 14:52
kubectl logs might tell you something informative.– David Maze
Jan 4 at 14:44
kubectl logs might tell you something informative.– David Maze
Jan 4 at 14:44
MySQL pod literally nothing but Microservice pod returns me an general exception "java.io.EOFException" but the problem is not with Microservice pod/app, the problem is when I try to login with MySQL Client and it crashes. I think if we solve the basic one problem, microservice as more general should work too.
– Dejan
Jan 4 at 14:52
MySQL pod literally nothing but Microservice pod returns me an general exception "java.io.EOFException" but the problem is not with Microservice pod/app, the problem is when I try to login with MySQL Client and it crashes. I think if we solve the basic one problem, microservice as more general should work too.
– Dejan
Jan 4 at 14:52
add a comment |
1 Answer
1
active
oldest
votes
Maybe you can wait for your application to have dependencies ready before requesting them.
You could use readiness probe and init containers to delay your application from starting.
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54039860%2fmysql-pod-crashes-when-connecting-to-it-from-other-pods-minikube-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Maybe you can wait for your application to have dependencies ready before requesting them.
You could use readiness probe and init containers to delay your application from starting.
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
add a comment |
Maybe you can wait for your application to have dependencies ready before requesting them.
You could use readiness probe and init containers to delay your application from starting.
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
add a comment |
Maybe you can wait for your application to have dependencies ready before requesting them.
You could use readiness probe and init containers to delay your application from starting.
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
Maybe you can wait for your application to have dependencies ready before requesting them.
You could use readiness probe and init containers to delay your application from starting.
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
answered Jan 4 at 14:42
Quentin RevelQuentin Revel
75539
75539
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
add a comment |
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
Tried but waiting isn't the problem. Problem is when I simply try to login from microservice Pod (I installed mysql client there just for this test) to MySQL server (on MySQL pod) and it instantly crashes the moment I press an enter.
– Dejan
Jan 4 at 14:55
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54039860%2fmysql-pod-crashes-when-connecting-to-it-from-other-pods-minikube-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
kubectl logsmight tell you something informative.– David Maze
Jan 4 at 14:44
MySQL pod literally nothing but Microservice pod returns me an general exception "java.io.EOFException" but the problem is not with Microservice pod/app, the problem is when I try to login with MySQL Client and it crashes. I think if we solve the basic one problem, microservice as more general should work too.
– Dejan
Jan 4 at 14:52