from:"Claudio Kuenzler"

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2022-01-18 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

2021-05-04 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1897561

Title:
  libperl.so.5.30.0 causes nginx to segfault

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]

  1) launch a focal container
  $ lxc launch images:ubuntu/focal focal-1897561
  2) enter the container
  $ lxc shell focal-1897561
  3) install libnginx-mod-http-perl
  # apt-get install -y nginx-core libnginx-mod-http-perl
  4) check nginx journal
  # journalctl -fu nginx &
  5) reload nginx 2-3 times
  # systemctl reload nginx

  Eventually you will see this from the journal:

  Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web 
server and a reverse proxy server.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 
'core-dump'.

  [Workaround]

  If libnginx-mod-http-perl is not needed, purging it and restarting
  nginx sidesteps the problem.

  [Original bug description]

  Ubuntu 20.04 LTS

  Looks that Perl 5.30 has bug that causes nginx to die, usually occurs
  after "service nginx reload"

  This looks like nginx, but it really is perl issue:
  https://github.com/Perl/perl5/issues/17154

  Fix done in 5.32 (Perl5 commit bf0) and people are asking backport
  to 5.30 to get fix also to nginx.

  Error:
  Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 
ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in

[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS

2020-09-15 Thread Claudio Kuenzler

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:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset

[Touch-packages] [Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

2020-09-15 Thread Claudio Kuenzler

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 in cups package in Ubuntu:
  Confirmed

Bug description:
  When I print to my smb printer, I get a dbus notification of the
  following entries in my syslog:

  Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 
audit(1398770835.923:150): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 
audit(1398770835.923:151): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 
audit(1398770835.923:152): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7

  I get new entries every time I print. I'm running Ubuntu 14.04 with
  cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw.

  I saw this replicated on http://www.dedoimedo.com/computers/ubuntu-
  trusty-tahr-laptop-ultrabook.html .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1314160/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-05-12 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in keepalived source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   #

[Touch-packages] [Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments

2020-02-13 Thread Claudio Kuenzler

   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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

2016-10-11 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/940030

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20120223'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog to /var/log/syslog-20120223
  running postrotate script
  removing old log /var/log/syslog-20111219.gz

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

2016-10-10 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/940030

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

2016-06-15 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1565679

Title:
  No console/display output after boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

2016-04-04 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1565679

Title:
  No console/display output after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

2016-04-04 Thread Claudio Kuenzler

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:
  No console/display output after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565699] Re: Front VGA connector not showing output

2016-04-04 Thread Claudio Kuenzler

** 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.
https://bugs.launchpad.net/bugs/1565699

Title:
  Front VGA connector not showing output

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565699] Re: Front VGA connector not showing output

2016-04-04 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1565699

Title:
  Front VGA connector not showing output

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565699] [NEW] Front VGA connector not showing output

2016-04-04 Thread Claudio Kuenzler

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:

[Touch-packages] [Bug 1565699] Re: Front VGA connector not showing output

2016-04-04 Thread Claudio Kuenzler

** 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.
https://bugs.launchpad.net/bugs/1565699

Title:
  Front VGA connector not showing output

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565699/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

2016-04-04 Thread Claudio Kuenzler

** 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.
https://bugs.launchpad.net/bugs/1565679

Title:
  No console/display output after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

2016-04-04 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1565679

Title:
  No console/display output after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565679] [NEW] No console/display output after boot

2016-04-04 Thread Claudio Kuenzler

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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1565679

Title:
  No console/display output after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups

2015-11-24 Thread Claudio Kuenzler

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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/94940

Title:
  mdns listed in nsswitch.conf causes excessive time  for dns lookups

Status in avahi package in Ubuntu:
  Confirmed
Status in nss-mdns package in Ubuntu:
  Confirmed
Status in nss-mdns package in Debian:
  Fix Released

Bug description:
  Binary package hint: avahi-daemon

  I encountered this problem on a machine that is integrated into our
  work network. I performed a dist-upgrade to Feisty on my desktop and
  all went well. I've noticed recently that any dns based work seemed to
  take a significantly longer time then normal.

  My system is getting dns information on our company internal systems
  from two dns servers. Previously, if I tried to establish an ssh
  connection with another system I could generally expect the connection
  in under 3 secs.

  After the dist-upgrade the time went from under 3 seconds to
  approximately 25 seconds. After searching around the system I found an
  entry in /etc/nsswitch.conf that cause me a little concern. The line
  in question is:

 hosts:  files mdns4_minimal [NOTFOUND=return] dns mdns4

  I looked around a bit and it seems that the references to mdns are
  really talking about communication with the Avahi mDNS/DNS-SD daemon.
  Since this looks to be a part of a zeroconf configuration I wasn't
  expecting too much in my current environment, as we really only have
  three Mac's.

  What concerned me is the idea that if we hit files with no answer
  there is a delay while we hit the other options until we hit dns,
  which is where the information I seek existed.

  For an experiment I tried two separate tests. The first changed the
  line to looks like:

  hosts:  files dns mdns4_minimal [NOTFOUND=return] mdns

  The change should have improved the time, but I was still looking at
  approximately 23 seconds to return a command prompt on the destination
  machine.

  Finally, I change the entry to simply:

  hosts:  files dns

  After this change I was again receiving the destination command prompt
  in under 3 seconds. I don't know if simply changing the file will
  correct the problem long-term or not. Seems to help me, but might be
  the way to go for most Ubuntu users.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Mar 22 18:10:54 2007
  DistroRelease: Ubuntu 7.04
  Uname: Linux samdesk 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 
i686 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/94940/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS

[Touch-packages] [Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Touch-packages] [Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

[Touch-packages] [Bug 1565699] Re: Front VGA connector not showing output

[Touch-packages] [Bug 1565699] Re: Front VGA connector not showing output

[Touch-packages] [Bug 1565699] [NEW] Front VGA connector not showing output

[Touch-packages] [Bug 1565699] Re: Front VGA connector not showing output

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

[Touch-packages] [Bug 1565679] Re: No console/display output after boot

[Touch-packages] [Bug 1565679] [NEW] No console/display output after boot

[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups

19 matches

Site Navigation

Mail list logo

Footer information