[Kernel-packages] [Bug 1731069] Re: Debug symbols missing: Unable to locate package ssldump-dbgsym
This bug has nothing to do with the kernel, no idea why it's trying to get me to run apport-collect. ** Package changed: linux (Ubuntu) => ssldump (Ubuntu) ** Changed in: ssldump (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731069 Title: Debug symbols missing: Unable to locate package ssldump-dbgsym Status in ssldump package in Ubuntu: Confirmed Bug description: When trying to debug a segmentation fault in ssldump, the debug symbols are missing. This renders debugging impossible. root@sql01:~# apt-get install ssldump-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ssldump-dbgsym This affects Xenial: Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ssldump/+bug/1731069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731069] [NEW] Debug symbols missing: Unable to locate package ssldump-dbgsym
Public bug reported: When trying to debug a segmentation fault in ssldump, the debug symbols are missing. This renders debugging impossible. root@sql01:~# apt-get install ssldump-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ssldump-dbgsym This affects Xenial: Description:Ubuntu 16.04.3 LTS Release:16.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731069 Title: Debug symbols missing: Unable to locate package ssldump-dbgsym Status in linux package in Ubuntu: New Bug description: When trying to debug a segmentation fault in ssldump, the debug symbols are missing. This renders debugging impossible. root@sql01:~# apt-get install ssldump-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ssldump-dbgsym This affects Xenial: Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620744] Re: sssd/ntpd/postfix + overlayfs startup failure: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied]
Zooming in to the behaviour of sssd, it appears the permission denied error happens like so: - A working sssd installation is installed and the daemon started. Logfiles are created in /var/log/sssd, including /var/log/sssd/sssd.log, owned by and exclusively read/writable by root: root@syslog01:~# ls -al /var/log/sssd total 12 drwxr-x--- 1 sssd sssd 4096 Jun 6 14:55 . drwxrwxr-x 1 root syslog 4096 Jun 6 10:45 .. -rw--- 1 root root 0 Jun 6 14:55 ldap_child.log -rw--- 1 root root 0 Jun 6 14:55 sssd_LDAP.log -rw--- 1 root root 0 Jun 6 14:55 sssd.log -rw--- 1 root root260 Jun 6 14:56 sssd_nss.log -rw--- 1 root root 0 Jun 6 14:55 sssd_pam.log -rw--- 1 root root 0 Jun 6 14:55 sssd_ssh.log -rw--- 1 root root 0 Jun 6 14:55 sssd_sudo.log - overlayfs is mounted successfully over /var/log. - sssd is restarted (manually, or at next boot). sssd cannot open /var/log/sssd/sssd.log despite having permission to do so, with permission denied. - Manually removing /var/log/sssd/* and restarting sssd causes sssd to start successfully, and the logfiles are recreated successfully with the same mode and user as above. It seems overlayfs fails at the copy-up step when sssd tries to open existing logfiles that exist in the lowerdir by not yet exist in the upperdir. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620744 Title: sssd/ntpd/postfix + overlayfs startup failure: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied] Status in linux package in Ubuntu: Triaged Bug description: If an attempt is made to mount an overlay filesystem over the /var/log directory, this causes sssd to refuse to start up. The startup fails at the point where sssd attempts to write to its logfiles: sssd: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied] sssd is running as root, and should have no problem writing to logfiles. Removing the -f option from sssd causes sshd to not attempt to write to /var/log/ssshd/ssshd.log and sshd startup succeeds. Running sssd without any flags logs to syslog, and this works correctly, logging to /var/log/syslog on the overlayfs filesystem. Removing the file /etc/apparmor.d/usr.sbin.sssd causes sssd to start up correctly, logging to the overlayfs /var/log/sssd directory without an issue. Looks like the apparmour configration for sssd breaks when an overlayfs is present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620744] Re: sssd/ntpd/postfix + overlayfs startup failure: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied]
I removed apparmor completely, and it made no difference - postfix+overlayfs is still broken without apparmor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620744 Title: sssd/ntpd/postfix + overlayfs startup failure: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied] Status in linux package in Ubuntu: Triaged Bug description: If an attempt is made to mount an overlay filesystem over the /var/log directory, this causes sssd to refuse to start up. The startup fails at the point where sssd attempts to write to its logfiles: sssd: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied] sssd is running as root, and should have no problem writing to logfiles. Removing the -f option from sssd causes sshd to not attempt to write to /var/log/ssshd/ssshd.log and sshd startup succeeds. Running sssd without any flags logs to syslog, and this works correctly, logging to /var/log/syslog on the overlayfs filesystem. Removing the file /etc/apparmor.d/usr.sbin.sssd causes sssd to start up correctly, logging to the overlayfs /var/log/sssd directory without an issue. Looks like the apparmour configration for sssd breaks when an overlayfs is present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620744] Re: sssd/ntpd/postfix + overlayfs startup failure: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied]
Update the package to the linux kernel, as this bug affects multiple services. ** Package changed: sssd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620744 Title: sssd/ntpd/postfix + overlayfs startup failure: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied] Status in linux package in Ubuntu: Triaged Bug description: If an attempt is made to mount an overlay filesystem over the /var/log directory, this causes sssd to refuse to start up. The startup fails at the point where sssd attempts to write to its logfiles: sssd: Could not open file [/var/log/sssd/sssd.log]. Error: [13][Permission denied] sssd is running as root, and should have no problem writing to logfiles. Removing the -f option from sssd causes sshd to not attempt to write to /var/log/ssshd/ssshd.log and sshd startup succeeds. Running sssd without any flags logs to syslog, and this works correctly, logging to /var/log/syslog on the overlayfs filesystem. Removing the file /etc/apparmor.d/usr.sbin.sssd causes sssd to start up correctly, logging to the overlayfs /var/log/sssd directory without an issue. Looks like the apparmour configration for sssd breaks when an overlayfs is present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 613022] Re: ssh daemon hangs after publickey packet sent
I am seeing this bug in Ubuntu v14.04. No obvious cause. When it's happened we've physically replaced the instances, as there is no console access at AWS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/613022 Title: ssh daemon hangs after publickey packet sent Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Bug description: A launched ec2 instance in ap-southeast-1 region is unreachable via ssh. $ ssh -vvv ec2-175-41-171-225.ap-southeast-1.compute.amazonaws.com shows progress up to : debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: smoser@brickies debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply Then nothing for minutes before session is killed (manually). In a 'good' connection, the following would be next: debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey I'll attach full 'ssh -vvv' logs good and bad connection. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openssh-server 1:5.5p1-4ubuntu3 ProcVersionSignature: User Name 2.6.35-14.19-virtual 2.6.35 Uname: Linux 2.6.35-14-virtual x86_64 Architecture: amd64 Date: Tue Aug 3 14:45:25 2010 Ec2AMI: ami-9fc4bbcd Ec2AMIManifest: ubuntu-images-testing-ap-southeast-1/ubuntu-maverick-daily-amd64-server-20100803.1.manifest.xml Ec2AvailabilityZone: ap-southeast-1a Ec2InstanceType: m1.large Ec2Kernel: aki-11d5aa43 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/613022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
