|
Size: 2836
Comment: Destroy existing tickets for screen FAQ item before acquiring new ones
|
Size: 3061
Comment: stress that kinit, krenew can be used in regular shell sessions
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 29: | Line 29: |
| = How do I run screen for a long time on mire? = If you want to have a long-running {{{screen}}} session and avoid permission denied errors, then log into mire and do the following: |
= How do I run a shell session for a long time on mire? = If you want to have a long-running session with or without {{{screen}}}, there are simple ways to avoid AFS permission denied errors due to expiring tokens. If you don't use screen, just pay attention to the `kinit` and `krenew` commands. `krenew` can be a daemon by using the `-b` argument. |
| Line 34: | Line 36: |
| # Once screen has loaded, then execute the following commands, # or place them in a script. |
# Once screen has loaded (or you have begun a regular shell session), # then execute the following commands, or place them in a script. |
| Line 41: | Line 43: |
| This will last until the ticket can no longer be renewed (approximately 8 days). However, you can kinit and krenew again while in the screen session to restart the clock. If the ticket expires while in a screen session, then you need to repeat those steps while in screen but be sure to add `aklog` for AFS ticket. You do not have to restart the screen session. In fact, you can dedicate a screen window just for monitoring and using kinit, aklog, and krenew. With this simple method, your screen session can run indefinitely with minimal weekly input. | This will last until the ticket can no longer be renewed (approximately 8 days). However, you can `kinit` and `krenew` again while in the screen session to restart the clock. If the ticket expires while in a screen session, then you need to repeat those steps while in screen but be sure to add `aklog` for AFS ticket. You do not have to restart the screen session. In fact, you can dedicate a screen window just for monitoring and using `kinit`, `aklog`, and `krenew`. With this simple method, your screen session can run indefinitely with minimal weekly input. |
This page contains answers to questions often asked about DomTool and our setup.
Services that worked fine yesterday suddenly don't work anymore
The most likely reason for IMAP, DNS, and web hosting to suddenly stop working is that there is a syntax error in one of the files in your ~/.domtool directory. Admins sometimes need to regenerate all domtool configuration files after making a change to domtool; if one of the files in your ~/.domtool directory has errors, it could prevent other files in that directory from being activated.
To figure out whether this was the problem: for each file <FILE> in your ~/.domtool directory, run
domtool -tc ~/.domtool/<FILE>
If you see any problems, either move the file into a different directory, or fix the problems.
When done, run domtool on each file in your ~/.domtool directory, and everything should be back to normal.
It is highly recommended to keep files in a different directory while testing them, and then copy them to ~/.domtool once you are certain that they are error-free.
If you don't find any errors in your domtool configuration, then you might want to file a support request.
Reference: MemberManual/UsingDomtool.
How do I read my Apache logs?
They are stored in ~/.logs/apache in subdirectories corresponding to machine and domain, and are updated every 20 minutes.
Reference: MemberManual/ServingWebsites.
How do I run a shell session for a long time on mire?
If you want to have a long-running session with or without screen, there are simple ways to avoid AFS permission denied errors due to expiring tokens.
If you don't use screen, just pay attention to the kinit and krenew commands. krenew can be a daemon by using the -b argument.
screen # Once screen has loaded (or you have begun a regular shell session), # then execute the following commands, or place them in a script. kdestroy unlog kinit -l 10d krenew -K 540 -t -b
This will last until the ticket can no longer be renewed (approximately 8 days). However, you can kinit and krenew again while in the screen session to restart the clock. If the ticket expires while in a screen session, then you need to repeat those steps while in screen but be sure to add aklog for AFS ticket. You do not have to restart the screen session. In fact, you can dedicate a screen window just for monitoring and using kinit, aklog, and krenew. With this simple method, your screen session can run indefinitely with minimal weekly input.
Reference: ["MemberManual/TransferringFiles/OpenAFS/Debian"]
Have changes been made to Domtool that render domtool related files invalid if copied verbatim from Fyodor?
Yes, Domtool has changed significantly from the version used in our old infrastructure on Fyodor. Please see the page MemberManual/UsingDomtool for instructions related to the most recent version of Domtool.