sysstat.service is enabled by default on 24.04 lts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
New
|
Undecided
|
Unassigned | ||
sysstat (Ubuntu) |
Triaged
|
High
|
Robie Basak |
Bug Description
[ Impact ]
The sysstat services are not enabled by default in jammy. They are enabled by default in noble not due to any packaging change, but because the package is now seeded and the services are processed by systemd preset on the first system boot. This is (arguably) a regression.
On package upgrades, the sysstat postinst script checks the debconf setting for the service and calls systemctl to ensure that the service is set to the state declared through debconf. In the seeded pre-installed package in noble, this is set to "disabled". This is done in the postinst AFTER the dh_installsystemd hooks, so the current service "enabled/disabled" status is ignored. This means that, as soon as we upgrade sysstat in a noble (or later) system, the services which are enabled by default will be disabled. this is a bug.
[ Test Plan ]
[ Where problems could occur ]
[ Other info ]
[Original message]
Today i occasionally found that /var/log/sysstat is full with sar data files on my laptop.
I remember i didn't turn this on.
Then
cat /etc/default/
But systemctl status sysstat.service shows enabled.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: sysstat 12.6.1-2
ProcVersionSign
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sun May 19 23:07:31 2024
InstallationDate: Installed on 2024-04-26 (23 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-
XDG_RUNTIME_
SourcePackage: sysstat
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in sysstat (Ubuntu): | |
assignee: | nobody → Robie Basak (racb) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Would you mind answering these following questions questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
Until then, since I find it hard to reason whether this is indeed a bug or a local configuration issue, I am marking this bug as incomplete. Please, set it back to new once the information is provided.