mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Carl Chave <online@chave.us>
To: musl@lists.openwall.com
Subject: [musl] Hung processes with althttpd web server
Date: Wed, 4 Oct 2023 21:41:41 -0400	[thread overview]
Message-ID: <CAGP1gyMYk3ORW37Do3E5OZyEM1sRks-Ni0OaYaX0GzMyTM4h+A@mail.gmail.com> (raw)

Hello, I'm running the althttpd web server on Alpine Linux using a Ramnode VPS.

I've been having issues for quite a while with "hung" processes. There
is a long lived parent process and then a short lived forked process
for each http request. What I've been seeing is that the forked
processes will sometimes get stuck:

sod01:/srv/www/log$ sudo strace -p 11329
strace: Process 11329 attached
futex(0x7f5bdcd77900, FUTEX_WAIT_PRIVATE, 4294967295, NULL

Please see this forum thread for additional information:
https://sqlite.org/althttpd/forumpost/4dc31619341ce947

That thread is kind of all over the place though as I banged around
trying to figure out how to troubleshoot the issue. The last thing I
tried was to statically build althttpd in a glibc based Void Linux
chroot. I ran that on the Alpine VPS for 37 days without issue. I
switched back to the musl dynamically linked build and 14 hours later
got a hung process.

Can you give me any tips on how to troubleshoot this further?

Thanks,
Carl

             reply	other threads:[~2023-10-05  2:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  1:41 Carl Chave [this message]
2023-10-05  2:15 ` Rich Felker
2023-10-05  2:43   ` Carl Chave
2023-10-05 13:39     ` Szabolcs Nagy
2023-10-05 18:26       ` Carl Chave
2023-10-05 18:48         ` Markus Wichmann
2023-10-05 19:06           ` Carl Chave
2023-10-05  3:37 ` Markus Wichmann
2023-10-05 12:39   ` Rich Felker
2023-10-05 18:34     ` Markus Wichmann
2023-10-05 18:52   ` Carl Chave

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGP1gyMYk3ORW37Do3E5OZyEM1sRks-Ni0OaYaX0GzMyTM4h+A@mail.gmail.com \
    --to=online@chave.us \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).