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

2016-02-22 Thread Jiri Hoogeveen
Hi,

I  had this issue in Ubuntu 15.10 fresh install. I know my PTR is oke.
host: cc04
localdomein: bla.example

ping cc04 works, gives me the IP and the reverse lookup
ping cc04.bla.example does not work.

after removing mdns4_minimal [NOTFOUND=return] from /etc/nsswitch
everything is working again.

-- 
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 789174] Re: rsyslog fails to create tcp socket.

2014-09-02 Thread Jiri Hoogeveen
also fixed in 14.04, YEaaah :)

-- 
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/789174

Title:
  rsyslog fails to create tcp socket.

Status in “rsyslog” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rsyslog

  My package:
  ii  rsyslog   4.6.4-2ubuntu4

  The thing is that when starting rsyslog first drop privileges and then
  tries to create socket and more. This seems to be a bug, because the
  same configuration works fine on 10.04. Configuration is attached.

  rsyslog output:
  May 27 18:37:55 ubuntu01 kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  May 27 18:37:55 ubuntu01 rsyslogd: [origin software=rsyslogd 
swVersion=4.6.4 x-pid=5547 x-info=http://www.rsyslog.com;] (re)start
  May 27 18:37:55 ubuntu01 rsyslogd: rsyslogd's groupid changed to 103
  May 27 18:37:55 ubuntu01 rsyslogd: rsyslogd's userid changed to 101
  May 27 18:37:55 ubuntu01 rsyslogd-2039: Could no open output pipe 
'/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
  May 27 18:37:55 ubuntu01 rsyslogd-2077: Could not create tcp listener, 
ignoring port 514. [try http://www.rsyslog.com/e/2077 ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+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