unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: 55585@debbugs.gnu.org
Subject: bug#55585: inetd-based bitlbee service terminating on new connections
Date: Wed, 25 May 2022 12:04:04 +0200	[thread overview]
Message-ID: <87fskyhqsr.fsf@gnu.org> (raw)
In-Reply-To: <wmHxeqWy4si1yqzgk0QyczFZXxZFcOCJDNht1TPYpg7ijPzzzzz7ov2kWuhrj5xbBG0_ZEsxogiz1JVCF1bQMhtop1mRIrfev7gRMP9MtEY=@protonmail.com> (Kaelyn's message of "Sun, 22 May 2022 21:19:07 +0000")

Hi Kaelyn,

Kaelyn <kaelyn.alexi@protonmail.com> skribis:

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

What configuration of Bitlbee are you using?

I have this:

  (service bitlbee-service-type
           (bitlbee-configuration
            (bitlbee bitlbee-purple)
            (plugins (list purple-mattermost))))

and it works well, modulo warnings from libpurple about locale
conversion errors it seems (I haven’t investigated, but it’s harmless).

What do you see in your IRC client when connecting?

Can you reproduce the problem in a VM with ‘guix system vm’?

Thanks in advance,
Ludo’.




  reply	other threads:[~2022-05-25 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 21:19 bug#55585: inetd-based bitlbee service terminating on new connections Kaelyn via Bug reports for GNU Guix
2022-05-25 10:04 ` Ludovic Courtès [this message]
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=87fskyhqsr.fsf@gnu.org \
    --to=ludo@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).