Skip to content
Snippets Groups Projects
Commit 95246444 authored by Michael Davis's avatar Michael Davis
Browse files

Documents how to start CTA Front End

parent 075d4422
No related branches found
No related tags found
No related merge requests found
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
......@@ -371,7 +371,6 @@ sec.protocol sss -s /etc/ctafrontend_server_sss.keytab -c /etc/ctafrontend_clien
# Only Kerberos 5 and sss are allowed
sec.protbind * only sss krb5
sec.protbind * only sss krb5
# Allow copying from absolute paths
all.export /
......@@ -380,7 +379,7 @@ all.export /
xrootd.async off
# Use a port other than 1094, already used by EOS xroot server
xrd.port 10955
xrd.port 10956
\end{lstlisting}
\begin{alertbox}
......@@ -451,14 +450,7 @@ MSG="ProcessForkerConnectionHandler handling ProcessExited message" pid="32453"
MSG="Tape session finished"
\end{boxedverbatim}
\section{Start CTA Front End}
\begin{lstlisting}
# su - cta
[~]$ xrootd -n cta -c /etc/xrootd/xrootd-cta.cfg -I v4
\end{lstlisting}
\subsection{Starting up the xroot server with the CTA plugin}
\section{Start the XRoot daemon with CTA Front End plugin}
Before starting the xroot server we need to change the VFS backend permissions again (because new files have been created with the \texttt{stage:st} user by the tapeserver daemon). Example:
......@@ -466,59 +458,16 @@ Before starting the xroot server we need to change the VFS backend permissions a
$ chmod -R 0777 /tmp/jobStoreVFSOKJCjW
\end{verbatim}
We now create some useful soft links to simplify the xrootd configuration:
\begin{verbatim}
$ ln -s <CTA build directory>/xroot_plugins/libXrdCtaOfs.so /usr/lib64/libXrdCtaOfs.so
$ ln -s <CTA src directory>/xroot_plugins/xrd.cf.cta /etc/xrd.cf.cta
\end{verbatim}
The \emph{xroot} server then can be launched with the following command:
\begin{verbatim}
$ xrootd -n cta -c /etc/xrd.cf.cta -I v4
\end{verbatim}
Where the first parameter is the name of the xroot instance, the second one is the configuration file above and the third one basically instructs \emph{xroot} to use IPv4. The result of the command is typically something like:
\begin{verbatim}
151009 15:59:19 18239 Starting on Linux 2.6.32-573.3.1.el6.x86_64
Copr. 2004-2012 Stanford University, xrd version v4.2.3
++++++ xrootd anon@dkruse.cern.ch initialization started.
Config using configuration file /home/dkruse/CTA/CTA/xroot_plugins/xrd.cf.cta
=====> xrd.port 10955
Config maximum number of connections restricted to 4096
Copr. 2012 Stanford University, xrootd protocol 3.0.0 version v4.2.3
++++++ xrootd protocol initialization started.
=====> xrootd.fslib /home/dkruse/CTA/build/xroot_plugins/libXrdCtaOfs.so
=====> xrootd.seclib libXrdSec.so
=====> all.export /
=====> xrootd.async off
Config exporting /
Plugin loaded
++++++ Authentication system initialization started.
Plugin loaded
Template for exports not set
=====> sec.protocol krb5 /etc/krb5.keytab.cta host/<host>@CERN.CH
=====> sec.protbind * only krb5
Config 2 authentication directives processed in
/home/dkruse/CTA/CTA/xroot_plugins/xrd.cf.cta
------ Authentication system initialization completed.
Config Routing for dkruse.cern.ch: local pub4 prv4
Config Route all4: dkruse.cern.ch Dest=[::137.138.33.124]:10955
Plugin No such file or directory
loading fslib /home/dkruse/CTA/build/xroot_plugins/libXrdCtaOfs-4.so
Config Falling back to using /home/dkruse/CTA/build/xroot_plugins/libXrdCtaOfs.so
Plugin loaded
[WARNING] Could not create the admin user and admin host. CTA exception caught:
In RootEntry::addAdminUser: entry already exists
Config warning: asynchronous I/O has been disabled!
Config warning: 'xrootd.prepare logdir' not specified; prepare tracking disabled.
------ xrootd protocol initialization completed.
------ xrootd anon@dkruse.cern.ch:10955 initialization completed.
\end{verbatim}
The \emph{xroot} server can be stopped by pressing \texttt{Ctrl+c}. Once the server is running, the CTA CLI will be able to send commands and receive results.
Start the XRoot daemon, specifying the name of the XRoot instance (\texttt{-n}), the name of the configuration file we
just created (\texttt{-c}), use IPv4 protocol (\texttt{-I v4}), run in the background (\texttt{-b}) and where to put the
log file (\texttt{-l})\footnote{For full documentation of command line options, see
\href{http://xrootd.org/doc/dev44/xrd_config.htm\#_Toc98765632}{http://xrootd.org/doc/dev44/xrd\_config.htm}}:
\begin{lstlisting}
# su - cta
[~]$ xrootd -n cta -c /etc/xrootd/xrootd-cta.cfg -I v4 -b -l /tmp/ctafrontend.log
\end{lstlisting}
Once the XRoot daemon is running, the CTA CLI will be able to send commands and receive results (See
Chapters~\ref{admin_commands} and~\ref{user_commands}).
\section{Configure an EOS workflow to allow EOS to talk to the CTA front-end}
......
No preview for this file type
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment