[Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
Can confirm, this bug is still a reality in Ubuntu 20.04 (focal) and is triggered by two reloads in a row. root@nginx:~# ps aux|grep nginx root 3356067 0.0 0.1 71600 9788 ?Ss 15:46 0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; www-data 3356068 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356069 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356070 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356071 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356072 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356073 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356074 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356075 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process root 3356102 0.0 0.0 8900 676 pts/0S+ 15:46 0:00 grep --color=auto nginx root@nginx:~# service nginx reload root@nginx:~# ps aux|grep nginx root 3356067 0.2 0.3 81404 28848 ?Ss 15:46 0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; www-data 3356266 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356267 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356268 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356269 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356270 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356271 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356272 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356273 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process root 3356296 0.0 0.0 17196 7168 ?R15:46 0:00 /usr/bin/pgrep nginx root 3356309 0.0 0.0 8900 736 pts/0S+ 15:46 0:00 grep --color=auto nginx root@nginx:~# service nginx reload root@nginx:~# ps aux|grep nginx root 3356355 0.0 0.0 8900 736 pts/0S+ 15:46 0:00 grep --color=auto nginx At the time of the second reload, the following segfault is logged in /var/log/kern.log: May 4 15:46:50 onl-paylb02-p kernel: [4141537.262674] nginx[3356067]: segfault at 51 ip 7f6b7d1535c9 sp 7ffe634334d0 error 4 in libperl.so.5.30.0[7f6b7d0eb000+166000] May 4 15:46:50 onl-paylb02-p kernel: [4141537.262681] Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430696] Re: Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown connection handle
Same problem here on a DELL Latitude E7440 with Linux Mint 17.3 (based on Ubuntu 14.04 LTS) installed. When I use a Plantronics Voyager which connects directly to the notebook's internal bluetooth chip, I get these dmesg entries: $ dmesg | grep -i Bluetooth [3.994061] Bluetooth: Core ver 2.21 [3.994078] Bluetooth: HCI device and connection manager initialized [3.994082] Bluetooth: HCI socket layer initialized [3.994085] Bluetooth: L2CAP socket layer initialized [3.994095] Bluetooth: SCO socket layer initialized [4.014377] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [4.014381] Bluetooth: BNEP filters: protocol multicast [4.014384] Bluetooth: BNEP socket layer initialized [4.017044] Bluetooth: RFCOMM TTY layer initialized [4.017049] Bluetooth: RFCOMM socket layer initialized [4.017054] Bluetooth: RFCOMM ver 1.11 [4.119489] Bluetooth: hci0: read Intel version: 370710018002030d37 [4.119491] Bluetooth: hci0: Intel device is already patched. patch num: 37 [ 32.154782] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 32.164817] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 32.164821] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 572.934811] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 572.934815] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 572.934817] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 641.073418] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 646.105832] Bluetooth: hci0 SCO packet for unknown connection handle 257 [ 646.105837] Bluetooth: hci0 SCO packet for unknown connection handle 257 [ 646.105839] Bluetooth: hci0 SCO packet for unknown connection handle 257 The headset is not correctly recognized. Sometimes works, sometimes doesn't (sound output works better than input, microphone seems not available). In VMware Player, the headset is not recognized to add as a removable device into the VM. However if I use an almost identical headset, also a Plantronics Voyager but with a bluetooth usb dongle, I get no problems at all and I am able to add it as a removable device into the VM. So same OS, same hardware but different handling of internal bluetooth vs. bluetooth dongle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430696 Title: Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown connection handle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658691] Re: Docker service is not properly restarted when updating docker.io package
Either a restart after the package upgrade or nothing at all. But not a 'start' of Docker as it is was when I opened the bug. Don't know if that has changed since, almost a year has passed by. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658691 Title: Docker service is not properly restarted when updating docker.io package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1658691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
FYI I stumbled on this problem after a system update (which broke production!) and collected data in a troubleshooting session and documented this here https://www.claudiokuenzler.com/blog/959 /keepalived-virtual-ip-addresses-gone-lost-after-systemd-update. Once I found out the restart of systemd-networkd causes the keepalived vips to be gone, I finally came across this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668621] [NEW] No restart of Docker daemon after docker.io package is updated
Public bug reported: In our setup using Ubuntu 16.04 Xenial, Rancher as orchestration and docker.io package from the Ubuntu repos, we've already hit twice a problem after the docker.io packages was updated (once manually, once through unattended upgrades). The first time new containers couldn't be deployed/started anymore and I documented this on the following article: https://www.claudiokuenzler.com/blog/689/rancher-error-response-from-daemon-dockerd-deleted-no-such-file-or-directory The second time (discovered a few days ago and fixed today) cross communication between containers on host #1 and containers on host #2 didn't work anymore. thanks to the logs in /var/log/apt/ I saw that an update of docker.io was installed . A manual restart of the Docker daemon solved the problems in both cases. The root cause seems to be a lack of a "stop" of the Docker daemon in a preinst file followed by a "start" (or a "restart" to keep it simple) of the Docker daemon in a postinst file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: docker.io 1.12.3-0ubuntu4~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Feb 28 14:46:05 2017 InstallationDate: Installed on 2016-12-08 (81 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: - In our setup using Ubuntu 16.04 Xenial, Rancher as orchestration and docker.io package from the Ubuntu repos, we've already hit twice a problem after the docker.io packages was updated (once manually, once through unattended upgrades). - The first time new containers couldn't be deployed/started anymore and I documented this on the following article: + In our setup using Ubuntu 16.04 Xenial, Rancher as orchestration and docker.io package from the Ubuntu repos, we've already hit twice a problem after the docker.io packages was updated (once manually, once through unattended upgrades). + The first time new containers couldn't be deployed/started anymore and I documented this on the following article: https://www.claudiokuenzler.com/blog/689/rancher-error-response-from-daemon-dockerd-deleted-no-such-file-or-directory The second time (today) cross communication between containers on host #1 and containers on host #2 didn't work anymore. thanks to the logs in /var/log/apt/ I saw that an update of docker.io was installed . A manual restart of the Docker daemon solved the problems in both cases. The root cause seems to be a lack of a "stop" of the Docker daemon in a - preinst file or a "restart" of the Docker daemon in a postinst file. + preinst file followed by a "start" (or a "restart" to keep it simple) of + the Docker daemon in a postinst file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: docker.io 1.12.3-0ubuntu4~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Feb 28 14:46:05 2017 InstallationDate: Installed on 2016-12-08 (81 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: - LANGUAGE=en_US:en - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In our setup using Ubuntu 16.04 Xenial, Rancher as orchestration and docker.io package from the Ubuntu repos, we've already hit twice a problem after the docker.io packages was updated (once manually, once through unattended upgrades). The first time new containers couldn't be deployed/started anymore and I documented this on the following article: https://www.claudiokuenzler.com/blog/689/rancher-error-response-from-daemon-dockerd-deleted-no-such-file-or-directory - The second time (today) cross communication between containers on host #1 and containers on host #2 didn't work anymore. thanks to the logs in /var/log/apt/ I saw that an update of docker.io was installed . A manual restart of the Docker daemon solved the problems in both cases. + The second time (discovered a few days ago and fixed today) cross communication between containers on host #1 and containers on host #2 didn't work anymore. thanks to the logs in /var/log/apt/ I saw that an update of docker.io was installed . A manual restart of the Docker daemon solved the problems in both cases. The root cau
[Bug 1668621] Re: No restart of Docker daemon after docker.io package is updated
*** This bug is a duplicate of bug 1658691 *** https://bugs.launchpad.net/bugs/1658691 Dang! I already opened such a ticket. Please refer to https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1658691. Where'd my mind go...?! ** This bug has been marked a duplicate of bug 1658691 Docker service is not properly restarted when updating docker.io package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668621 Title: No restart of Docker daemon after docker.io package is updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1668621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324082] [NEW] Missing dependency for innotop (libterm-readkey-perl)
Public bug reported: Description:Ubuntu 14.04 LTS Release:14.04 mariadb-client-5.5: Installed: 5.5.37-0ubuntu0.14.04.1 Candidate: 5.5.37-0ubuntu0.14.04.1 innotop is installed through the mariadb-client-5.5 package but cannot be launched: # innotop Can't locate Term/ReadKey.pm in @INC (you may need to install the Term::ReadKey module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at /usr/bin/innotop line 1341. BEGIN failed--compilation aborted at /usr/bin/innotop line 1341. It seems that a dependency to the package "libterm-readkey-perl" is missing. Once manually installed "libterm-readkey-perl", the innotop command was working. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mariadb-client 5.5.37-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag veth bridge stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp gpio_ich kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd sb_edac serio_raw joydev lpc_ich hpilo edac_core ioatdma hpwdt dca ipmi_si acpi_power_meter mac_hid lp parport hid_generic psmouse usbhid tg3 hid ptp hpsa pps_core ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed May 28 13:28:45 2014 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mariadb-5.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mariadb-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1324082 Title: Missing dependency for innotop (libterm-readkey-perl) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-5.5/+bug/1324082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319066] Re: [HP ProLiant DL380p Gen8 Server] kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50()
OK, warnings re-appeared after an uptime of 3124s: [ 3124.055076] [ cut here ] [ 3124.055100] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50() [ 3124.055105] Hardware name: ProLiant DL380p Gen8 [ 3124.055108] Modules linked in: des_generic md4 nls_utf8 cifs fscache veth vesafb coretemp kvm_intel bridge kvm ghash_clmulni_intel aesni_intel cryptd stp llc aes_x86_64 gpio_ich hpilo hpwdt psmouse joydev microcode sb_edac mac_hid edac_core serio_raw ioatdma lpc_ich acpi_power_meter lp ext2 parport hid_generic usbhid hid hpsa tg3 igb dca [ 3124.055178] Pid: 8137, comm: jsvc Tainted: GW3.5.0-49-generic #74~precise1-Ubuntu [ 3124.055182] Call Trace: [ 3124.055197] [] warn_slowpath_common+0x7f/0xc0 [ 3124.055204] [] warn_slowpath_null+0x1a/0x20 [ 3124.055212] [] drop_nlink+0x46/0x50 [ 3124.055233] [] cifs_unlink+0x1b0/0x3f0 [cifs] [ 3124.055243] [] vfs_unlink.part.25+0x80/0xf0 [ 3124.055250] [] vfs_unlink+0x3c/0x60 [ 3124.055259] [] do_unlinkat+0x1aa/0x1d0 [ 3124.055267] [] ? sys_newstat+0x2a/0x40 [ 3124.055276] [] sys_unlink+0x16/0x20 [ 3124.055288] [] system_call_fastpath+0x16/0x1b [ 3124.055293] ---[ end trace 4b4d7bb0b6038fe6 ]--- Will try with newer BIOS next time, thanks for the hint. It might take a while until I get another downtime for this host though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319066 Title: [HP ProLiant DL380p Gen8 Server] kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1319066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940030] Re: rsyslog stops working after logrotate until restarted
Can confirm the same behavior on Ubuntu 16.04 LTS. Log files are rotated by logrotate but postrotate command doesn't seem to work. ls -ltr /var/log | tail -rw-r- 1 syslog adm 0 Aug 19 06:42 kern.log -rw-rw 1 root utmp0 Sep 1 06:49 btmp.1 -rw-r--r-- 1 root root 252 Sep 7 17:02 memcached.log -rw-rw-r-- 1 root utmp15360 Sep 29 15:43 wtmp.1 -rw-rw 1 root utmp0 Oct 1 06:41 btmp -rw-r- 1 syslog adm605488 Oct 10 11:56 mail.log.1 -rw-rw-r-- 1 root utmp 4224 Oct 10 12:38 wtmp -rw-rw-r-- 1 root utmp 292876 Oct 10 12:38 lastlog -rw-r- 1 syslog adm 17692156 Oct 10 13:53 auth.log.1 -rw-r- 1 syslog adm 3045212 Oct 10 13:53 syslog.1 postrotate command seems wrong anyway: # cat /etc/logrotate.d/rsyslog | grep -A 2 postrotate postrotate invoke-rc.d rsyslog rotate > /dev/null endscript -- postrotate invoke-rc.d rsyslog rotate > /dev/null endscript invoke-rc.d rsyslog rotate doesn't work: # invoke-rc.d rsyslog rotate initctl: invalid command: rotate Try `initctl --help' for more information. invoke-rc.d: initscript rsyslog, action "rotate" failed. But in general postrotate commands don't seem to be executed at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/940030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940030] Re: rsyslog stops working after logrotate until restarted
Correction: "But in general postrotate commands don't seem to be executed at all." Yes it does work, phew. But the command "invoke-rc.d rsyslog rotate" is wrong as it doesn't work: # invoke-rc.d rsyslog rotate initctl: invalid command: rotate Try `initctl --help' for more information. invoke-rc.d: initscript rsyslog, action "rotate" failed. https://bugs.launchpad.net/nginx/stable/+bug/1450770 is related. There it's also the problem with a non-working postrotate command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/940030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
Hello Christopher, I am not sure whether this is a xorg or kernel issue. xorg is not installed. When I reported the bug, I could only select xorg when reporting a display error. The apport-collect command does not update this bug because: Package xorg not installed and no hook available, ignoring *** Updating problem report No additional information collected. Please feel free to move this bug to the right package. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687038/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687040/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687042/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687043/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687041/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
apport information ** Tags added: apport-collected ** Description changed: Ubuntu 16.04 BETA2 installed correctly on Dell PowerEdge 1850 server. Booting seems to work correctly too (can see it on the monitor), but when I expect the login prompt, no output is sent to the monitor (black). I documented this on the following video: https://www.youtube.com/watch?v=VAtnBv8uZf8 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Apr 4 12:23:48 2016 InstallationDate: Installed on 2016-04-04 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Apr 28 11:14 seq + crw-rw+ 1 root audio 116, 33 Apr 28 11:14 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=4ea2a341-bca0-41da-aa0b-d99329ad9670 + InstallationDate: Installed on 2016-04-04 (76 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) + IwConfig: Error: [Errno 2] No such file or directory + MachineType: Dell Computer Corporation PowerEdge 1850 + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=a9f64ee8-64f7-4b9f-96e3-5d0032701ada ro + ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-15-generic N/A + linux-backports-modules-4.4.0-15-generic N/A + linux-firmware1.157 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 04/25/2008 + dmi.bios.vendor: Dell Computer Corporation + dmi.bios.version: A07 + dmi.board.name: 0D8266 + dmi.board.vendor: Dell Computer Corporation + dmi.board.version: A02 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Computer Corporation + dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd04/25/2008:svnDellComputerCorporation:pnPowerEdge1850:pvr:rvnDellComputerCorporation:rn0D8266:rvrA02:cvnDellComputerCorporation:ct23:cvr: + dmi.product.name: PowerEdge 1850 + dmi.sys.vendor: Dell Computer Corporation ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687036/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687046/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687039/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687045/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687037/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4687044/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658691] [NEW] Docker service is not properly restarted when updating docker.io package
Public bug reported: After the docker.io package was updated last Friday (Jan 20 2017) we started experiencing issues and getting errors when new containers should be launched. Here's an excerpt of errors found in syslog: Jan 23 06:25:07 dockerserver kernel: [7751793.479504] aufs au_opts_verify:1597:dockerd[10676]: dirperm1 breaks the protection by the permission bits on the lower branch Jan 23 06:25:07 dockerserver dockerd[13066]: time="2017-01-23T06:25:07.616134541+01:00" level=error msg="containerd: start container" error="oci runtime err or: process_linux.go:330: running prestart hook 0 caused \"fork/exec /usr/bin/dockerd (deleted): no such file or directory: \"" id=e20acb788ee6554bb1240bc7c07 bd033a8d15d8e4f246c553120beba4bfbcb2f Jan 23 06:25:07 dockerserver dockerd[13066]: time="2017-01-23T06:25:07.627421952+01:00" level=error msg="Create container failed with error: oci runtime err or: process_linux.go:330: running prestart hook 0 caused \"fork/exec /usr/bin/dockerd (deleted): no such file or directory: \"" Jan 23 06:25:07 dockerserver dockerd[13066]: time="2017-01-23T06:25:07.647734613+01:00" level=warning msg="Couldn't run auplink before unmount /var/lib/dock er/aufs/mnt/e513ea71816cd308e5815c5b24ce34833f1de4e6d4f700de090c50c70b050678: exec: \"auplink\": executable file not found in $PATH" Jan 23 06:25:07 dockerserver dockerd[13066]: time="2017-01-23T06:25:07.664973641+01:00" level=error msg="Handler for POST /v1.22/containers/e20acb788ee6554b b1240bc7c07bd033a8d15d8e4f246c553120beba4bfbcb2f/start returned error: oci runtime error: process_linux.go:330: running prestart hook 0 caused \"fork/exec /us r/bin/dockerd (deleted): no such file or directory: \"" Jan 23 06:25:07 dockerserver kernel: [7751793.760983] aufs au_opts_verify:1597:dockerd[30845]: dirperm1 breaks the protection by the permission bits on the lower branch Jan 23 06:25:07 dockerserver dockerd[13066]: time="2017-01-23T06:25:07.902874678+01:00" level=error msg="containerd: start container" error="oci runtime err or: process_linux.go:330: running prestart hook 0 caused \"fork/exec /usr/bin/dockerd (deleted): no such file or directory: \"" id=e20acb788ee6554bb1240bc7c07 bd033a8d15d8e4f246c553120beba4bfbcb2f It looks like the update was installed correctly and afterwards started the Docker service (engine) - but there was no stop before applying the update (which could be added in a docker.io.preinst file). apt history shows: Start-Date: 2017-01-20 15:04:06 Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold install docker.io Requested-By: ansible (1001) Upgrade: runc:amd64 (1.0.0~rc1-0ubuntu1~16.04, 1.0.0~rc1-0ubuntu2~16.04.1), docker.io:amd64 (1.12.1-0ubuntu13~16.04.1, 1.12.3-0ubuntu4~16.04.2) End-Date: 2017-01-20 15:04:10 syslog shows for that timeframe (15.04:06 to 15:04:10): Jan 20 15:04:03 dockerserver systemd[1]: Created slice User Slice of ansible. Jan 20 15:04:03 dockerserver systemd[1]: Starting User Manager for UID 1001... Jan 20 15:04:03 dockerserver systemd[1]: Started Session 14956 of user ansible. Jan 20 15:04:03 dockerserver systemd[18545]: Reached target Sockets. Jan 20 15:04:03 dockerserver systemd[18545]: Reached target Timers. Jan 20 15:04:03 dockerserver systemd[18545]: Reached target Paths. Jan 20 15:04:03 dockerserver systemd[18545]: Reached target Basic System. Jan 20 15:04:03 dockerserver systemd[18545]: Reached target Default. Jan 20 15:04:03 dockerserver systemd[18545]: Startup finished in 22ms. Jan 20 15:04:03 dockerserver systemd[1]: Started User Manager for UID 1001. Jan 20 15:04:08 dockerserver systemd[1]: Reloading. Jan 20 15:04:09 dockerserver systemd[1]: apt-daily.timer: Adding 37min 2.565881s random time. Jan 20 15:04:09 dockerserver systemd[1]: Started ACPI event daemon. Jan 20 15:04:09 dockerserver systemd[1]: Reloading. Jan 20 15:04:09 dockerserver systemd[1]: apt-daily.timer: Adding 5h 27min 32.130480s random time. Jan 20 15:04:09 dockerserver systemd[1]: Started ACPI event daemon. Jan 20 15:04:10 dockerserver systemd[1]: Reloading. Jan 20 15:04:10 dockerserver systemd[1]: apt-daily.timer: Adding 11h 55min 14.530665s random time. Jan 20 15:04:10 dockerserver systemd[1]: Started ACPI event daemon. Jan 20 15:04:10 dockerserver systemd[1]: Reloading. Jan 20 15:04:10 dockerserver systemd[1]: apt-daily.timer: Adding 11h 16min 17.514645s random time. Jan 20 15:04:10 dockerserver systemd[1]: Started ACPI event daemon. Jan 20 15:04:10 dockerserver systemd[1]: Started Docker Application Container Engine. Jan 20 15:04:10 dockerserver systemd[1]: Reloading. Jan 20 15:04:10 dockerserver systemd[1]: apt-daily.timer: Adding 11h 42min 36.963745s random time. Jan 20 15:04:10 dockerserver systemd[1]: Started ACPI event daemon. So there's indeed a Start of Docker at 15:04:10 but where's the stop prior to that? If I manually restart the Docker service, syslog entries look like: Jan 23 09:54:38 dockerserver systemd[1]: Stop
[Bug 1565679] Re: No console/display output after boot
Hello Christopher, I installed the 4.7.0-040700rc6-generic mainline kernel and the problem still exists. # uname -a Linux ub1604test 4.7.0-040700rc6-generic #201607040332 SMP Mon Jul 4 07:34:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I booted with the new kernel. At the login prompt the screen goes dark. I unplugged the VGA cable and connected it at the back (primary) VGA adaptor of the server and I could see the login prompt. Logged in. Unplugged the VGA cable from the back and connected it to the front VGA connector again. Screen went dark. Let me know if I can do more to help. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
apport information ** Description changed: Ubuntu 16.04 BETA2 installed correctly on Dell PowerEdge 1850 server. Booting seems to work correctly too (can see it on the monitor), but when I expect the login prompt, no output is sent to the monitor (black). I documented this on the following video: https://www.youtube.com/watch?v=VAtnBv8uZf8 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Apr 4 12:23:48 2016 InstallationDate: Installed on 2016-04-04 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 28 11:14 seq crw-rw+ 1 root audio 116, 33 Apr 28 11:14 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4ea2a341-bca0-41da-aa0b-d99329ad9670 InstallationDate: Installed on 2016-04-04 (76 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Computer Corporation PowerEdge 1850 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=a9f64ee8-64f7-4b9f-96e3-5d0032701ada ro ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/25/2008 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0D8266 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd04/25/2008:svnDellComputerCorporation:pnPowerEdge1850:pvr:rvnDellComputerCorporation:rn0D8266:rvrA02:cvnDellComputerCorporation:ct23:cvr: dmi.product.name: PowerEdge 1850 dmi.sys.vendor: Dell Computer Corporation + --- + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2016-04-04 (93 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) + Package: linux (not installed) + Tags: xenial + Uname: Linux 4.7.0-040700rc6-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4696378/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1565679/+attachment/4696379/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
** Tags added: kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream-4.7-rc6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
Sorry Christopher, I misread and by the time I read it correctly, apport already sent the data. I just unplugged and replugged the monitor on the front VGA. Then waited a few seconds and plugged the monitor to the back VGA connector. dmesg shows the following information: [ 6613.913005] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 92 [ 6613.913151] Raw EDID: [ 6613.913183] 00 ff ff ff ff ff ff 00 10 ac 07 a0 4c 4b 34 30 [ 6613.913255] 04 0f 01 03 0e 29 1f ff ff ff ff ff ff ff ff ff [ 6613.91] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 6613.913405] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 6613.913484] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 6613.913562] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 6613.913633] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 6613.913711] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 6613.914978] [drm:radeon_vga_detect [radeon]] *ERROR* VGA-2: probed a monitor but no|invalid EDID -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: [Dell PowerEdge 1850] No front VGA console/display output after boot
Christopher, thanks for pointing me to the correct upstream project. Bug was reported and can be found here: https://bugs.freedesktop.org/show_bug.cgi?id=96838 ** Bug watch added: freedesktop.org Bugzilla #96838 https://bugs.freedesktop.org/show_bug.cgi?id=96838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: [Dell PowerEdge 1850] No front VGA console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] [NEW] No console/display output after boot
Public bug reported: Ubuntu 16.04 BETA2 installed correctly on Dell PowerEdge 1850 server. Booting seems to work correctly too (can see it on the monitor), but when I expect the login prompt, no output is sent to the monitor (black). I documented this on the following video: https://www.youtube.com/watch?v=VAtnBv8uZf8 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Apr 4 12:23:48 2016 InstallationDate: Installed on 2016-04-04 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
Actually my screen was connected on the front VGA connector, therefore: [3.197764] [drm] Connector 1: [3.197770] [drm] VGA-2 [3.197778] [drm] DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c [3.197785] [drm] Encoders: [3.197791] [drm] CRT2: INTERNAL_DAC2 I just tested the same with Ubuntu 14.04 trusty and the front VGA doesn't show anything. Back VGA works. Will test with 16.04, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+attachment/4622790/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565699] [NEW] Front VGA connector not showing output
Public bug reported: Installation and booting is shown correctly on monitor when connected to servers (a Dell PowerEdge 1850) front VGA connector. However after the boot process is completed and the login prompt should show up, the monitor doesn't display anything anymore (black) - as if there is no input. On dmesg I found the following errors: [ 62.364246] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 34 [ 62.364385] Raw EDID: [ 62.364419] 00 ff ff ff ff ff ff 00 10 ac 07 a0 4c 4b 34 30 [ 62.364494] 04 0f 01 03 0e 29 1f 78 ee 63 90 a3 57 4b 9b 25 [ 62.364575] 11 50 54 a5 4b 00 81 80 a9 40 71 4f 01 01 01 01 [ 62.364655] 01 01 01 01 01 01 48 3f 40 30 62 b0 32 40 40 c0 [ 62.364736] 13 00 6f 13 11 00 00 1e 00 00 00 ff 00 43 30 38 [ 62.364817] 38 31 35 31 49 30 34 4b 4c 20 00 00 00 fc 00 44 [ 62.364892] 45 4c 4c 20 32 30 30 31 46 50 09 ff ff ff ff ff [ 62.364966] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 62.366200] [drm:radeon_vga_detect [radeon]] *ERROR* VGA-2: probed a monitor but no|invalid EDID [ 62.427863] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 199 [ 62.427991] Raw EDID: [ 62.428038] 00 ff ff ff ff ff ff 00 10 ac 07 a0 4c 4b 34 30 [ 62.428147] 04 0f 01 03 0e 29 1f 78 ee 63 90 a3 57 4b 9b 25 [ 62.428245] 11 50 54 a5 4b 00 81 80 a9 40 71 4f 01 01 01 01 [ 62.428355] 01 01 01 01 01 01 48 3f 40 30 62 b0 32 40 40 c0 [ 62.428444] 13 00 6f 13 11 00 00 1e 00 00 00 ff 00 43 30 38 [ 62.428542] 38 31 35 31 49 30 34 4b 4c 20 00 00 00 fc 00 44 [ 62.428635] 45 4c 4c 20 32 30 30 31 46 ff ff ff ff ff ff ff [ 62.428732] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 62.429959] [drm:radeon_vga_detect [radeon]] *ERROR* VGA-2: probed a monitor but no|invalid EDID ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Mon Apr 4 13:03:27 2016 InstallationDate: Installed on 2016-04-04 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: Installation and booting is shown correctly on monitor when connected to - servers front VGA connector. However after the boot process is completed - and the login prompt should show up, the monitor doesn't display - anything anymore (black) - as if there is no input. + servers (a Dell PowerEdge 1850) front VGA connector. However after the + boot process is completed and the login prompt should show up, the + monitor doesn't display anything anymore (black) - as if there is no + input. On dmesg I found the following errors: [ 62.364246] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 34 [ 62.364385] Raw EDID: [ 62.364419]00 ff ff ff ff ff ff 00 10 ac 07 a0 4c 4b 34 30 [ 62.364494]04 0f 01 03 0e 29 1f 78 ee 63 90 a3 57 4b 9b 25 [ 62.364575]11 50 54 a5 4b 00 81 80 a9 40 71 4f 01 01 01 01 [ 62.364655]01 01 01 01 01 01 48 3f 40 30 62 b0 32 40 40 c0 [ 62.364736]13 00 6f 13 11 00 00 1e 00 00 00 ff 00 43 30 38 [ 62.364817]38 31 35 31 49 30 34 4b 4c 20 00 00 00 fc 00 44 [ 62.364892]45 4c 4c 20 32 30 30 31 46 50 09 ff ff ff ff ff [ 62.364966]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 62.366200] [drm:radeon_vga_detect [radeon]] *ERROR* VGA-2: probed a monitor but no|invalid EDID [ 62.427863] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 199 [ 62.427991] Raw EDID: [ 62.428038]00 ff ff ff ff ff ff 00 10 ac 07 a0 4c 4b 34 30 [ 62.428147]04 0f 01 03 0e 29 1f 78 ee 63 90 a3 57 4b 9b 25 [ 62.428245]11 50 54 a5 4b 00 81 80 a9 40 71 4f 01 01 01 01 [ 62.428355]01 01 01 01 01 01 48 3f 40 30 62 b0 32 40 40 c0 [ 62.428444]13 00 6f 13 11 00 00 1e 00 00 00 ff 00 43 30 38 [ 62.428542]38 31 35 31 49 30 34 4b 4c 20 00 00 00 fc 00 44 [ 62.428635]45 4c 4c 20 32 30 30 31 46 ff ff ff ff ff ff ff [ 62.428732]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 62.429959] [drm:radeon_vga_detect [radeon]] *ERROR* VGA-2: probed a monitor but no|invalid EDID ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture:
[Bug 1565699] Re: Front VGA connector not showing output
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+attachment/4622795/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565699 Title: Front VGA connector not showing output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
This bug is probably the same or at least related: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565699] Re: Front VGA connector not showing output
Same problem after running dist-upgrade. I see the login prompt for around 1 second before it disappears. dmesg error: [ 83.242723] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 142 [ 83.242872] Raw EDID: [ 83.242905] 00 ff ff ff ff ff ff 00 10 ac 07 a0 4c 40 00 00 [ 83.242986] 00 00 00 00 00 00 00 00 00 00 00 00 00 07 ff ff [ 83.243061] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.243141] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.243222] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.243297] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.243378] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.243453] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.244719] [drm:radeon_vga_detect [radeon]] *ERROR* VGA-2: probed a monitor but no|invalid EDID [ 91.246961] init: tty1 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565699 Title: Front VGA connector not showing output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565699] Re: Front VGA connector not showing output
** Attachment added: "dmesg-after-upgrade.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+attachment/4622829/+files/dmesg-after-upgrade.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565699 Title: Front VGA connector not showing output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565679] Re: No console/display output after boot
Complete new reinstall on the same server and I can confirm that the main VGA connector works. If I switch to the front VGA the screen is black. On trusty I see at least errors in dmesg (see mentioned bug in #4) but nothing on xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565679 Title: No console/display output after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573561] Re: /etc/default/varnish is ignored (fixed values in systemd service)
Thats a good hint, Knut. However on Ubuntu's side, the /etc/default/varnish file should disappear as it only creates confusion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573561 Title: /etc/default/varnish is ignored (fixed values in systemd service) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1573561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573561] [NEW] /etc/default/varnish is ignored (fixed values in systemd service)
Public bug reported: This is on a new installation of Ubuntu 16.04 xenial with Varnish 4.1.1-1. Any modification of /etc/default/varnish is being ignored by the daemon. Turns out that all the values are fixed in the systemd service of varnish (/lib/systemd/system/varnish.service): [Unit] Description=Varnish HTTP accelerator Documentation=https://www.varnish-cache.org/docs/4.1/ man:varnishd [Service] Type=simple LimitNOFILE=131072 LimitMEMLOCK=82000 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m ExecReload=/usr/share/varnish/reload-vcl ProtectSystem=full ProtectHome=true PrivateTmp=true PrivateDevices=true [Install] WantedBy=multi-user.target ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: varnish 4.1.1-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 14:07:10 2016 InstallationDate: Installed on 2016-04-18 (4 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: varnish UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.varnish: 2016-04-22T14:01:03.786366 ** Affects: varnish (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - /etc/default/varnish is ignored (fixed in systemd service) + /etc/default/varnish is ignored (fixed values in systemd service) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573561 Title: /etc/default/varnish is ignored (fixed values in systemd service) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1573561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434991] Re: python attributeError 'SSLTimeoutError' after upgrade
I have released a new version of check_esxi_hardware which adds compatibility between the old/unpatched pywbem 0.7.0 and patched pywbem 0.7.0. Other distros (e.g. openSUSE) was also affected by it. Please check it out on http://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php However the whole pywbem upstream and Linux distro patching must be looked at separately and improved. For years now the same version (0.7.0) was used. Upstream seemed dead, came back in September 2014 and seems dead again. Distros started applying own patches without having an official upstream release etc. That's sad :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434991 Title: python attributeError 'SSLTimeoutError' after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pywbem/+bug/1434991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494141] [NEW] HAProxy 1.5 init script does not terminate processes
Public bug reported: On a new installation of Ubuntu 14.04.3 LTS I installed HAProxy 1.5 from trusty-backports (1.5.4-1ubuntu2.1~ubuntu14.04.1). When I restarted HAProxy, I got random HTTP 503 although the backend servers were all working fine. By checking netstat, I saw that HAProxy was listening multiple times on the frontend ports. It seems that the init script coming with the installation does not work correctly. The processes are not terminated correctly when using stop (or restart, in this matter, either). Only with a kill I was able to correctly terminate the HAProxy processes. The following output should show more clarity: root@mylinux:~# netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 4653/haproxy tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 4221/haproxy tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN 956/nginx tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 855/sshd tcp0 0 0.0.0.0:80900.0.0.0:* LISTEN 4653/haproxy tcp0 0 0.0.0.0:80900.0.0.0:* LISTEN 4221/haproxy tcp0 0 0.0.0.0:80990.0.0.0:* LISTEN 4653/haproxy tcp0 0 0.0.0.0:80990.0.0.0:* LISTEN 4221/haproxy tcp6 0 0 :::22 :::*LISTEN 855/sshd root@mylinux:~# service haproxy stop * Stopping haproxy haproxy [ OK ] root@mylinux:~# service haproxy status haproxy not running. root@mylinux:~# netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 4653/haproxy tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 4221/haproxy tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN 956/nginx tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 855/sshd tcp0 0 0.0.0.0:80900.0.0.0:* LISTEN 4653/haproxy tcp0 0 0.0.0.0:80900.0.0.0:* LISTEN 4221/haproxy tcp0 0 0.0.0.0:80990.0.0.0:* LISTEN 4653/haproxy tcp0 0 0.0.0.0:80990.0.0.0:* LISTEN 4221/haproxy tcp6 0 0 :::22 :::*LISTEN 855/sshd root@mylinux:~# killall haproxy root@mylinux:~# netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN 956/nginx tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 855/sshd tcp6 0 0 :::22 :::*LISTEN 855/sshd root@mylinux:~# service haproxy start * Starting haproxy haproxy [ OK ] root@mylinux:~# netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 8205/haproxy tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN 956/nginx tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 855/sshd tcp0 0 0.0.0.0:80900.0.0.0:* LISTEN 8205/haproxy tcp0 0 0.0.0.0:80990.0.0.0:* LISTEN 8205/haproxy tcp6 0 0 :::22 :::*LISTEN 855/sshd root@mylinux:~# service haproxy restart * Restarting haproxy haproxy [ OK ] root@nzzad-lb01-test:~# netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 8286/haproxy tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN 8205/haproxy tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN 956/nginx tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 855/sshd tcp0 0 0.0.0.0:80900.0.0.0:*
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
By the way... this bug was also backported into the official trusty version of HAProxy (1.4).. Jeez! In the meantime its fixed again. haproxy (1.4.24-2ubuntu0.2) trusty; urgency=high * debian/haproxy.init: + Pass the pidfile to the --pidfile argument instead of the PID number. (LP: #1477198). -- Jorge Niedbalski Wed, 22 Jul 2015 11:12:26 -0500 haproxy (1.4.24-2ubuntu0.1) trusty; urgency=medium * debian/haproxy.init: + Backport of utopic start/stop routines, uses start-stop-daemon to reliable terminate all haproxy processes and return the proper exit code. (LP: #1462495). + Backport of utopic check_haproxy_config routine, that test the configuration before start or reload. (LP: #1468879) -- Jorge Niedbalski Thu, 25 Jun 2015 12:51:05 -0700 That's just as an additional note. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
Chase them with beer. Works faster ^^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
Salut Louis, Thanks for taking care of this bug. Have I understood correctly that the haproxy package in trusty-backports is already updated? Or do I have to wait until the package is released to all mirrors? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
The "new bug" for trusty concerning if nproc > 1 is probably this one: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Still present in 14.04 trusty on Desktop (not Server), see http://www.claudiokuenzler.com/blog/600/ubuntu-desktop-ntp-ntpdate- error-resolving-name-or-service-not-known-mdns -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/94940 Title: mdns listed in nsswitch.conf causes excessive time for dns lookups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/94940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024475] Re: libnss-ldap causes boot hang on Ubuntu 12.04 Precise
I ran into this issue today and I'm very surprised this issue is that old. This bug makes Ubuntu as an LDAP client unusable. #17 did help for faster booting of the machine, but that's it. Any command is still so slow, the machine is useless. #2 tried it like this: - Adapted init script /etc/init.d/libnss-ldap like mentioned - created /etc/nsswitch.conf.local which does NOT contain ldap - created /etc/nsswitch.conf.ldap which does contain ldap This again works for a very fast boot, but once libnss-ldap is started (and therefore the ldap version of nsswitch.conf becomes active), the system is bloody slow again. #1 works to regain a "normal" system with local logins but ldap logins still time out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024475 Title: libnss-ldap causes boot hang on Ubuntu 12.04 Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325971] [NEW] Wrong LVM pv size by using installer
Public bug reported: Hello, According to https://wiki.ubuntu.com/Bugs/FindRightPackage#When_installing_Ubuntu_.28or_Derivatives.29 bugs in the installer (of Ubuntu Server) need to be reported against the package debian-installer. I got a weird partitioning setup after having done a manual partitioning. I created one primary partition for the root/slash partition (with 10GB) and two extended partitions tagged as Linux LVM. Partition table: Disk /dev/sda: 1799.8 GB, 1799798437888 bytes 255 heads, 63 sectors/track, 218813 cylinders, total 3515231324 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 262144 bytes / 786432 bytes Disk identifier: 0x00021c16 Device Boot Start End Blocks Id System /dev/sda1 *153619531775 9765120 83 Linux /dev/sda219533310 3515229695 17478481935 Extended Partition 2 does not start on physical sector boundary. /dev/sda519533312 11718758348827136 8e Linux LVM /dev/sda6 117189120 3515229695 1699020288 8e Linux LVM As you can see, /dev/sda5 has a size of around 50GB. /dev/sda6 fills up the rest of the disk (which is around 1.7TB) I then created the Volume Groups vgsystem and lxc in the installer. For vgsystem I chose the PV /dev/sda5 and to my big surprise the installer took a size of 1.6TB instead of the 50GB (which is the size of the partition). I deleted and recreated the VG/PV but this bug could be reproduced all the time. Here the pvdisplay output: --- Physical volume --- PV Name /dev/sda6 VG Name lxc PV Size 1.58 TiB / not usable 3.50 MiB Allocatable yes PE Size 4.00 MiB Total PE 414799 Free PE 401487 Allocated PE 13312 PV UUID zxwiIK-7n6s-RAEx-F4OT-5FIf-ybzd-ptkbMR --- Physical volume --- PV Name /dev/sda5 VG Name system PV Size 1.63 TiB / not usable 3.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 426720 Free PE 418138 Allocated PE 8582 PV UUID iI5MtU-09e5-cfC7-aHVk-NIgv-Ei5n-pu4M5O ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: debian-installer (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Tue Jun 3 14:47:36 2014 InstallationDate: Installed on 2013-12-22 (163 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: HP ProLiant DL380p Gen8 MemoryUsage: total used free sharedbuffers cached Mem: 329073805925376 26982004 1116 2911403904188 -/+ buffers/cache:1730048 31177332 Swap: 15622140 0 15622140 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c91d09d0-ebbb-4c3f-92bd-722f2801de39 ro SourcePackage: debian-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: HP dmi.bios.version: P70 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP70:bd12/20/2013:svnHP:pnProLiantDL380pGen8:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380p Gen8 dmi.sys.vendor: HP ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325971 Title: Wrong LVM pv size by using installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1325971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319066] [NEW] kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50()
Public bug reported: Seems to be bug #1116731 May 13 13:11:03 global1-dpr kernel: [94752.690848] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50() May 13 13:11:03 global1-dpr kernel: [94752.690852] Modules linked in: des_generic md4 nls_utf8 cifs fscache veth ext2 vesafb coretemp kvm_intel bridge kvm stp llc ghash_clmulni_intel aesni_intel cryptd aes_x86_64 ioatdma sb_edac edac_core hpwdt gpio_ich hpilo psmouse joydev serio_raw microcode mac_hid lpc_ich acpi_power_meter lp parport hid_generic usbhid hid hpsa igb tg3 dca May 13 13:11:03 global1-dpr kernel: [94752.690899] Call Trace: May 13 13:11:03 global1-dpr kernel: [94752.690915] [] warn_slowpath_null+0x1a/0x20 May 13 13:11:03 global1-dpr kernel: [94752.690936] [] cifs_unlink+0x1b0/0x3f0 [cifs] May 13 13:11:03 global1-dpr kernel: [94752.690954] [] vfs_unlink+0x3c/0x60 May 13 13:11:03 global1-dpr kernel: [94752.690969] [] sys_unlink+0x16/0x20 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-48-generic 3.5.0-48.72~precise1 ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31 Uname: Linux 3.5.0-48-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 May 12 10:50 seq crw-rw---T 1 root audio 116, 33 May 12 10:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Date: Tue May 13 16:14:09 2014 HibernationDevice: RESUME=UUID=39d33e08-772a-4478-8cd6-3d24ddd3f7cf IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380p Gen8 MarkForUpload: True PciMultimedia: ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-48-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-48-generic N/A linux-backports-modules-3.5.0-48-generic N/A linux-firmware1.79.11 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-quantal UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/14/2012 dmi.bios.vendor: HP dmi.bios.version: P70 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP70:bd12/14/2012:svnHP:pnProLiantDL380pGen8:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380p Gen8 dmi.sys.vendor: HP ** Affects: linux-lts-quantal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise qa-kernel-lts-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319066 Title: kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1319066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116731] Re: [HP Pavilion p6-2352eg Desktop PC] WARNING: at /build/buildd/linux-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50()
Let's reactivate this bug... i created a dup bug 1319066 with fresh information and logs. OS is 12.04 with quantal kernel but the kernel warnings are the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116731 Title: [HP Pavilion p6-2352eg Desktop PC] WARNING: at /build/buildd/linux-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319066] Re: kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50()
*** This bug is a duplicate of bug 1116731 *** https://bugs.launchpad.net/bugs/1116731 ** This bug has been marked a duplicate of bug 1116731 [HP Pavilion p6-2352eg Desktop PC] WARNING: at /build/buildd/linux-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50() ** Description changed: Seems to be bug #1116731 - May 13 13:11:03 global1-dpr kernel: [94752.690848] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50() + May 13 13:11:03 hostname kernel: [94752.690848] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/fs/inode.c:281 drop_nlink+0x46/0x50() May 13 13:11:03 global1-dpr kernel: [94752.690852] Modules linked in: des_generic md4 nls_utf8 cifs fscache veth ext2 vesafb coretemp kvm_intel bridge kvm stp llc ghash_clmulni_intel aesni_intel cryptd aes_x86_64 ioatdma sb_edac edac_core hpwdt gpio_ich hpilo psmouse joydev serio_raw microcode mac_hid lpc_ich acpi_power_meter lp parport hid_generic usbhid hid hpsa igb tg3 dca May 13 13:11:03 global1-dpr kernel: [94752.690899] Call Trace: May 13 13:11:03 global1-dpr kernel: [94752.690915] [] warn_slowpath_null+0x1a/0x20 May 13 13:11:03 global1-dpr kernel: [94752.690936] [] cifs_unlink+0x1b0/0x3f0 [cifs] May 13 13:11:03 global1-dpr kernel: [94752.690954] [] vfs_unlink+0x3c/0x60 May 13 13:11:03 global1-dpr kernel: [94752.690969] [] sys_unlink+0x16/0x20 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-48-generic 3.5.0-48.72~precise1 ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31 Uname: Linux 3.5.0-48-generic x86_64 AlsaDevices: - total 0 - crw-rw---T 1 root audio 116, 1 May 12 10:50 seq - crw-rw---T 1 root audio 116, 33 May 12 10:50 timer + total 0 + crw-rw---T 1 root audio 116, 1 May 12 10:50 seq + crw-rw---T 1 root audio 116, 33 May 12 10:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Date: Tue May 13 16:14:09 2014 HibernationDevice: RESUME=UUID=39d33e08-772a-4478-8cd6-3d24ddd3f7cf IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380p Gen8 MarkForUpload: True PciMultimedia: - + ProcEnviron: - LANGUAGE=en_US: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-48-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.5.0-48-generic N/A - linux-backports-modules-3.5.0-48-generic N/A - linux-firmware1.79.11 + linux-restricted-modules-3.5.0-48-generic N/A + linux-backports-modules-3.5.0-48-generic N/A + linux-firmware1.79.11 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-quantal UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 12/14/2012 dmi.bios.vendor: HP dmi.bios.version: P70 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP70:bd12/14/2012:svnHP:pnProLiantDL380pGen8:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380p Gen8 dmi.sys.vendor: HP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319066 Title: kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1319066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319066] Re: [HP ProLiant DL380p Gen8 Server] kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50()
I just updated to the latest kernel (3.5.0-49-generic) and will keep an eye on this server for the next days. So far the warning entries have not re-appeared but the system's uptime is only a few minutes. Will keep you posted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319066 Title: [HP ProLiant DL380p Gen8 Server] kernel warnings cifs mounts inode.c:281 drop_nlink+0x46/0x50() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1319066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318551] Re: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.
Have two servers within 9 days which crashed because of this bug. Both HP DL 380 Gen8 with Ubuntu 14.04 LTS and Kernel 3.13.0-24 generic. Copied the panic from ILO's text console: [1863292.758326] [] hrtimer_interrupt+0xef/0x230 [1863292.786466] [] local_apic_timer_interrupt+0x37/0x60 [1863292.818554] [] smp_apic_timer_interrupt+0x3f/0x60 [1863292.850351] [] apic_timer_interrupt+0x6d/0x80 [1863292.879596] [] ? panic+0x196/0x1d7 [1863292.910248] [] hpwdt_pretimeout+0xdd/0xdd [hpwdt] [1863292.941162] [] ? sched_clock+0x9/0x10 [1863292.968075] [] nmi_handle.isra.3+0x88/0x180 [1863292.996345] [] do_nmi+0x1bd/0x340 [1863293.020585] [] end_repeat_nmi+0x1e/0x2e [1863293.046908] [] ? intel_idle+0xd8/0x140 [1863293.073359] [] ? intel_idle+0xd8/0x140 [1863293.099900] [] ? intel_idle+0xd8/0x140 [1863293.125429] <> [] cpuidle_enter_state+0x40/0xc0 [1863293.157562] [] cpuidle_idle_call+0xb9/0x1f0 [1863293.185072] [] arch_cpu_idle+0xe/0x30 [1863293.212075] [] cpu_startup_entry+0xc5/0x290 [1863293.239492] [] rest_init+0x77/0x80 [1863293.263435] [] start_kernel+0x438/0x443 [1863293.289440] [] ? repair_env_string+0x5c/0x5c [1863293.317249] [] ? early_idt_handlers+0x120/0x120 [1863293.348279] [] x86_64_start_reservations+0x2a/0x2c [1863293.378575] [] x86_64_start_kernel+0x143/0x152 [1863293.407399] ---[ end trace de17fe13514d8515 ]--- ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318551 Title: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] [NEW] haproxy package misses creation of default stats socket path
Public bug reported: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners Starting HAProxy manually will show the following error: # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] After manual creation of the directory, the start works: # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg This can be reproduced with a simple Docker container the following Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Description changed: When installing the haproxy package from the current Ubuntu 18.04 Bionic - repos, the package does not install the directory `/run/haproxy`. This + repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file - `/etc/haproxy/haproxy.cfg`: + /etc/haproxy/haproxy.cfg: - ``` - stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners - ``` + + stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners + Starting HAProxy manually will show the following error: - ``` - # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg + + # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] - ``` + After manual creation of the directory, the start works: - ``` + # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg - ``` - This can be reproduced with a simple Docker container the following - Dockerfile: - ``` + This can be reproduced with a simple Docker container the following Dockerfile: + + -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ - && apt-get install -y -qq haproxy + && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg"] - ``` + -- Checking the haproxy package for the run directory shows nothing: - ``` - # dpkg -L haproxy | grep run ; date + + # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 - ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
** Summary changed: - haproxy package misses creation of default socket path + haproxy package misses creation of default stats socket path -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
** Description changed: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: - - stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners - + stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd + listeners Starting HAProxy manually will show the following error: - # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] - After manual creation of the directory, the start works: - # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg - - This can be reproduced with a simple Docker container the following Dockerfile: + This can be reproduced with a simple Docker container the following + Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy - CMD ["/usr/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg"] + CMD ["/usr/sbin/haproxy","-f","/etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: - # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
** Description changed: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners Starting HAProxy manually will show the following error: # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] After manual creation of the directory, the start works: # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg This can be reproduced with a simple Docker container the following Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy","-f","/etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 + + *** + + Update: After analysis of the haproxy package (see + https://www.claudiokuenzler.com/blog/917/haproxy-ubuntu-18.04-docker- + image-not-starting-cannot-bind-unix-socket), it turns out that the + /run/haproxy directory is defined in debian/haproxy.tmpfile. However + tmpfile's are only considered in systems with SystemD. As Docker + containers run without Systemd, this directory is never created. + + Suggestion: Do not rely on Systemd to create /run/haproxy. Maybe use + debian/haproxy.dirs? However the permissions are not set in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
Thanks, Christian, for your response. I agree, this might likely have a bigger impact than expected (I only figured this out after package analysis), because a lot of packages now depend on systemd for the package installation - yet systemd does not run in Docker. That's (most likely) the reason why the official HAProxy docker image builds on Alpine Linux which uses Open RC as init system. I could of course switch to Alpine but during early development phase of that container I wanted to use Ubuntu 18.04 for additional troubleshooting purposes. It will probably come down whether or not the Ubuntu packages officially support being installed/run in a Docker container or not. I can already imagine the fuss and heavily debated conversations about this topic :-/ . Let me know if I can be of help somehow. ** Summary changed: - haproxy package misses creation of default stats socket path + haproxy package misses creation of default stats socket path in Docker container -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path in Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path in Docker container
Can't edit my comment (#2) so I just wanted to correct the sentence "That's (most likely) the reason why the official HAProxy docker image builds on Alpine Linux which uses Open RC as init system.". The official HAProxy Docker image runs on Debian but also supports Alpine Linux. The big difference there: They don't install HAProxy from a deb package but rather build HAProxy from source (during image build). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path in Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863210] [NEW] apache2 event mpm: keeps hanging in gracefully finishing when reloading (logrotate)
Public bug reported: This is Apache2 bug 53555 (https://bz.apache.org/bugzilla/show_bug.cgi?id=53555). It was fixed in 2.4.25 but on Ubuntu Xenial, Apache2 runs with 2.4.18 and the fix was not backported yet. This particular Apache2 setup runs with event mpm and is used as reverse proxy in front of a Tomcat (but that's irrelevant I guess). A daily log rotation happens on the Apache2 logs, causing an Apache2 reload (graceful restart). A check of apache-status each day confirms Apache bug 53555. February 4th: Current Time: Tuesday, 04-Feb-2020 17:19:28 CET Restart Time: Monday, 03-Feb-2020 09:20:48 CET Parent Server Config. Generation: 2 Parent Server MPM Generation: 1 Server uptime: 1 day 7 hours 58 minutes 39 seconds Server load: 0.00 0.00 0.00 Total accesses: 59027 - Total Traffic: 1.7 GB CPU Usage: u175.56 s424.83 cu0 cs0 - .522% CPU load .513 requests/sec - 15.7 kB/second - 30.6 kB/request 1 requests currently being processed, 49 idle workers PIDConnectionsThreads Async connections total accepting busy idle writing keep-alive closing 31339 1 no000 0 0 31340 1 no000 0 0 21534 0 yes 025 0 0 0 21535 0 yes 124 0 0 0 Sum 2 149 0 0 0 GG__ __W_ .. A couple of days later, February 7th: Current Time: Friday, 07-Feb-2020 14:06:52 CET Restart Time: Monday, 03-Feb-2020 09:20:48 CET Parent Server Config. Generation: 5 Parent Server MPM Generation: 4 Server uptime: 4 days 4 hours 46 minutes 3 seconds Server load: 0.00 0.00 0.00 Total accesses: 152913 - Total Traffic: 20.9 GB CPU Usage: u520.6 s1424.31 cu0 cs0 - .536% CPU load .422 requests/sec - 60.5 kB/second - 143.5 kB/request 1 requests currently being processed, 24 idle workers PIDConnectionsThreads Async connections total accepting busy idle writing keep-alive closing 31339 1 no000 0 0 31340 1 no000 0 0 11925 0 yes 124 0 0 0 21535 1 no000 0 0 4156 1 no000 0 0 29454 1 no000 0 0 Sum 5 124 0 0 0 GG__W___ ___G GG On February 8th, the remaining open slots were fully used and HTTP didn't respond anymore. Error logs filling up with the following message: "[mpm_event:error] [pid 5587:tid 139748587677568] AH00485: scoreboard is full, not at MaxRequestWorkers" Solution a) Update package to a newer upstream version for xenial-updates Solution b) Backport the fix from Apache bug 53555 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apache2 2.4.18-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 Apache2ConfdDirListing: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Feb 14 07:43:55 2020 InstallationDate: Installed on 2017-01-26 (1113 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apache2 UpgradeStatus: No upgrade log present (probably fresh install) error.log: [Fri Feb 14 06:25:06.928096 2020] [ssl:warn] [pid 27506:tid 140172129879936] AH01909: mcp-somcwc01-p.nzzmg.local:443:0 server certificate does NOT include an ID which matches the server name [Fri Feb 14 06:25:06.930524 2020] [mpm_event:notice] [pid 27506:tid 140172129879936] AH00489: Apache/2.4.18 (Ubuntu) mod_jk/1.2.41 OpenSSL/1.0.2g configured -- resuming normal operations [Fri Feb 14 06:25:06.930532 2020] [core:notice] [pid 27506:tid 140172129879936] AH00094: Command line: '/usr/sbin/apache2' modified.conffile..etc.apache2.sites-available.000-default.conf: [modified] modified.conffile..etc.apache2.sites-available.default-ssl.conf: [modified] mtime.conffile..etc.apache2.sites-available.000-default.conf: 2017-02-14T07:38:24.570441 mtime.conffile..etc.apache2.sites-available.default-ssl.conf: 2018-04-09T15:47:05.141386 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863210 Title: apache2 event mpm: keeps hanging in gracefully finishing when reloading (logrotate) To manage notifications about this bug go to: htt
[Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments
Hi Christian
According to https://www.debian.org/vote/2019/vote_002#outcome the
decision was to use "Systemd but we support exploring alternatives".
>From the proposal:
"Packages should include service units or init scripts to start daemons
and services. Packages may use any systemd facility at the package
maintainer's discretion, provided that this is consistent with other
Policy requirements and the normal expectation that packages shouldn't
depend on experimental or unsupported (in Debian) features of other
packages. Packages may include support for alternate init systems
besides systemd and may include alternatives for any systemd-specific
interfaces they use. Maintainers use their normal procedures for
deciding which patches to include."
>From my understanding this means that supporting an alternative init
system is optional ("Packages may include support for alternate init
systems besides systemd"). So basically this is up to the package
maintainer whether or not the package should support an alternative init
system.
Given the (still rising) popularity of Docker/Kubernetes containers, it
would indeed by very nice that the affected packages (such as haproxy)
do adjust for a non-systemd environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855140
Title:
How to handle tmpfiles.d in non-systemd environments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb
Still present in 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314160 Title: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1314160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660316] Re: apparmor denial of CUPS
Same happens in 18.04 (Linux Mint 19.3). Needed to manually add the net_admin caps as mentioned by Jamie. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1660316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940525] Re: check_http regression, 2.2 ignores -k Host header
Hi Robie Thx for checking. The problem with the host header set by -H parameter is that it automatically applies the port, if a port is used with the -p parameter. $ /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -H www.example.com -p 8083 -v GET / HTTP/1.1 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close Host: www.example.com:8083 (this can cause problems depending on the infrastructure, e.g. using load balancers forwarding the requested host header to the backend) To get rid of the port in the Host header, the workaround using -k and defining the "Host" header again has worked in the past. But it seems that by using a combination of -H and -k "Host" the previous behaviour can be established again: $ /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 8083 -k "Host: www.example.com" -H www.example.com -v |more GET / HTTP/1.1 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close Host: www.example.com So it's strange, that the "Host" header is ignored when using -k - but in combination with -H it works. I can live with that workaround but if you want to report it upstream let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940525] Re: check_http regression, 2.2 ignores -k Host header
Or you can close this bug issue. I don't think that it's actually something Ubuntu/Canonical can do in this case. I might check with upstream but the workaround (combination of the two) works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586528] Re: Avahi-daemon withdraws address record
I've just seen this issue the first time on a Ubuntu 20.04 (updated several months ago from 16.04) AWS EC2 machine. Looking closer into this, the machine lost its IP address multiple times in the last hours. The following avahi-daemon log messages made me find this bug report: ck@focal:~$ grep avahi-daemon /var/log/syslog | grep -i withdrawing Jan 18 20:17:42 inf-mon04-p avahi-daemon[941]: Withdrawing address record for 10.10.1.41 on eth0. Jan 18 21:44:52 inf-mon04-p avahi-daemon[941]: Withdrawing address record for 10.10.1.41 on eth0. It's very interesting, that both of these events happened EXACTLY one hour after the system boot: ck@focal:~$ last | head ck pts/0xx.xx.xx.xxx Tue Jan 18 22:11 still logged in root ttyS0 Tue Jan 18 21:50 still logged in reboot system boot 5.4.0-91-generic Tue Jan 18 20:44 still running reboot system boot 5.4.0-91-generic Tue Jan 18 19:17 - 20:39 (01:22) Running "dhclient" on the EC2 console, as suggested in comment #46, re- assigns the IP address. Relevant versions installed: ck@focal:~$ dpkg -l|egrep "(dhcp|network-manager)" ii isc-dhcp-client 4.4.1-2.1ubuntu5.20.04.2 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.4.1-2.1ubuntu5.20.04.2 amd64common manpages relevant to all of the isc-dhcp packages ii network-manager 1.22.10-1ubuntu2.2 amd64network management framework (daemon and userspace tools) ii network-manager-gnome1.8.24-1ubuntu3 amd64network management framework (GNOME frontend) ii network-manager-pptp 1.2.8-2 amd64network management framework (PPTP plugin core) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950751] [NEW] docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart)
Public bug reported: Dear maintainers, I noticed a changed behaviour when starting the Docker service after the docker.io package was upgraded from 19.3.6 to 20.10.7. When the Docker host was reset/cleaned, which involves a 'rm -rf /var/lib/docker/*', the sub-directories are not automatically created anymore after a start of the service: root@dockerhost:~# rm -rf /var/lib/docker/* root@dockerhost:~# service docker start root@dockerhost:~# ll /var/lib/docker/ total 0 Without these directories, Docker containers cannot be created. Example with a 'docker pull': root@dockerhost:~# docker pull rancher/rke-tools:v0.1.78 v0.1.78: Pulling from rancher/rke-tools 540db60ca938: Pulling fs layer 0ae30075c5da: Pulling fs layer 9da81141e74e: Pulling fs layer b2e41dd2ded0: Pulling fs layer 7f40e809fb2d: Pulling fs layer 758848c48411: Pulling fs layer 4aa8101d7589: Pulling fs layer 68bd44136930: Pulling fs layer ae3790b81ced: Pulling fs layer f9c62a2baf95: Pulling fs layer 759049e20249: Pulling fs layer 6713b6a87a77: Pulling fs layer e1631138f00b: Pulling fs layer 063b41c39c12: Pulling fs layer c7844f3999c4: Pulling fs layer d8473758fa62: Pulling fs layer f83b3d05af4e: Pulling fs layer open /var/lib/docker/tmp/GetImageBlob573083372: no such file or directory However a restart does re-create the missing folders: root@dockerhost:~# service docker restart root@dockerhost:~# ll /var/lib/docker/ total 44 drwx--x--x 4 root root 4096 Nov 11 13:49 buildkit drwx--x--- 2 root root 4096 Nov 11 13:49 containers drwx-- 3 root root 4096 Nov 11 13:49 image drwxr-x--- 3 root root 4096 Nov 11 13:49 network drwx--x--- 3 root root 4096 Nov 11 13:49 overlay2 drwx-- 4 root root 4096 Nov 11 13:49 plugins drwx-- 2 root root 4096 Nov 11 13:49 runtimes drwx-- 2 root root 4096 Nov 11 13:49 swarm drwx-- 2 root root 4096 Nov 11 13:49 tmp drwx-- 2 root root 4096 Nov 11 13:49 trust drwx-x 2 root root 4096 Nov 11 13:49 volumes This happens with docker.io 20.10.x on both Ubuntu 18.04 Bionic and 20.04 Focal. Compared to the behaviour of docker.io 19.3.x: root@focal:~# docker info | head Client: Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 19.03.8 root@focal:~# service docker stop root@focal:~# rm -rf /var/lib/docker/* root@focal:~# service docker start root@focal:~# ll /var/lib/docker/ drwx--x--x 14 root root 4096 Nov 12 07:33 ./ drwxr-xr-x 29 root root 4096 Oct 29 14:06 ../ drwx-- 2 root root 4096 Nov 12 07:33 builder/ drwx--x--x 4 root root 4096 Nov 12 07:33 buildkit/ drwx-- 2 root root 4096 Nov 12 07:33 containers/ drwx-- 3 root root 4096 Nov 12 07:33 image/ drwxr-x--- 3 root root 4096 Nov 12 07:33 network/ drwx-- 3 root root 4096 Nov 12 07:33 overlay2/ drwx-- 4 root root 4096 Nov 12 07:33 plugins/ drwx-- 2 root root 4096 Nov 12 07:33 runtimes/ drwx-- 2 root root 4096 Nov 12 07:33 swarm/ drwx-- 2 root root 4096 Nov 12 07:33 tmp/ drwx-- 2 root root 4096 Nov 12 07:33 trust/ drwx-- 2 root root 4096 Nov 12 07:33 volumes/ Conclusion: The start script in docker.io 20.10.x should create the sub- directories in /var/lib/docker if they are missing (same as service restart). cheers, ck ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950751 Title: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950751] Re: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart)
> I see you run "service docker stop" before deleting the contents of "/var/lib/docker" but I do not see that in your first example, service docker stop is part of the general clean up strategies, for Rancher related Docker hosts anyway (see https://www.claudiokuenzler.com/blog/674/reset-clean-up-a-rancher- docker-host). So yes, this command definitely happened. The command would also throw a ton of errors, if Docker service would still be running due to busy/opened files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950751 Title: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940525] [NEW] check_http regression, 2.2 ignores -k Host header
Public bug reported: With Ubuntu 20.04 focal, the monitoring-plugins package is at version 2.2 This seems to have introduced a regression in the check_http plugin: When using -k parameter to set a "Host" header, this is ignored instead of used. In 2.1.2 on Ubuntu 16.04, the following behavior is seen: # /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 4007 -k "Host: www.example.com" -v |more GET / HTTP/1.0 User-Agent: check_http/v2.1.2 (monitoring-plugins 2.1.2) Connection: close Host: www.example.com Ubuntu 20.04 with monitoring-plugins 2.2: # /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 4007 -k "Host: www.example.com" -v |more GET / HTTP/1.0 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close ** Affects: monitoring-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
