Socket hangs after upgrade from Debian 9.7 to 9.8What's the difference between Unix socket and TCP/IP...
Is a party consisting of only a bard, a cleric, and a warlock functional long-term?
Can I use USB data pins as a power source?
Could this Scherzo by Beethoven be considered to be a fugue?
How difficult is it to simply disable/disengage the MCAS on Boeing 737 Max 8 & 9 Aircraft?
Are ETF trackers fundamentally better than individual stocks?
Why is the President allowed to veto a cancellation of emergency powers?
What is the adequate fee for a reveal operation?
Why do newer 737s use two different styles of split winglets?
Do I need life insurance if I can cover my own funeral costs?
Are all passive ability checks floors for active ability checks?
Happy pi day, everyone!
Describing a chess game in a novel
How to prove the triangle inequality for this metric space
Professor being mistaken for a grad student
Does multi-classing into Fighter give you heavy armor proficiency?
Have the tides ever turned twice on any open problem?
New passport but visa is in old (lost) passport
Does .bashrc contain syntax errors?
Violin - Can double stops be played when the strings are not next to each other?
How to pronounce "I ♥ Huckabees"?
Is it insecure to send a password in a `curl` command?
Recruiter wants very extensive technical details about all of my previous work
Why Choose Less Effective Armour Types?
et qui - how do you really understand that kind of phraseology?
Socket hangs after upgrade from Debian 9.7 to 9.8
What's the difference between Unix socket and TCP/IP socket?update from debian lenny to squeezeMake PHP-FPM Listen at 'IPAddress:Port' Instead of '/var/run/php5-fpm.sock;'socket timeout exception on ubuntuLSI 3Ware tw_cli and tdm2 segfault with Debian Linux kernels after 3.8Debian upgrade Nginx from sourcenginx php5-fpm “File not found” — FastCGI sent in stderr: “Primary script unknown”LDAP_route not working after upgrade from Debian Lenny to WheezyWill debian update packages that I've personally build from their official sources?504 timeout after migrating from Ubuntu to Debian server
I have a frontend with Nginx talking to Puma over a Unix socket in two separate containers. The base image for the Puma container is ruby:2.5-slim. After clearing my Docker cache two days ago and attempting to deploy a newly built frontend, I discovered that Nginx and Puma are no longer talking to one another over the Unix socket. I have traced the immediate cause back to a shift in the version of Debian used in the ruby:2.5-slim base image from Debian 9.7 to 9.8. One thought is that there was a change in a relevant security setting between the two releases.
I've determined that rebuilding an image similar to ruby:2.5-slim starting from Debian 9.7 resolves the immediate issue. But I would like to deal with the deeper problem so that I don't have to pin the version of Debian.
What are some next steps that will help to troubleshoot this issue?
nginx debian socket
asked 1 hour ago
Eric W.Eric W.
1136
add a comment |
I have a frontend with Nginx talking to Puma over a Unix socket in two separate containers. The base image for the Puma container is ruby:2.5-slim. After clearing my Docker cache two days ago and attempting to deploy a newly built frontend, I discovered that Nginx and Puma are no longer talking to one another over the Unix socket. I have traced the immediate cause back to a shift in the version of Debian used in the ruby:2.5-slim base image from Debian 9.7 to 9.8. One thought is that there was a change in a relevant security setting between the two releases.
I've determined that rebuilding an image similar to ruby:2.5-slim starting from Debian 9.7 resolves the immediate issue. But I would like to deal with the deeper problem so that I don't have to pin the version of Debian.
What are some next steps that will help to troubleshoot this issue?
nginx debian socket
asked 1 hour ago
Eric W.Eric W.
1136
Don't use Unix domain sockets, of course.
– Michael Hampton♦
53 mins ago
Hrm. I'm seeing the same thing with a tcp socket. The Puma process won't even respond to alocalhost:3001/healthcheck from within its own container. When Nginx is taken out of the picture and Puma is placed on the outbound port, it works fine, including responding to the health check from within the container.
– Eric W.
15 mins ago
Eh? How did you create these containers? Show yourdocker-compose.yml.
– Michael Hampton♦
4 mins ago
add a comment |
I have a frontend with Nginx talking to Puma over a Unix socket in two separate containers. The base image for the Puma container is ruby:2.5-slim. After clearing my Docker cache two days ago and attempting to deploy a newly built frontend, I discovered that Nginx and Puma are no longer talking to one another over the Unix socket. I have traced the immediate cause back to a shift in the version of Debian used in the ruby:2.5-slim base image from Debian 9.7 to 9.8. One thought is that there was a change in a relevant security setting between the two releases.
I've determined that rebuilding an image similar to ruby:2.5-slim starting from Debian 9.7 resolves the immediate issue. But I would like to deal with the deeper problem so that I don't have to pin the version of Debian.
What are some next steps that will help to troubleshoot this issue?
nginx debian socket
asked 1 hour ago
Eric W.Eric W.
1136
I have a frontend with Nginx talking to Puma over a Unix socket in two separate containers. The base image for the Puma container is ruby:2.5-slim. After clearing my Docker cache two days ago and attempting to deploy a newly built frontend, I discovered that Nginx and Puma are no longer talking to one another over the Unix socket. I have traced the immediate cause back to a shift in the version of Debian used in the ruby:2.5-slim base image from Debian 9.7 to 9.8. One thought is that there was a change in a relevant security setting between the two releases.
I've determined that rebuilding an image similar to ruby:2.5-slim starting from Debian 9.7 resolves the immediate issue. But I would like to deal with the deeper problem so that I don't have to pin the version of Debian.
What are some next steps that will help to troubleshoot this issue?
nginx debian socket
nginx debian socket
asked 1 hour ago
Eric W.Eric W.
1136
asked 1 hour ago
Eric W.Eric W.
1136
edited 1 min ago
Eric W.
asked 1 hour ago
Eric W.Eric W.
1136
asked 1 hour ago
Eric W.Eric W.
1136
asked 1 hour ago
Eric W.Eric W.
1136
1136
Don't use Unix domain sockets, of course.
– Michael Hampton♦
53 mins ago
Hrm. I'm seeing the same thing with a tcp socket. The Puma process won't even respond to alocalhost:3001/healthcheck from within its own container. When Nginx is taken out of the picture and Puma is placed on the outbound port, it works fine, including responding to the health check from within the container.
– Eric W.
15 mins ago
Eh? How did you create these containers? Show yourdocker-compose.yml.
– Michael Hampton♦
4 mins ago
add a comment |
Don't use Unix domain sockets, of course.
– Michael Hampton♦
53 mins ago
Hrm. I'm seeing the same thing with a tcp socket. The Puma process won't even respond to alocalhost:3001/healthcheck from within its own container. When Nginx is taken out of the picture and Puma is placed on the outbound port, it works fine, including responding to the health check from within the container.
– Eric W.
15 mins ago
Eh? How did you create these containers? Show yourdocker-compose.yml.
– Michael Hampton♦
4 mins ago
Don't use Unix domain sockets, of course.
– Michael Hampton♦
53 mins ago
Don't use Unix domain sockets, of course.
– Michael Hampton♦
53 mins ago
Hrm. I'm seeing the same thing with a tcp socket. The Puma process won't even respond to a
localhost:3001/health check from within its own container. When Nginx is taken out of the picture and Puma is placed on the outbound port, it works fine, including responding to the health check from within the container.– Eric W.
15 mins ago
Hrm. I'm seeing the same thing with a tcp socket. The Puma process won't even respond to a
localhost:3001/health check from within its own container. When Nginx is taken out of the picture and Puma is placed on the outbound port, it works fine, including responding to the health check from within the container.– Eric W.
15 mins ago
Eh? How did you create these containers? Show your
docker-compose.yml.– Michael Hampton♦
4 mins ago
Eh? How did you create these containers? Show your
docker-compose.yml.– Michael Hampton♦
4 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f958639%2fsocket-hangs-after-upgrade-from-debian-9-7-to-9-8%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f958639%2fsocket-hangs-after-upgrade-from-debian-9-7-to-9-8%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
Don't use Unix domain sockets, of course.
– Michael Hampton♦
53 mins ago
Hrm. I'm seeing the same thing with a tcp socket. The Puma process won't even respond to a
localhost:3001/healthcheck from within its own container. When Nginx is taken out of the picture and Puma is placed on the outbound port, it works fine, including responding to the health check from within the container.– Eric W.
15 mins ago
Eh? How did you create these containers? Show your
docker-compose.yml.– Michael Hampton♦
4 mins ago