Mercurial > dive4elements > gnv-client
comparison doc/admin-manual/operating-the-system.tex @ 949:11d8cc2deb92 1.0
merged doc/1.0
| author | Thomas Arendsen Hein <thomas@intevation.de> |
|---|---|
| date | Fri, 28 Sep 2012 12:13:58 +0200 |
| parents | ec28a68b5a87 |
| children | 17c3770e6c63 |
comparison
equal
deleted
inserted
replaced
| 899:3f9fc88aec2b | 949:11d8cc2deb92 |
|---|---|
| 1 \section{Management of operational processes} | |
| 2 | |
| 3 For running the entire GNV-system the following components have to be | |
| 4 available in the described sequence: | |
| 5 \begin{enumerate} | |
| 6 \item Database server | |
| 7 \item Artifact-server | |
| 8 \item Apache Tomcat running the WebClient | |
| 9 \item Apache WebServer | |
| 10 \end{enumerate} | |
| 11 | |
| 12 During a server startup the installed components get started | |
| 13 automatically. | |
| 14 | |
| 15 \subsection{Managing the Artifact Server} | |
| 16 | |
| 17 \subsubsection*{Starting and Stopping} | |
| 18 | |
| 19 The artifact-server can be restarted without stopping the WebClient. | |
| 20 During the restart-process client accessing the server get an approriate | |
| 21 message. Their session data will not be lost if the artifact database | |
| 22 will remain untouched. | |
| 23 | |
| 24 Stopping artifact-server: | |
| 25 \begin{lstlisting} | |
| 26 /etc/init.d/artifact-server stop | |
| 27 \end{lstlisting} | |
| 28 | |
| 29 Starting artifact server | |
| 30 \begin{lstlisting} | |
| 31 /etc/init.d/artifact-server start | |
| 32 \end{lstlisting} | |
| 33 | |
| 34 Restarting artifact server | |
| 35 \begin{lstlisting} | |
| 36 /etc/init.d/artifact-server restart | |
| 37 \end{lstlisting} | |
| 38 | |
| 39 \subsubsection*{Troubleshooting} | |
| 40 | |
| 41 \paragraph*{Database problems} | |
| 42 For checking problems with the connection to the database server, check | |
| 43 the logfile of the artifact-server (c.f. | |
| 44 chapter~\chapter{ref:artifact-server-install}, | |
| 45 p.~pageref{ref:artifact-server-install}. | |
| 46 | |
| 47 In most cases, a restart of the artifact-server will help to solve | |
| 48 problems in the artifact-server. If you still encounter problems, check | |
| 49 for the network connection to the database server and the maturity of | |
| 50 the database server. | |
| 51 | |
| 52 \paragraph*{Caching problems} | |
| 53 Inconsistencies between original data and cached data: | |
| 54 The artifact-server stores result sets of the database in a cache and | |
| 55 provides maps via configuration files for MapServer based on shapefiles. | |
| 56 In case of inconsistencies showing up for longer than twice the | |
| 57 maximum of the update cycle of internal ETL processes, do the following | |
| 58 as user \verb+root+: | |
| 59 | |
| 60 \begin{lstlisting} | |
| 61 cd /opt/artifact-server | |
| 62 /etc/init.d/artifact-server stop | |
| 63 rm -ri cache/* | |
| 64 /etc/init.d/artifact-server start | |
| 65 \end{lstlisting} | |
| 66 | |
| 67 \subsection{Managing the GNV-Client} | |
| 68 \subsubsection*{Start Stop Restart} | |
| 69 | |
| 70 The GNV-WebClient can be managed by controlling Apache Tomcat instance: | |
| 71 | |
| 72 Status GNV-WebClient | |
| 73 \begin{lstlisting} | |
| 74 /etc/init.d/tomcat5.5 status | |
| 75 \end{lstlisting} | |
| 76 | |
| 77 Stopping GNV-WebClient | |
| 78 \begin{lstlisting} | |
| 79 /etc/init.d/tomcat5.5 stop | |
| 80 \end{lstlisting} | |
| 81 | |
| 82 Starting GNV-WebClient | |
| 83 \begin{lstlisting} | |
| 84 /etc/init.d/tomcat5.5 start | |
| 85 \end{lstlisting} | |
| 86 | |
| 87 Restarting GNV-WebClient | |
| 88 \begin{lstlisting} | |
| 89 /etc/init.d/tomcat5.5 restart | |
| 90 \end{lstlisting} | |
| 91 | |
| 92 \subsubsection*{Troubleshooting} | |
| 93 | |
| 94 If the GNV-WebClient can not be accessed through the Apache WebServer, do the | |
| 95 following: | |
| 96 \begin{lstlisting} | |
| 97 1. /etc/init.d/apache2 restart | |
| 98 2. Check in your browser at http://$SERVERNAME/gnv | |
| 99 \end{lstlisting} | |
| 100 | |
| 101 If you still encounter problems, follow the next these steps: | |
| 102 | |
| 103 {\bf Caution: The entire application will be down until the WebServer is | |
| 104 back up.} | |
| 105 \begin{lstlisting} | |
| 106 /etc/init.d/apache2 stop | |
| 107 /etc/init.d/tomcat5.5 stop | |
| 108 rm -r /usr/share/tomcat5.5/work/Catalina/localhost/gnv/* | |
| 109 /etc/init.d/tomcat5.5 start # wait until tomcat is up | |
| 110 /etc/init.d/apache2 start | |
| 111 \end{lstlisting} | |
| 112 | |
| 113 For further information, you look into the log information during the use of the | |
| 114 GNV WebClient | |
| 115 \begin{lstlisting} | |
| 116 tail -f -n 50 /usr/share/tomcat5.5/logs/gnv.log | |
| 117 \end{lstlisting} | |
| 118 | |
| 119 To get even more logging, do the following: | |
| 120 | |
| 121 {\bf Caution: The entire application will be down until the Apache Tomcat | |
| 122 has been started properly; the higher log-level can affect the | |
| 123 runtime-behaviour of the client. For further instructions, c.f. | |
| 124 Chapter~\ref{ref:webclient-config}, p.~\pageref{ref:webclient-config}.} | |
| 125 | |
| 126 \begin{lstlisting} | |
| 127 /etc/init.d/tomcat5.5 stop | |
| 128 Set logging to DEBUG | |
| 129 vim /usr/share/tomcat5.5/webapps/gnv/WEB-INF/classes/log4j.properties | |
| 130 /etc/init.d/tomcat5.5 start # wait until tomcat is up | |
| 131 tail -f -n 50 /usr/share/tomcat5.5/logs/gnv.log | |
| 132 \end{lstlisting} | |
| 133 | |
| 134 It is recommended to undo the logging configuration, after the relevant | |
| 135 part has been found. |