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
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
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.
*** 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
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
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:
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
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] [8108ed3f] hrtimer_interrupt+0xef/0x230
[1863292.786466] [81043087]
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
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
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
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:
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:
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
Chase them with beer. Works faster ^^
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init script does not terminate processes
To manage notifications about
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
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
Server Team,
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
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
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:
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
Server Team, which is subscribed to the bug report.
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.
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,
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).
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
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
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.
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
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
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
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:
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.
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
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.
Thanks for everyone involved to fix the bug. I can confirm stop/restart
works as expected now with 1.5.14-1ubuntu0.15.10.1~ubuntu14.04.1
installed from backports on trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
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
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
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
** 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.
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:
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
** 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:
** 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:
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
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):
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:
** 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
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
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
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
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
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]
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
*** 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
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
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
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.
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
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
:
--
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 t
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"]
** 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
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&quo
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
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
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
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
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
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
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
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
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
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
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
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
> 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
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
77 matches
Mail list logo
