[Group.of.nepali.translators] [Bug 1732150] Re: Unbound behaviour changes (wrong) when domain-insecure is set for a stub zone with multiple stub-addr(s)
** Changed in: unbound (Ubuntu Bionic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1732150 Title: Unbound behaviour changes (wrong) when domain-insecure is set for a stub zone with multiple stub-addr(s) Status in Unbound - Caching DNS Resolver: Unknown Status in unbound package in Ubuntu: Fix Released Status in unbound source package in Trusty: Won't Fix Status in unbound source package in Xenial: Won't Fix Status in unbound source package in Bionic: Won't Fix Bug description: [Impact] * DNSSEC setup with domain-insecure set fail to work. The lookup will process all available servers leading to a very long lookup time. * Backport upstream fix to stop checking for further trust points in that case. [Test Case] * TBD: Waiting for the bug reporter to provide the initial steps that we migth refine [Regression Potential] * The change will make it stop iterating for further DNSSEC records in certain configuration cases (domain-insecure). But this is just what the respective configuration is meant to do (see http://manpages.ubuntu.com/manpages/bionic/man5/unbound.conf.5.html) So it should speed up certain cases were so far it still iterated through servers, but giving that up early is just what it shoudl be per config. I can think of a slight behavior change due to being faster now, but the end result should not change due to this. With that background I could think of two regressions: a) the faster lookup makes automation wonder b) there would be a condition we (and upstream) missed which would change the actual lookup return Given that the code was not reverted upstream for quite a while I'd think the latter is only theoretical, and the former should be of low risk. [Other Info] * n/a --- Unbound contains a bug when domain-insecure is set for a (stub) zone. This bug is fixed, see https://www.nlnetlabs.nl/bugs- script/show_bug.cgi?id=2882. Can you please backport this to the Trusty package? With regards, Richard Arends To manage notifications about this bug go to: https://bugs.launchpad.net/unbound/+bug/1732150/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
** Changed in: cyrus-sasl2 (Ubuntu Impish) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Won't Fix Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Won't Fix Status in cyrus-sasl2 source package in Jammy: Triaged Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1971489] Re: exim4 GnuTLS breakage with outgoing TLS 1.3 "Resource temporarily unavailable"
Thanks for taking the time to test the patch, Kamal :-).
As Athos already mentioned above, we will need a reproducer in order to
move forward with the SRU. Unfortunately this means that the bug will
be put in our queue until someone has the time to work more on it and
come up with a way to reproduce the problem.
As a side note: because Kinetic is not affected by the bug, I've marked
its task as "Fix Released".
Thanks.
** Changed in: exim4 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1971489
Title:
exim4 GnuTLS breakage with outgoing TLS 1.3 "Resource temporarily
unavailable"
Status in exim4 package in Ubuntu:
Fix Released
Status in exim4 source package in Trusty:
Won't Fix
Status in exim4 source package in Xenial:
Won't Fix
Status in exim4 source package in Bionic:
Triaged
Bug description:
Very recently, my (unchanged for years) bionic exim4 flow ( outgoing
SMTP -> smtp.canonical.com ) abruptly stopped working, with exim4 log
as follows:
SMTP<< 220 smtp-relay-canonical-1.canonical.com ESMTP Postfix (Ubuntu)
SMTP>> EHLO myhostname
SMTP<< 250-smtp-relay-canonical-1.canonical.com
250-PIPELINING
250-SIZE 6144
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250-SMTPUTF8
250 CHUNKING
SMTP>> STARTTLS
SMTP<< 220 2.0.0 Ready to start TLS
SMTP>> EHLO myhostname
H=smtp.canonical.com [185.125.188.121] TLS error on connection (recv):
Resource temporarily unavailable, try again.
SMTP(close)>>
H=smtp.canonical.com [185.125.188.121]: Remote host closed connection in
response to EHLO myhostname
This appears to be a manifestation of this exim4 bug which was fixed in exim4
(4.92): https://bugs.exim.org/show_bug.cgi?id=2359
See also: https://www.mail-archive.com/exim-users@exim.org/msg53121.html
I found and installed a PPA version of exim4 (4.94) for bionic, which
did fix the problem for me.
I believe that all Ubuntu versions which supply exim4 < 4.92 {Bionic,
Xenial, Trusty} are affected by this bug, which leaves exim4
mysteriously broken when the server side happens to move to TLS 1.3.
I suggest updating exim4 on the affected Ubuntu versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1971489/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
Ubuntu Xenial has reached end of standard support, so I marked its task as Won't Fix. ** Changed in: openconnect (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Won't Fix Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs
[Group.of.nepali.translators] [Bug 1668474] Re: AH00526 when using long ProxyPass worker name
Trusty has reached EOL and Xenial has reached end of standard support, so I'm marking their tasks as Won't Fix. I've verified this bug on Focal and Jammy and found that apache2 on both systems accepts a worker name whose length is 256 chars, which, although not great, is the fix provided by upstream to this bug. Therefore, I'm marking this bug as Fix Released on Jammy. ** Changed in: apache2 (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: apache2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668474 Title: AH00526 when using long ProxyPass worker name Status in Apache2 Web Server: Fix Released Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Trusty: Won't Fix Status in apache2 source package in Xenial: Won't Fix Status in apache2 source package in Yakkety: Won't Fix Status in apache2 package in Debian: New Bug description: When using a long ProxyPass worker name such as unix:///var/php- fpm/146527084714328.sock|fcgi://localhost/home/mysite/domains/subdomain.com/public_html/$1 Apache issues the fatal error AH00526 and refuses to proceed during reload. This is a typical configuration generated by Virtualmin for a subdomain running php-fpm. A couple of workarounds are available using mod_rewrite, but they do not use connection pooling for the proxy and aren't available for packaged solutions like Virtualmin. The patch from trunk is fairly straightforward. To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1668474/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1668474] Re: AH00526 when using long ProxyPass worker name
** Changed in: apache2 (Ubuntu Trusty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668474 Title: AH00526 when using long ProxyPass worker name Status in Apache2 Web Server: Fix Released Status in apache2 package in Ubuntu: Triaged Status in apache2 source package in Trusty: Won't Fix Status in apache2 source package in Xenial: Triaged Status in apache2 source package in Yakkety: Won't Fix Status in apache2 package in Debian: New Bug description: When using a long ProxyPass worker name such as unix:///var/php- fpm/146527084714328.sock|fcgi://localhost/home/mysite/domains/subdomain.com/public_html/$1 Apache issues the fatal error AH00526 and refuses to proceed during reload. This is a typical configuration generated by Virtualmin for a subdomain running php-fpm. A couple of workarounds are available using mod_rewrite, but they do not use connection pooling for the proxy and aren't available for packaged solutions like Virtualmin. The patch from trunk is fairly straightforward. To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1668474/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Xenial has reached end of standard support. ** Changed in: dnsmasq (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq source package in Xenial: Won't Fix Status in dnsmasq source package in Bionic: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
Xenial has reached end of standard support. ** Changed in: open-iscsi (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in open-iscsi source package in Bionic: Triaged Bug description: Overview --- It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
Xenial has reached end of standard support.
** Changed in: mysql-5.7 (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1877442
Title:
Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
Status in mysql-5.7 package in Ubuntu:
Triaged
Status in mysql-8.0 package in Ubuntu:
Triaged
Status in mysql-5.7 source package in Xenial:
Won't Fix
Status in mysql-8.0 source package in Xenial:
Invalid
Status in mysql-5.7 source package in Bionic:
Triaged
Status in mysql-8.0 source package in Bionic:
Invalid
Status in mysql-5.7 source package in Eoan:
Invalid
Status in mysql-8.0 source package in Eoan:
Won't Fix
Status in mysql-5.7 source package in Focal:
Invalid
Status in mysql-8.0 source package in Focal:
Triaged
Bug description:
[Impact]
This is a regression in MySQL 5.7.30 (does not affect 8.0 which is in focal
and development release, nor 5.7.29). The CONCAT function has inconsistent
behavior depending on whether or not the result is assigned to a variable,
which is leading to a crash in slurmdbd.
Since it's limited to 5.7.30, the bug only affects stable releases
Bionic and Xenial.
[Test Case]
- Start up MySQL Server 5.7.30
- Connect to it with the mysql cli (with default install of the server, "sudo
mysql" will connect to the MySQL root user)
- Run the following two queries:
* SELECT CONCAT('');
* SET @var = ""; SELECT @var := CONCAT('');
They should give the same output, but the second one returns NULL instead of
an empty string when using 5.7.30.
[Regression Potential]
The patch changes fairly low-level code, which can always carry some risk.
[Other info]
This bug is fixed in the next upstream release of MySQL (5.7.31), so the
patch would only be needed until that is picked.
--- ORIGINAL DESCRIPTION ---
Hi,
Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
segfaulting.
Upon inspection, the slurmdbd crash is caused by a change of behaviour
of the SQL CONCAT function. The new behaviour seems wrong.
Calling
SELECT CONCAT('');
will result in an empty string as expected however if the result is assigned
to a variable with:
SET @var = ""; SELECT @var := CONCAT('');
the variable will be NULL instead of an empty string.
It seems that when the output of CONCAT is assigned to a variable; if
CONCAT should have returned an empty string, it will set the variable
to NULL instead.
SLURM itself crashes because it uses a stored procedure which relies
on the output of CONCAT to be an empty string rather than a NULL
variable and tries to dereference the pointer.
I wasn’t able to get hold of 5.7.29-0ubuntu0.18.04.1 via APT so I
tested on 5.7.21-1ubuntu1. On 5.7.21, the variable was correctly set
to an empty string. I have also tried on 20.04 and the behaviour is
correct as well. So the problem seems to be present only in the
version 5.7.30-0ubuntu0.18.04.1.
I think that the behaviour was introduced in the 5.7 branch by this commit:
https://github.com/mysql/mysql-server/commit/addb2aab601d98e685eccae545f79d120561ad9b
but I am not entirely sure.
This bug is a bit annoying because it makes SLURM with accounting
enabled completely unusable. However downgrading MySQL to
5.7.29-0ubuntu0.18.04.1 temporarily fixed the problem.
I have attached a log file with examples to reproduce the bug.
Thank you very much.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1466926] Re: reload apache2 with mpm_event cause scoreboard is full
Xenial has reached its end of standard support. ** Changed in: apache2 (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1466926 Title: reload apache2 with mpm_event cause scoreboard is full Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Trusty: Won't Fix Status in apache2 source package in Xenial: Won't Fix Status in apache2 source package in Zesty: Fix Released Bug description: [Impact] * apache2 reload can fill up the scorecard with graceful reastarting workers to an amount that it is unable to serve more requests. * Backport fix from upstream to avoid the issue [Test Case] * In comment #8 I outlined some steps to fill up the scorecard with Gracefully stopping processes. But that never triggered the reported bug of eventually breaking new requests for me (It is still good to verify some busy tests on this part of the apache code) -> Therefore one of the reporters of the bug tested the ppa quite a while on his main machines that formerly were affected by the issue. -> no clear "do this then X happens" test case steps * Perform arbitrary additional functional tests on the package to make sure no regressions are visible [Regression Potential] * It is a rather complex code change in the mpm event handling. Only the first change is to code, the other two are for the documentation to match. We tested some apache benchmarks to check the effect, but found neither a positive nor negative impact in general (other than the bug being resolved). Yet if people rely on very specific behavior of the mpm handling that might change a bit. It will change for the good of it, but always remember xkcd.com/1172 TL;DR: IMHO it clearly has a ">none" regression potential on the mpm event handling [Other Info] * Since this is hard to test we had a 2+ week test on the ppa, see comments c#8 - c#15 * It clearly is a fix for some (e.g. the reporter of the bug), but I'd understand if the SRU Team would rate it as feature and deny it for an SRU - depends on the POV, certainly worth to be reviewed at least. On the clean install Ubuntu 14.04 with Apache without almost any client load the Apache server with the command "service apache2 reload" itself allocates slots marked with "Gracefully finishing" for which rejects new connections. For full rejection of new requests is sufficient to perform 4x command "service apache2 reload". Ubuntu 14.04.2 LTS Apache 2.4.7-ubuntu4.4 (mpm_event) Kernel 2.16.0-30-generic Reproduce problem: # 1/ service apache2 start __W_ ___. .. 2/ service apache2 reload .GGG GGG__W__ __ 3/ service apache2 reload ___W_GGG GGG__... .. 4/ service apache2 reload G___ W_ 5/ service apache2 reload -> Server Apache not responding With logs in apache error log file: ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, not at MaxRequestWorkers ... # My workaround was change to MPM module from "mpm_event" to "mpm_worker". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1789527] Re: Galera agent doesn't work when grastate.dat contains safe_to_bootstrap
Xenial has reached its end of standard support. ** Changed in: resource-agents (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1789527 Title: Galera agent doesn't work when grastate.dat contains safe_to_bootstrap Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Trusty: Won't Fix Status in resource-agents source package in Xenial: Won't Fix Status in resource-agents source package in Bionic: Fix Released Bug description: Galera resource agent is not able to put mysql up and master even if safe_to_bootstrap flag in grastate.dat is set to 1. * res_percona_promote_0 on 09fde2-2 'unknown error' (1): call=1373, status=complete, exitreason='MySQL server failed to start (pid=2432) (rc=0), please check your installation', The resource agent is not able to handle safe_to_bootstrap feature in galera: http://galeracluster.com/2016/11/introducing-the-safe-to-bootstrap-feature-in-galera-cluster/ I use percona cluster database which uses the same galera mechanism for clustering. Packages I use in Xenial: resource-agents 3.9.7-1 percona-xtradb-cluster-server-5.6 5.6.37-26.21-0ubuntu0.16.04.2 pacemaker 1.1.14-2ubuntu1.4 corosync 2.3.5-3ubuntu2.1 A workaround exist in : https://github.com/ClusterLabs/resource-agents/issues/915 A fix also exist but it was not addressed to xenial package: https://github.com/ClusterLabs/resource-agents/pull/1022 Is it possible to add this fix on the recent package of resource- agents in Xenial ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1789527/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1633485] Re: Backport login throttling plugin to 5.6 and 5.7
Trusty has reached its end of standard support. ** Changed in: mysql-5.6 (Ubuntu Trusty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1633485 Title: Backport login throttling plugin to 5.6 and 5.7 Status in mysql-5.6 package in Ubuntu: Invalid Status in mysql-5.7 package in Ubuntu: Fix Released Status in mysql-5.6 source package in Precise: Invalid Status in mysql-5.7 source package in Precise: Invalid Status in mysql-5.6 source package in Trusty: Won't Fix Status in mysql-5.7 source package in Trusty: Invalid Status in mysql-5.6 source package in Xenial: Invalid Status in mysql-5.7 source package in Xenial: Fix Released Status in mysql-5.6 source package in Yakkety: Invalid Status in mysql-5.7 source package in Yakkety: Invalid Bug description: In MySQL 8.0 we (Oracle) are adding a plugin to rate-limit/throttle login attempts in order to stop brute-force attacks. Since this is a security mechanism that has been requested by users, we would also like to backport this plugin to MySQL 5.6 and 5.7. After consulting with Robie Basak (racb), we understand this change to be allowed in Ubuntu under the SRU process (Sect. 2.2, https://wiki.ubuntu.com/StableReleaseUpdates), but if there are any comments or objections, we'd like to hear them now. Impact == This functionality is implemented in a plugin. The plugin is not loaded, and the functionality will not be activated unless the DBA explicitly activates it. Regression potential The potential for regression is considered low for the following reasons: - The new functionality is in a plugin that 1) is not loaded by default, and 2) can be unloaded if it causes problems. - The change does not introduce new SQL syntax, and no existing syntax is affected. - The plugin is new, so it's not used by any other packages in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1633485/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1745185] Re: If apt-get upgrade is run on mysql server when the server is disabled, the upgrade fails.
Xenial has reached its end of standard support. ** Changed in: mysql-5.7 (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1745185 Title: If apt-get upgrade is run on mysql server when the server is disabled, the upgrade fails. Status in mysql-5.7 package in Ubuntu: Invalid Status in mysql-5.7 source package in Xenial: Won't Fix Bug description: Since I only use the mysql server for development, I tend to keep the server disabled with systemctl. If mysql server is upgraded while the service is disabled, apt-get fails. To remedy this, I must run "systemctl enable mysqld" before "apt-get upgrade". Since I found a work around, it isn't a big deal, but a less experienced user may have trouble diagnosing this. Possible solutions are: 1) Better error message 2) If the server must be running for upgrade, the upgrade could start it. Maybe prompting first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1745185/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Xenial has reached its end of standard support. ** Changed in: haproxy (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates Status in haproxy package in Ubuntu: Confirmed Status in haproxy source package in Xenial: Won't Fix Status in haproxy source package in Bionic: Confirmed Bug description: I suspect this is the same thing reported on StackOverflow: "I had this same issue where even after reloading the config, haproxy would randomly serve old certs. After looking around for many days the issue was that "reload" operation created a new process without killing the old one. Confirm this by "ps aux | grep haproxy"." https://stackoverflow.com/questions/46040504/haproxy-wont-recognize- new-certificate In our setup, we automate Let's Encrypt certificate renewals, and a fresh certificate will trigger a reload of the service. But occasionally this reload doesn't seem to do anything. Will update with details next time it happens, and hopefully confirm the multiple process theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts
Trusty has reached its end of standard support, so this bug will not be fixed for that release. ** Changed in: pacemaker (Ubuntu Trusty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1052449 Title: corosync hangs due to missing pacemaker shutdown scripts Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Precise: Won't Fix Status in pacemaker source package in Trusty: Won't Fix Status in pacemaker source package in Xenial: Fix Released Bug description: The pacemaker package installs the right init script but doesn't link it to the according runlevels. If corosync is activated and started on the system this leads to a hanging shutdown / reboot because corosync only ends if pacemaker is stopped beforehand. In addition to this the pacemaker daemon has to start after corosync but has to stop before corosync. A possible solution would be to link the init script accordingly an enable it throug /etc/default/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589531] Re: HA_VARRUN has trailing slash
Xenial has reached its end of standard support. ** Changed in: resource-agents (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589531 Title: HA_VARRUN has trailing slash Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Xenial: Won't Fix Status in resource-agents source package in Bionic: Fix Released Status in resource-agents source package in Eoan: Fix Released Bug description: Because HA_VARRUN contains a trailing slash a check in ocf_mkstatedir if $path starts with /var/run/ fails. This is a bug in 3.9.7-1 on Xenial. Fix in upstream: https://github.com/ClusterLabs/resource-agents/commit/571f8dd928b168eef36f79316a5198df9cbdbdca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1589531/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732150] Re: Unbound behaviour changes (wrong) when domain-insecure is set for a stub zone with multiple stub-addr(s)
Xenial and Trusty have reached end of standard support. ** Changed in: unbound (Ubuntu Trusty) Status: Triaged => Won't Fix ** Changed in: unbound (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1732150 Title: Unbound behaviour changes (wrong) when domain-insecure is set for a stub zone with multiple stub-addr(s) Status in Unbound - Caching DNS Resolver: Unknown Status in unbound package in Ubuntu: Fix Released Status in unbound source package in Trusty: Won't Fix Status in unbound source package in Xenial: Won't Fix Status in unbound source package in Bionic: Incomplete Bug description: [Impact] * DNSSEC setup with domain-insecure set fail to work. The lookup will process all available servers leading to a very long lookup time. * Backport upstream fix to stop checking for further trust points in that case. [Test Case] * TBD: Waiting for the bug reporter to provide the initial steps that we migth refine [Regression Potential] * The change will make it stop iterating for further DNSSEC records in certain configuration cases (domain-insecure). But this is just what the respective configuration is meant to do (see http://manpages.ubuntu.com/manpages/bionic/man5/unbound.conf.5.html) So it should speed up certain cases were so far it still iterated through servers, but giving that up early is just what it shoudl be per config. I can think of a slight behavior change due to being faster now, but the end result should not change due to this. With that background I could think of two regressions: a) the faster lookup makes automation wonder b) there would be a condition we (and upstream) missed which would change the actual lookup return Given that the code was not reverted upstream for quite a while I'd think the latter is only theoretical, and the former should be of low risk. [Other Info] * n/a --- Unbound contains a bug when domain-insecure is set for a (stub) zone. This bug is fixed, see https://www.nlnetlabs.nl/bugs- script/show_bug.cgi?id=2882. Can you please backport this to the Trusty package? With regards, Richard Arends To manage notifications about this bug go to: https://bugs.launchpad.net/unbound/+bug/1732150/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1676328] Re: sssd_be is leaking memory
Xenial has reached end of standard support, so I'm marking this bug as Won't Fix. ** Changed in: sssd (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1676328 Title: sssd_be is leaking memory Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: Won't Fix Status in sssd source package in Yakkety: Won't Fix Bug description: The bug is described here: https://pagure.io/SSSD/sssd/issue/3176 Please consider to upgrade from 1.13.4 to 1.13.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1676328/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1755189] Re: squid3 helper basic_pop3_auth crashes
Cosmic has reached EOL in 2019; Xenial has entered ESM last year. Therefore, making this bug as Won't Fix for both. ** Changed in: squid3 (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: squid (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1755189 Title: squid3 helper basic_pop3_auth crashes Status in squid package in Ubuntu: Fix Released Status in squid3 package in Ubuntu: Invalid Status in squid source package in Xenial: Invalid Status in squid3 source package in Xenial: Won't Fix Status in squid source package in Bionic: Invalid Status in squid3 source package in Bionic: Triaged Status in squid source package in Cosmic: Won't Fix Status in squid3 source package in Cosmic: Invalid Bug description: Ubuntu Xenial perl is v5.22.1 squid3 version 3.5.12-1ubuntu7.5 Running basic_pop3_auth pop3_server gives : Global symbol "$server" requires explicit package name (did you forget to declare "my $server"?) at ./basic_pop3_auth line 92. Global symbol "$pop" requires explicit package name (did you forget to declare "my $pop"?) at ./basic_pop3_auth line 99. Global symbol "$server" requires explicit package name (did you forget to declare "my $server"?) at ./basic_pop3_auth line 99. Global symbol "$pop" requires explicit package name (did you forget to declare "my $pop"?) at ./basic_pop3_auth line 100. Global symbol "$pop" requires explicit package name (did you forget to declare "my $pop"?) at ./basic_pop3_auth line 106. Global symbol "$pop" requires explicit package name (did you forget to declare "my $pop"?) at ./basic_pop3_auth line 111. Global symbol "$pop" requires explicit package name (did you forget to declare "my $pop"?) at ./basic_pop3_auth line 112. ./basic_pop3_auth had compilation errors. adding my before $server on line 92 and before $pop on line 99 solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1755189/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1775636] Re: sss_ssh_authorizedkeys fails with: Error looking up public keys when client cert present in IPA
Xenial has entered ESM, so I'm marking this bug as Won't Fix for it. ** Changed in: sssd (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1775636 Title: sss_ssh_authorizedkeys fails with: Error looking up public keys when client cert present in IPA Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: Won't Fix Bug description: When trying to get the key for a person with also a client cert present in IPA the following error shows: ``` (Thu Jun 7 14:37:11:920526 2018) [/usr/bin/sss_ssh_authorizedkeys] [main] (0x0020): sss_ssh_get_ent() failed (14): Bad address Error looking up public keys ``` What is supposed to happen: return public key for user Version Information: Ubuntu 16.04.2 LTS Updated sssd-common and related tools to latest: libipa-hbac0 libsss- idmap0 python-libipa-hbac python-sss sssd sssd-ad sssd-ad-common sssd- common sssd-ipa sssd-krb5 sssd-krb5-common sssd-ldap sssd-proxy so sssd is now at: ii sssd-common1.13.4-1ubuntu1.10 amd64System Security Services Daemon -- common files This doesn't happen on Centos 7.5 (sssd-common-1.16.0-19.el7.x86_64) nor on ubuntu 14.04 (sssd-common==1.11.8-0ubuntu0.7) IPA server is on CentOS 7.5: ipa-server-4.5.4-10.el7.centos.x86_64 From what I've seen upstream, it might be related to the fairly new handling of x509 certificates with ssh certificates in them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1775636/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1641203] Re: SSSD can't process GPO from Active Directory when it contains lines with no equal sign
Xenial has entered ESM, therefore I am marking this bug as Won't Fix for
it.
** Changed in: sssd (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1641203
Title:
SSSD can't process GPO from Active Directory when it contains lines
with no equal sign
Status in ding-libs package in Ubuntu:
Fix Released
Status in sssd package in Ubuntu:
Fix Released
Status in ding-libs source package in Xenial:
Won't Fix
Status in sssd source package in Xenial:
Won't Fix
Status in ding-libs source package in Yakkety:
Won't Fix
Status in sssd source package in Yakkety:
Won't Fix
Bug description:
[Impact]
This bug hits users who is joined to a domain server (probably MS Active
Directory) where there is a GPO line that doesn't contain an equal sign (=).
See more info in the upstreams bug report linked below. This could be rather
common in corporate environments and normally nothing you "fix" on the domain
controller side to be able to use SSSD clients. This means all clients that
upgrades to 16.04 using SSSD with a GPO containing a line without equal sign
will be affected.
[Test Case]
Steps to reproduce (you'll need a domain server with GPO containing a line
withouth equal sign!):
- Install:
apt install krb5-user samba sssd ntp
- Make sure the default realm is setup properly (FQDN in uppercase):
dpkg-reconfigure krb5-config
- Set up /etc/samba/smb.conf like this: https://paste.ubuntu.com/24407627/
- Set up /etc/sssd/sssd.conf like this: https://paste.ubuntu.com/24407643/
- File permissions:
sudo chown root:root /etc/sssd/sssd.conf
sudo chmod 600 /etc/sssd/sssd.conf
- Restart services:
sudo service ntp restart
sudo service smbd restart
sudo service nmbd restart
- Join domain with:
sudo net ads join -U "administra...@domain.com"
"createcomputer=Servers/Virtual" osName=Ubuntu osVer=16.04
- Start SSSD:
sudo service sssd start
- Verify:
getent passwd administra...@qrtech.se
- Add creation of home directories on login (check the unchecked box):
sudo pam-auth-update
- Now try to login to the server with a domain user:
arune@d152:~$ ssh ar...@domain.com@server.domain.com
- This should fail and you'll find in the logs:
grep "ad_gpo_store_policy_settings" /var/log/sssd/*
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_store_policy_settings] (0x0020):
[/var/lib/sss/gpo_cache/DOMAIN.COM/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/Machine/Microsoft/Windows
NT/SecEdit/GptTmpl.inf]: ini_config_parse failed [5][Input/output error]
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_store_policy_settings] (0x0020): Error (5) on
line 20: Equal sign is missing.
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_store_policy_settings] (0x0020): Error
encountered: 5.
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_cse_done] (0x0040): ad_gpo_store_policy_settings
failed: [5](Input/output error)
[Regression Potential]
The current state of SSSD in Xenial is broken for _some_ users (where the GPO
has a line without equal sign) it's _not known_ how many users are affected. A
potential regression could mean even more users are affected by a new unknown
bug.
Upstreams bugreport and patch:
https://fedorahosted.org/sssd/ticket/2751
Please backport to xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ding-libs/+bug/1641203/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1685131] Re: root cannot login to system without password
Yakkety has EOL'ed, and Xenial has entered the ESM (Extended Support) period. Therefore, I am marking both tasks as Won't Fix. ** Changed in: sssd (Ubuntu Yakkety) Status: New => Won't Fix ** Changed in: sssd (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1685131 Title: root cannot login to system without password Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: Won't Fix Status in sssd source package in Yakkety: Won't Fix Bug description: similar issue: https://pagure.io/SSSD/sssd/issue/3003 (Workaround suggested above don't work on Xenial) dev3 detail: /var/log/auth.log - dev3 sshd[77]: error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys root failed, status 1 root@dev3:~# cat .k5login us...@hk.domain.com root@dev3:~# cat /root/.k5login us...@hk.domain.com root@dev3:~# sss_ssh_authorizedkeys user1 root@dev3:~# sss_ssh_authorizedkeys root Error looking up public keys root@dev3:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial root@dev3:~# sssd --version 1.13.4 root@dev3:~# cat /etc/nsswitch.conf passwd: compat sss group: compat sss shadow: compat sss gshadow:files hosts: files dns networks: files protocols: db files services: db files sss ethers: db files rpc:db files netgroup: nis sss sudoers: files sss login from Mocha to dev3: user1@mocha:~$ ssh r...@dev3.hk.domain.com r...@dev3.hk.domain.com's password: (Ctrl+c) user1@mocha:~$ ssh us...@dev3.hk.domain.com Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-72-generic x86_64) user1@dev3:/home/user1$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1685131/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1597916] Re: SSSD authentication fails against AD on Samba4 domain controller host
Sorry about the delay on this. Unfortunately, Yakkety is EOL and Xenial entered its ESM period, so I am marking this bug as Won't Fix for both tasks. ** Changed in: sssd (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: sssd (Ubuntu Yakkety) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1597916 Title: SSSD authentication fails against AD on Samba4 domain controller host Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: Won't Fix Status in sssd source package in Yakkety: Won't Fix Bug description: When SSSD is run on a server that hosts an AD domain controller powered by Samba4, all authentication attempts will fail if SSSD is configured to use the said AD DC as backend and access_provider = ad is specified in the SSSD configuration. No problems with authentication other servers with the same SSSD setup, it'll fail just for the host running the DC. This is a known bug documented and fixed with a simple patch available at https://fedorahosted.org/sssd/ticket/2870. Upstream has merged this and will be available in SSSD 1.14 when released. Please consider merging this patch for the Debian/Ubuntu SSSD packaging. I'd love to see this uploaded to xenial also. Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: sssd 1.13.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: i3 Date: Thu Jun 30 23:48:09 2016 InstallationDate: Installed on 2015-04-16 (441 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150321) SourcePackage: sssd UpgradeStatus: Upgraded to xenial on 2016-04-22 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1597916/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1636205] Re: NumberFormatter has incorrect currency symbols for certain locales
Xenial has entered ESM (Extended Support) recently. As such, I am closing its task as Won't Fix. ** Changed in: icu (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1636205 Title: NumberFormatter has incorrect currency symbols for certain locales Status in icu package in Ubuntu: Fix Released Status in php7.0 package in Ubuntu: Fix Released Status in icu source package in Xenial: Won't Fix Status in php7.0 source package in Xenial: Invalid Status in icu source package in Yakkety: Fix Released Status in php7.0 source package in Yakkety: Fix Released Bug description: Intl seems to be missing certain currency symbols in certain locales on ubuntu 16.04. I noticed while doing some unit tests. Under hu_HU locale, the expected result was 5 000 Ft The actual result turned out to be 5 000 HUF. It seems to be specific to this build, as this passes without problems on the CI server, and also worked fine on other distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1636205/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1890276] Re: rpcbind changes after bionic broke rup broadcast feature
Thanks for the further investigation, taraijpn. Indeed, I was able to (1) reproduce the scenario reported in the description, and (2) confirm that adding the "-r" option to /etc/default/rpcbind's OPTION variable will make the service run as the reporter expected. I appreciate the time Rafael spent on this bug and his conclusions; it was easy to verify the scenario following his comments. Having said all that, I consider that this is not a bug, and is properly documented in the manpages. I am therefore setting the status of this bug to Invalid; feel free to change it back to New and to provide more information if you disagree with this decision. Thank you. ** Changed in: rpcbind (Ubuntu) Status: Confirmed => Invalid ** Changed in: rpcbind (Ubuntu Eoan) Status: Confirmed => Invalid ** Changed in: rpcbind (Ubuntu Focal) Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1890276 Title: rpcbind changes after bionic broke rup broadcast feature Status in rpcbind package in Ubuntu: Invalid Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind source package in Eoan: Invalid Status in rpcbind source package in Focal: Invalid Bug description: When I call inetd services rup or rusersd in broadcast mode, I get answers from my Ubuntu 18.04 machines only. An Ubuntu 20.04 machine (here rzpc101) answers only when addressed directly: zierke@rzpc100$ rup rzpc100.informatik.un 14:02 up 10 days,8:30, load 0.52 0.38 0.23 rzlinux.informatik.un 14:02 up1 day,3:12, load 0.04 0.09 0.03 rzpc174.informatik.un 14:02 up 4 days, 19:28, load 0.00 0.01 0.00 ^C zierke@rzpc100$ rup rzpc101 rzpc101.informatik.un 14:02 up 3:29, 3 users, load 0.33 0.32 0.15 zierke@rzpc100$ rusers rzpc100.informatik.u zierke zierke rzlinux.informatik.u zierke zierke zierke ^C zierke@rzpc100$ rusers rzpc101 rzpc101.informatik.u zierke zierke zierke zierke@rzpc101$ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 zierke@rzpc100$ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openbsd-inetd 0.20160825-4build1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 14:03:06 2020 InstallationDate: Installed on 2020-07-24 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: openbsd-inetd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1890276/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
I took the liberty to clean up this bug and mark things as Invalid/Fix Released as needed. Hopefully I got everything right, but feel free to reopen/re-classify a task if there's something wrong. Thanks. ** Changed in: libseccomp (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: libseccomp (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: Invalid Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Released Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Released Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: docker.io (Ubuntu Bionic) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Focal) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Bionic) Status: Fix Released => Invalid ** Changed in: docker.io (Ubuntu Xenial) Status: Won't Fix => Invalid ** Changed in: docker.io (Ubuntu Focal) Status: Fix Released => Invalid ** Changed in: docker.io (Ubuntu Hirsute) Status: Fix Released => Invalid ** Changed in: libseccomp (Ubuntu Xenial) Status: New => Fix Released ** Changed in: libseccomp (Ubuntu Bionic) Status: New => Fix Released ** Changed in: libseccomp (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: docker.io (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with:
[Group.of.nepali.translators] [Bug 1883614] Re: sssd got killed due to segfault in ubuntu 16.04
Xenial is in ESM state right now, and as such there are no immediate
plans to fix this bug in it.
** Changed in: sssd (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed due to segfault in ubuntu 16.04
Status in sssd package in Ubuntu:
Triaged
Status in sssd source package in Xenial:
Won't Fix
Bug description:
SSSD.LOG
--
(Sun Jun 14 20:23:53 2020) [sssd] [mt_svc_sigkill] (0x0010): [pam][13305] is
not responding to SIGTERM. Sending SIGKILL.
(Sun Jun 14 20:29:34 2020) [sssd] [monitor_restart_service] (0x0010): Process
[nss], definitely stopped!
apport.log:
--
ERROR: apport (pid 623) Sun Jun 14 20:25:21 2020: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 515, in
get_pid_info(pid)
File "/usr/share/apport/apport", line 62, in get_pid_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
FileNotFoundError: [Errno 2] No such file or directory: '/proc/13305'
ERROR: apport (pid 623) Sun Jun 14 20:25:21 2020: pid: 623, uid: 0, gid: 0,
euid: 0, egid: 0
ERROR: apport (pid 623) Sun Jun 14 20:25:21 2020: environment: environ({})
root@gamma13:/var/log# ps -fp 13305
UIDPID PPID C STIME TTY TIME CMD
syslog
--
Jun 14 20:20:32 gamma13 sssd[be[myorg]]: Starting up
Jun 14 20:22:06 gamma13 kernel: [2543859.316724] sssd_pam[13305]: segfault at
a4 ip 7f0f77329989 sp 7fff35844480 error 4 in
libdbus-1.so.3.14.6[7f0f772ff000+4b000]
Jun 14 20:22:06 gamma13 sssd[be[myorg]]: Starting up
Jun 14 20:22:53 gamma13 sssd: Killing service [pam], not responding to pings!
Jun 14 20:23:53 gamma13 sssd: [pam][13305] is not responding to SIGTERM.
Sending SIGKILL.
Jun 14 20:23:58 gamma13 sssd[pam]: Starting up
Jun 14 20:24:27 gamma13 smtpd[1732]: smtp-in: session 689f0b74a7b74828:
connection from host gamma13.internal.myorg.com.internal.myorg.com [local]
established
Jun 14 20:25:01 gamma13 CRON[1041]: (root) CMD (command -v debian-sa1 >
/dev/null && debian-sa1 1 1)
Jun 14 20:25:01 gamma13 CRON[1042]: (root) CMD (/usr/sbin/icsisnap
/var/lib/icsisnap)
Jun 14 20:27:57 gamma13 sssd[be[myorg]]: Starting up
Jun 14 20:27:58 gamma13 systemd[1]: Started Session 16859 of user kamals.
Jun 14 20:29:18 gamma13 sssd[be[myorg]]: Starting up
Jun 14 20:29:28 gamma13 sssd[nss]: Starting up
Jun 14 20:29:30 gamma13 sssd[nss]: Starting up
Jun 14 20:29:37 gamma13 sssd[nss]: Starting up
Jun 14 20:29:37 gamma13 sssd: Exiting the SSSD. Could not restart critical
service [nss].
Jun 14 20:29:44 gamma13 sssd[be[myorg]]: Shutting down
Jun 14 20:29:44 gamma13 sssd[pam]: Shutting down
[Another server had this log
Jun 9 21:12:52 grid kernel: [5088481.338650] rpcmgr[1409]: segfault
at 7fa5541c1d13 ip 7fa5dcb5be8f sp 7fa5d35ccc80 error 4 in
libpthread-2.23.so[7fa5dcb54000+18000]
]
kamals@gamma13:~$ uname -r
4.4.0-178-generic
kamals@gamma13:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
Hi, the sssd got killed for second time with segfault, the above log is the
latest sssd shutdown.
Please help me how to fix this issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1883614/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1453463] Re: undefined symbol: FAMNoExists
** Changed in: lighttpd (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1453463 Title: undefined symbol: FAMNoExists Status in lighttpd: Fix Released Status in lighttpd package in Ubuntu: Fix Committed Status in lighttpd source package in Xenial: Won't Fix Status in lighttpd source package in Bionic: Triaged Status in lighttpd source package in Focal: Confirmed Bug description: lighttpd won't start. Steps to reproduce: $ sudo /usr/sbin/lighttpd or $ sudo systemctl start lighttpd Expected outcome: daemon starts. Seen instead: /usr/sbin/lighttpd: symbol lookup error: /usr/sbin/lighttpd: undefined symbol: FAMNoExists or Job for lighttpd.service failed. See "systemctl status lighttpd.service" and "journalctl -xe" for details. $ systemctl status lighttpd.service -l May 09 17:53:32 deunan systemd[1]: Starting Lighttpd Daemon... May 09 17:53:32 deunan lighttpd[8229]: /usr/sbin/lighttpd: symbol lookup error: /usr/sbin/lighttpd: undefined symbol: FAMNoExists Other info: `ldd /usr/sbin/lighttpd` does not report any missing shared libraries. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lighttpd 1.4.35-4ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 Date: Sat May 9 17:51:52 2015 InstallationDate: Installed on 2013-06-08 (700 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) ProcEnviron: LANGUAGE=en_CA:en TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lighttpd UpgradeStatus: Upgraded to vivid on 2015-04-25 (14 days ago) mtime.conffile..etc.lighttpd.conf.available.10.cgi.conf: 2013-08-02T23:17:55 mtime.conffile..etc.lighttpd.conf.available.10.fastcgi.conf: 2013-09-11T11:19:16 To manage notifications about this bug go to: https://bugs.launchpad.net/lighttpd/+bug/1453463/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1904620] Re: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9
Thank you for taking the time to report this bug and helping to make Ubuntu better. If someone can prepare a backport, please follow the steps at: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure All the steps documented there need to be followed. In particular: 1) Explain the bug well enough so the SRU team (who are probably not familiar with this package) can understand the real user impact in terms of use case so they can make a decision as to whether backporting the fix to stable releases justifies the regression risk to existing, unaffected users. 2) Make sure that the fixing this in a stable Ubuntu release does not regress existing users of the module not affected by this bug (e.g. other architectures or ways of consuming this module). 3) Have a test case that can be followed by someone not familiar with the package for SRU verification purposes. ** Also affects: tomcat8 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: tomcat8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1904620 Title: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9 Status in tomcat8 package in Ubuntu: Invalid Status in tomcat8 source package in Xenial: New Bug description: An update to the BCEL library has been pushed upstream since Tomcat 8.0.42 : https://bz.apache.org/bugzilla/show_bug.cgi?id=60688 Without this update, loading libraries which are compatible with Java 8 or older but compiled for Java 9 on Tomcat 8.0.32 on Ubuntu Xenial prevents Tomcat from starting. Is it possible to backport this update to the BECL library on Tomcat 8.0.32 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1904620/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
** Tags added: server-next ** Also affects: rsync (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: New Status in rsync source package in Xenial: Triaged Status in rsync source package in Bionic: Triaged Status in rsync source package in Focal: Triaged Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
I'm marking the dnsmasq bug as Invalid since this is a problem with squid/systemd. ** Changed in: squid (Ubuntu Xenial) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: dnsmasq (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1761096 Title: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed Status in dnsmasq package in Ubuntu: Fix Released Status in squid package in Ubuntu: Fix Released Status in dnsmasq source package in Xenial: Invalid Status in squid source package in Xenial: Confirmed Bug description: [Impact] When using dnsmasq along with squid on Ubuntu Xenial, the user will experience a deadlock while performing on every second execution of the "systemctl start dnsmasq.service" command. The deadlock will be caused by an attempt to invoke, by nss-lookup.target, a "systemctl reload squid.service", which will itself try to start the nss- lookup.target, which will be waiting on squid, therefore eventually leading to a timeout. The underlying cause of this deadlock is related to how systemd used to handle dependencies between multiple jobs being started in the same transaction. [Test Case] One can reproduce the issue on a Xenial container: $ lxc launch ubuntu-daily:xenial squid-bug1761096 $ lxc shell squid-bug1761096 # apt update # apt install squid dnsmasq -y It is quite possible that during "apt install" the bug will manifest, and dnsmasq will fail to start due to a timeout. The user might see a message like: Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. If the bug doesn't manifest itself during installation, the following commands in sequence should trigger it: # systemctl restart dnsmasq.service # systemctl restart dnsmasq.service [Regression Potential] This change only touches the mechanism by which squid has its configuration reloaded in case of a DNS resolver change. Because "systemctl reload --no-block" returns practically immediately, if squid's configuration file is invalid the user won't see any notifications. However, this behaviour is already present currently, because "systemctl reload squid" invokes "/etc/init.d/squid reload"; the user has to check "journalctl -u squid.service" if she wants to verify whether there were any failures during the reload. Other than that, and because systemctl will offload the service to the SysV script as usual (in the case of squid), I don't foresee any potential regressions. [Original Description] Setup to reproduce: Ubuntu Xenial amd64 net install iso from http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer- amd64/current/images/netboot/mini.iso Install system with mostly defaults + LVM + OpenSSH server Note that this bug applies to both DHCP and static IP+DNS network configurations Once server rebooted and is available, log in and install dnsmasq + squid: apt-get update && apt-get install squid dnsmasq output of this can be found at https://pastebin.com/9Atuipju journalctl -xe output at https://pastebin.com/uLhfM4jN Furthermore at this point I can run alternating errors root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:18:07 CEST 2018 Wed Apr 4 09:18:07 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq stop ; date Wed Apr 4 09:18:39 CEST 2018 Wed Apr 4 09:18:39 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:19:10 CEST 2018 Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. Wed Apr 4 09:20:40 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:42:57 CEST 2018 Wed Apr 4 09:42:57 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq stop ; date Wed Apr 4 09:43:14 CEST 2018 Wed Apr 4 09:43:14 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:43:26 CEST 2018 Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. Wed Apr 4 09:44:56 CEST 2018 and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s timeout Complete journalctl -xe output attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1761096/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Po
[Group.of.nepali.translators] [Bug 1705483] Re: ADT tests periodically failing on amd64 - file exists after removal
This is still happening on xenial, although it seems to be happening on s390x now, so I decided to investigate why. I reserved two s390x instances running xenial on canonistack and used them to run the dep8 tests. On the first machine, after dget'ing the source package for nfs-utils and rebuilding it locally, I did: # adt-run -o dep8 -B ./nfs-utils_1.2.8-9ubuntu12.3.dsc --- ssh -H 10.48.132.122 -l ubuntu -r Where 10.48.132.122 is the IP address of the *second* machine. This assumes that everything is properly configured there: sudo, ssh keys. When I do this, I get the exact same error message as the reporter. After analyzing a lot of debug logs (using "rpcdebug -m nfs -s all", "rpcdebug -m nfsd -s all", "rpcdebug -m rpc -s all"), I finally found that the problem are the lease and the grace times used by nfsd. There are various reports on the internet about problems very similar to this one and that are caused by the same reason. Since we're dealing with a relatively old nfsd, which doesn't support the --lease-time nor --grace-time options, the only way to adjust these parameters is through /proc/fs/nfsd/. That's what I did. The fix for this problem is relatively simple. On debian/tests/local- server-client, right at the start of the "post_boot_tests" function, we have to do: systemctl stop nfs-server.service echo 10 > /proc/fs/nfsd/nfsv4leasetime echo 10 > /proc/fs/nfsd/nfsv4gracetime systemctl start nfs-server.service After this, I see the test passing for me: adt-run [14:25:43]: test local-server-client: ---] adt-run [14:25:44]: test local-server-client: - - - - - - - - - - results - - - - - - - - - - local-server-client PASS adt-run [14:25:44]: summary local-server-client PASS Since this is happening on xenial, I don't believe a SRU is justified to fix this issue. Therefore, I will propose that we force-badtest this particular test instead. I'm writing this comment more as a reference. ** Changed in: nfs-utils (Ubuntu) Importance: Undecided => Low ** Changed in: nfs-utils (Ubuntu) Status: New => Confirmed ** Also affects: nfs-utils (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1705483 Title: ADT tests periodically failing on amd64 - file exists after removal Status in nfs-utils package in Ubuntu: Confirmed Status in nfs-utils source package in Xenial: New Bug description: http://autopkgtest.ubuntu.com/packages/nfs-utils/artful/amd64 You can see that sometimes the ADT tests fail. With retries working. FAIL: /mnt/nfs_home/hello.txt exists after removal autopkgtest [06:24:45]: test local-server-client: ---] autopkgtest [06:24:46]: test local-server-client: - - - - - - - - - - results - - - - - - - - - - local-server-client FAIL non-zero exit status 1 autopkgtest [06:24:46]: test local-server-client: - - - - - - - - - - stderr - - - - - - - - - - FAIL: /mnt/nfs_home/hello.txt exists after removal autopkgtest [06:24:46]: summary local-server-client FAIL non-zero exit status 1 Exit request sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1705483/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
