---+ Disk Pool Manager %TOC% ---+++ Functional description [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmGeneralDescription][ See DPM General Description]] ---+++ Daemons running [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmAdminGuide#Run_the_Daemons][ See DPM Daemon Description]] Command line arguments can be found on the documentation On the DPNS server machine : * /opt/lcg/bin/dpnsdaemon On each disk server managed by the DPM : * /opt/lcg/bin/rfiod On the DPM and SRM server machine(s) : * /opt/lcg/bin/dpm * /opt/lcg/bin/srmv1 * /opt/lcg/bin/srmv2 * /opt/lcg/bin/srmv2.2 On each disk server managed by the DPM : * /opt/globus/sbin/globus-gridftp-server If Xrootd is configured: * /opt/lcg/bin/dpm-manager-xrootd * /opt/lcg/bin/dpm-manager-olbd * /opt/lcg/bin/dpm-xrootd * /opt/lcg/bin/dpm-olbd !WebAccess: * dpm-http ---+++ Init scripts and options (start|stop|restart|...) * /etc/init.d/dpnsdaemon {start|stop|status|restart|condrestart} * /etc/init.d/rfiod {start|stop|status|restart|condrestart} * /etc/init.d/dpm {start|stop|status|restart|condrestart} * /etc/init.d/srmv1 {start|stop|status|restart|condrestart} * /etc/init.d/srmv2 {start|stop|status|restart|condrestart} * /etc/init.d/srmv2.2 {start|stop|status|restart|condrestart} * /etc/init.d/dpm-gsiftp {start|stop|restart|reload|condrestart|status} * Xrootd disk server: * service dpm-xrd <start|status|stop...> * service dpm-olb <start|status|stop...> * Xrootd head node: * service dpm-manager-xrd * service dpm-manager-olb * To start the DPM apache service run o /etc/init.d/dpm-httpd start * To stop the DPM apache service run o /etc/init.d/dpm-httpd stop * To check the status run o /etc/init.d/dpm-httpd status * To restart the DPM apache service o /etc/init.d/dpm/httpd restart ---+++ Configuration files location with example or template [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmAdminGuide#DPM_Configuration][ See DPM Configuration]] By default, the database configuration files are : * /opt/lcg/etc/NSCONFIG * /opt/lcg/etc/DPMCONFIG Configuration: * /etc/sysconfig/dpnsdaemon * /etc/sysconfig/rfiod * /etc/sysconfig/srmv1 * /etc/sysconfig/srmv2.2 * /etc/sysconfig/srmv2 * /etc/sysconfig/dpm-gsiftp * /etc/sysconfig/dpm * /etc/sysconfig/dpm-xrd * lcgdm-mapfile Xrootd: * /etc/shift.conf * /etc/sysconfig/dpm-xrd !WebAccess: * Run the configuration script depending if you have a single head/disk-node or a seperate head- and seperate disk-nodes o /opt/lcg/etc/dpm/https/conf/dpm-https-conf.sh --type sor o /opt/lcg/etc/dpm/https/conf/dpm-https-conf.sh --type head-node o /opt/lcg/etc/dpm/https/conf/dpm-https-conf.sh --type disk-node * Whenever you add or remove disks to a DPM pool, you have to run on the disk node o /opt/lcg/etc/dpm/https/conf/dpm-https-conf.sh --pools ---+++ Logfile locations (and management) and other useful By default, the log files are : * /var/log/dpns/log * /var/log/dpm/log * /var/log/srmv1/log * /var/log/srmv2/log * /var/log/rfiod/log * /var/log/messages (Griftp server) * /var/log/xroot/ * /var/log/dpm-httpd/access * /var/log/dpm-httpd/errors # The redirection CGI script writes a special log file under /var/log/dpm-httpd/cgilog. Errors are logged also in syslog ---+++ Open ports * DPM server: port 5015/tcp must be open locally at your site at least (can be incoming access as well) * DPNS server: port 5010/tcp must be open locally at your site at least (can be incoming access as well) * SRM servers: ports 8443/tcp (SRMv1), 8444/tcp (SRMv2) and 8446/tcp (SRMv2.2) must be opened to the outside world (incoming access) * RFIO server: port 5001/tcp and data ports 20000-25000/tcp must be open to the outside world (incoming access), in the case your site wants to allow RFIO access from outside * Gridftp server: control port 2811/tcp and data ports 20000-25000/tcp (or any range specified by GLOBUS TCP PORT RANGE) must be opened to the outside world (incoming access) * Xrootd: The manager xrootd listens by default on port 1094. The diskserver xrootd port listens by default on port 1095. You have to allow incoming access towards this ports from expected client machines. All transfers run via port 1095 - there is no need for an open high port range. * !WebAccess: * Head-Node o Virtual Host Port 443 + main entrance point for web file access to a DPM 'https://<dpm-headnode>/dpm/cern.ch/filename' with default redirection to HTTP transport o Virtual Host Port 883 + main entrance point for web file access to a DPM with forced redirection to HTTPS transport ( slower ) * Disk-Server o Virtual Host Port 777 + tranpsport endpoint for HTTP web file access with redirector authorization o Virtual Host Port 884 + tranpsport endpoint for HTTPS web file access with redirector authorization ---+++ Possible unit test of the service UI , WN and from itself ---+++ Where is service state held (and can it be rebuilt) ---+++ Cron jobs None ---+++ How the site admin can block a specific user ---+++ Utility scripts [[http://www.gridpp.ac.uk/wiki/DPM-admin-tools][GridPP DPM administation toolkit]] ---+++ Monitoring [[http://www.gridpp.ac.uk/wiki/DPM_Monitoring][GridPP DPM monitoring system]] ---+++ Location of reference documentation for users [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmGeneralDescription][ See DPM Documentation]] ---+++ Location of reference documentation for administrators [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmAdminGuide][ See DPM Documentation]] [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmXrootAccess][ See Xrootd Documentation]] [[https://twiki.cern.ch/twiki/bin/view/LCG/DpmHttpsAccess][See web access on DPM Documentation] -- Main.RicardoMendes - 05 Aug 2008
This topic: EGEE
>
WebHome
>
SA3
>
GliteDPM
Topic revision: r7 - 2009-01-09 - LorenzoSbolgi
Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Ask a support question
or
Send feedback