Void Linux discussion
 help / color / mirror / Atom feed
From: Leah Neukirchen <leah@vuxu.org>
To: Diego Augusto Molina <diegoaugustomolina@gmail.com>
Cc: leahutils@inbox.vuxu.org,  voidlinux@googlegroups.com
Subject: Re: epona.vuxu.org outage post mortem
Date: Sat, 16 Feb 2019 22:07:19 +0100	[thread overview]
Message-ID: <871s47wigo.fsf@vuxu.org> (raw)
In-Reply-To: <CAGOxLdFfv=EH61i2wnkk9=XRHUr9WYG0auUb9yP-yPK8bkGuJA@mail.gmail.com> (Diego Augusto Molina's message of "Sat, 16 Feb 2019 02:15:07 +0000")

Diego Augusto Molina <diegoaugustomolina@gmail.com> writes:

> Here's my suggestion:
>
> # ss -nlpt | grep 3722
>
> That should include your offending instance of socat listening on TCP
> 3722, stating the PID that has the resource (a.k.a., the socat process
> that opened the port). Killing that PID blindly might not always do
> the trick (e.g. "while true; do socat ...; sleep 1; done") so you may
> want to kill parents/children too. With that PID in mind use "ps faux"
> to navigate through the process tree. My way is:

Yes, this didn't help here as the socket was in TIME-WAIT.

ss -napt however works.

-- 
Leah Neukirchen  <leah@vuxu.org>  http://leah.zone

-- 
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/871s47wigo.fsf%40vuxu.org.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2019-02-16 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 21:54 Leah Neukirchen
2019-02-14 22:07 ` hiro
2019-02-15  8:11 ` Quentin Rameau
2019-02-15  8:59   ` Leah Neukirchen
2019-02-16  2:15 ` Diego Augusto Molina
2019-02-16 21:07   ` Leah Neukirchen [this message]
2019-02-23  1:14 ` Chris Brannon

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=871s47wigo.fsf@vuxu.org \
    --to=leah@vuxu.org \
    --cc=diegoaugustomolina@gmail.com \
    --cc=leahutils@inbox.vuxu.org \
    --cc=voidlinux@googlegroups.com \
    --subject='Re: epona.vuxu.org outage post mortem' \
    /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

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).