From: subashkc1 <subashkc1@protonmail.com>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public@yhbt.net, Mike Perham <mike@perham.net>
Subject: Re: unicorn worker being killed issue
Date: Fri, 12 May 2023 06:41:17 +0000 [thread overview]
Message-ID: <NKz1jqrQCIvqJ0onbjG-qgrItFUx95UbXKPjkeAIsJUu6NeKC--XIUMXaBAsVj46IxDi5t39GZaCOs6uFK2GnDN68kLNGPOGmNrdmoUpxxQ=@protonmail.com> (raw)
In-Reply-To: <20230511190838.M197223@dcvr>
Hi Eric,
Here is the trace from accept4 upto SIGKILL
46585 16:32:39 accept4(11, {sa_family=AF_INET, sin_port=htons(59496), sin_addr=inet_addr("127.0.0.1")}, [128 => 16], SOCK_CLOEXEC) = 9
46585 16:32:39 recvfrom(9, 0x56012fa88ca0, 16384, MSG_DONTWAIT, NULL, NULL) = -1 EAGAIN (Resource temporarily unavailable)
46585 16:32:39 getpid() = 46585
46585 16:32:39 ppoll([{fd=9, events=POLLIN}], 1, NULL, NULL, 8 <unfinished ...>
46601 16:33:38 <... ppoll resumed>) = 0 (Timeout)
46601 16:33:38 getpid() = 46585
46601 16:33:38 read(3, 0x7fc1327506a0, 8) = -1 EAGAIN (Resource temporarily unavailable)
46601 16:33:38 getpid() = 46585
46601 16:33:38 sched_yield() = 0
46601 16:33:38 ppoll([{fd=3, events=POLLIN}], 1, {tv_sec=60, tv_nsec=0}, NULL, 8 <unfinished ...>) = ?
46586 16:33:40 <... futex resumed>) = ?
46585 16:33:40 <... ppoll resumed> <unfinished ...>) = ?
46601 16:33:40 +++ killed by SIGKILL +++
46586 16:33:40 +++ killed by SIGKILL +++
46585 16:33:40 +++ killed by SIGKILL +++
I've uploaded the whole strace dump into codeshare if you need the whole file, https://codeshare.io/3AdLy6.
Warm Regards
Subash K.C., Software Developer | 397 Mt Dandenong Road, Croydon, VIC 3134 | 0405299404
Sent with Proton Mail secure email.
------- Original Message -------
On Friday, May 12th, 2023 at 05:08, Eric Wong <e@80x24.org> wrote:
> subashkc1 subashkc1@protonmail.com wrote:
>
> > Eric Wong wrote:
> >
> > > Or use a single unicorn worker, then strace/truss that worker.
> > > Something like `strace -p $PID_OF_WORKER -f -v -s5000 -o /tmp/dump`
> > > (assuming Linux)
> > > I did this, but the output was so verbose I couldn't make any
> > > sense of it as I wasn't sure what to look for
>
>
> +cc Mike Perham since it's sidekiq-related
>
> subashkc1: Can you show us the lines leading up to the SIGKILL?
>
> Anything starting with the last accept|accept4 syscall up to
> when it says the process is killed should help.
>
> Adding `-t' to enable strace timestamps can also help, thus` strace -t -p $PID_OF_WORKER -f -v -s5000 -o /tmp/dump`
>
>
> reminders: disable HTML and reply-to-all to ensure replication + archival
> subscribers: use List-Unsubscribe header for one-click unsubscribe
next prev parent reply other threads:[~2023-05-12 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 22:02 unicorn worker being killed issue subashkc1
2023-05-07 23:13 ` Eric Wong
2023-05-10 21:34 ` subashkc1
2023-05-11 19:08 ` Eric Wong
2023-05-12 6:41 ` subashkc1 [this message]
2023-05-12 8:05 ` Eric Wong
2023-05-13 0:10 ` Eric Wong
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
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='NKz1jqrQCIvqJ0onbjG-qgrItFUx95UbXKPjkeAIsJUu6NeKC--XIUMXaBAsVj46IxDi5t39GZaCOs6uFK2GnDN68kLNGPOGmNrdmoUpxxQ=@protonmail.com' \
--to=subashkc1@protonmail.com \
--cc=e@80x24.org \
--cc=mike@perham.net \
--cc=unicorn-public@yhbt.net \
/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://yhbt.net/unicorn.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).