Request Tracking System (contacting root)

From CS Support Wiki
Revision as of 15:16, 17 September 2015 by Jpr9c (Talk | contribs) (Created page with "The systems staff group (aka "root@cs.virginia.edu") should be contacted using the Request Tracker system via email to root@cs.virginia.edu. Please do not email individual st...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The systems staff group (aka "root@cs.virginia.edu") should be contacted using the Request Tracker system via email to root@cs.virginia.edu. Please do not email individual staff members directly, even if you are addressing the request to a particular staff member (this is fine). Using the request tracker system allows all of us to see the request (in the event a particular staff member is not working) in order to keep up to date on the status of various requests; it also helps us manage our work flow.Thank you!

Reporting Problems

Diagnostic information

Please include as much diagnostic information as possible when you send a request to root or report a problem. The more information you give us, the easier it is for us to quickly respond to your problem. Please include the command you were executing, the directory and or files you were reading|writing to, and the error reported. Ideally, if you can cut-and-paste a copy of what is in your terminal window, this will convey a huge amount of information to us. This helps us *duplicate your problem*, which is critical to being able to diagnose it!

Troubleshooting

Error: "Extended mailgate error"

Sometimes when sending mail to root, you may receive this response from the system.

The RT program|system has the ability to react to commands embedded in email message bodies.

The parser looks at the first line of the body of the message to see if the first word ends in a colon; from your original message:

Hide quoted text >> --001a1143d5e476f322051fdf95a1 >> content-type: text/plain; charset="utf-8" >> X-RT-Original-Encoding: utf-8 >> >> lg5bt@power1:~/.ssh$ ssh-keygen >>

if RT does find a colon at the end of the first "word" (non-whitespace characters), then it tries to interpret the word as an RT command; in this case it doesn't understand the command "lg5bt@power1":

Hide quoted text >> Failed command 'lg5bt@power1: ~/.ssh$ ssh-keygen' >> Error message: Command 'lg5bt@power1' is unknown