- link to GGUS as a primary support contact

- change item order

diff --git a/org.glite.lb.doc/src/LBUG-Troubleshooting.tex b/org.glite.lb.doc/src/LBUG-Troubleshooting.tex
index 4153ae6..15fca01 100644 (file)
--- a/org.glite.lb.doc/src/LBUG-Troubleshooting.tex
+++ b/org.glite.lb.doc/src/LBUG-Troubleshooting.tex
@@ -1,29 +1,38 @@
 \section{Troubleshooting}
 
-Please, report all bugs to EU EGEE Bug Tracking System located at
+Please, report usage problems via the GGUS support system at
+\begin{center}
+\url{https://gus.fzk.de/index.html}
+\end{center}
+Apparent software bugs are tracked in Savannah at
 \begin{center}
 \url{https://savannah.cern.ch/bugs/?func=additem&group=jra1mdw}
 \end{center}
 
-When submitting a \LB spcecific bug, the following information might be useful:
+When submitting a \LB spcecific problem/bug, the following information might be useful:
 \begin{itemize}
+\item version of software used (all \verb'glite-lb-*' packages installed at your site)
 \item description of the problem, the \verb'jobId', addresses of all relevant
- machines (LB server, ...), environment variables set, etc.
+ machines (\LB server, ...), environment variables set, etc.
 \item output from the following commands:
 \begin{verbatim}
    glite-wms-job-status <jobId>
    glite-wms-job-logging-info -v 3 <jobID>
 \end{verbatim}
-\item sometimes it can be useful also output from the commands
+\item information on your proxy:
+\begin{verbatim}
+   voms-proxy-info -debug -all
+\end{verbatim}
+or, if VOMS client is not installed, 
+\begin{verbatim}
+   grid-proxy-info -debug 
+\end{verbatim}
+\item sometimes additional information can be found in the output from the commands
 \begin{verbatim}
    glite-lb-job_status <jobId>
    glite-lb-job_log <jobId>
 \end{verbatim}
 that should be available in the \verb'$GLITE_LOCATION/examples' directory,
-or command
-\begin{verbatim}
-   grid-proxy-info -debug
-\end{verbatim}
 \item appropriate excerpts from the logs on the server side are also highly appreciated, 
 please tell your administrator to look at the Troubleshooting section in LB Administrator's 
 Guide \cite{lbag} to follow the steps there and provide you the necessary information.