FS#31453 - [dhcpcd,networkmanager] timeout when trying to reach my online NAS HDD

Attached to Project: Arch Linux
Opened by Frederic Bezies (fredbezies) - Friday, 07 September 2012, 11:29 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 20 October 2012, 12:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ronald van Haren (pressh)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Hello.

For a few days - less than a week), when I try to use Nautilus to reach my NAS HDD (which is in my ISP router), I cannot get it listed. I can use ftp to access it.

Using zeroconf browser, I got a timeout error while trying to reach my NAS HDD; either using my wireless connection (with my laptop) or my wired connection (using my desktop computer) :

Error: org.freedesktop.Avahi.TimeoutError: Timeout reached

Both computer are running up-to-date archlinux with testing repository enabled, and Gnome 3.4.x on it.

And there are full systemd powered. Avahi services are enabled and running.

Additional info:

avahi : 0.6.31-3
systemd : 189-4
systemd-arch-units : 20120704-5
systemd-sysvcompat : 189-4

[fred@fredo-arch-laptop ~]$ systemctl status avahi-daemon
avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled)
Active: active (running) since Fri, 07 Sep 2012 13:02:10 +0200; 26min ago
Main PID: 259 (avahi-daemon)
Status: "Server startup complete. Host name is fredo-arch-laptop.local. Local service cookie is 3217430624."
CGroup: name=systemd:/system/avahi-daemon.service
├ 259 avahi-daemon: running [fredo-arch-laptop.local]
└ 272 avahi-daemon: chroot helper

[fred@fredo-arch-laptop ~]$ systemctl status avahi-dnsconfd
avahi-dnsconfd.service - Avahi DNS Configuration Daemon
Loaded: loaded (/usr/lib/systemd/system/avahi-dnsconfd.service; enabled)
Active: active (running) since Fri, 07 Sep 2012 13:02:07 +0200; 27min ago
Main PID: 262 (avahi-dnsconfd)
CGroup: name=systemd:/system/avahi-dnsconfd.service
└ 262 /usr/sbin/avahi-dnsconfd -s

Steps to reproduce:
   Capture du 2012-09-07 13:26:1... (38.1 KiB)
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Saturday, 20 October 2012, 12:03 GMT
Reason for closing:  Fixed
Comment by Frederic Bezies (fredbezies) - Friday, 07 September 2012, 15:19 GMT
Had an idea, and verified it. Downgrading networkmanager fixes the bug. Could it be related - in some way - to dhcpcd upgrade which is a networkmanager depend ?
Comment by Frederic Bezies (fredbezies) - Friday, 07 September 2012, 15:36 GMT
Well, I rebuilt networkmanager / networkmanager applet with dhcpcd 5.6.2 and all is working great.

So, rebuilding networkmanager against dhcpcd 5.6.2 could be a great idea, I think.
Comment by André Prata (nDray) - Friday, 07 September 2012, 16:23 GMT
Humm, am I wrong that there is no "building against dhcpcd" involved? NetworkManager can live just fine without dhcpcd...
Comment by Frederic Bezies (fredbezies) - Friday, 07 September 2012, 16:29 GMT
Erh...

[fred@fredo-arch ~]$ pacman -Qi networkmanager
Name : networkmanager
Version : 0.9.6.0-1
URL : http://www.gnome.org/projects/NetworkManager/
Licenses : GPL
Groups : None
Provides : None
Depends On : dbus-glib iproute2 libnl nss polkit udev wpa_supplicant
ppp dhcpcd libsoup

Well, looks like dhcpcd is a depend of NetworkManager...
Comment by André Prata (nDray) - Friday, 07 September 2012, 16:30 GMT
But it works with just as dhclient as well...
Comment by Gaetan Bisson (vesath) - Sunday, 09 September 2012, 01:43 GMT
Avahi hasn't been touched since April, so as you have already pointed out this is most certainly a networkmanager/dhcpcd issue; I'm reassigning this bug.
Comment by Jan Alexander Steffens (heftig) - Sunday, 09 September 2012, 02:35 GMT
There's no reason a simple rebuild of NM should change anything.
dhcpcd is not a library, nor is any information extracted from the daemon at build time.

Did you try reverting to the repo packages?
Comment by Frederic Bezies (fredbezies) - Sunday, 09 September 2012, 05:51 GMT
To sum up things.

1) Tried downgrading NM and its applet : still timeout, no direct access to my nas hdd.
2) I noticed that dhcpcd was upgraded around the same time I see the bug.
3) Build NM and its applet using new dhcpcd : work again.

Well, as there were no other NM depends modified since and as bug is "dead", I thought it was the answer.
Comment by Frederic Bezies (fredbezies) - Saturday, 20 October 2012, 11:03 GMT
Well, looks like network manager updates fixes this bug. Requesting closure of this report.
Comment by Greg (dolby) - Saturday, 20 October 2012, 11:17 GMT
Keep in mind next time, the request closure button is up there^ :)

Loading...