Also, the various packages here have a similar error message but the
error is probably caused by different things. This is a generic error
message from init-system-helpers.
Now, with that said, I agree init-system-helpers should be more verbose
when this error happens.
--
You received this bug
netvicious or Dan, do you have the AMI that you used to produce that
error with proftpd-core?
I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was
not able to reproduce that failure.
I just booted a fresh t3.micro instance with the above AMI, then
proceeded to run `apt update
Same problem here with Ubuntu 22.04.4 LTS in a brand new AWS EC2
directly born as Ubuntu 22.
Setting up proftpd-core (1.3.7c+dfsg-1build1) ...
usermod: no changes
Synchronizing state of proftpd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing:
hey, i removed the "quiet" and did a bit of alternate outputs. the
action is 'start' for my failing 'xrdp'.
Job for xrdp.service failed because the control process exited with error code.
See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for
details.
Could not execute
I'm changing my opinion here.
I feel like this is indeed a problem with how init-system-helpers (more
specifically, deb-systemd-invoke) warns users about errors. Since it
uses "--quiet" when invoking systemctl, I believe it needs to be a bit
more verbose to explain what happened.
What's
This bug also affects installing proftpd under 22.04.
apt install proftpd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'proftpd-core' instead of 'proftpd'
proftpd-core is already the newest version (1.3.7c+dfsg-1build1).
0
so perhaps the message should be more descriptive such as "we tried to
start the $some.service, but it failed", instead of misleading "Could
not execute systemctl".
and also should print, "oh, by the way, this is the complete output and
exit error code of invoking systemctl "
--
You received
this in turn fails when linux modules extra is not installed (it's the
one that ships the zram module on which the package installed relies on)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
probably because the service failed to start?
$ journalctl --no-hostname -u zramswap
Dec 07 20:55:42 systemd[1]: Starting Linux zramswap setup...
Dec 07 20:55:42 root[452655]: Starting Zram
Dec 07 20:55:42 zramswap[452655]: <13>Dec 7 20:55:42 root: Starting Zram
Dec 07 20:55:42 zramswap[452656]:
same error when installing `zram-tools` under jammy 22.04.3 LTS
$ sudo eatmydata apt install zram-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
bc
The following NEW packages will be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: krb5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
There is a bunch of interesting order-of-events issues I'm discovering
with what I'm doing, and because of that it is creating errors that are
obscured in the packaging process. I don't know if there's a fix, or
just some alerts, etc. The package failure appears to be because I did
NOT set up a
> "Sergio" == Sergio Durigan Junior <2003...@bugs.launchpad.net> writes:
Sergio> systemd-invoke will try to run systemctl like this:
Sergio> systemctl --quiet --system restart krb5-kdc.service
Sergio> which fails because of the problem mentioned above.
So, there was a bug that
FWIW, because Focal's deb-systemd-invoke doesn't use --quiet we end up
getting a clearer error there:
# dpkg-reconfigure krb5-kdc
Job for krb5-kdc.service failed because the control process
I did a little debugging, and the problem happens because
krb5-kdc.service fails to start with:
Feb 02 15:22:34 krb5-test systemd[1]: Starting Kerberos 5 Key Distribution
Center...
Feb 02 15:22:34 krb5-test krb5kdc[3957]: Cannot open DB2 database
'/var/lib/krb5kdc/principal': No such file or
Just a follow up, I'm getting the same issue on Ubuntu 22.10 as well. I
reimaged the server from scratch and tried to install the following,
which had the same issue:
apt -y install db-util db5.3-util krb5-admin-server krb5-config krb5-kdc
krb5-kdc-ldap krb5-user ldap-utils libgssrpc4
then this must be a bug in the init-system-helpers package providing the
deb-systemd-invoke command; reassigning.
** Package changed: krb5 (Ubuntu) => init-system-helpers (Ubuntu)
** Changed in: init-system-helpers (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
Running it with no arguments gives me a giant list of services, targets,
etc. All the normal systemd stuff you would expect. I can even see
krb5-kdc red and failed in the list.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
/usr/bin/systemctl
It's definitely installed; I've just stopped and started slapd with it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/2003756
Title:
Cannot configure
systemctl is a non-optional component of an Ubuntu 22.04 system. What
does `which systemctl` return for you? What does `systemctl` return
when you run it?
** Changed in: krb5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
21 matches
Mail list logo
