Hello,
Server is a Dell R660XS. Booting install via ipxe.
It just drops into busybox and says that it cannot download
ubuntu-22.04.2-live-server-amd64.iso
And then about 10 seconds later the NIC it needs to download that file comes up
but by then it's already broken.
Thanks,
-Drew
--
I'm using this bug for a new merge to Groovy Mathew, why to change the
summary without syncing first ?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877617
Title:
Automatic scans cause
** Changed in: ipmitool (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1621901
Title:
impitool lacks support for ipv6 addresses
To manage
** Changed in: mysql-5.7 (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1745185
Title:
If apt-get upgrade is run on mysql server when the server
Thank you for taking the time to file a bug report.
Per your console log:
Renaming removed key_buffer and myisam-recover options (if present)
Initialization of mysqld failed: 0
Warning: Unable to start the server. Please restart MySQL and run mysql_upgrade
to ensure the database is ready for
Hello Logan,
I haven't started yet the work of merging and syncing HA packages for
20.10, but will do very soon. Added this to my queue!
Thank you!
** Changed in: ocfs2-tools (Ubuntu)
Status: New => Triaged
** Changed in: ocfs2-tools (Ubuntu)
Assignee: (unassigned) => Rafael David
Thank you for taking the time to file a bug report.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would
Hello Luis,
it seems that somehow the package has been corrupted and you were not
able to install it. Would you mind trying:
$ sudo rm /var/cache/apt/archives/*
$ sudo apt-get autoclean
$ sudo apt-get update
$ sudo apt-get -f install
$ sudo apt-get install python3-markdown
and see if it
This seems like a dpkg in a quick triage look. Flagging it
appropriately.
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: autofs (Ubuntu)
Status: New => Invalid
** Changed in: dpkg (Ubuntu)
Status: New => Triaged
--
You received this bug
It says that your ldap database cannot be opened... There is a debconf
option that says:
"Do you want the database to be removed when slapd is purged?"
I wonder if you had that enabled before the upgrade.
During slapd upgrade, it asks to create a backup of /var/lib/slapd:
From:
bool init_compiled_charsets(myf flags MY_ATTRIBUTE((unused)))
there are charsets being added to "all_charsets" (global variable)
through:
void add_compiled_collation(CHARSET_INFO *cs) {
DBUG_ASSERT(cs->number < array_elements(all_charsets));
all_charsets[cs->number] = cs;
Rolf,
Thank you for taking the time to file a bug report.
I have just used the following in my .bashrc (like keychain man page
says so):
"""
keychain id_rsa id_dsa id_ecdsa
[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
[ -f $HOME/.keychain/$HOSTNAME-sh ] && . $HOME/.keychain/$HOSTNAME-sh
[ -f
Okay so the 3 SRUs are uploaded waiting to be approved.
I have also proposed a merge request in salsa:
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/4
refactoring a bit the package itself and solving the openssl linking
issue the upstream maintainer has observed.
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Changed in: sssd (Ubuntu Eoan)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot, stays offline forever
To manage
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
This is fixed in 4.12.2 uploaded to groovy, so marking that task as fix
released.
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Mustapa, about files being shown as directories, you are probably being
affected by bug
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476 which is an
in-progress SRU and has a fix uploaded to focal-proposed already.
--
You received this bug notification because you are a member of
autopackage tests are also green: https://people.canonical.com/~ubuntu-
archive/proposed-migration/focal/update_excuses.html#python-certbot-
nginx
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
@nagendra-d, it does not look like this is a software bug, but a
configuration issue that @skliarie has faced. Feel free to
talk to him through this bug (for documenting purposes) but
I'm keeping the status here as Invalid so we can better track
things we actually have an action for.
Thank you
Hello Alexander,
I believe your fuzz test result was meant to the upstream project so I
moved it.
o/
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server,
There is a very similar (to yours) problem described here:
https://dovecot.org/pipermail/dovecot/2014-May/095998.html
one of the developers tell end-user to move away from mbox,
and there seems to exist a correct answer stating that mbox
is a supported format and there is no current
Checks (a), (b), (c), (d) passed, plus the comments from others who
installed the package on their servers or test rigs. Marking the
verification as succeeded.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you
Moving back to incomplete as stated by @paelzer.
** Changed in: libseccomp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876486
a) Run https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript.
Full output attached.
Package from proposed is installed:
*** 0.40.0-0ubuntu0.1 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
0.39.0-1 500
Focal verification tests (b), (c) and (d) below:
a) Running script from
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript
b) Request a registration with nginx
sudo certbot -d certbot-test.justgohome.co.uk --agree-tos --staging
--register-unsafely-without-email --nginx
@napsty: the "workaround" (from your blog) is actually to use:
- ifupdown/bridge-utils/vlan/resolvconf for network setup OR
- use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network
file
Just highlighting it here.
@ddstreet, you said you would try to come up with the
TL;DR TODO SUMMARY:
- netplan change to support KeepConfiguration= for systemd-networkd backend
(Groovy)
- backport this change: netplan for Ubuntu Focal (SRU)
- backport this change: netplan for Ubuntu Eoan (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
-
Yes, I'm working with upstream:
https://salsa.debian.org/linux-blocks-team/open-
iscsi/-/merge_requests/4/commits
I have basically reviewed all previous open-iscsi packages.
Let's see further discussions on how they see that.
For the SRUs (3 of them, in the merge requests). They were accepted
** Description changed:
+ [Impact]
+ sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
+
+ In ubuntu that file is a
** Changed in: sssd (Ubuntu Eoan)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I'm trying[1] to back this out, but it will remove symbols from the
library without bumping the soname. Our next chance is when openldap 2.5
comes out, which will likely bump the soname.
1.
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/383797
--
You
Not the entire version bump, no, per SRU guidelines
(https://wiki.ubuntu.com/StableReleaseUpdates). The auto_scan change,
yes.. I'm backporting it to bionic. Anything besides that would have to
be a backport, maintained *by someone* in -backports
Just tested and eoan is affected, focal is clear.
** Also affects: sssd (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Well, yep, Ubuntu tries not to add deltas to Debian unless they're
*really* needed. This makes Debian and Ubuntu healthy. Upstream has
merged my request to experimental, I'll sync it back to Ubuntu as soon
as our importers have recognized the new version.
Cheers!
--
You received this bug
Ok, I have a simple way to reproduce this, and was able to test the
upstream patch. I'll polish it up and put it up for review, then prepare
the SRU paperwork.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Sure Ben,
I have also suggested Debian maintainers:
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/1
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/2
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/3
to sync with upstream.
** Changed in: sssd (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
For the SRU team reviewing this, I can confirm the bug is fixed in samba
4.12.2 which I will upload to groovy shortly:
root@groovy-samba-file-folder:~# gio info smb://127.0.0.1/testshare/123.txt |
grep '^type:'
type: regular
root@groovy-samba-file-folder:~# apt-cache policy samba
samba:
No, comment #8 shows disco is already fixed. This may be SRU material
for Bionic.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1827041
Title:
Regression in smbclient, username required
Alright,
waiting on ubuntu server team review for the SRUs:
- will upload as soon as I get +1.
for Groovy, will work with Debian to merge with upstream:
- @Ritesh Raj Sarraf
rafaeldtinoco@workstation:~/.../sources/upstream/open-iscsi$ git tag
2.0.873
2.0.874
2.0.875
2.0.876
2.0.877
2.0.878
I have also created the PPA:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1877617
just as proforma for the merge reviews.
Will get back to this (groovy) very soon.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Alright, this *new feature* (which is actually fixing an unwanted
behavior) has the following section added to iscsid.conf:
# To prevent doing automatic scans that would add unwanted luns to the system
# we can disable them and have sessions only do manually requested scans.
# Automatic scans are
Hello Ben,
Yes, those commits were added at:
rafaeldtinoco@workstation:~/.../sources/upstream/open-iscsi$ git describe
--tags 5e32aea95741a07d53153c658a0572588eae494d
2.0.874-7-g5e32aea
rafaeldtinoco@workstation:~/.../sources/upstream/open-iscsi$ git describe
--tags
BTW, it is very likely that I'll sponsor your changes and upload to
queue - letting the SRU team to decide - and merge open-iscsi to latest
upstream.
Thanks for the bug report!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
I patched the patch, ugh, but I'll think of a nice way to set this
dynamically before uploading. I'm dropping a lot of delta in the 2.4.50
merge :)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I don't think this change is worth an SRU for focal, as the goal is to
drop a delta. It would also change a signature of sorts, so best not to
change that in an LTS release.
** Changed in: openldap (Ubuntu Focal)
Status: Triaged => Won't Fix
** Changed in: openldap (Ubuntu)
Assignee:
That comes from debian/patches/set-maintainer-name
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875697
Title:
drop fix-ldap-distribution.patch?
To manage notifications about this bug
I think dropping this delta is fine, as the "ubuntu" name will still
show as long as there is a delta. But looks like the email is wrong, we
should be showing ubuntu-devel@ there instead of the debian maintainers
list.
--
You received this bug notification because you are a member of Ubuntu
Debian tried it, and disabled this support again because it pulled in
too many dependencies: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=941654
Samba 4.12.x has another spotlight backend, elastic search:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941654
I'm not a macos user so I'm
Public bug reported:
https://launchpad.net/ubuntu/+source/memcached/1.6.5-2/
build log (warning: over 10Mb):
https://launchpad.net/ubuntu/+source/memcached/1.6.5-2/+build/19216634/+files
/buildlog_ubuntu-groovy-s390x.memcached_1.6.5-2_BUILDING.txt.gz
On s390x:
Test Summary Report
I'm marking this as incomplete for 18.04.2 and wont fix for xenial based
on @ahasenack's last input.
** Also affects: base-installer (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also
Thank you for taking the time to file a bug report.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete
Need more information
Thank you for taking the time to file a bug report.
"""
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 5424
Error: Unable to shut down server with process id 5424
"""
Since there is not enough information in your report to begin triage or to
Need more information
Thank you for taking the time to file a bug report.
"""
mysql server could not be stopped:
mysqld is running as pid 4475
Error: Unable to shut down server with process id 4475
by the post install scripts. Unfortunately logs don't tell why this has
happened, it could be
Need more information
Thank you for taking the time to file a bug report.
"""
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 56734
Error: Unable to shut down server with process id 56734
"""
Since there is not enough information in your report to begin triage or to
Uploaded, waiting for SRU team.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage notifications about
** Tags added: bitesize
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
To manage
Thank you for taking the time to report this bug and helping to make Ubuntu
better. I appreciate the quality of this bug report and I'm sure it will be
helpful to others experiencing the same issue.
This sounds like an upstream bug to me. The best route to getting it fixed
in Ubuntu in this case
Hello Robert,
This is a community supported bug system and sometimes bugs don't get
expected visibility for many reasons. If you're looking for support
services, with different support levels and expected servicing times,
you can always look for Ubuntu Advantage options:
FYIO, from now on all the "merge" work will be done in the merge
requests being linked to this BUG (at the top). @paelzer will be
verifying those.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
** Description changed:
This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot.
[Impact]
Reguesting a certificate via the nginx
** Description changed:
This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot.
[Impact]
Reguesting a certificate via the nginx
Successful run with apache:
ubuntu@certbot-test:~$ sudo certbot -d certbot-test.justgohome.co.uk
--agree-tos --staging --register-unsafely-without-email --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new
** Description changed:
This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot.
[Impact]
Not directly applicable; see the exception
** Description changed:
- This issue only affects version 0.39.0-1 of the python-certbot-nginx
- package in Ubuntu 20.04.
+ This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
+
+ This update includes bugfixes only following the SRU policy exception
+ defined at
Staging server test worked just fine. I'll prepare the SRU paperwork.
ubuntu@certbot-test:~$ sudo certbot -d certbot-test.justgohome.co.uk
--agree-tos --staging --register-unsafely-without-email --nginx
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator
** Description changed:
+ [Impact]
+
+ * QEMU locking primitives might face a race condition in QEMU Async I/O
+ bottom halves scheduling. This leads to a dead lock making either QEMU
+ or one of its tools to hang indefinitely.
+
+ [Test Case]
+
+ * qemu-img convert -f qcow2 -O qcow2
** Changed in: qemu (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu
Status: In Progress => Fix Released
** Changed in: qemu (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: qemu (Ubuntu Eoan)
Status: Incomplete
Thanks for the test update, worked great:
(...)
testing section-continuations-2525.conf...passed
testing section-empty-continuations-2731.conf...passed
testing semacode-1598.conf...passed
testing two-blocks-one-line-1693.conf...passed
Success!
Package versions tested:
certbot 0.40.0-1
letsencrypt
https://launchpad.net/~ahasenack/+archive/ubuntu/certbot-
tlssni01-1875471-d
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with its
Hello Ike,
Please, let me know if you want me to go after the needed SRUs for this
fix or if you will.
I'll wait for the final feedback from tests with your PPA.
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
That sounds good, let me prepare a separate ppa for (d)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage
The testscript at
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript no
longer works:
Cloning into '/root/gopath/src/github.com/letsencrypt/boulder'...
remote: Enumerating objects: 2676, done.
remote: Counting objects: 100% (2676/2676), done.
remote: Compressing objects: 100%
Ok, I filed bugs for the FTBFS issues, but per policy, we won't do an
update just to fix failed-to-build-from-source bugs: these should be
updated together with something else.
Thanks for all the options you outlined in comment #8, and for the check
in comment #11.
So to keep things simple:
a)
The server guide has a warning about this package being deprecated
(paride just added it):
https://ubuntu.com/server/docs/mail-postfix
"""
Deprecation warning: please note that the mail-stack-delivery metapackage has
been deprecated in Focal. The package still exists for compatibility reasons,
This was the deprecation notice sent back then:
https://lists.ubuntu.com/archives/ubuntu-server/2018-March/007682.html
some replies came back in May:
https://lists.ubuntu.com/archives/ubuntu-server/2018-May/007707.html
--
You received this bug notification because you are a member of Ubuntu
Thanks for getting back to us. I'll close the bug.
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1876622
Title:
Can't
I think this bug is wontfix, or opinion, but we need tasks for the Focal
release notes, and the server guide. I'm failing at that, can't figure
out the UI to do it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Also affects: samba (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu Focal)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: samba (Ubuntu Focal)
Status: New => In Progress
** Changed in: samba (Ubuntu Focal)
Haw,
I have just uploaded all SRUs to the archive. Now the SRU team will be
in charge of approving/reviewing them. After, and if, they are accepted,
you will be asked to verify the fixes from [proposed] repository and
change tags here at this bug, from verification-needed to verification-
done.
** Description changed:
[Impact]
- * check_http nagios plugin module faces timeouts multiple times when
- checking for http health.
+ * Based on the test case numbers, and the numbers provided by the end
+ user, it seems that memory reclaiming for the http buffer, in check_http
+ module,
** Also affects: monitoring-plugins (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: monitoring-plugins (Ubuntu Groovy)
Importance: Undecided
Status: In Progress
** Also affects: monitoring-plugins (Ubuntu Bionic)
Importance: Undecided
Status: New
Quick update on the current focal situation regarding some of these
packages:
These are currently an FTBFS in focal:
- python-certbot 0.40.0-1 (build-time tests fail)
- python-acme 1.1.0-1 (build-dep python3-idna <<2.8 not satisfied. When it was
last built in focal, python3-idna was at 2.6)
-
Sorry for having gone radio silent in the past few days. I'm back on
this tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with
Sorry, "Pay close attention", not "Play" :)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1876622
Title:
Can't upgrade samba-common-bin: undefined symbol: smb_strtoul
To manage
Yeah, that was probably the cause. To finish fixing your system
regarding the samba packages, you should be able to run these now:
sudo apt update
sudo apt -f install
Play close attention to what the last one tells you ("-f" stands for "fix"). If
it doesn't look unreasonable and it's asking
You may have had an old samba from 18.04 still installing, as a result
of your release upgrade. Could you please run this command and show the
output?
dpkg -l | grep -E "(samba|smb|registry-tools|winbind|libwbclient|ctdb)"
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You
** Description changed:
+ [Impact]
+
+ * check_http nagios plugin module faces timeouts multiple times when
+ checking for http health.
+
+ [Test Case]
+
+ * not specific clear one. to measure http health in a big environment.
+ * being tested by real user case.
+
+ [Regression Potential]
Nice! Knowing that the patch is a a small subset of an upstream patch
makes our life easier! Since you provided the test, we can go ahead and
do the SRU with the testcase you provided. I'll sponsor the backport for
you.
** Changed in: nagios-plugins (Ubuntu)
Assignee: Rafael David Tinoco
@Haw,
I need some clarification here. You have applied a temporary mitigation
that improves check_http by not constantly freeing and allocating heap
memory. You have indicated upstream patches (2 of them) dealing with the
constant timeout for the checker.
monitoring-plugins 2.2 version
I'm adding this to my list of delta to drop in this cycle.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875697
Title:
drop fix-ldap-distribution.patch?
To manage notifications about
@paelzer,
I really think the right place for a fix like this would be to have a
rule at:
/lib/udev/rules.d/99-vmware-scsi-udev.rules
from open-vm-tools package.
>From a previous fix I did to sg3-tools, I remember ignoring disks
without VPDs and providing them a SCSI_ID based on something else.
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1393403
Title:
dovecot unable to create files in /var/mail
To manage notifications about this bug go to:
1 - 100 of 143428 matches
Mail list logo
