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
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
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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1660316
Title:
Still present in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1314160
Title:
Apparmor profile violated: cupsd does mknod on
/var/cache/samba/gencache.tdb
Status
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
/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 Cla
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.
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
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,
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
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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1565679
Title:
** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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
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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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
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:
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
Touch seeded packages, which is subscribed to
19 matches
Mail list logo
