From: Kaelyn via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 55585@debbugs.gnu.org
Subject: bug#55585: inetd-based bitlbee service terminating on new connections
Date: Sun, 22 May 2022 21:19:07 +0000 [thread overview]
Message-ID: <wmHxeqWy4si1yqzgk0QyczFZXxZFcOCJDNht1TPYpg7ijPzzzzz7ov2kWuhrj5xbBG0_ZEsxogiz1JVCF1bQMhtop1mRIrfev7gRMP9MtEY=@protonmail.com> (raw)
Hi,
Recently I upgraded my server running bitlbee for the first time in a few weeks (from guix commit 3363f2c878 to 14384d9586), and after rebooting I was unable to connect to bitlbee because the child service spawned on connect terminates within a few seconds. I'm not certain, but I believe commit 211fe3f66e "services: bitlbee: Use 'make-inetd-constructor'." is the culprit. From /var/log/messages (with the IP address edited out) when I try to connect:
May 21 21:24:31 localhost shepherd[1]: Accepted connection on 0.0.0.0:22 from W.X.Y.Z:38014.
May 21 21:25:21 localhost shepherd[1]: 0 connections still in use after bitlbee-3 termination.
May 21 21:25:21 localhost shepherd[1]: Service bitlbee-3 has been disabled.
May 21 21:25:21 localhost shepherd[1]: Transient service bitlbee-3 terminated, now unregistered.
May 21 21:25:26 localhost shepherd[1]: Accepted connection on 0.0.0.0:6969 from W.X.Y.Z:46492.
May 21 21:25:26 localhost shepherd[1]: Service bitlbee-4 has been started.
May 21 21:25:26 localhost shepherd[1]: 0 connections still in use after bitlbee-4 termination.
May 21 21:25:26 localhost shepherd[1]: Service bitlbee-4 has been disabled.
May 21 21:25:26 localhost shepherd[1]: Transient service bitlbee-4 terminated, now unregistered.
May 21 21:25:56 localhost shepherd[1]: Accepted connection on 0.0.0.0:6969 from W.X.Y.Z:46494.
May 21 21:25:56 localhost shepherd[1]: Service bitlbee-5 has been started.
May 21 21:27:57 localhost shepherd[1]: Service bitlbee-5 has been stopped.
May 21 21:27:57 localhost shepherd[1]: Transient service bitlbee-5 unregistered.
May 21 21:27:57 localhost shepherd[1]: Accepted connection on 0.0.0.0:6969 from W.X.Y.Z:46496.
May 21 21:27:57 localhost shepherd[1]: Service bitlbee-6 has been started.
May 21 21:27:57 localhost shepherd[1]: 1 connection still in use after bitlbee-6 termination.
May 21 21:27:57 localhost shepherd[1]: Service bitlbee-6 has been disabled.
May 21 21:27:57 localhost shepherd[1]: Transient service bitlbee-6 terminated, now unregistered.
May 21 21:28:02 localhost shepherd[1]: Service bitlbee has been stopped.
May 21 21:28:28 localhost shepherd[1]: Service bitlbee has been started.
May 21 21:28:56 localhost shepherd[1]: Accepted connection on 0.0.0.0:6969 from W.X.Y.Z:46500.
May 21 21:28:56 localhost shepherd[1]: Service bitlbee-7 has been started.
May 21 21:28:56 localhost shepherd[1]: 1 connection still in use after bitlbee-7 termination.
May 21 21:28:56 localhost shepherd[1]: Service bitlbee-7 has been disabled.
May 21 21:28:56 localhost shepherd[1]: Transient service bitlbee-7 terminated, now unregistered.
May 21 21:29:26 localhost shepherd[1]: Accepted connection on 0.0.0.0:6969 from W.X.Y.Z:46502.
May 21 21:29:26 localhost shepherd[1]: Service bitlbee-8 has been started.
May 21 21:29:45 localhost shepherd[1]: Service bitlbee has been stopped.
May 21 21:29:51 localhost shepherd[1]: 1 connection still in use after bitlbee-8 termination.
May 21 21:29:51 localhost shepherd[1]: Service bitlbee-8 has been disabled.
May 21 21:29:51 localhost shepherd[1]: Transient service bitlbee-8 terminated, now unregistered.
Cheers,
Kaelyn
Sent with ProtonMail secure email.
next reply other threads:[~2022-05-22 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 21:19 Kaelyn via Bug reports for GNU Guix [this message]
2022-05-25 10:04 ` bug#55585: inetd-based bitlbee service terminating on new connections Ludovic Courtès
2022-05-25 15:31 ` Kaelyn via Bug reports for GNU Guix
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='wmHxeqWy4si1yqzgk0QyczFZXxZFcOCJDNht1TPYpg7ijPzzzzz7ov2kWuhrj5xbBG0_ZEsxogiz1JVCF1bQMhtop1mRIrfev7gRMP9MtEY=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=55585@debbugs.gnu.org \
--cc=kaelyn.alexi@protonmail.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.savannah.gnu.org/cgit/guix.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).