[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#55585: inetd-based bitlbee service terminating on new connections
From: |
Kaelyn |
Subject: |
bug#55585: inetd-based bitlbee service terminating on new connections |
Date: |
Sun, 22 May 2022 21:19:07 +0000 |
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.
- bug#55585: inetd-based bitlbee service terminating on new connections,
Kaelyn <=