OpenAFS client does not wait for DHCP lease
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
openafs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: openafs-client
Hi,
I'm using the openafs-client package from Ubuntu Gutsy (openafs-client 1.4.4.dfsg1-7). Sometimes the DHCP server is quite slow to respond, but OpenAFS already tries to use the network and fails to contact the volume location server, making AFS unusable from this client. See the log below.
I think the OpenAFS client should only be started after the network connection is set up correctly, but it seems to be started too early.
Regards,
Ansgar
Log for a cold-start with the DHCP server only answering after a few seconds:
Jul 16 09:25:31 loonquawl dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 16 09:25:36 loonquawl dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 16 09:25:37 loonquawl kernel: [ 24.268000] openafs: module license 'http://
Jul 16 09:25:37 loonquawl kernel: [ 24.632000] Starting AFS cache scan...found 313 non-empty cache files (20%%).
Jul 16 09:25:41 loonquawl dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jul 16 09:25:46 loonquawl kernel: [ 33.228000] afs: Lost contact with volume location server 129.206.26.16 in cell mathi.uni-
Jul 16 09:25:46 loonquawl kernel: [ 33.228000] afs: Lost contact with volume location server 129.206.26.16 in cell mathi.uni-
Jul 16 09:25:49 loonquawl dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Jul 16 09:25:55 loonquawl kernel: [ 42.300000] afs: Lost contact with volume location server 129.206.26.22 in cell mathi.uni-
Jul 16 09:25:55 loonquawl kernel: [ 42.300000] afs: Lost contact with volume location server 129.206.26.22 in cell mathi.uni-
Jul 16 09:26:04 loonquawl dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Jul 16 09:26:04 loonquawl dhclient: DHCPOFFER from 129.206.26.17
Jul 16 09:26:04 loonquawl dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 16 09:26:04 loonquawl dhclient: DHCPACK from 129.206.26.17
Changed in ifupdown (Ubuntu): | |
status: | New → Invalid |
Ansgar Burchardt <ansgar@43-1.org> writes:
> I'm using the openafs-client package from Ubuntu Gutsy (openafs-client
> 1.4.4.dfsg1-7). Sometimes the DHCP server is quite slow to respond, but
> OpenAFS already tries to use the network and fails to contact the volume
> location server, making AFS unusable from this client. See the log
> below.
>
> I think the OpenAFS client should only be started after the network
> connection is set up correctly, but it seems to be started too early.
Be sure that you're using -dynroot -afsdb, and you shouldn't have this
problem. OpenAFS only attempts to locate the VLDBs on boot if -dynroot is
not given; otherwise, it waits until you attempt to access files.
-- www.eyrie. org/~eagle/>
Russ Allbery (<email address hidden>) <http://