 |
PLEASE READ THIS PAGE TO THE END BEFORE SUBMITTING
BUGS.
|
Known Issues, FAQ
A list of known issues is listed in the Release
Notes of each gLite release. These will give you the corresponding
list of known open issues at the time of the release. In addition,
the EGEE
Savannah pages can be consulted (queried) to get the
list of current open issues. The following links may be helpful:
There is also a list of Frequently
Asked Questions in the Wiki area listing common errors and mistakes during setup and configuration. |
Getting Help
There are several ways to get help, depending on your context.
There are several mailinglists where we are giving help, please
choose carefully in order not to annoy the audience :-) :
| glite-discuss@cern.ch |
This is the generic gLite discussion list
for all questions concerning gLite, including of course
the FTS. Glite users and also the developers are subscribed
who may help with 'regular' issues.
- You are new to gLite and are trying FTS out.
- You are a user and have problems to use/install the
FTS
|
| project-eu-egee-pre-production-service@cern.ch |
The preproduction service list, discussing all issues
around the pre-production, including FTS.
- You work on the PPS as an admin
- You work on the PPS as a tester
- You are running your jobs on the PPS infrastructure
- You are using the PPS for a tutorial
|
| lcg-sc.support@cern.ch |
Contact list for support of all LCG Service Challenge
Services.
- You are a VO administrator or middleware contact
- You work on the Service Challenge setup as a user
|
| fts-support@cern.ch |
The 3rd level support for the FTS, i.e. the developers
of the service.
- You are part of the LCG Service Coordination team
- You are participating in the LCG Service Challenges as
an administrator
- You are member of the EGEE user support or test team
|
If you are sure that your issue is a 'real' issue with the FTS,
submit a bug (see below). |
Bug Reporting
If you are certain that you have found a new bug, please submit
a new bug through the Savannah
bug tracking system. Please fill in the bug submission using
the following guidelines:
- Category: Data Management
- Item Group: depending on what you see
- Privacy: Public
- Release: please put in the gLite release you are experiencing
the bug on (like 1.4.1)
- Severity: Critical means it will be raised to top-level management
immediately, use with care.
- Status and Assigned to can be left on 'Unknown'.
- Summary: Please always start with 'FTS:'. The summary should
be as short but descriptive as possible
- Original Submission: You can copy and paste as much text
here as you like. However, if you have logfiles, please use
the 'attach file' possibility furthere down the bug submission
page.
Make sure that for all submissions you supply the version of
the tool actually used. For example many of the command
line interface utilities support the -V option that prints
the tool's version and exits - this printout should be part
of all bug submissions that concern these clients. Make sure
that log files that you know about (client logs, server logs)
are all attached. Log files are usually at:
- Web Service: The directory $CATALINE_HOME/logs contains
several logfiles, where CATALINA_HOME is the installation
home of tomcat5
(/var/tomcat5?). Also $GLITE_LOCATION/etc/log4j.properties may give an insight where the log goes to (look for file
names in this file):
- org.glite.data : generic logs
- org.glite.data.transfer.fts-calls : logging the received
calls to the FTS Transfer interface
- org.glite.data.transfer.channeladmin-calls : logging
the received calls to the FTS Channel Interface
- Agent: /var/log/glite/ usually contains all the logs
if not configured differently.
- Mail Notification: Add any other party (including yourself)
who should always be notified if the status of this bug changes.
Please continue all discussion on the bug through savannah, not
over regular email in order to keep everything in one place. |
|
