Void Linux discussion
 help / color / mirror / Atom feed
From: Quentin Rameau <quinq@fifth.space>
To: voidlinux@googlegroups.com
Subject: Re: epona.vuxu.org outage post mortem
Date: Fri, 15 Feb 2019 09:11:15 +0100	[thread overview]
Message-ID: <20190215091115.1444c0c7@fifth.space> (raw)
In-Reply-To: <87mumyvxxc.fsf@vuxu.org>

Hi Leah,

> My assumption was there was a runaway instance of socat running (for
> unknown reasons), and I decided to kill all socat instances.  My usual
> tool of choice would have been `killall socat`, but as there were other
> socat instances running on the machine, I only wanted to kill the port
> 3722 ones.
>
> Lessons learned:
> - The first intuition is often right, even if it's not plausible at first.
> - Don't use `pkill -f` as root, at least not without careful checking
>   and regexp anchoring.
> - If a box doesn't react to reset requests, try sending wake-on-lan to
>   turn it on.
> - runit should reboot by default, not shutdown!

Or track the origin of the issue (runaway socat instance), did you find
anything?

-- 
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/20190215091115.1444c0c7%40fifth.space.
For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2019-02-15  8:11 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 [this message]
2019-02-15  8:59   ` Leah Neukirchen
2019-02-16  2:15 ` Diego Augusto Molina
2019-02-16 21:07   ` Leah Neukirchen
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=20190215091115.1444c0c7@fifth.space \
    --to=quinq@fifth.space \
    --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).