Database insert causes docker container to crash?
I'm using Zend Framework 2. When I make a request that involves making an INSERT query into the database, the request hangs with no response or error thrown, and running docker ps takes a while and returns this error:
Error response from daemon: The requested address is not valid in its context.
I'd have to restart docker then to get it to work again.
I can make SELECT, UPDATE, AND DELETE queries with no problem.
Now, while debugging, I created a new database and tried to make the same request there, with an INSERT query, same code, same hostname, just a different database name used, and the INSERT worked.
Has anyone run into this kind of problem before? Any hints? Both databases use MyISAM engine.
I'm not sure what other information to include here, please let me know.
UPDATE: This doesn't happen if I perform a DELETE query first before executing the INSERT.
mysql docker zend-framework2
asked Nov 23 '18 at 4:11
herondale
14410
add a comment |
I'm using Zend Framework 2. When I make a request that involves making an INSERT query into the database, the request hangs with no response or error thrown, and running docker ps takes a while and returns this error:
Error response from daemon: The requested address is not valid in its context.
I'd have to restart docker then to get it to work again.
I can make SELECT, UPDATE, AND DELETE queries with no problem.
Now, while debugging, I created a new database and tried to make the same request there, with an INSERT query, same code, same hostname, just a different database name used, and the INSERT worked.
Has anyone run into this kind of problem before? Any hints? Both databases use MyISAM engine.
I'm not sure what other information to include here, please let me know.
UPDATE: This doesn't happen if I perform a DELETE query first before executing the INSERT.
mysql docker zend-framework2
asked Nov 23 '18 at 4:11
herondale
14410
add a comment |
I'm using Zend Framework 2. When I make a request that involves making an INSERT query into the database, the request hangs with no response or error thrown, and running docker ps takes a while and returns this error:
Error response from daemon: The requested address is not valid in its context.
I'd have to restart docker then to get it to work again.
I can make SELECT, UPDATE, AND DELETE queries with no problem.
Now, while debugging, I created a new database and tried to make the same request there, with an INSERT query, same code, same hostname, just a different database name used, and the INSERT worked.
Has anyone run into this kind of problem before? Any hints? Both databases use MyISAM engine.
I'm not sure what other information to include here, please let me know.
UPDATE: This doesn't happen if I perform a DELETE query first before executing the INSERT.
mysql docker zend-framework2
asked Nov 23 '18 at 4:11
herondale
14410
I'm using Zend Framework 2. When I make a request that involves making an INSERT query into the database, the request hangs with no response or error thrown, and running docker ps takes a while and returns this error:
Error response from daemon: The requested address is not valid in its context.
I'd have to restart docker then to get it to work again.
I can make SELECT, UPDATE, AND DELETE queries with no problem.
Now, while debugging, I created a new database and tried to make the same request there, with an INSERT query, same code, same hostname, just a different database name used, and the INSERT worked.
Has anyone run into this kind of problem before? Any hints? Both databases use MyISAM engine.
I'm not sure what other information to include here, please let me know.
UPDATE: This doesn't happen if I perform a DELETE query first before executing the INSERT.
mysql docker zend-framework2
mysql docker zend-framework2
asked Nov 23 '18 at 4:11
herondale
14410
asked Nov 23 '18 at 4:11
herondale
14410
edited Nov 23 '18 at 5:32
asked Nov 23 '18 at 4:11
herondale
14410
asked Nov 23 '18 at 4:11
herondale
14410
asked Nov 23 '18 at 4:11
herondale
14410
14410
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
As a reference for others who will encounter this in the future, the cause for me was referencing a column name with a trailing whitespace (which it should not have), and trying to insert a NULL value into a NOT NULL field.
answered Nov 29 '18 at 3:19
herondale
14410
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%2f53440564%2fdatabase-insert-causes-docker-container-to-crash%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
As a reference for others who will encounter this in the future, the cause for me was referencing a column name with a trailing whitespace (which it should not have), and trying to insert a NULL value into a NOT NULL field.
answered Nov 29 '18 at 3:19
herondale
14410
add a comment |
As a reference for others who will encounter this in the future, the cause for me was referencing a column name with a trailing whitespace (which it should not have), and trying to insert a NULL value into a NOT NULL field.
answered Nov 29 '18 at 3:19
herondale
14410
add a comment |
As a reference for others who will encounter this in the future, the cause for me was referencing a column name with a trailing whitespace (which it should not have), and trying to insert a NULL value into a NOT NULL field.
answered Nov 29 '18 at 3:19
herondale
14410
As a reference for others who will encounter this in the future, the cause for me was referencing a column name with a trailing whitespace (which it should not have), and trying to insert a NULL value into a NOT NULL field.
answered Nov 29 '18 at 3:19
herondale
14410
edited Dec 7 '18 at 8:51
answered Nov 29 '18 at 3:19
herondale
14410
answered Nov 29 '18 at 3:19
herondale
14410
answered Nov 29 '18 at 3:19
herondale
14410
14410
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53440564%2fdatabase-insert-causes-docker-container-to-crash%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
