RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1222646 - avahi connection timeouts too easily ....
Summary: avahi connection timeouts too easily ....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: avahi
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Sekletar
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks: 1289485 1295396 1313485
TreeView+ depends on / blocked
 
Reported: 2015-05-18 17:40 UTC by Matěj Cepl
Modified: 2016-11-04 08:27 UTC (History)
3 users (show)

Fixed In Version: avahi-0.6.31-17.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 08:27:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2549 0 normal SHIPPED_LIVE avahi bug fix update 2016-11-03 14:20:22 UTC

Description Matěj Cepl 2015-05-18 17:40:26 UTC 
Description of problem:
Even though I am on the local network with not completely slow
connection (see below) ssh mediated via avahi quite often timeouts.
I have to repeat multiple times before the connection happens. (see
below, the repeated runs of ssh just happened by the immediate repeating
[Up]+[Enter]).

matej@mitmanek: ~$ ping narcis.local
PING narcis.local (192.168.0.5) 56(84) bytes of data.
64 bytes from 192.168.0.5: icmp_seq=1 ttl=64 time=1.32 ms
64 bytes from 192.168.0.5: icmp_seq=2 ttl=64 time=3.70 ms
^C
--- narcis.local ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.329/2.515/3.701/1.186 ms
matej@mitmanek: ~$ ssh narcis
ssh: Could not resolve hostname narcis.local: Name or service not known
matej@mitmanek: ~$ ssh narcis
ssh: Could not resolve hostname narcis.local: Name or service not known
matej@mitmanek: ~$ ssh narcis
ssh: Could not resolve hostname narcis.local: Name or service not known
matej@mitmanek: ~$ ssh narcis
Last login: Mon May 18 18:08:55 2015 from 192.168.0.3
marketa@narcis:~$ logout

Connection to narcis.local closed.
marketa@narcis:~$

Version-Release number of selected component (if applicable):
(on client)
matej@mitmanek: ~$ rpm -qa avahi\*
avahi-debuginfo-0.6.31-14.el7.x86_64
avahi-gobject-0.6.31-14.el7.x86_64
avahi-devel-0.6.31-14.el7.x86_64
avahi-autoipd-0.6.31-14.el7.x86_64
avahi-tools-0.6.31-14.el7.x86_64
avahi-glib-devel-0.6.31-14.el7.x86_64
avahi-glib-0.6.31-14.el7.x86_64
avahi-0.6.31-14.el7.x86_64
avahi-libs-0.6.31-14.el7.x86_64
avahi-ui-gtk3-0.6.31-14.el7.x86_64

(on server)
marketa@narcis:~$ rpm -qa avahi\*
avahi-libs-0.6.25-15.el6.i686
avahi-ui-0.6.25-15.el6.i686
avahi-glib-0.6.25-15.el6.i686
avahi-tools-0.6.25-15.el6.i686
avahi-ui-tools-0.6.25-15.el6.i686
avahi-autoipd-0.6.25-15.el6.i686
avahi-0.6.25-15.el6.i686
marketa@narcis:~$ 


How reproducible:
Happens quite often (I guess there is some caching, so sometimes ssh
uses cached IP)

Steps to Reproduce:
1. run ssh to the avahi connected server (narcis is here defined as
marketa so it goes over avahi).
2.
3.

Actual results:
Times out.

Expected results:
It should work reliably on LAN with not much problems with connection.
Comment 4 Michal Sekletar 2016-05-25 21:06:18 UTC 
Are you still able to reproduce this? If yes, can you please gather avahi-daemon log?
Comment 5 Michal Sekletar 2016-05-30 14:36:19 UTC 
I am not sure whether this is the same bug, but I've built a test package with possible fix for,

https://github.com/lathiat/avahi/pull/11

Note that before updating to fixed version I was able to get avahi into the bad state by running,

service avahi-daemon restart; service network restart

Here is a scratch build, please test.

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11104865
Comment 6 Matěj Cepl 2016-06-13 13:17:56 UTC 
(In reply to Michal Sekletar from comment #5)
> Note that before updating to fixed version I was able to get avahi into the
> bad state by running,
> 
> service avahi-daemon restart; service network restart
> 
> Here is a scratch build, please test.
> 
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11104865

I am not 100% certain that it has been fixed, because I really didn't have foolproof reproduction steps (also, I don't have updated packages on the other side of the connection, which is RHEL-6), but certainly the situation is not worse, and it perhaps looks better. I haven't got the stalled connection for some time.
Comment 15 errata-xmlrpc 2016-11-04 08:27:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2549.html
Note You need to log in before you can comment on or make changes to this bug.