22.04 network Install bug -- tries to download iso before NIC is up
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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: Automatic scans cause instability for cloud use cases
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 instability for cloud use cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1621901] Re: impitool lacks support for ipv6 addresses
** 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 notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621901/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1745185] Re: If apt-get upgrade is run on mysql server when the server is disabled, the upgrade fails.
** 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 is disabled, the upgrade fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1745185/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1879155] Re: package mysql-server-5.7 5.7.21-1ubuntu1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
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 use. /var/lib/mysql/ibdata1: 30680 ERROR: Database files are locked. Daemon already running? Warning: Unable to start the server. Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. invoke-rc.d: initscript mysql, action "start" failed. It looks that previous database process (the existing/installed one) hasn't shutdown correctly and it is still holding a lock for the database file. Make sure you kill existing previous databases processes and try again re-starting the mysql service. 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 provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: mysql-5.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-5.7 in Ubuntu. Matching subscriptions: main https://bugs.launchpad.net/bugs/1879155 Title: package mysql-server-5.7 5.7.21-1ubuntu1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1879155/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1879106] Re: Sync ocfs2-tools 1.8.6-3 (main) from Debian unstable (main)
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 Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879106 Title: Sync ocfs2-tools 1.8.6-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1879106/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1879067] Re: package python3-markdown 3.1.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.
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 provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community -- 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/1879067 Title: package python3-markdown 3.1.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-markdown/+bug/1879067/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1879067] Re: package python3-markdown 3.1.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.
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 addresses your issue ? -- Parece que de alguna manera el paquete se ha dañado y no pudo instalarlo. ¿Te importaría intentarlo? $ 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 y ver si aborda su problema? ** Changed in: python-markdown (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-markdown in Ubuntu. https://bugs.launchpad.net/bugs/1879067 Title: package python3-markdown 3.1.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-markdown/+bug/1879067/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1878972] Re: Package installation fails if TMPDIR is automounted directory
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 notification because you are a member of Ubuntu Server, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1878972 Title: Package installation fails if TMPDIR is automounted directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1878972/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1878945] Re: crash slapd after update
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: (c)rafaeldtinoco@focal:/var/lib/ldap$ sudo dpkg-reconfigure -p low slapd Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.49+dfsg-2ubuntu1.2... done. Moving old database directory to /var/backups: - directory unknown... done. Creating initial configuration... done. Creating LDAP directory... done. Do you have anything under /var/backups/* named '*slapd*' ? ** Changed in: openldap (Ubuntu) Status: New => Triaged -- 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/1878945 Title: crash slapd after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
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;
map_coll_name_to_number(cs->name, cs->number);
map_cs_name_to_number(cs->csname, cs->number, cs->state);
cs->state |= MY_CS_AVAILABLE;
}
and that contain NO COLLATION, this way.. when uniting them:
void charset_uninit() {
for (CHARSET_INFO *cs : all_charsets) {
if (cs && cs->coll->uninit) {
cs->coll->uninit(cs);
}
}
cs->coll is NULL. This is an upstream bug.. would you like to report ?
You can report upstream and link it here so we can backport a fix
whenever someone fixes it. Maybe @lars can tackle it.
--
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/1877504
Title:
new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-
set, mythbackend and mythfrontend to segfault on exit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
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 $HOME/.keychain/$HOSTNAME-sh-gpg ] && . $HOME/.keychain/$HOSTNAME-sh-gpg """ and I have all my keys already set: """ * keychain 2.8.5 ~ http://www.funtoo.org * Found existing ssh-agent: 3684816 * Known ssh key: /home/rafaeldtinoco/.ssh/id_rsa * Known ssh key: /home/rafaeldtinoco/.ssh/id_dsa * Known ssh key: /home/rafaeldtinoco/.ssh/id_ecdsa rafaeldtinoco@workstation:~$ """ for every new shell. Just needed to put my password once. 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 provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream
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. Haven't yet decided if Ubuntu will keep the CHAP auth algs support from openssl or not (pending ubuntu-devel@ mailing list discussion thread). For now thats it, waiting on upstream and SRU. -- 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: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps. When prompted for an openldap/slapd password, chose any
password you want. It won't be needed again:
$ sudo apt update && sudo apt dist-upgrade
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Open another terminal/screen and tail the sssd logs with a grep:
# tail -f /var/log/sssd/sssd.log | grep -i resolv
Start sssd
# systemctl restart sssd
The tail output from that other terminal should say sssd is monitoring
/etc/resolv.conf (that's the broken symlink):
(Mon May 18 17:32:34 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Repeat this sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
The log should now say:
(Mon May 18 17:33:30 2020) [sssd] [process_dir_event] (0x0400): Not
interested in resolv.conf.target
This shows that sssd didn't pick up that resolv.conf changed, via the
target of the symlink.
Run sssctl again, and the online status will remain offline.
With the fixed packages, the sssd startup log will say:
(Mon May 18 17:17:06 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf.target with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Showing that it's monitoring the symlink target.
And after fixing the broken symlink, it will say:
(Mon May 18 17:18:06 2020) [sssd] [process_dir_event] (0x0400): received
notification for watched file [resolv.conf.target] under /etc
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps. When prompted for an openldap/slapd password, chose any
password you want. It won't be needed again:
$ sudo apt update && sudo apt dist-upgrade
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Open another terminal/screen and tail the sssd logs with a grep:
# tail -f /var/log/sssd/sssd.log | grep -i resolv
Start sssd
# systemctl restart sssd
The tail output from that other terminal should say sssd is monitoring
/etc/resolv.conf (that's the broken symlink):
(Mon May 18 17:32:34 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Repeat this sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
The log should now say:
(Mon May 18 17:33:30 2020) [sssd] [process_dir_event] (0x0400): Not
interested in resolv.conf.target
This shows that sssd didn't pick up that resolv.conf changed, via the
target of the symlink.
Run sssctl again, and the online status will remain offline.
With the fixed packages, the sssd startup log will say:
(Mon May 18 17:17:06 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf.target with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Showing that it's monitoring the symlink target.
And after fixing the broken symlink, it will say:
(Mon May 18 17:18:06 2020) [sssd] [process_dir_event] (0x0400): received
notification for watched file [resolv.conf.target] under /etc
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps. When prompted for an openldap/slapd password, chose any
password you want. It won't be needed again:
$ sudo apt update && sudo apt dist-upgrade
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Open another terminal/screen and tail the sssd logs with a grep:
- # tail -f /var/log/sssd/sssd.log | grep resolv
+ # tail -f /var/log/sssd/sssd.log | grep -i resolv
Start sssd
# systemctl restart sssd
The tail output from that other terminal should say sssd is monitoring
/etc/resolv.conf (that's the broken symlink):
(Mon May 18 17:32:34 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Repeat this sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
The log should now say:
(Mon May 18 17:33:30 2020) [sssd] [process_dir_event] (0x0400): Not
interested in resolv.conf.target
This shows that sssd didn't pick up that resolv.conf changed, via the
target of the symlink.
Run sssctl again, and the online status will remain offline.
With the fixed packages, the sssd startup log will say:
(Mon May 18 17:17:06 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf.target with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Showing that it's monitoring the symlink target.
And after fixing the broken symlink, it will say:
(Mon May 18 17:18:06 2020) [sssd] [process_dir_event] (0x0400): received
notification for watched file [resolv.conf.target] under /etc
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
- Preparation steps:
+ Preparation steps. When prompted for an openldap/slapd password, chose any
password you want. It won't be needed again:
$ sudo apt update && sudo apt dist-upgrade
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Open another terminal/screen and tail the sssd logs with a grep:
# tail -f /var/log/sssd/sssd.log | grep resolv
Start sssd
# systemctl restart sssd
The tail output from that other terminal should say sssd is monitoring
/etc/resolv.conf (that's the broken symlink):
(Mon May 18 17:32:34 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
-
Repeat this sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
The log should now say:
(Mon May 18 17:33:30 2020) [sssd] [process_dir_event] (0x0400): Not
interested in resolv.conf.target
This shows that sssd didn't pick up that resolv.conf changed, via the
target of the symlink.
Run sssctl again, and the online status will remain offline.
-
With the fixed packages, the sssd startup log will say:
(Mon May 18 17:17:06 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf.target with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
Showing that it's monitoring the symlink target.
And after fixing the broken symlink, it will say:
(Mon May 18 17:18:06 2020) [sssd] [process_dir_event] (0x0400): received
notification for watched file [resolv.conf.target] under /etc
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
-
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps:
$ sudo apt update && sudo apt dist-upgrade
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Open another terminal/screen and tail the sssd logs with a grep:
# tail -f /var/log/sssd/sssd.log | grep resolv
Start sssd
# systemctl restart sssd
- Repeat the sssctl call until it shows the offline mode persistently:
+ The tail output from that other terminal should say sssd is monitoring
/etc/resolv.conf (that's the broken symlink):
+ (Mon May 18 17:32:34 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
+
+
+ Repeat this sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
+ The log should now say:
+ (Mon May 18 17:33:30 2020) [sssd] [process_dir_event] (0x0400): Not
interested in resolv.conf.target
+
+ This shows that sssd didn't pick up that resolv.conf changed, via the
+ target of the symlink.
+
+ Run sssctl again, and the online status will remain offline.
+
+
+ With the fixed packages, the sssd startup log will say:
+ (Mon May 18 17:17:06 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf.target with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
+
+ Showing that it's monitoring the symlink target.
+
+ And after fixing the broken symlink, it will say:
+ (Mon May 18 17:18:06 2020) [sssd] [process_dir_event] (0x0400): received
notification for watched file [resolv.conf.target] under /etc
+
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
- For the above steps, the log file being tailed will show this for the startup
of sssd:
- (Mon May 18 17:17:06 2020) [sssd] [_snotify_create] (0x0400): Added a watch
for /etc/resolv.conf.target with inotify flags 0x8D88 internal flags 0x1 using
function resolv_conf_inotify_cb after delay 1.0
-
- And this for when the symlink is fixed:
- (Mon May 18 17:18:06 2020) [sssd] [process_dir_event] (0x0400): received
notification for watched file [resolv.conf.target] under /etc
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps:
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
+
+ Open another terminal/screen and tail the sssd logs with a grep:
+ # tail -f /var/log/sssd/sssd.log | grep resolv
Start sssd
# systemctl restart sssd
Repeat the sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps:
- $ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd ldap-utils dnsmasq
+ $ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Start sssd
# systemctl restart sssd
Repeat the sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
b) polling test
Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
# cat > /etc/sssd/sssd.conf
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
resolv.conf, but the target doesn't exist at all times during boot. It's
expected that symlink to be broken for a while during boot.
Turns out that the monitoring that sssd was doing on /etc/resolv.conf
didn't take into consideration that what could change was the *target*
of the symlink. it completely ignored that fact, and didn't notice when
the resolv.conf contents actually changed in this scenario, which
resulted in sssd staying in the offline mode when it shouldn't.
There are two fixes being pulled in for this SRU:
a) fix the monitoring of the target of the /etc/resolv.conf symlink
b) change the fallback polling code to keep trying, instead of giving up
right away
[Test Case]
It's recommended to test this in a lxd container, or a vm.
Preparation steps:
$ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd ldap-utils dnsmasq
Become root:
$ sudo su -
Detect your ip:
# export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
# export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
Confirm the $ip variable is correct for your case:
# echo $ip
Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
# cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
Confirm /etc/resolv.conf is a broken symlink:
# ll /etc/resolv.conf*
lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
-rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
Start sssd
# systemctl restart sssd
Repeat the sssctl call until it shows the offline mode persistently:
# sssctl domain-status LDAP
Online status: Offline
Active servers:
LDAP: not connected
Discovered LDAP servers:
- ldap01.example.com
"Unbreak" the symlink:
# cp /etc/resolv.conf.good /etc/resolv.conf.target
Run sssctl again, it should almost immediately switch to online:
# sssctl domain-status LDAP
Online status: Online
Active servers:
LDAP: ldap01.example.com
Discovered LDAP servers:
- ldap01.example.com
+ b) polling test
+ Repeat the previous test, but with "try_inotify = false" in sssd.conf, like
this:
+ # cat > /etc/sssd/sssd.conf
[Bug 1872476] Re: Shared files are shown as folders
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. https://bugs.launchpad.net/bugs/1872476 Title: Shared files are shown as folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875354] Re: No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
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 Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1875354 Title: No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1875354/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 907816] Re: libapache2-mod-php5 forgets timezone definition after some time
@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 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 provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: apache2 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/907816 Title: libapache2-mod-php5 forgets timezone definition after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/907816/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1878134] Re: Assertion failures in ati_reg_read_offs/ati_reg_write_offs
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, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1878134 Title: Assertion failures in ati_reg_read_offs/ati_reg_write_offs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1878134/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user
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 documentation saying that mbox format is broken. Unfortunately that thread did not have a better ending. Several discussions, dated from before 2014, stating that from time to time the cache gets corrupted. There might be more than 1 reason on why the cache gets corrupted - doing a parallel to any other kind of journaling scheme - so... without having an exact reproducer it would be very difficult to check why the cache gets corrupted :\. Moving this to confirmed as it seems to still exist. ** Changed in: dovecot (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1876537 Title: dovecot eating mail indexes /var/dovecot-index/user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1876537/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
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 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages Script being run with CERTBOT_PREINSTALLED=1 because not all certbot packages were updated in this SRU (...) testing roundcube-1222.conf...passed 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 python3-acme1.1.0-1 python3-certbot 0.40.0-1 python3-certbot-apache 0.39.0-1 python3-certbot-nginx 0.40.0-0ubuntu0.1 python3-josepy 1.2.0-2 real4m23.223s ** Attachment added: "sru-1875471-test-a-log.txt" https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+attachment/5371730/+files/sru-1875471-test-a-log.txt -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 python3-certbot-nginx from proposed: Version table: *** 0.40.0-0ubuntu0.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe ppc64el Packages 100 /var/lib/dpkg/status 0.39.0-1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/universe ppc64el Packages 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 nginx, Installer nginx Registering without email! Obtaining a new certificate Performing the following challenges: http-01 challenge for certbot-test.justgohome.co.uk Waiting for verification... Cleaning up challenges Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/default Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Redirecting all traffic on port 80 to ssl in /etc/nginx/sites-enabled/default - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Congratulations! You have successfully enabled https://certbot-test.justgohome.co.uk You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=certbot-test.justgohome.co.uk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/certbot-test.justgohome.co.uk/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/certbot-test.justgohome.co.uk/privkey.pem Your cert will expire on 2020-08-12. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot renew" - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. c) Request a registration using apache sudo certbot -d certbot-test.justgohome.co.uk --agree-tos --staging --register-unsafely-without-email --apache python3-certbot-apache from release: Version table: *** 0.39.0-1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/universe ppc64el Packages 100 /var/lib/dpkg/status 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 Registering without email! Obtaining a new certificate Performing the following challenges: http-01 challenge for certbot-test.justgohome.co.uk Enabled Apache rewrite module Waiting for verification... Cleaning up challenges Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf Enabled Apache socache_shmcb module Enabled Apache ssl module Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Enabled Apache rewrite module Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Congratulations! You have successfully enabled
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
@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 netplan change for KeepConfiguration. Did you have time to check on this ? (just checking). Cheers o/ ** Changed in: keepalived (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Xenial) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Bionic) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Xenial) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Bionic) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: netplan Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** No longer affects: keepalived (Ubuntu Eoan) ** No longer affects: keepalived (Ubuntu Disco) ** Also affects: heartbeat (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Released ** Changed in: keepalived (Ubuntu Focal) Status: New => Confirmed ** No longer affects: heartbeat (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
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) - backport this change: netplan for Ubuntu Xenial (SRU, WontFix ?) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream
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 by a peer of mine, so I basically to test if behavior is kept as default for all 3 of them and then I'll upload the fixes. I'll basically run your test case on all 3 packages and upload the binaries after I'm done. Will finish this soon, gave a better attention to upstream so we could bump the version there. -- 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: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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 to /run/systemd/resolve/stub-
+ resolv.conf, but the target doesn't exist at all times during boot. It's
+ expected that symlink to be broken for a while during boot.
+
+ Turns out that the monitoring that sssd was doing on /etc/resolv.conf
+ didn't take into consideration that what could change was the *target*
+ of the symlink. it completely ignored that fact, and didn't notice when
+ the resolv.conf contents actually changed in this scenario, which
+ resulted in sssd staying in the offline mode when it shouldn't.
+
+ There are two fixes being pulled in for this SRU:
+ a) fix the monitoring of the target of the /etc/resolv.conf symlink
+ b) change the fallback polling code to keep trying, instead of giving up
right away
+
+ [Test Case]
+ It's recommended to test this in a lxd container, or a vm.
+
+ Preparation steps:
+ $ sudo apt install sssd-ldap sssd-tools sssd-dbus slapd ldap-utils dnsmasq
+
+ Become root:
+ $ sudo su -
+
+ Detect your ip:
+ # export interface=$(ip route | grep default | sed -r 's,^default via .* dev
([a-z0-9]+) .*,\1,')
+ # export ip=$(ip addr show dev $interface | grep "inet [0-9]" | awk '{print
$2}' | cut -d / -f 1)
+
+ Confirm the $ip variable is correct for your case:
+ # echo $ip
+
+ Create /etc/dnsmasq.d/sssd-test.conf using your real ip:
+ # cat > /etc/dnsmasq.d/sssd-test.conf < /etc/sssd/sssd.conf /etc/resolv.conf.good
+
+ Confirm /etc/resolv.conf is a broken symlink:
+ # ll /etc/resolv.conf*
+ lrwxrwxrwx 1 root root 23 May 13 20:48 /etc/resolv.conf ->
/etc/resolv.conf.target
+ -rw-r--r-- 1 root root 24 May 13 20:48 /etc/resolv.conf.good
+
+ Start sssd
+ # systemctl restart sssd
+
+ Repeat the sssctl call until it shows the offline mode persistently:
+ # sssctl domain-status LDAP
+ Online status: Offline
+
+ Active servers:
+ LDAP: not connected
+
+ Discovered LDAP servers:
+ - ldap01.example.com
+
+ "Unbreak" the symlink:
+ # cp /etc/resolv.conf.good /etc/resolv.conf.target
+
+ Run sssctl again, it should almost immediately switch to online:
+ # sssctl domain-status LDAP
+ Online status: Online
+
+ Active servers:
+ LDAP: ldap01.example.com
+
+ Discovered LDAP servers:
+ - ldap01.example.com
+
+
+ [Regression Potential]
+
+ * discussion of how regressions are most likely to manifest as a result
+ of this change.
+
+ * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+
+ * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+
+ [Other Info]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
+
+ [Original Description]
+
SSSD 1.15.3-2ubuntu1 on 17.10/artful (previous versions on artful were
also affected) is offline on boot and seems to stay offline forever (I
waited over 20 minutes).
sssd_nss.log:
(Fri Oct 13 09:49:50 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data
Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline]
(Fri Oct 13 09:49:51 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data
Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline]
(Fri Oct 13 09:49:51 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data
Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline]
(Fri Oct 13 09:49:51 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data
Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline]
...
SSSD immediately returns to normal operation after restarting it or
after sending SIGUSR2.
A workaround for the problem is creating the file
/etc/systemd/system/sssd.service.d/override.conf with contents
[Unit]
Requires=network-online.target
After=network-online.target
** Description changed:
- [Impact]
+ [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 to /run/systemd/resolve/stub-
resolv.conf, but the
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 495418] Re: Enable GSSAPI support (for likewise-open)
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 received this bug notification because you are a member of Ubuntu Server, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/495418 Title: Enable GSSAPI support (for likewise-open) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/495418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream
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 (https://help.ubuntu.com/community/UbuntuBackports). -- 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: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1723350] Re: sssd offline on boot, stays offline forever
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 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream
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 notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877617 Title: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1723350] Re: sssd offline on boot, stays offline forever
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. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream
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. Will give them a while to provide answers so I can merge/sync with Debian. If, by any chance, they don't sync with upstream, I'll move Ubuntu forward to 2.1.1 and let them to catch up eventually. Cheers -- 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: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1723350] Re: sssd offline on boot, stays offline forever
** 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. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1872476] Re: Shared files are shown as folders
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: Installed: 2:4.12.2+dfsg-0ubuntu1~ppa2 Candidate: 2:4.12.2+dfsg-0ubuntu1~ppa2 Version table: *** 2:4.12.2+dfsg-0ubuntu1~ppa2 500 500 http://ppa.launchpad.net/ahasenack/samba-4122/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 2:4.11.6+dfsg-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages -- 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/1872476 Title: Shared files are shown as folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1827041] Re: Regression in smbclient, username required for anonymous login
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 for anonymous login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1827041/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: Automatic scans cause instability for cloud use cases
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 2.1.0 2.1.1 Will check if we can get it to 2.1.1: https://github.com/open-iscsi/open-iscsi/blob/master/Changelog ** Changed in: open-iscsi (Ubuntu Groovy) Status: Confirmed => Triaged ** Changed in: open-iscsi (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: open-iscsi (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: open-iscsi (Ubuntu Bionic) Status: Confirmed => In Progress ** Summary changed: - Automatic scans cause instability for cloud use cases + open-iscsi automatic scans disable AND groovy merge with upstream -- 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: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream
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. https://bugs.launchpad.net/bugs/1877617 Title: open-iscsi automatic scans disable AND groovy merge with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: Automatic scans cause instability for cloud use cases
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 performed on startup, on login, and on AEN/AER reception # on devices supporting it. For HW drivers all sessions will use the value # defined in the configuration file. This configuration option is independent # of scsi_mod scan parameter. (The default behavior is auto): node.session.scan = auto And this makes it to have the exact same behavior as before this fix, so this makes it suitable for SRU. I'm doing the merge requests and will link to this bug. I'm doing the same change for groovy BUT it will be a new merge with upstream. -- 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 instability for cloud use cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: Automatic scans cause instability for cloud use cases
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 d5483b0df96bd2a1cf86039cf4c6822ec7d7f609 2.0.874-23-gd5483b0 Looks like we've been very cautious with open-iscsi package: open-iscsi | 2.0.871-0ubuntu9 | precise | open-iscsi | 2.0.871-0ubuntu9.12.04.2 | precise-updates | open-iscsi | 2.0.873-3ubuntu5~ubuntu12.04.1| precise-backports | open-iscsi | 2.0.873-3ubuntu9 | trusty| open-iscsi | 2.0.873+git0.3b4b4500-14ubuntu3 | xenial| open-iscsi | 2.0.873+git0.3b4b4500-14ubuntu3.7 | xenial-updates| open-iscsi | 2.0.874-5ubuntu2 | bionic| open-iscsi | 2.0.874-5ubuntu2.7| bionic-updates| open-iscsi | 2.0.874-5ubuntu2.9| bionic-proposed | open-iscsi | 2.0.874-5ubuntu15 | disco | open-iscsi | 2.0.874-7.1ubuntu3| eoan | open-iscsi | 2.0.874-7.1ubuntu6| focal | open-iscsi | 2.0.874-7.1ubuntu6| groovy| I'm marking this for a merge for groovy and blocking -proposed for groovy. Since this is behavior change I'll have to discuss this as being a SRU with a broader audience (specially our openstack team).. but marking as affecting all previous supported releases as well. ** Also affects: open-iscsi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: open-iscsi (Ubuntu Bionic) Status: New => Confirmed ** Changed in: open-iscsi (Ubuntu Eoan) Status: New => Confirmed ** Changed in: open-iscsi (Ubuntu Focal) Status: New => Confirmed ** Changed in: open-iscsi (Ubuntu Groovy) Status: New => Confirmed ** Changed in: open-iscsi (Ubuntu Groovy) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Tags added: block-proposed-focal block-proposed-groovy -- 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 instability for cloud use cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877617] Re: Automatic scans cause instability for cloud use cases
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 report. https://bugs.launchpad.net/bugs/1877617 Title: Automatic scans cause instability for cloud use cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875697] Re: drop fix-ldap-distribution.patch?
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. https://bugs.launchpad.net/bugs/1875697 Title: drop fix-ldap-distribution.patch? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875697] Re: drop fix-ldap-distribution.patch?
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: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: openldap (Ubuntu) Status: Triaged => In Progress -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875697] Re: drop fix-ldap-distribution.patch?
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 go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875697] Re: drop fix-ldap-distribution.patch?
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 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 go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1872454] Re: Enable timemachine support
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 not sure how these are used or which one is best. I'll rely on the community to chime in here. ** Bug watch added: Debian Bug tracker #941654 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941654 -- 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/1872454 Title: Enable timemachine support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872454/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1877623] [NEW] ftbfs s390x, riscv
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 --- t/binary-extstore.t (Wstat: 65280 Tests: 8290 Failed: 1) Failed test: 8286 Non-zero exit status: 255 Parse errors: No plan found in TAP output t/chunked-extstore.t (Wstat: 65024 Tests: 413 Failed: 346) Failed tests: 2, 48-87, 94, 100, 104, 106, 112-361, 363-413 Non-zero exit status: 254 t/extstore.t (Wstat: 1024 Tests: 26 Failed: 4) Failed tests: 4, 13-14, 16 Non-zero exit status: 4 Files=77, Tests=72502, 365 wallclock secs ( 5.94 usr 0.52 sys + 13.27 cusr 4.42 csys = 24.15 CPU) Result: FAIL make[1]: *** [Makefile:2220: test] Error 1 On riscv: Test Summary Report --- t/chunked-extstore.t (Wstat: 2304 Tests: 413 Failed: 9) Failed tests: 131-133, 187-189, 243-245 Non-zero exit status: 9 t/restart.t (Wstat: 512 Tests: 1 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=77, Tests=103639, 1959 wallclock secs (221.09 usr 32.88 sys + 562.72 cusr 245.87 csys = 1062.56 CPU) Result: FAIL ** Affects: memcached (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs ** Description changed: 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 --- t/binary-extstore.t (Wstat: 65280 Tests: 8290 Failed: 1) - Failed test: 8286 - Non-zero exit status: 255 - Parse errors: No plan found in TAP output + Failed test: 8286 + Non-zero exit status: 255 + Parse errors: No plan found in TAP output t/chunked-extstore.t (Wstat: 65024 Tests: 413 Failed: 346) - Failed tests: 2, 48-87, 94, 100, 104, 106, 112-361, 363-413 - Non-zero exit status: 254 + Failed tests: 2, 48-87, 94, 100, 104, 106, 112-361, 363-413 + Non-zero exit status: 254 t/extstore.t (Wstat: 1024 Tests: 26 Failed: 4) - Failed tests: 4, 13-14, 16 - Non-zero exit status: 4 + Failed tests: 4, 13-14, 16 + Non-zero exit status: 4 Files=77, Tests=72502, 365 wallclock secs ( 5.94 usr 0.52 sys + 13.27 cusr 4.42 csys = 24.15 CPU) Result: FAIL make[1]: *** [Makefile:2220: test] Error 1 + + On riscv: + Test Summary Report + --- + t/chunked-extstore.t (Wstat: 2304 Tests: 413 Failed: 9) + Failed tests: 131-133, 187-189, 243-245 + Non-zero exit status: 9 + t/restart.t (Wstat: 512 Tests: 1 Failed: 0) + Non-zero exit status: 2 + Parse errors: No plan found in TAP output + Files=77, Tests=103639, 1959 wallclock secs (221.09 usr 32.88 sys + 562.72 cusr 245.87 csys = 1062.56 CPU) + Result: FAIL -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1877623 Title: ftbfs s390x, riscv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1877623/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
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 affects: live-installer (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: live-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: live-installer (Ubuntu) Status: Confirmed => Incomplete ** Changed in: live-installer (Ubuntu Bionic) Status: New => Incomplete ** Changed in: live-installer (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/1582899 Title: in-target: mkinitramfs: failed to determine device for / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
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 description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community -- 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/1582899 Title: in-target: mkinitramfs: failed to determine device for / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876783] Re: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
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 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 description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: mysql-8.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1876783 Title: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1876783/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876852] Re: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
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 because of many reasons. """ 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 description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1876852 Title: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1876852/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876900] Re: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de
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 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 description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1876900 Title: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1876900/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1867688] Re: Vague error message: sss_ssh_authorizedkeys: Error looking up public keys
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 would be to file an bug with the upstream project. Otherwise, I am not sure what we can do directly in Ubuntu to fix the problem. The upstream place where you can open an issue is: https://github.com/SSSD/sssd/issues And you can basically copy and paste what you wrote here there. If you do end up filing an upstream bug, please link to it from here, this way, when upstream addresses it, we can implement the functionality in Ubuntu. Note: you can link the upstream issue here and change the bug to "Whishlist" and this will be tracked for Ubuntu developers when doing next merges/fixes for the sssd package. Thanks! -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to sssd in Ubuntu. https://bugs.launchpad.net/bugs/1867688 Title: Vague error message: sss_ssh_authorizedkeys: Error looking up public keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1867688/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user
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: https://ubuntu.com/legal/ubuntu-advantage-service-description -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1876537 Title: dovecot eating mail indexes /var/dovecot-index/user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1876537/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images
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. https://bugs.launchpad.net/bugs/1805256 Title: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
** 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 plugin fails: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. [Major Changes] To fix the problem, python-certbot-nginx is being updated from 0.39.0 to 0.40.0. The diff[1] is small and is about removing TLSSNI01 support. It was also noticed that the build-time tests were never run due to a bug in how they were called in d/rules. This has been fixed, and turns out the current version in focal release (0.39.0-1) is already an FTBFS when tests are properly run during build. To have the tests run at build time (as was the original intention), the conditional in d/rules was fixed and a patch from upstream was added. I also submitted the d/rules fix to Debian via [2]. Once that is merged, groovy will have the fix as well via a standard sync. Note the extra patch isn't needed in that version. 1. see the linked MP. Getting a diff from github just for the nginx plugin is hard because it is a subdirectory of the bigger certbot project. You can try, though: https://github.com/certbot/certbot/compare/v0.39.0...v0.40.0 and search for "certbot-nginx" 2. https://salsa.debian.org/letsencrypt-team/certbot/certbot-nginx/-/merge_requests/1 [Test Plan] a) See https://wiki.ubuntu.com/StableReleaseUpdates/Certbot#SRU_Verification_Process. Run https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript (script updated by Brad Warren for this update, thank you!). Sample trailer output in comment #18. b) Request a registration with nginx (example shown in comment #19): sudo certbot -d --agree-tos --staging --register-unsafely-without-email --nginx c) Request a registration using apache (example shown in comment #21): sudo certbot -d --agree-tos --staging --register-unsafely-without-email --apache - TODO: add testscript.sh run results + d) Search build logs for "dh_auto_test" and confirm it was called and + that the build-time tests were run. In launchpad, you can find these by + going to https://launchpad.net/ubuntu/+source/python-certbot-nginx and + clicking through the version of this package in focal-proposed and the + builds on the right hand side of the screen. [Regression Potential] Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. python-acme 1.x which removed TLSSNI01 (among other changes) shouldn't have migrated to the release pocket without also migrating a newer 1.x version of python-certbot-*. This was fixed in the development release and in Debian via an ABI provides. This situation of having a more recent python-acme in focal but not accompanying python-certbot-* version bumps to the same series also made some related packages to become FTBFS in focal release: - bug #1876933: python-certbot FTBFS due to failing build time tests - bug #1876929: python-acme FTBFS due to unsatisfied dependency on python3-idna << 2.8 - bug #1876934: python-certbot-apache FTBFS due to failing build time tests python-certbot-nginx 0.39.0 didn't become an FTBFS like python-certbot- apache just because of the d/rules error in calling those tests, which is being fixed in this update. Fixing those FTBFS issues in the other packages is not in scope for this SRU. It is expected that certbot in general will get more updates in the future during the lifecycle of Ubuntu Focal, and updating the packages at that time will fix the build problem. At the moment, they don't impact the functionality of the system. See the discussion further down here in this bug, in particular comment #12 and comment #15, the latter being what was implemented for this SRU. [Original Description] This issue only affects version 0.39.0-1 of the python-certbot-nginx package in Ubuntu 20.04. To reproduce the problem, install python3-certbot-nginx and run a command like: sudo certbot -d example.org --agree-tos --staging --register-unsafely- without-email --nginx This command will fail and the relevant output is: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
** 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 plugin fails: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. [Major Changes] To fix the problem, python-certbot-nginx is being updated from 0.39.0 to 0.40.0. The diff[1] is small and is about removing TLSSNI01 support. It was also noticed that the build-time tests were never run due to a bug in how they were called in d/rules. This has been fixed, and turns out the current version in focal release (0.39.0-1) is already an FTBFS when tests are properly run during build. To have the tests run at build time (as was the original intention), the conditional in d/rules was fixed and a patch from upstream was added. I also submitted the d/rules fix to Debian via [2]. Once that is merged, groovy will have the fix as well via a standard sync. Note the extra patch isn't needed in that version. - 1. see the linked MP. Getting a diff from github just for the nginx plugin is hard because it is a subdirectory of the bigger certbot project. + 1. see the linked MP. Getting a diff from github just for the nginx plugin is hard because it is a subdirectory of the bigger certbot project. You can try, though: https://github.com/certbot/certbot/compare/v0.39.0...v0.40.0 and search for "certbot-nginx" 2. https://salsa.debian.org/letsencrypt-team/certbot/certbot-nginx/-/merge_requests/1 [Test Plan] a) See https://wiki.ubuntu.com/StableReleaseUpdates/Certbot#SRU_Verification_Process. Run https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript (script updated by Brad Warren for this update, thank you!). Sample trailer output in comment #18. b) Request a registration with nginx (example shown in comment #19): sudo certbot -d --agree-tos --staging --register-unsafely-without-email --nginx c) Request a registration using apache (example shown in comment #21): sudo certbot -d --agree-tos --staging --register-unsafely-without-email --apache TODO: add testscript.sh run results [Regression Potential] Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. python-acme 1.x which removed TLSSNI01 (among other changes) shouldn't have migrated to the release pocket without also migrating a newer 1.x version of python-certbot-*. This was fixed in the development release and in Debian via an ABI provides. This situation of having a more recent python-acme in focal but not accompanying python-certbot-* version bumps to the same series also made some related packages to become FTBFS in focal release: - bug #1876933: python-certbot FTBFS due to failing build time tests - bug #1876929: python-acme FTBFS due to unsatisfied dependency on python3-idna << 2.8 - bug #1876934: python-certbot-apache FTBFS due to failing build time tests python-certbot-nginx 0.39.0 didn't become an FTBFS like python-certbot- apache just because of the d/rules error in calling those tests, which is being fixed in this update. Fixing those FTBFS issues in the other packages is not in scope for this SRU. It is expected that certbot in general will get more updates in the future during the lifecycle of Ubuntu Focal, and updating the packages at that time will fix the build problem. At the moment, they don't impact the functionality of the system. See the discussion further down here in this bug, in particular comment #12 and comment #15, the latter being what was implemented for this SRU. [Original Description] This issue only affects version 0.39.0-1 of the python-certbot-nginx package in Ubuntu 20.04. To reproduce the problem, install python3-certbot-nginx and run a command like: sudo certbot -d example.org --agree-tos --staging --register-unsafely- without-email --nginx This command will fail and the relevant output is: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. As the upstream maintainer of this package, I'll suggest two ways to fix this problem: 1. Update python-certbot-nginx to our 0.40.0 release. The benefit
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 certificate Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf Enabled Apache socache_shmcb module Enabled Apache ssl module Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Enabled Apache rewrite module Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Congratulations! You have successfully enabled https://certbot-test.justgohome.co.uk You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=certbot-test.justgohome.co.uk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/certbot-test.justgohome.co.uk/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/certbot-test.justgohome.co.uk/privkey.pem Your cert will expire on 2020-08-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot renew" ** 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 policy document at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot Reguesting a certificate via the nginx plugin fails: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. [Major Changes] To fix the problem, python-certbot-nginx is being updated from 0.39.0 to 0.40.0. The diff[1] is small and is about removing TLSSNI01 support. It was also noticed that the build-time tests were never run due to a bug in how they were called in d/rules. This has been fixed, and turns out the current version in focal release (0.39.0-1) is already an FTBFS when tests are properly run during build. To have the tests run at build time (as was the original intention), the conditional in d/rules was fixed and a patch from upstream was added. I also submitted the d/rules fix to Debian via [2]. Once that is merged, groovy will have the fix as well via a standard sync. Note the extra patch isn't needed in that version. 1. see the linked MP. Getting a diff from github just for the nginx plugin is hard because it is a subdirectory of the bigger certbot project. 2. https://salsa.debian.org/letsencrypt-team/certbot/certbot-nginx/-/merge_requests/1 [Test Plan] - See + a) See https://wiki.ubuntu.com/StableReleaseUpdates/Certbot#SRU_Verification_Process + + b) Request a registration with nginx: + sudo certbot -d --agree-tos --staging --register-unsafely-without-email --nginx + + c) Request a registration using apache: + sudo certbot -d --agree-tos --staging --register-unsafely-without-email --apache + + Comment #19 shows a successful manual registration using nginx and + packages from a test PPA TODO: add testscript.sh run results TODO: add manual registration results with nginx and apache against staging [Regression Potential] Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. python-acme 1.x which removed TLSSNI01 (among other changes) shouldn't have migrated to the release pocket
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
** 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 policy document at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot Reguesting a certificate via the nginx plugin fails: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. [Major Changes] To fix the problem, python-certbot-nginx is being updated from 0.39.0 to 0.40.0. The diff[1] is small and is about removing TLSSNI01 support. It was also noticed that the build-time tests were never run due to a bug in how they were called in d/rules. This has been fixed, and turns out the current version in focal release (0.39.0-1) is already an FTBFS when tests are properly run during build. To have the tests run at build time (as was the original intention), the conditional in d/rules was fixed and a patch from upstream was added. I also submitted the d/rules fix to Debian via [2]. Once that is merged, groovy will have the fix as well via a standard sync. Note the extra patch isn't needed in that version. - 1. see the linked MP. Getting a diff from github just for the nginx plugin is hard because it is a subdirectory of the bigger certbot project. 2. https://salsa.debian.org/letsencrypt-team/certbot/certbot-nginx/-/merge_requests/1 [Test Plan] See https://wiki.ubuntu.com/StableReleaseUpdates/Certbot#SRU_Verification_Process TODO: add testscript.sh run results TODO: add manual registration results with nginx and apache against staging [Regression Potential] Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. python-acme 1.x which removed TLSSNI01 (among other changes) shouldn't have migrated to the release pocket without also migrating a newer 1.x version of python-certbot-*. This was fixed in the development release and in Debian via an ABI provides. This situation of having a more recent python-acme in focal but not accompanying python-certbot-* version bumps to the same series also made some related packages to become FTBFS in focal release: - bug #1876933: python-certbot FTBFS due to failing build time tests - bug #1876929: python-acme FTBFS due to unsatisfied dependency on python3-idna << 2.8 - bug #1876934: python-certbot-apache FTBFS due to failing build time tests python-certbot-nginx 0.39.0 didn't become an FTBFS like python-certbot- apache just because of the d/rules error in calling those tests, which is being fixed in this update. Fixing those FTBFS issues in the other packages is not in scope for this SRU. It is expected that certbot in general will get more updates in the future during the lifecycle of Ubuntu Focal, and updating the packages at that time will fix the build problem. At the moment, they don't impact the functionality of the system. See the discussion further down - here in this bug. + here in this bug, in particular comment #12 and comment #15, the latter + being what was implemented for this SRU. [Original Description] This issue only affects version 0.39.0-1 of the python-certbot-nginx package in Ubuntu 20.04. To reproduce the problem, install python3-certbot-nginx and run a command like: sudo certbot -d example.org --agree-tos --staging --register-unsafely- without-email --nginx This command will fail and the relevant output is: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. As the upstream maintainer of this package, I'll suggest two ways to fix this problem: 1. Update python-certbot-nginx to our 0.40.0 release. The benefit of this is it sticks to well tested versions of our software rather than making potentially error prone backports. Certbot has an SRU exception which can be seen at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot. The diff of code upstream between 0.39.0 and 0.40.0 if you all want to take this route can be see at https://gist.github.com/bmw/a88429687f4aed13e300fafdad85ce30. 2. You can manually backport minimal fixes. The only changes that should required from the above gist are the changes to: *
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
** 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 https://wiki.ubuntu.com/StableReleaseUpdates/Certbot. + + [Impact] + + Not directly applicable; see the exception policy document at + https://wiki.ubuntu.com/StableReleaseUpdates/Certbot + + Reguesting a certificate via the nginx plugin fails: + + AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' + + The problem here is python-certbot-nginx contains references to code in + python-acme that has been removed. This problem makes python-certbot- + nginx completely unable to obtain certificates. + + [Major Changes] + + To fix the problem, python-certbot-nginx is being updated from 0.39.0 to + 0.40.0. The diff[1] is small and is about removing TLSSNI01 support. + + It was also noticed that the build-time tests were never run due to a + bug in how they were called in d/rules. This has been fixed, and turns + out the current version in focal release (0.39.0-1) is already an FTBFS + when tests are properly run during build. + + To have the tests run at build time (as was the original intention), the + conditional in d/rules was fixed and a patch from upstream was added. I + also submitted the d/rules fix to Debian via [2]. Once that is merged, + groovy will have the fix as well via a standard sync. Note the extra + patch isn't needed in that version. + + + 1. see the linked MP. Getting a diff from github just for the nginx plugin is hard because it is a subdirectory of the bigger certbot project. + 2. https://salsa.debian.org/letsencrypt-team/certbot/certbot-nginx/-/merge_requests/1 + + [Test Plan] + + See + https://wiki.ubuntu.com/StableReleaseUpdates/Certbot#SRU_Verification_Process + + TODO: add testscript.sh run results + TODO: add manual registration results with nginx and apache against staging + + [Regression Potential] + + Upstream performs extensive testing before release, giving us a high + degree of confidence in the general case. There problems are most likely + to manifest in Ubuntu-specific integrations, such as in relation to the + versions of dependencies available and other packaging-specific matters. + + python-acme 1.x which removed TLSSNI01 (among other changes) shouldn't + have migrated to the release pocket without also migrating a newer 1.x + version of python-certbot-*. This was fixed in the development release + and in Debian via an ABI provides. + + This situation of having a more recent python-acme in focal but not accompanying python-certbot-* version bumps to the same series also made some related packages to become FTBFS in focal release: + - bug #1876933: python-certbot FTBFS due to failing build time tests + - bug #1876929: python-acme FTBFS due to unsatisfied dependency on python3-idna << 2.8 + - bug #1876934: python-certbot-apache FTBFS due to failing build time tests + + python-certbot-nginx 0.39.0 didn't become an FTBFS like python-certbot- + apache just because of the d/rules error in calling those tests, which + is being fixed in this update. + + Fixing those FTBFS issues in the other packages is not in scope for this + SRU. It is expected that certbot in general will get more updates in the + future during the lifecycle of Ubuntu Focal, and updating the packages + at that time will fix the build problem. At the moment, they don't + impact the functionality of the system. See the discussion further down + here in this bug. + + [Original Description] + This issue only affects version 0.39.0-1 of the python-certbot-nginx package in Ubuntu 20.04. To reproduce the problem, install python3-certbot-nginx and run a command like: sudo certbot -d example.org --agree-tos --staging --register-unsafely- without-email --nginx This command will fail and the relevant output is: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. As the upstream maintainer of this package, I'll suggest two ways to fix this problem: 1. Update python-certbot-nginx to our 0.40.0 release. The benefit of this is it sticks to well tested versions of our software rather than making potentially error prone backports. Certbot has an SRU exception which can be seen at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot. The diff of code upstream between 0.39.0 and 0.40.0 if you all want to take this route can be see at https://gist.github.com/bmw/a88429687f4aed13e300fafdad85ce30. 2. You can manually backport minimal fixes. The only changes that should required from the above gist are the changes to: *
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 nginx, Installer nginx Obtaining a new certificate Performing the following challenges: http-01 challenge for certbot-test.justgohome.co.uk Waiting for verification... Cleaning up challenges Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/default Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Redirecting all traffic on port 80 to ssl in /etc/nginx/sites-enabled/default - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Congratulations! You have successfully enabled https://certbot-test.justgohome.co.uk You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=certbot-test.justgohome.co.uk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/certbot-test.justgohome.co.uk/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/certbot-test.justgohome.co.uk/privkey.pem Your cert will expire on 2020-08-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot renew" -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images
** 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 ./disk01.qcow2 ./output.qcow2 + + Hangs indefinitely approximately 30% of the runs in Aarch64. + + [Regression Potential] + + * This is a change to a core part of QEMU: The AIO scheduling. It works + like a "kernel" scheduler, whereas kernel schedules OS tasks, the QEMU + AIO code is responsible to schedule QEMU coroutines or event listeners + callbacks. + + * There was a long discussion upstream about primitives and Aarch64. + After quite sometime Paolo released this patch and it solves the issue. + Tested platforms were: amd64 and aarch64 based on his commit log. + + * Christian suggests that this fix stay little longer in -proposed to + make sure it won't cause any regressions. + + [Other Info] + + * Original Description bellow: + + Command: qemu-img convert -f qcow2 -O qcow2 ./disk01.qcow2 ./output.qcow2 Hangs indefinitely approximately 30% of the runs. Workaround: qemu-img convert -m 1 -f qcow2 -O qcow2 ./disk01.qcow2 ./output.qcow2 Run "qemu-img convert" with "a single coroutine" to avoid this issue. (gdb) thread 1 ... (gdb) bt #0 0xbf1ad81c in __GI_ppoll #1 0xaabcf73c in ppoll #2 qemu_poll_ns #3 0xaabd0764 in os_host_main_loop_wait #4 main_loop_wait ... (gdb) thread 2 ... (gdb) bt #0 syscall () #1 0xaabd41cc in qemu_futex_wait #2 qemu_event_wait (ev=ev@entry=0xaac86ce8 ) #3 0xaabed05c in call_rcu_thread #4 0xaabd34c8 in qemu_thread_start #5 0xbf25c880 in start_thread #6 0xbf1b6b9c in thread_start () (gdb) thread 3 ... (gdb) bt #0 0xbf11aa20 in __GI___sigtimedwait #1 0xbf2671b4 in __sigwait #2 0xaabd1ddc in sigwait_compat #3 0xaabd34c8 in qemu_thread_start #4 0xbf25c880 in start_thread #5 0xbf1b6b9c in thread_start (gdb) run Starting program: /usr/bin/qemu-img convert -f qcow2 -O qcow2 ./disk01.ext4.qcow2 ./output.qcow2 [New Thread 0xbec5ad90 (LWP 72839)] [New Thread 0xbe459d90 (LWP 72840)] [New Thread 0xbdb57d90 (LWP 72841)] [New Thread 0xacac9d90 (LWP 72859)] [New Thread 0xa7ffed90 (LWP 72860)] [New Thread 0xa77fdd90 (LWP 72861)] [New Thread 0xa6ffcd90 (LWP 72862)] [New Thread 0xa67fbd90 (LWP 72863)] [New Thread 0xa5ffad90 (LWP 72864)] [Thread 0xa5ffad90 (LWP 72864) exited] [Thread 0xa6ffcd90 (LWP 72862) exited] [Thread 0xa77fdd90 (LWP 72861) exited] [Thread 0xbdb57d90 (LWP 72841) exited] [Thread 0xa67fbd90 (LWP 72863) exited] [Thread 0xacac9d90 (LWP 72859) exited] [Thread 0xa7ffed90 (LWP 72860) exited] """ All the tasks left are blocked in a system call, so no task left to call qemu_futex_wake() to unblock thread #2 (in futex()), which would unblock thread #1 (doing poll() in a pipe with thread #2). Those 7 threads exit before disk conversion is complete (sometimes in the beginning, sometimes at the end). - [ Original Description ] - On the HiSilicon D06 system - a 96 core NUMA arm64 box - qemu-img frequently hangs (~50% of the time) with this command: qemu-img convert -f qcow2 -O qcow2 /tmp/cloudimg /tmp/cloudimg2 Where "cloudimg" is a standard qcow2 Ubuntu cloud image. This qcow2->qcow2 conversion happens to be something uvtool does every time it fetches images. Once hung, attaching gdb gives the following backtrace: (gdb) bt #0 0xae4f8154 in __GI_ppoll (fds=0xe8a67dc0, nfds=187650274213760, timeout=, timeout@entry=0x0, sigmask=0xc123b950) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0xbbefaf00 in ppoll (__ss=0x0, __timeout=0x0, __nfds=, __fds=) at /usr/include/aarch64-linux-gnu/bits/poll2.h:77 #2 qemu_poll_ns (fds=, nfds=, timeout=timeout@entry=-1) at util/qemu-timer.c:322 #3 0xbbefbf80 in os_host_main_loop_wait (timeout=-1) at util/main-loop.c:233 #4 main_loop_wait (nonblocking=) at util/main-loop.c:497 #5 0xbbe2aa30 in convert_do_copy (s=0xc123bb58) at qemu-img.c:1980 #6 img_convert (argc=, argv=) at qemu-img.c:2456 #7 0xbbe2333c in main (argc=7, argv=) at qemu-img.c:4975 Reproduced w/ latest QEMU git (@ 53744e0a182) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1805256 Title: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions --
[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images
** 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 => In Progress ** Changed in: qemu (Ubuntu Disco) Status: Incomplete => In Progress ** Changed in: qemu (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: qemu (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1805256 Title: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 python3-acme1.1.0-1 python3-certbot 0.40.0-1 python3-certbot-apache 0.39.0-1 python3-certbot-nginx 0.40.0-0ubuntu0.1~ppa1 python3-josepy 1.2.0-2 Looks like we can proceed with (d). I'll do a real test with the staging server 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 its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images
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. https://bugs.launchpad.net/bugs/1805256 Title: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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% (2106/2106), done. remote: Total 2676 (delta 577), reused 1597 (delta 425), pack-reused 0 Receiving objects: 100% (2676/2676), 4.68 MiB | 6.77 MiB/s, done. Resolving deltas: 100% (577/577), done. sed: can't read tests/boulder-integration.sh: No such file or directory -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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) update just python-certbot-nginx to 0.40.0, and gloss over the fact that the build-time tests are being skipped; b) fix the build-time tests call in python-certbot-nginx, which will require these other changes: - bump python-certbot-apache to 0.40.0 - drop TLSSNI01 from python-certbot 0.40.0 - preferably fix python-acme's idna build-deps and update it together, as that would also run tests with the current idna in focal I didn't check if the version bumps have the commits you mentioned, but the tests and a minimal run worked. If this looks feasable, the next step would be to run the full test suite, and also try this on a live server with proper DNS setup. c) bump everything to what we have in groovy, so that the versions match expectations and we don't have this big mismatch we are seeing in focal right now There is a feeling we should go with (a) to fix the immediate problem, and (b) can be done over time, or even (c). I have the (b) scenario done in my ppa at https://launchpad.net/~ahasenack/+archive/ubuntu/certbot- tlssni01-1875471 -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876564] Re: mail-stack-delivery has missing packages on focal
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, but won’t setup a working email system. """ A search doesn't turn mail-stack-delivery up anywhere else, so I'm marking that task as released. ** Changed in: serverguide Status: New => Fix Released -- 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/1876564 Title: mail-stack-delivery has missing packages on focal To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1876564/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876564] Re: mail-stack-delivery has missing packages on focal
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 Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1876564 Title: mail-stack-delivery has missing packages on focal To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1876564/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876622] Re: Can't upgrade samba-common-bin: undefined symbol: smb_strtoul
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 upgrade samba-common-bin: undefined symbol: smb_strtoul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1876622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876564] Re: mail-stack-delivery has missing packages on focal
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. https://bugs.launchpad.net/bugs/1876564 Title: mail-stack-delivery has missing packages on focal To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1876564/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1872476] Re: Shared files are shown as folders
** 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) 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/1872476 Title: Shared files are shown as folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875517] Re: check_http inefficient and sometimes times out
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. Would you be able to verify the fixes for me ? Please let me know if there is anything else you need on this. Best Regards Rafael D. Tinoco -- 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/1875517 Title: check_http inefficient and sometimes times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875517] Re: check_http inefficient and sometimes times out
** 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, is the real issue here. It turns out that, a heavily overloaded + servers might be under big memory pressure and having difficulties + trying to reclaim heap memory pages (flushing dirty cache/buffers, + swapped_cached pages, or worst) for the check_http network buffer. [Test Case] - * not specific clear one. to measure http health in a big environment. - * being tested by real user case. + * Execute check_http with a 150MB file: + + - Unpatched (~ 108 sec) + + | $ /usr/lib/nagios/plugins/check_http -H archive.ubuntu.com -j GET -u /ubuntu/pool/main/l/linux-hwe-5.0/linux-hwe-5.0_5.0.0.orig.tar.gz -t 600 + | HTTP OK: HTTP/1.1 200 OK - 162594115 bytes in 108.216 second response time |time=108.215539s;;;0.00 size=162594115B;;;0 + + - Patched (~ 0.5 sec) + + | $ /usr/lib/nagios/plugins/check_http -H archive.ubuntu.com -j GET -u /ubuntu/pool/main/l/linux-hwe-5.0/linux-hwe-5.0_5.0.0.orig.tar.gz -t 600 + | HTTP OK: HTTP/1.1 200 OK - 162594115 bytes in 0.499 second response time + |time=0.498710s;;;0.00;600.00 size=162594115B;;;0 [Regression Potential] - * check_http module might face a regression (only code touched). - * we are using realloc instead of a new free/malloc for the http buffer - * change is based in an upstream commit and proposed by end-user + * Very little but existent for the network receiving buffer logic under check_http module. + * Change is based in an bigger upstream commit and only a minor subset of the upstream patch is being backported. [Other Info] - * Original Description: + * Original Description: Hi, We're frequently seeing socket timeouts with some checks using the check_http plugin. It seems this is a known issue with some fixes upstream: | https://github.com/nagios-plugins/nagios-plugins/commit/2b38350d546ef9632ccd90e300eeaf6eda0ca32c | https://github.com/nagios-plugins/nagios-plugins/commit/fc1bf94655aaed32eeb6fb5c33b6d093f5564bad Think we can backport these fixes? -- 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/1875517 Title: check_http inefficient and sometimes times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875517] Re: check_http inefficient and sometimes times out
** 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 ** Also affects: monitoring-plugins (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: monitoring-plugins (Ubuntu Groovy) ** Changed in: monitoring-plugins (Ubuntu Bionic) Status: New => In Progress ** Changed in: monitoring-plugins (Ubuntu Eoan) Status: New => In Progress ** Changed in: monitoring-plugins (Ubuntu Focal) Status: New => In Progress -- 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/1875517 Title: check_http inefficient and sometimes times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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) - python-certbot-apache 0.39.0-1 (build-time tests fail) python-certbot-nginx 0.39.0-1 builds, but just because the tests are incorrectly skipped in d/rules. If they run, they fail, and that would FTBFS this package as well. If I change python-acme to accept python3-idna 2.8 as a build-dep (changing d/control do python3-idna << 2.9), then it builds. I don't know if this change is acceptable. Upstream python-idna made a 2.9 release in February 17th 2020, which we have in groovy and debian unstable. Will continue 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 its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
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 its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876622] Re: Can't upgrade samba-common-bin: undefined symbol: smb_strtoul
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1876622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876622] Re: Can't upgrade samba-common-bin: undefined symbol: smb_strtoul
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 to proceed, you may do so. In
the end, the dpkg -l list should only contain "ii" or "rc" packages, not iU or
iF which indicates problems.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1876622/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1876622] Re: Can't upgrade samba-common-bin: undefined symbol: smb_strtoul
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1876622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875517] Re: check_http inefficient and sometimes times out
** 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] + + * check_http module might face a regression (only code touched). + * we are using realloc instead of a new free/malloc for the http buffer + * change is based in an upstream commit and proposed by end-user + + [Other Info] + + * Original Description: + Hi, We're frequently seeing socket timeouts with some checks using the check_http plugin. It seems this is a known issue with some fixes upstream: | https://github.com/nagios-plugins/nagios-plugins/commit/2b38350d546ef9632ccd90e300eeaf6eda0ca32c | https://github.com/nagios-plugins/nagios-plugins/commit/fc1bf94655aaed32eeb6fb5c33b6d093f5564bad Think we can backport these fixes? -- 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/1875517 Title: check_http inefficient and sometimes times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875517] Re: check_http inefficient and sometimes times out
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 (rafaeldtinoco) => (unassigned) ** No longer affects: nagios-plugins (Ubuntu) ** Changed in: monitoring-plugins (Ubuntu) Status: Triaged => In Progress -- 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/1875517 Title: check_http inefficient and sometimes times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875517] Re: check_http inefficient and sometimes times out
@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 check_http SEEMs to be close to nagios- plugins 1.5 version. The nagios-plugins you pointed out are backportable to release-2.2.0 of NAGIOS-PLUGINS package and not monitoring-plugins. Have you tested those ? Do you need nagios-plugins backport (of those 2 patches) to test and see if it mitigates your issue ? Per SRU guidelines I can't simply backport those 2 without a testcase and the guarantee they're addressing your issue with a successful testcase being fixed. Waiting a feedback here. Thanks for reporting this. ** Also affects: nagios-plugins (Ubuntu) Importance: Undecided Status: New ** No longer affects: monitoring-plugins (Ubuntu Bionic) ** No longer affects: monitoring-plugins (Ubuntu Eoan) ** No longer affects: monitoring-plugins (Ubuntu Focal) ** No longer affects: monitoring-plugins (Ubuntu Groovy) ** No longer affects: nagios-plugins (Ubuntu Groovy) ** No longer affects: nagios-plugins (Ubuntu Focal) ** No longer affects: nagios-plugins (Ubuntu Eoan) ** No longer affects: nagios-plugins (Ubuntu Bionic) ** No longer affects: nagios-plugins (Ubuntu) ** Also affects: nagios-plugins (Ubuntu) Importance: Undecided Status: New ** Changed in: nagios-plugins (Ubuntu) Status: New => Triaged ** Changed in: nagios-plugins (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- 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/1875517 Title: check_http inefficient and sometimes times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875697] Re: drop fix-ldap-distribution.patch?
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1875594] Re: multipathd failed to get udev uid, add missing path
@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. We could do the same here. Do you agree ? I can provide the patch. ** Also affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: open-vm-tools (Ubuntu) Status: New => Triaged ** Changed in: multipath-tools (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) -- 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/1875594 Title: multipathd failed to get udev uid, add missing path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393403] Re: dovecot unable to create files in /var/mail
** 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: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1393403/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
