problem with starting openafs-client at boottime

Bug #318605 reported by Jakob Runge
2
Affects Status Importance Assigned to Milestone
openafs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: openafs-client

I've installed openafs-client on Ubuntu 8.10 the way that it should startup along with the rest of the system.
However, nothing is mounted to /afs/ until i stop-start /etc/init.d/openafs-client manually as root.
After some tests i discovered that setting the starttime of openafs-client
from /etc/rc2.d/S25openafs-client to /etc/rc2.d/S99openafs-client fixes this problem.
So in this case using afs works just like a charm, whilest starting it earlier doesn't realy work.
I guess openafs-client might have problems, if it is started earlier than NetworkManager,
system-tools-backends, or something.

Revision history for this message
Russ Allbery (rra-debian) wrote : Re: [Bug 318605] [NEW] problem with starting openafs-client at boottime

Jakob Runge <email address hidden> writes:

> I've installed openafs-client on Ubuntu 8.10 the way that it should
> startup along with the rest of the system. However, nothing is mounted
> to /afs/ until i stop-start /etc/init.d/openafs-client manually as root.
> After some tests i discovered that setting the starttime of
> openafs-client from /etc/rc2.d/S25openafs-client to
> /etc/rc2.d/S99openafs-client fixes this problem. So in this case using
> afs works just like a charm, whilest starting it earlier doesn't realy
> work. I guess openafs-client might have problems, if it is started
> earlier than NetworkManager, system-tools-backends, or something.

Do you have openafs-client configured to use dynroot? If not, does
reconfiguring it to use dynroot (with dpkg-reconfigure openafs-client) and
then moving the start script back to its former position fix the problem?
OpenAFS should tolerate starting before the network as long as it's not
configured to contact the VLDB servers immediately on startup.

--
Russ Allbery (<email address hidden>) <http://www.eyrie.org/~eagle/>

Revision history for this message
Jakob Runge (sicarius) wrote : Re: [Bug 318605] [NEW] problem with starting openafs-client at boottime

*sorry it took me so long to answer to that afs problem.
For quite some time my internet-connection on the ubuntu-computer was
broken, so i could not test it. Indeed the Problem is solved trough the
usage of dynroot. Thank you for you patience and help :).
*

Revision history for this message
Russ Allbery (rra-debian) wrote :

Jakob Runge <email address hidden> writes:

> *sorry it took me so long to answer to that afs problem.
> For quite some time my internet-connection on the ubuntu-computer was
> broken, so i could not test it. Indeed the Problem is solved trough the
> usage of dynroot. Thank you for you patience and help :).

Excellent, thanks for letting me know. I'm going to make dynroot the
default for new installs in the next release.

--
Russ Allbery (<email address hidden>) <http://www.eyrie.org/~eagle/>

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.9 KiB)

This bug was fixed in the package openafs - 1.4.8.dfsg1-2

---------------
openafs (1.4.8.dfsg1-2) unstable; urgency=low

  * Make openafs-modules-source architecture-specific (arch: any instead
    of arch: all). The new method for generating the kernel source tree
    only generates correct build machinery for the architecture on which
    it was built, making the package architecture-specific. The generated
    tree is so much smaller that this still only uses about 1MB of archive
    space more than the old method and makes each openafs-modules-source
    package much smaller. This is a workaround until we can fix
    libafs_tree to include enough build machinery to handle all Linux
    architectures from one source tree. (Closes: #516023)
  * Explicitly remove *-stamp files in the clean target of the module
    build until the module build is upgraded to debhelper 7.

openafs (1.4.8.dfsg1-1) unstable; urgency=low

  * New upstream release. (Closes: #511535)
    - Support 2.6.28 kernels. (LP: #303112)
    - Check at compile time that the kernel has keyring support rather
      than building non-functional modules. (Closes: #500850)
    - Include vos clone man page. (LP: #324449)
  * Apply upstream CVS deltas:
    - STABLE14-libuafs-updates-20081229: prerequisite for other deltas.
    - STABLE14-linux-truncate-race-20090109: avoid race condition during
      truncation.
    - STABLE14-linux-i-size-20090112: further fix for truncation race.
    - STABLE14-linux-truncate-cleanup-20090113: further truncation fix.
    - STABLE14-osi-probe-check-result-cope-with-enoent-20090115: fix for
      syscall probing.
    - STABLE14-linux-2629-20090115: support for 2.6.29 kernels.
      (Closes: #513680)
    - STABLE14-rx-idledead-only-ignore-keepalives-20081222: rx bug fix to
      not ignore other ping packets.
    - STABLE14-rx-rdwr-writeproc-race-20081228: fix rx race condition that
      could result in reuse of freed memory.
    - STABLE14-rx-do-not-race-current-packet-20090105: fix rx race
      condition.
  * Use make libafs_tree to generate the tree for the kernel module
    compile rather than copying the entire source tree.
  * Compress the source in openafs-modules-source with bzip2 instead of
    gzip to reduce the package size.
  * Make dynroot the default for new installations. It works much better
    with systems that don't bring up their network until late in the boot
    process, such as wireless laptops. (LP: #249240, #318605)
  * Mention libpam-afs-session instead of libpam-openafs-session in the
    description of libpam-openafs-kaserver, and mention libpam-krb5 by
    name. Thanks, Philipp Kaluza. (Closes: #501308)
  * Suggest module-assistant auto-install in README.modules and be clearer
    that building one's own kernel is not required. Thanks, Anders
    Kaseorg and Lutz Goehring for suggestions. (LP: #295897)
  * Allow time-daemon to satisfy the openafs-fileserver recommends in
    addition to ntp, allowing for openntpd. (Closes: #508258)
  * General improvements to debconf configuration handling.
    - Do not abort the config script if we have no default realm and
      dnsdomainname fails. (LP: #274886, #318...

Read more...

Changed in openafs:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.