Difference between revisions of "Server maintenence"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
old>Admin
Line 4: Line 4:


The page is: ''http://SERVER/APPLICATION/service?PASSWORD''
The page is: ''http://SERVER/APPLICATION/service?PASSWORD''
Password can be set in the confguration: ''healthMonitorPassword''


Reponse will look something like
Reponse will look something like
<blockquote><p>
<blockquote><p>
&lt;serverstatus&gt;
&lt;serverstatus&gt;<br>
&lt;flag name=&quot;Source version&quot;&gt;2081&lt;/flag&gt;
&lt;flag name=&quot;Source version&quot;&gt;2081&lt;/flag&gt;<br>
&lt;flag name=&quot;Unused storage&quot;&gt;27%&lt;/flag&gt;
&lt;flag name=&quot;Unused storage&quot;&gt;27%&lt;/flag&gt;<br>
&lt;flag name=&quot;Database motor&quot;&gt;OK&lt;/flag&gt;
&lt;flag name=&quot;Database motor&quot;&gt;OK&lt;/flag&gt;<br>
&lt;flag name=&quot;Authentication&quot;&gt;OK&lt;/flag&gt;
&lt;flag name=&quot;Authentication&quot;&gt;OK&lt;/flag&gt;<br>
&lt;flag name=&quot;Daemon running&quot;&gt;NO&lt;/flag&gt;
&lt;flag name=&quot;Daemon running&quot;&gt;NO&lt;/flag&gt;<br>
&lt;flag name=&quot;Server healthy&quot;&gt;HEALTHY&lt;/flag&gt;
&lt;flag name=&quot;Server healthy&quot;&gt;HEALTHY&lt;/flag&gt;<br>
&lt;flag name=&quot;Is user online&quot;&gt;NO&lt;/flag&gt;
&lt;flag name=&quot;Is user online&quot;&gt;NO&lt;/flag&gt;<br>
&lt;flag name=&quot;Session length&quot;&gt;30&lt;/flag&gt;
&lt;flag name=&quot;Session length&quot;&gt;30&lt;/flag&gt;<br>
&lt;flag name=&quot;DB schema LIVE&quot;&gt;tslive&lt;/flag&gt;
&lt;flag name=&quot;DB schema LIVE&quot;&gt;tslive&lt;/flag&gt;<br>
&lt;flag name=&quot;DB schema TEST&quot;&gt;tstest&lt;/flag&gt;
&lt;flag name=&quot;DB schema TEST&quot;&gt;tstest&lt;/flag&gt;<br>
&lt;flag name=&quot;Last view data&quot;&gt;2013-02-12 16:53:11&lt;/flag&gt;
&lt;flag name=&quot;Last view data&quot;&gt;2013-02-12 16:53:11&lt;/flag&gt;<br>
&lt;flag name=&quot;Last exception&quot;&gt;2013-02-12 12:28:16&lt;/flag&gt;
&lt;flag name=&quot;Last exception&quot;&gt;2013-02-12 12:28:16&lt;/flag&gt;<br>
&lt;/serverstatus&gt;
&lt;/serverstatus&gt;
</p></blockquote>
</p></blockquote>
Line 27: Line 29:
* DB connections are accessible
* DB connections are accessible
* Data / log disc is not full
* Data / log disc is not full
Password can be set in the confguration: ''healthMonitorPassword''


== Backup and restore ==
== Backup and restore ==

Revision as of 18:22, 12 February 2013

Server monitor page

Each application contains a public page that can be queried for server status.

The page is: http://SERVER/APPLICATION/service?PASSWORD

Password can be set in the confguration: healthMonitorPassword

Reponse will look something like

<serverstatus>
<flag name="Source version">2081</flag>
<flag name="Unused storage">27%</flag>
<flag name="Database motor">OK</flag>
<flag name="Authentication">OK</flag>
<flag name="Daemon running">NO</flag>
<flag name="Server healthy">HEALTHY</flag>
<flag name="Is user online">NO</flag>
<flag name="Session length">30</flag>
<flag name="DB schema LIVE">tslive</flag>
<flag name="DB schema TEST">tstest</flag>
<flag name="Last view data">2013-02-12 16:53:11</flag>
<flag name="Last exception">2013-02-12 12:28:16</flag>
</serverstatus>

If the goodword HEALTY is found the following things are ok

  • Server is open for logins
  • DB connections are accessible
  • Data / log disc is not full

Backup and restore

TS has inbuilt manual functions on the solution level, but measures have to taken to back the data IN the solutions.

Backups should optimally be done either by dumping the database. Alternatively the database can be stopped (important) and data folders can be backed up normally.

The following guide contains directions for setting up incremental backups to remote location, using rsync and SSH connections.

http://tempusserva.dk/mediawiki/index.php?title=Backup_and_restore

Table naming conventions

Every solution has its own table namespace of "data_" followed by the system solution name.

Example for the solution named XXX:

  • data_XXX

Other related tables include

  • data_XXX_file
  • data_XXX_mail
  • data_XXX_comment
  • data_XXX_contact
  • data_XXX_measure
  • data_XXX_member
  • data_XXX_t_YYY
  • data_XXX_accesslog
  • data_XXX_statuslog
  • data_XXX_revisionlog

Deleted tables are prefixed by a timestamp

URL redirects and rewrites

Tempus Serva (version 2090+) contains server filters for URL rewrite, redirects and forwards.

The filter is deactivated by default, but can be enabled by

  1. Rename /WEB-INF/web.xml.urlrewrite to web.xml
  2. Change /WEB-INF/urlrewrite.xml as needed
  3. Restart the server

Other options include merging web.xml.urlrewrite into the existing web.xml.

Documentation can be found in following pages

Retrieved from "https://wiki.tempusserva.dk/index.php?title=Server_maintenence&oldid=4027"