welcome: please sign in

Diff for "MemberManual/FAQ"

Differences between revisions 22 and 23
Revision 22 as of 2007-12-27 04:12:52
Size: 3297
Editor: MichaelOlson
Comment: Add Email quota FAQ item and reword title
Revision 23 as of 2007-12-29 00:09:08
Size: 3700
Editor: AdamChlipala
Comment: Reorganize and add "Internal Server Error"
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
= Services that worked fine yesterday suddenly don't work anymore = = Shell Access =

== 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"]

= Web Sites =

== 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.

== I get a very unhelpful "Internal Server Error" page from Apache when I try to access my dynamic web site content. ==

Check `error.log` in your virtual host's log directory. See the last answer for where that is.

= E-mail =

== I can't access my e-mail via IMAP anymore. ==

Check your quota on your e-mail volume by doing {{{
fs listquota ~/Maildir
}}}

If it is too low, then you will need to [https://members.hcoop.net/portal/quota request an increase in disk quota].

''Reference'': ["MemberManual/Email"]

= Custom Daemons =

== Services that worked fine yesterday suddenly don't work anymore. ==
Line 24: Line 72:
= 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.
= Migration from Our Old Servers (for members who joined before December 2007) =
Line 27: Line 74:
''Reference'': MemberManual/ServingWebsites. == Can I copy my Domtool configuration verbatim from Fyodor? ==
Line 29: Line 76:
= 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"]

= Can I copy my Domtool configuration verbatim from Fyodor? =
Line 49: Line 77:

= I can't access my email via IMAP anymore =
Check your quota on your email volume by doing {{{
fs listquota ~/Maildir
}}}

If it is too low, then you will need to [https://members.hcoop.net/portal/quota request an increase in disk quota].

''Reference'': ["MemberManual/Email"]

This page contains answers to questions often asked about DomTool and our setup.

TableOfContents

Shell Access

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"]

Web Sites

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.

I get a very unhelpful "Internal Server Error" page from Apache when I try to access my dynamic web site content.

Check error.log in your virtual host's log directory. See the last answer for where that is.

E-mail

I can't access my e-mail via IMAP anymore.

Check your quota on your e-mail volume by doing

fs listquota ~/Maildir

If it is too low, then you will need to [https://members.hcoop.net/portal/quota request an increase in disk quota].

Reference: ["MemberManual/Email"]

Custom Daemons

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.

Migration from Our Old Servers (for members who joined before December 2007)

Can I copy my Domtool configuration verbatim from Fyodor?

No. 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.

MemberManual/FAQ (last edited 2016-09-13 03:37:37 by JackHill)