|
Size: 1784
Comment: initial content, from /afs/hcoop.net/user/b/bp/bpt/public/afs-debian-install
|
Size: 3681
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from MemberManual/TransferringFiles/OpenAFS/DebianClient | |
| Line 7: | Line 8: |
= OpenAFS Client Installation = {{{ aptitude install openafs-client }}} Answer the configuration questions as follows: * AFS cell this workstation belongs to: `hcoop.net` * The default value for "Size of AFS cache in kB" is okay. You can increase the cache size if you want. * Dynamically generate the contents of /afs? Yes * DB server host names for your home cell: `deleuze.hcoop.net` * Run Openafs client now and at boot? Yes |
|
| Line 12: | Line 28: |
| sudo aptitude install module-assistant sudo module-assistant prepare sudo module-assistant install openafs |
aptitude install module-assistant module-assistant prepare module-assistant auto-install openafs |
| Line 19: | Line 35: |
| = OpenAFS Client Installation = |
Restart OpenAFS: |
| Line 22: | Line 37: |
| sudo aptitude install openafs-client | /etc/init.d/openafs-client restart |
| Line 24: | Line 39: |
Answer the configuration questions as follows: * AFS cell this workstation belongs to: `hcoop.net` * The default value for "Size of AFS cache in kB" is okay. You can increase the cache size if you want. * Dynamically generate the contents of /afs? Yes * DB server host names for your home cell: `deleuze.hcoop.net` * Run Openafs client now and at boot? Yes |
|
| Line 39: | Line 45: |
| sudo aptitude install openafs-krb5 krb5-user | aptitude install openafs-krb5 krb5-user |
| Line 42: | Line 48: |
| The default Kerberos version 5 realm can be HCOOP.NET, and deleuze.hcoop.net will be both the Kerberos server for your realm and the administrative server for your realm. |
* Default Kerberos version 5 realm: `HCOOP.NET` * Kerberos servers for your realm: `deleuze.hcoop.net` * Administrative server for your Kerberos realm: `deleuze.hcoop.net` If you are using Ubuntu Hardy, you might also need to add the following to your {{{/etc/krb5.conf}}} file, in the {{{[domain_realm]}}} section. It gets rid of a pesky warning. {{{ hcoop.net = HCOOP.NET .hcoop.net = HCOOP.NET }}} = Using AFS = Typically, to gain access to your HCoop AFS share, do the following on your local system: {{{ kinit user@HCOOP.NET aklog -c hcoop.net }}} Be sure that the `openafs` module is loaded or there will be errors. The tickets gained will last up to 10 hours but can be renewed with `krenew` for up to 8 days. Here's a common use: {{{ krenew -K 30 -t }}} See the `krenew` man page to learn what these options are doing. = Troubleshooting = == ReiserFS == First, if you are using ReiserFS, the AFS daemon will simply refuse to work because it cannot use that filesystem for its cache. If the daemon doesn't run, you'll get a puzzling error message that might make you think you have a firewall problem. To get the daemon to work, edit the `/etc/openafs/afs.conf` to make it use the memory cache. It is said to be less stable than the hard disk cache. The {{{README.Debian}}} file also suggests creating a loopback ext2 filesystem for the cache. == Konqueror == Konqueror simply hangs when trying to browse {{{/afs}}} with the default CellServerDB. This happens because it is trying to access AFS volumes it doesn't have access to or that are not accessible, and hangs indefinitely. There is a lot of cells pre-configured in the Debian package, and probably some of them are not valid or not accessible. Once the content of {{{/etc/openafs/CellServerDB}}} has been erased of everything except for the hcoop.net entry, browsing {{{/afs}}} with Konqueror should work. |
This is the chapter of the MemberManual that describes how to install and configure OpenAFS Client on Debian based systems. These instructions were adapted from HCoop user bpt's instructions.
OpenAFS Client Installation
aptitude install openafs-client
Answer the configuration questions as follows:
AFS cell this workstation belongs to: hcoop.net
- The default value for "Size of AFS cache in kB" is okay. You can increase the cache size if you want.
- Dynamically generate the contents of /afs? Yes
DB server host names for your home cell: deleuze.hcoop.net
- Run Openafs client now and at boot? Yes
Kernel Module Installation
OpenAFS requires a kernel module, and Debian does not provide third-party kernel modules as binary packages. Module-assistant can download, compile, and install kernel modules for you. Install that, then install the OpenAFS module:
aptitude install module-assistant module-assistant prepare module-assistant auto-install openafs
OpenAFS's cache is located at /var/cache/openafs, and it must be on an ext2 or ext3 filesystem. If /var/cache is not on an ext2 or ext3 filesystem, you'll need to mount an ext2 or ext3 filesystem at /var/cache/openafs. OpenAFS cache does not work well, if at all, on ReiserFS systems.
Restart OpenAFS:
/etc/init.d/openafs-client restart
Now you should be able to see files in /afs/hcoop.net, but you won't have any AFS tokens. So let's install some Kerberos packages.
Kerberos Installation
aptitude install openafs-krb5 krb5-user
Default Kerberos version 5 realm: HCOOP.NET
Kerberos servers for your realm: deleuze.hcoop.net
Administrative server for your Kerberos realm: deleuze.hcoop.net
If you are using Ubuntu Hardy, you might also need to add the following to your /etc/krb5.conf file, in the [domain_realm] section. It gets rid of a pesky warning.
hcoop.net = HCOOP.NET
.hcoop.net = HCOOP.NET
Using AFS
Typically, to gain access to your HCoop AFS share, do the following on your local system:
kinit user@HCOOP.NET aklog -c hcoop.net
Be sure that the openafs module is loaded or there will be errors. The tickets gained will last up to 10 hours but can be renewed with krenew for up to 8 days. Here's a common use:
krenew -K 30 -t
See the krenew man page to learn what these options are doing.
Troubleshooting
ReiserFS
First, if you are using ReiserFS, the AFS daemon will simply refuse to work because it cannot use that filesystem for its cache. If the daemon doesn't run, you'll get a puzzling error message that might make you think you have a firewall problem.
To get the daemon to work, edit the /etc/openafs/afs.conf to make it use the memory cache. It is said to be less stable than the hard disk cache. The README.Debian file also suggests creating a loopback ext2 filesystem for the cache.
Konqueror
Konqueror simply hangs when trying to browse /afs with the default CellServerDB. This happens because it is trying to access AFS volumes it doesn't have access to or that are not accessible, and hangs indefinitely. There is a lot of cells pre-configured in the Debian package, and probably some of them are not valid or not accessible. Once the content of /etc/openafs/CellServerDB has been erased of everything except for the hcoop.net entry, browsing /afs with Konqueror should work.