I looked into the openafs-client init script. This is on my work laptop. The init script is modified. Our AFS servers are on the intranet and therefore openafs with my cells will only work if the laptop is on the intranet. Since trying to connect to afs servers on the intranet when not on the intranet can take a very long time before it times out, the openafs-client init script has been modified to first check to see if on the intranet and if the cells are reachable and only start the client if so. There is a binary which I can't look into called quickresolv that does the checking to see if the laptop is connected to the intranet. It probably does a dig, or nslookup, or ping to a known intranet id(I think it is w3.ibm.com). If it fails, it doesn't start openafs otherwise it does. The reason it is important that dnsmasq starts first is that w3.ibm.com will not resolve otherwise. That is why in the log where dnsmasq doesn't start first you see this:
Thu Jun 17 08:03:16 2010: 1st attempt to contact IBM Intranet Thu Jun 17 08:03:16 2010: Checking for IBM Intranet Activity - FAILED. Thu Jun 17 08:03:16 2010: Thu Jun 17 08:03:16 2010: 2nd attempt to contact IBM Intranet Thu Jun 17 08:03:16 2010: Checking for IBM Intranet Activity - FAILED. Thu Jun 17 08:03:16 2010: Thu Jun 17 08:03:16 2010: 3rd attempt to contact IBM Intranet Thu Jun 17 08:03:16 2010: Checking for IBM Intranet Activity - FAILED. Thu Jun 17 08:03:16 2010: quitting Thu Jun 17 08:03:16 2010: AFS will not start When dnsmasq is started first you see this: Thu Jun 17 09:37:19 2010: 1st attempt to contact IBM Intranet Thu Jun 17 09:37:19 2010: Checking for IBM Intranet Activity - SUCCESS Thu Jun 17 09:37:19 2010: Thu Jun 17 09:37:19 2010: Checking 9.56.253.117 is reachable... Thu Jun 17 09:37:19 2010: 9.56.253.117 is reachable, starting afs Thu Jun 17 09:37:19 2010: Starting AFS services: openafs afsd. Thu Jun 17 09:37:19 2010: afsd: All AFS daemons started. So, it doesn't look like an openafs problem since the init script has been modified. It would be nice though if I could figure out how to make dnsmasq start first. If I could figure it out, would I have to change it every time openafs-client or dnsmasq is updated? To answer your question, in the case when openafs-client doesn't start during boot, it does start manually because by then dnsmasq is started. I don't know about the reportbug oddness. I build my own kernels and modules if that makes reportbug look different. On Thu, 2010-06-17 at 10:34 -0700, Russ Allbery wrote: > > > I see openafs-client and dnsmasq are both s21. Does anything break the > > tie or is that why they are started in different orders some time? > > Shouldn't make any difference which order they're started in. > > When OpenAFS doesn't start at boot, does running > /etc/init.d/openafs-client start as root after the system starts work? > > > Versions of packages openafs-client recommends: > > ii 4.81.dfsg.1-1 List open files > > ii 1.4.11+dfsg-6+2.6.30.091211-10.00.Cu AFS distributed filesystem > > kernel > > ii 1.4.11+dfsg-6+2.6.32.100131-10.00.Cu AFS distributed filesystem > > kernel > > ii 1.4.11+dfsg-6+2.6.32.100210-10.00.Cu AFS distributed filesystem > > kernel > > ii 1.4.11+dfsg-6+2.6.32.100315-10.00.Cu AFS distributed filesystem > > kernel > > ii 1.4.12.1+dfsg-1+2.6.32.100608-10.00. AFS distributed filesystem > > kernel > > ii 1.4.12.1+dfsg-1 AFS distributed filesystem > > kernel > > Something is very odd with the output of reportbug here. > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
