Stunnel installation fails with connection refused
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
stunnel4 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
--->
Vorbereitung zum Entpacken von .../stunnel4_
Entpacken von stunnel4 (3:5.72-3) ...
stunnel4 (3:5.72-3) wird eingerichtet ...
Failed to check if group stunnel4 already exists: Connection refused
Failed to check if group stunnel4 already exists: Connection refused
Group stunnel4 not found.
Created symlink /etc/systemd/
/bin/chown: invalid user: ‘stunnel4:stunnel4’
/bin/chown: invalid user: ‘stunnel4:stunnel4’
dpkg: Fehler beim Bearbeiten des Paketes stunnel4 (--configure):
»installiertes post-installati
Trigger für man-db (2.12.1-2) werden verarbeitet ...
Not building database; man-db/auto-update is not 'true'.
Trigger für doc-base (0.11.2) werden verarbeitet ...
Processing 1 added doc-base file...
Fehler traten auf beim Bearbeiten von:
stunnel4
Error: Sub-process /usr/bin/dpkg returned an error code (1)
<---
After
addgroup stunnel4
usermod -aG stunnel4 nteodosio
and logging out and in again, the problem persists, though the message 'group stunnel4 not found' is gone:
--->
stunnel4 (3:5.72-3) wird eingerichtet ...
Failed to check if user stunnel4 already exists: Connection refused
/bin/chown: invalid user: ‘stunnel4:stunnel4’
/bin/chown: invalid user: ‘stunnel4:stunnel4’
dpkg: Fehler beim Bearbeiten des Paketes stunnel4 (--configure):
»installiertes post-installati
Fehler traten auf beim Bearbeiten von:
stunnel4
Error: Sub-process /usr/bin/dpkg returned an error code (1)
<---
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: stunnel4 3:5.72-3
ProcVersionSign
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu4
Architecture: amd64
CasperMD5CheckR
Date: Thu Jun 20 12:43:37 2024
InstallationDate: Installed on 2022-05-16 (766 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: stunnel4
UpgradeStatus: No upgrade log present (probably fresh install)
Ah, actually I read the error too fast,
useradd -g stunnel4 stunnel4
fixes it, but it should not be happening in the first place, right?