From: Eric Wong <e@80x24.org>
To: subashkc1 <subashkc1@protonmail.com>
Cc: unicorn-public@yhbt.net, Mike Perham <mike@perham.net>
Subject: Re: unicorn worker being killed issue
Date: Thu, 11 May 2023 19:08:38 +0000 [thread overview]
Message-ID: <20230511190838.M197223@dcvr> (raw)
In-Reply-To: <Duci227PYeBVohB90iG1Hc3x5cS11voaHImp0vHOOJDOxvzcBJbGOlhtNAW5lEmM_lzzMbRKslopgr5EtSXv5NxAdLqvIpw73fMbnTwe_i4=@protonmail.com>
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-11 19:08 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 [this message]
2023-05-12 6:41 ` subashkc1
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=20230511190838.M197223@dcvr \
--to=e@80x24.org \
--cc=mike@perham.net \
--cc=subashkc1@protonmail.com \
--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).