Public bug reported:
we're trying to migrate our network configuration from lucid to precise.
in 10.04 we tied eth0+eth1 together into bond0, then set br0 up on top
of that and assigned an address via dhcp. in 12.04 this only works if
br0 is configured with a static ip address. it fails when
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
when adding a bond the bridge fails to acquire a dhcp address
To manage notifications about this bug go to:
contents of /var/log/upstart attached. as a note our legacy naming for
the bridge is br_phys so there is some output related to trials using
that name instead of br0.
** Attachment added: _var_log_upstart.tar.gz
interfaces.fail does not work. as best i can tell the encoding is the
only difference between them.
** Attachment added: failing version; interfaces.fail: ASCII text
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+attachment/3163697/+files/interfaces.fail
--
You
i believe that i've narrowed it down a bit. it seems improbable, but
from what i can tell it is related to the character encoding of the
file. i'm including 2 versions of the interfaces file. interfaces.utf8
works.
** Attachment added: working version; interfaces.utf8: UTF-8 Unicode text
sorry, on closer inspection the interfaces.utf8 file has some non-
printing characters. an interfaces file with no leading spaces still
fails (attached). so, despite that red herring, i think the root
problem remains. i'm presently unsure why the utf version of the file
works. it doesn't seem
i believe that we're seeing the same problem with ganeti-managed kvm
instances running on 12.04 utilizing a bridged network.
in an initial deployment of 8 guests (also 12.04) we had half of them
drop off the network within a few hours. there is a weak correlation
between high network load in the
thanks for looking into this. one thing worth noting is that the ascii
version of the file attached in comment #5 (interfaces.fail) is indented
but non-working. in fact, i only found that the utf8 version worked by
accident; i cut'n'pasted what i had posted in the original report back
into my
it appears that the suggested edit to /lib/udev/rules.d/40-bridge-
network-interface.rules fixed the problem i was seeing (don't have the
vlan-related file on the system). thank you! the interfaces.fail and
interfaces.nospc files both now work as expected, as does our standard
interfaces
we had 12.04 vms experiencing these hangs regularly (sometimes only
staying online for hours). after enabling vhost_net there was a period
of weeks without issue but a few days one of them hung again with the
same (or very similar) symptoms. an ifdown/ifup from within the guest
brought it back
as a counter-example, our original deployment of eight 12.04 guests on
12.04 hosts were dropping off the network regularly. when the guests
were reinstalled as 10.04 (on the same hosts, with the same workload)
the problem did not recur.
--
You received this bug notification because you are a
can this move out of Incomplete status? as noted in my last comment
the suggested fix appears to work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
bond
Public bug reported:
Binary package hint: ipvsadm
Description:Ubuntu 10.04.1 LTS
Release:10.04
ipvsadm:
Installed: 1:1.25.clean-1
Candidate: 1:1.25.clean-1
Version table:
*** 1:1.25.clean-1 0
500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages
** Patch added: ipvsadm-activeconn.patch
https://bugs.launchpad.net/bugs/663564/+attachment/1702170/+files/ipvsadm-activeconn.patch
--
Don't report persistentconns as activeconns
https://bugs.launchpad.net/bugs/663564
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: upstart
the sysvinit implementation of init supported booting in emergency
(-b) mode where it would Boot directly into a single user shell
without running any other startup scripts. i have found this useful
in the past and was wondering if the
Public bug reported:
the man page for sgdisk(8) states that for the --largest-new=num option A
num value of 0 causes the program to use the first available partition number.
this does not appear to be the case. using a value of 0 returns the following
error:
% sgdisk --version
GPT fdisk
Public bug reported:
Binary package hint: ipvsadm
Description:Ubuntu 10.04.1 LTS
Release:10.04
ipvsadm:
Installed: 1:1.25.clean-1
Candidate: 1:1.25.clean-1
Version table:
*** 1:1.25.clean-1 0
500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages
** Patch added: ipvsadm-activeconn.patch
https://bugs.launchpad.net/bugs/663564/+attachment/1702170/+files/ipvsadm-activeconn.patch
--
Don't report persistentconns as activeconns
https://bugs.launchpad.net/bugs/663564
You received this bug notification because you are a member of Ubuntu
i recently compiled and installed the maverick 2.6.35.2 kernel on a
server running jaunty. i believe that i am encountering the same (or a
very similar) issue. when booted with the new kernel, the server hangs
with a kernel oops when lshw is run, apparently while probing the
Framebuffer device.
this remains a problem in 10.04.1 and likely in maverick as well:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.1 LTS
Release:10.04
Codename: lucid
# grub-install --version
grub-install (GNU GRUB 1.98-1ubuntu5)
# grub-install
looks good in my testing, too. with bridge-utils 1.5-2ubuntu7 the
previously failing versions of my interfaces file work. our current live
version of the interfaces continues to work, and a variant w/o the pre-
up workaround from my initial report works as well. thanks!
--
You received this
Public bug reported:
we're trying to migrate our network configuration from lucid to precise.
in 10.04 we tied eth0+eth1 together into bond0, then set br0 up on top
of that and assigned an address via dhcp. in 12.04 this only works if
br0 is configured with a static ip address. it fails when
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
when adding a bond the bridge fails to acquire a dhcp address
To manage notifications about this bug go to:
i believe that we're seeing the same problem with ganeti-managed kvm
instances running on 12.04 utilizing a bridged network.
in an initial deployment of 8 guests (also 12.04) we had half of them
drop off the network within a few hours. there is a weak correlation
between high network load in the
thanks for looking into this. one thing worth noting is that the ascii
version of the file attached in comment #5 (interfaces.fail) is indented
but non-working. in fact, i only found that the utf8 version worked by
accident; i cut'n'pasted what i had posted in the original report back
into my
still unresolved in 12.04:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04 LTS
Release:12.04
Codename: precise
# grub-install --version
grub-install (GRUB) 1.99-21ubuntu3
# grub-install --no-floppy /dev/md0
/usr/sbin/grub-setup:
i'm still seeing this on a newly-built 12.04 server (installed using
fai). the`locale-gen` workaround takes care of it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/229699
Title:
setting
contents of /var/log/upstart attached. as a note our legacy naming for
the bridge is br_phys so there is some output related to trials using
that name instead of br0.
** Attachment added: _var_log_upstart.tar.gz
i believe that i've narrowed it down a bit. it seems improbable, but
from what i can tell it is related to the character encoding of the
file. i'm including 2 versions of the interfaces file. interfaces.utf8
works.
** Attachment added: working version; interfaces.utf8: UTF-8 Unicode text
interfaces.fail does not work. as best i can tell the encoding is the
only difference between them.
** Attachment added: failing version; interfaces.fail: ASCII text
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+attachment/3163697/+files/interfaces.fail
--
You
sorry, on closer inspection the interfaces.utf8 file has some non-
printing characters. an interfaces file with no leading spaces still
fails (attached). so, despite that red herring, i think the root
problem remains. i'm presently unsure why the utf version of the file
works. it doesn't seem
i noticed a related failure and these errors after installing a ganeti
host as precise and then attempting a master-failover to it. compiling
the python-pycurl package against openssl and installing it on this new
precise host allows master-failover to succeed.
--
You received this bug
can this move out of Incomplete status? as noted in my last comment
the suggested fix appears to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
bond entries in
it appears that the suggested edit to /lib/udev/rules.d/40-bridge-
network-interface.rules fixed the problem i was seeing (don't have the
vlan-related file on the system). thank you! the interfaces.fail and
interfaces.nospc files both now work as expected, as does our standard
interfaces
Public bug reported:
i've been starting down the migration path from one lts release to
another and trying out vm installs using fai 3.4.8ubuntu2 on precise
hosts. the vms (ganeti-managed) are built using fai dirinstall.
it appears that upstart in precise behaves differently than lucid with
** Patch added: one-line change to /usr/lib/fai/updatebase to additionally
divert /sbin/initctl
https://bugs.launchpad.net/bugs/1021506/+attachment/3214485/+files/fai_updatebase.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
we had 12.04 vms experiencing these hangs regularly (sometimes only
staying online for hours). after enabling vhost_net there was a period
of weeks without issue but a few days one of them hung again with the
same (or very similar) symptoms. an ifdown/ifup from within the guest
brought it back
as a counter-example, our original deployment of eight 12.04 guests on
12.04 hosts were dropping off the network regularly. when the guests
were reinstalled as 10.04 (on the same hosts, with the same workload)
the problem did not recur.
--
You received this bug notification because you are a
Public bug reported:
this was discussed in a pair of email threads some months ago. the
patch (attached) from https://lists.uni-koeln.de/pipermail/linux-
fai/2011-November/009355.html resolves the initial problem but does not
address the further issues raised by the original poster in
** Patch added: fai-abspath.patch
https://bugs.launchpad.net/bugs/1040254/+attachment/3272256/+files/fai-abspath.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040254
Title:
disk
i can confirm that the patch allows an instance to start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932166
Title:
ganeti2 can not determine kvm version
To manage notifications about this bug
the kernel from linux-image-3.13.0-37-generic does indeed eliminate that
error. thank you!
tag updated to: verification-done-trusty
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
we're in the process of migrating from 12.04 to 14.04 and are noticing a
problem apparently related to the kernel and ipmi. after an
indeterminate period of regular ipmi queries (e.g., nagios checks using
ipmitool) the kipmi0 process pegs a cpu to ~100% usage and further
i've installed and rebooted 16 of the 14.04 hosts so that they are now
running w/the 3.13.0-38.65-generic #lp1383921 kernel. i'll update the
ticket if i see the symptoms recur on this set.
the remaining 8 can't be rebooted until early next week.
thanks!
--
You received this bug notification
the workaround red hat suggests (forcing a hot-add/hot-remove cycle of
the IPMI interface) appears to work. the same page claims the issue was
resolved w/kernel-2.6.32-504.el6 from Errata RHSA-2014-1392 (released
2014-10-14). however, i'm unable to pinpoint the resolution in the
release or
** Attachment added: .var.log.upstart.mountall.log
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242076/+files/.var.log.upstart.mountall.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: .etc.network.interfaces
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242075/+files/.etc.network.interfaces
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
i'm uncertain exactly when this issue started as we use cfengine
(verifies all expected mounts in place, manually mounts those that are
not). from a note i have i believe it goes back as far as lucid.
the symptom is that an /etc/fstab entry for an nfs-mounted /home is not
i also attempted a boot w/the nfs server's ip address instead of
hostname (although technically i guess nfs-home is an alias). no
change, /home was still not mounted automatically on boot by mountall.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
`mountall --verbose` log w/ip addr in fstab
** Attachment added: mountall.log.ipaddr
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242077/+files/mountall.log.ipaddr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
the hot-add/hot-remove workaround was performed on a mishmash of hosts
where this has crept up. the majority were precise hosts w/a 3.5.0 hwe
kernel. one was trusty w/3.13.0-37-generic and the remainder are
running locally built kernels from linux-source 3.13.0-35.62 w/the patch
from lp#1368991
Public bug reported:
hello -
we had a freshly installed 14.04.1 server run into disk access issues
after swapping out a hard drive. on further investigation, whenever a
drive is pulled (on both the mptsas and mpt2sas systems i can test) the
included warning is logged.
the message is
fwiw zsh 5.0.5-4ubuntu1~ubuntu14.04.1 from backports does not have this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334858
Title:
histreduceblanks can corrupt history
To manage
verified that messages persist w/3.18.0-031800rc6-generic #201411231935
and sent email to linux-...@vger.kernel.org
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http://www.spinics.net/lists/linux-nfs/index.html#47942
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358226
Title:
kernel and lockd xprt_adjust_timeout rq_timeout
To manage notifications about
hello -
per the above comments, i installed the 3.18.0-031800rc1-generic mainline
kernel on the Ubuntu 14.04.1 LTS vm that we have been seeing log these errors.
the error persists:
Oct 29 22:30:37 vm1 kernel: [ 214.434104] xprt_adjust_timeout: rq_timeout = 0!
Oct 29 22:30:37 vm1 kernel: [
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358226
Title:
kernel and lockd xprt_adjust_timeout rq_timeout
To manage
the reboot was delayed but 7 of the 8 remaining hosts are now running the
3.13.0-38.65-generic #lp1383921
kernel. i have not yet seen a recurrence of the ipmi hang on any hosts running
this version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
agreed. thank you for providing the test kernel!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383921
Title:
kipmi0 process hangs with ipmitool
To manage notifications about this bug go to:
Matt - i am using the following (takes advantage of the ipmi_si module's hot
add and remove):
KIPMI_INST=0 # the web suggests this should increment but i've always seen 0
IPMI_PARAMS=$(cat /proc/ipmi/${KIPMI_INST}/params)
sudo sh -c echo remove,${IPMI_PARAMS}
@Joseph - rebooted into 3.18.0-031800rc5-generic #201411162035
and the msgs are still being logged:
[ 231.437941] xprt_adjust_timeout: rq_timeout = 0!
[ 231.437945] lockd: server nfs-home not responding, still trying
[ 231.441744] lockd: server nfs-home OK
--
You received this bug
@chris - i have 10 nodes that i just installed w/3.16.0-031600-generic
#201408031935
i will increase that number tomorrow and update thisbug report if i see
ipmi hangs on these hosts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@arges - fyi the 20 nodes running
3.16.0-031600-generic #201408031935
have not encountered this problem in the ~2 weeks since install reboot.
@matt-jarvis - thx for the verification, i was out-of-office most of
this week.
i just took the 20 nodes that had been running
3.13.0-38.65-generic
to apply to the 3.13 trusty kernel source i had to make a trivial edit
to the patch (result attached). the power user/developer whose workflow
typically triggers these messages has been using it and i have not yet
seen the errors recur.
** Patch added: initialising-nlmsvc_timeout.patch
still no errors seen. i believe this patch addresses the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358226
Title:
kernel and lockd xprt_adjust_timeout rq_timeout
To manage
doesn't appear to have made it into 3.19-rc3 but beyond that i don't
have any information other than what is in http://www.spinics.net/lists
/linux-nfs/msg48569.html (patch appears to be from and signed off by the
NFS client maintainer)
--
You received this bug notification because you are a
Public bug reported:
the sanity check of the TZ env variable implemented in
1.8.9p5-1ubuntu1.1 to address CVE-2014-9680 apparently has the side
effect of carrying forward the TZ variable despite explicit removal in
/etc/sudoers. 1.8.9p5-1ubuntu1 does not exhibit this behavior.
% fgrep env_
** Description changed:
the sanity check of the TZ env variable implemented in
1.8.9p5-1ubuntu1.1 to address CVE-2014-9680 apparently has the side
effect of carrying forward the TZ variable despite explicit removal in
/etc/sudoers. 1.8.9p5-1ubuntu1 does not exhibit this behavior.
%
updated patch for fai 5.0.3
** Patch added: "add /sbin/initctl to the list of automatic diversions in
updatebase."
https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1021506/+attachment/4629809/+files/fai-divert_initctl.diff
--
You received this bug notification because you are a member of
this patch appears to have been accepted upstream, cf.
https://github.com/faiproject/fai/pull/22
** Changed in: fai (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i attempted to make xenial my nfsroot w/fai 5.0.3. i was unsuccessful
due to the dracut requirement.
as suggested by a launchpad bug, i found the package(s) that depended on
initramfs-tools and rebuilt to depend on linux-initramfs-tool instead
(which dracut Provides). but once that was done it
apologies for commenting on a resolved bug, but adding another FTR
comment: it is my understanding that, contrary to statements above, the
upstart-specific "nobootwait" is/was not equivalent to the util-linux
defined "nofail." see e.g.,
it appears that this is resolved in xenial/16.04. booting with both an
empty /etc/hostname and no /etc/hostname result in the system picking up
its dhcp-assigned hostname.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
to locales/default_environment_locale (cf. the debconf error
above) without regard to its existing value.
tia!
andy
--
andrew bezella <abeze...@archive.org>
Internet Archive
** Attachment added: "interactive-dpkg-reconfigure+debug.log"
https://bugs.launchpad.net/bugs/1598326/
others have found the same problem, cf. https://lists.uni-
koeln.de/pipermail/linux-fai/2016-July/011398.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598326
Title:
preseeded value of
i am back to believing this is a bug, as others have found the same
problem, cf. https://lists.uni-koeln.de/pipermail/linux-
fai/2016-July/011398.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
full output
** Attachment added: "includes perl errors re: locale unset"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+attachment/4693898/+files/full.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
in attempting to track down why locales are unset, i noticed this issue
(perhaps related to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=684134). running
`/var/lib/dpkg/info/locales.postinst configure` appears to unset the
seeded value of
i'm much less clear on this now than i was yesterday. continuing to
investigate.
** Changed in: glibc (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/glibc/+question/295923
--
You received this bug notification because you are a
Public bug reported:
unattended-upgrades overrides the setting of APT_LISTCHANGES_FRONTEND.
per the comments, this was done at a time when apt-listchanges would
"always send a mail if there is a mail address set in the config
regardless of the frontend used." this is no longer the case and this
it looks like linux-image-4.8.0-52 has already been released. do you
think this fix might make it into the -53 version?
thanks again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691899
Title:
Public bug reported:
the 4.8 kernel does not create
symlinks/sys/block/*/device/enclosure_device:*. this appears to have
been resolved in 4.9+
what you expected to happen:
with the ga 4.4 and hwe-edge 4.10 kernels the symlinks are created
% ls -l /sys/block/*/device/enclosure*
lrwxrwxrwx 1
yep, looks good. thank you for the quick turnaround!
% uname -a
Linux ia805401.us.archive.org 4.8.0-52-generic #55~lp1691899 SMP Fri May 19
18:09:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
% ls -l /sys/block/*/device/enclosure*
lrwxrwxrwx 1 root root 0 May 19 12:01
details can be found at:
* https://bugzilla.redhat.com/show_bug.cgi?id=1394089
* https://bugzilla.redhat.com/show_bug.cgi?id=1427815
** Bug watch added: Red Hat Bugzilla #1394089
https://bugzilla.redhat.com/show_bug.cgi?id=1394089
** Bug watch added: Red Hat Bugzilla #1427815
hi - any update on including this fix in the next release of the 4.8
series? thanks in advance...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691899
Title:
regression: the 4.8 hwe kernel does
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691899
Title:
regression: the 4.8 hwe kernel does not create the
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633098
Title:
override of APT_LISTCHANGES_FRONTEND can/should be
did some quick testing (also on a single host) and the "Invalid action"
error is not appearing with the 1:5.16-2ubuntu0.2 version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786910
Title:
the linked comment seems to describe a different circumstance than the
comments in setup_apt_listchanges (which does not mention the pager
frontend). debian bug 579733 is also focused on mail behavior rather
than pager.
that said, i can confirm that u-u does NOT hang with the above patch
applied
thank you for the clarification and the suggestion. i was confused by
the timeout occurring after the message "Monitoring 38 ATA/SATA, 0
SCSI/SAS and 0 NVMe devices" as that seemed to indicate a successful
startup.
it appears to have been just the number of devices, not an issue with
any
we're testing blacklisting the floppy module as a workaround, per
https://tickets.puppetlabs.com/browse/FACT-1922 ([FACT-1922] Log file being
spammed with the error: floppy: error -5 while read
ing block 0 - Puppet Tickets)
--
You received this bug notification because you are a member of
Public bug reported:
the smartmontools.service is seen by systemd as timing out and is
terminated.
`systemctl status smartmontools.service` reports:
● smartmontools.service - Self Monitoring and Reporting Technology (SMART)
Daemon
Loaded: loaded (/lib/systemd/system/smartmontools.service;
92 matches
Mail list logo
