|
Size: 3824
Comment: transfer from AfsFedoraClientConfiguration, clean up.
|
Size: 2920
Comment: Brought page up to date, remove CategoryOutdated
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from MemberManual/TransferringFiles/OpenAFS/FedoraClient | |
| Line 3: | Line 4: |
| This is the chapter of the MemberManual that describes how to install the OpenAFS client on RedHat Fedora. | This is the chapter of the MemberManual that describes how to install the OpenAFS client on Fedora. |
| Line 5: | Line 6: |
| [[TableOfContents]] | NB: When this page was updated to reflect Fedora 23, some potentially helpful but unverified information from the out-of-date page was left in the page. This information will be prefaced with "OLD:" |
| Line 7: | Line 8: |
| = Packages to Install and Build = | <<TableOfContents>> |
| Line 9: | Line 10: |
| Download the [http://www.openafs.org/release/latest.html openafs source RPM] for your version of Fedora. This will have a filename like openafs-1.4.4-fc6.2.src.rpm. Build this package on your machine with the `rpmbuild` command, such as this one (please alter as necessary): {{{ sudo rpmbuild --rebuild --target=i686 openafs-1.4.4-fc6.2.src.rpm }}} '''Note:''' You will need to have the kernel-headers package installed for this to work. |
= Introduction = |
| Line 15: | Line 12: |
| If the build completed successfully, you should see some lines that say "Wrote: " towards the end of the output. To install the new created package, use `rpm`: {{{ rpm -ivh packagename" }}} '''Note:''' should you install a new kernel, you'll have to repeat this part of the process! |
There are different sets of RPMS available for OpenAFS. Currently, the easiest to install and maintain across system updates is probably a [[https://copr.fedoraproject.org/coprs/jsbillings/|copr]] repo. You must enable two repositories: |
| Line 21: | Line 14: |
| Now, install the openafs-1.4.4-fc6.2.i386.rpm, openafs-client-1.4.4-fc6.2.i386.rpm, and openafs-krb5-1.4.4-fc6.2.i386.rpm, or the newest stable packages for your platform. | {{{dnf copr enable jsbillings/openafs}}} {{{dnf copr enable jsbillings/openafs-kmod}}} = Install OpenAFS RPMS with Dnf = Once you've enabled both repositories on your machine, install the appropriate openafs kernel module. Check your currently-running kernel with {{{uname -a}}}, then use the template command below. {{{dnf install kmod-openafs-[PACKAGE.VERSION]-[KERNEL.VERSION]}}} NB: Dnf may default to the wrong kernel module. Check closely that the version ''exactly'' matches your running kernel. If not, manually type the entire package and kernel version numbers. Then, install the rest of the openafs rpm files through dnf: {{{dnf install openafs openafs-kmdl openafs-authlibs openafs-docs openafs-client openafs-krb5 openafs-kmod-docs}}} |
| Line 25: | Line 32: |
| * Change the home cell in {{{/usr/vice/etc/ThisCell}}} to hcoop.net. * Start the openafs client with {{{sudo /etc/init.d/openafs-client start}}} |
* Change the home cell in {{{/etc/openafs/ThisCell}}} to hcoop.net. * Start the openafs client ''once'' with {{{systemctl start openafs-client.service}}} * Enable the openafs client to run on boot with {{{systemctl enable openafs-client.service}}} |
| Line 28: | Line 36: |
| * Make sure that afsd is running. | * Make sure that the openafs client is running with {{{systemctl status openafs-client.service}}} |
| Line 32: | Line 40: |
| = Rebuilding the OpenAFS Module = | That's it! OLD: Your machine should automatically pick up new versions of the openafs kernel module when you do updates. |
| Line 34: | Line 42: |
| You will have to rebuild the source RPM every time your kernel is updated. If you followed the steps above, the source rpm should have been installed in /usr/src/redhat/SRPMS/. Use the rpmbuild command above to build this. This resulting RPM file will be put in an appropriate directory under /usr/src/redhat/RPMS if the build is successful. It will contain the name of the running kernel. Install this RPM, and when you run /etc/init.d/openafs-client start the daemon should start properly. | = OLD: Troubleshooting = |
| Line 36: | Line 44: |
| If you're lazy you may want to script the process of creating a new openafs module each time you install a new kernel. Here is a script that works no my Fedora 7 system. It rebuilds the source RPM, installs it, and starts the openafs daemon. It hasn't been well tested and I wrote it very quickly, so feel free to make it more robust if you want to: | If you get an error like "aklog: unable to obtain tokens for cell hcoop.net (status: 11862790)" it may mean that your router is blocking SRV requests. If you're running `djbdns` locally (used by lots of operating systems for embedded devices, such as OpenWrt), make sure that the line {{{filterwin2k}}} is commented out in /etc/dnsmasq.conf, or whatever the configuration file is on your machine. |
| Line 38: | Line 46: |
| {{{ #!/bin/bash |
If you get messages saying things like "libafs can't be found" when you try to start the client, you probably installed a version of openafs-kmdl that doesn't match your running kernel. Use yum to remove the openafs RPM packages and try again. |
| Line 41: | Line 48: |
| # Re-builds the openafs modules for the currently running kernel. # Should work on Fedora systems. # This has not been broadly tested, written Tue Jun 5 11:30:35 EDT 2007 # by Justin S. Leitgeb [leitgebj AT hcoop -- NOSPAM -- net]. OPENAFS_SRPM="/usr/src/redhat/SRPMS/openafs-1.4.4-fc6.2.src.rpm" if [ -a $OPENAFS_SRPM ] ; then echo SRPM $OPENAFS_SRPM exists, starting rebuild. ; rpmbuild --rebuild --target=i686 $OPENAFS_SRPM # Figure out what the filename should be for the new RPM based on # running kernel version, then install it. kernel_name_for_afs=`uname -r | sed 's/-/_/'` # Not a pretty command but it worked for me... we'll see if it does in the future. new_afs_rpm=`find /usr/src/redhat/RPMS/ -type f | grep openafs | grep $kernel_name_for_afs | grep kernel | head -1` rpm -ivh $new_afs_rpm echo Re-starting openafs client... /etc/init.d/openafs-client start fi }}} = Troubleshooting = If you get an error like "aklog: unable to obtain tokens for cell hcoop.net (status: 11862790)" it may mean that your router is blocking SRV requests. If you're running `djbdns` locally (used by lots of operating systems for embedded devices, such as OpenWrt), make sure that the line {{{filterwin2k}}} is commented out in /etc/dnsmasq.conf, or whatever the config file is on your machine. Read TroubleshootingKerberos for more. |
Read MemberManual/ShellAccess/TroubleshootingKerberos for more. ---- CategoryMemberManual |
This is the chapter of the MemberManual that describes how to install the OpenAFS client on Fedora.
NB: When this page was updated to reflect Fedora 23, some potentially helpful but unverified information from the out-of-date page was left in the page. This information will be prefaced with "OLD:"
Introduction
There are different sets of RPMS available for OpenAFS. Currently, the easiest to install and maintain across system updates is probably a copr repo. You must enable two repositories:
dnf copr enable jsbillings/openafs
dnf copr enable jsbillings/openafs-kmod
Install OpenAFS RPMS with Dnf
Once you've enabled both repositories on your machine, install the appropriate openafs kernel module. Check your currently-running kernel with uname -a, then use the template command below.
dnf install kmod-openafs-[PACKAGE.VERSION]-[KERNEL.VERSION]
NB: Dnf may default to the wrong kernel module. Check closely that the version exactly matches your running kernel. If not, manually type the entire package and kernel version numbers.
Then, install the rest of the openafs rpm files through dnf:
dnf install openafs openafs-kmdl openafs-authlibs openafs-docs openafs-client openafs-krb5 openafs-kmod-docs
Configuration
Change the home cell in /etc/openafs/ThisCell to hcoop.net.
Start the openafs client once with systemctl start openafs-client.service
Enable the openafs client to run on boot with systemctl enable openafs-client.service
- Run kinit and type your password
Make sure that the openafs client is running with systemctl status openafs-client.service
- Run "klist" just to make sure that you have a valid token.
- Run aklog - if this works you should be able to see /afs/hcoop.net.
That's it! OLD: Your machine should automatically pick up new versions of the openafs kernel module when you do updates.
OLD: Troubleshooting
If you get an error like "aklog: unable to obtain tokens for cell hcoop.net (status: 11862790)" it may mean that your router is blocking SRV requests. If you're running djbdns locally (used by lots of operating systems for embedded devices, such as OpenWrt), make sure that the line filterwin2k is commented out in /etc/dnsmasq.conf, or whatever the configuration file is on your machine.
If you get messages saying things like "libafs can't be found" when you try to start the client, you probably installed a version of openafs-kmdl that doesn't match your running kernel. Use yum to remove the openafs RPM packages and try again.
Read MemberManual/ShellAccess/TroubleshootingKerberos for more.