SCRUG-NA/2025
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[installation] Change to nightly

Browse Source
This commit is contained in:
Dirk Rössler
2025-10-30 12:04:59 +01:00
parent 2ff097f9d1
commit a31bc45cce
1441 changed files with 60368 additions and 56360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

316
share/doc/seiscomp/html/base/tutorials/upgrading.html
View File

@@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Upgrading SeisComP &#8212; SeisComP Release documentation</title>
<title>Updating/Upgrading SeisComP &#8212; SeisComP Development documentation</title>
<link rel="stylesheet" href="../../_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="../../_static/seiscomp.css" type="text/css" />
<link rel="stylesheet" type="text/css" href="../../_static/pygments.css?v=72bcf2f2" />
@@ -12,7 +12,7 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<script type="text/javascript" src="../../_static/seiscomp.js"></script>
<script type="text/javascript" id="documentation_options" data-url_root="../../" src="../../_static/documentation_options.js"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
@@ -25,8 +25,8 @@
<div class="container">
<div class="brand">
<img class="logo" src="../../_static/brands/seiscomp/text/white.svg"/>
<!-- span class="title">SeisComP Release</span -->
<span class="version">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@@ -69,16 +69,18 @@
<div class="fitted content" id="anchors-container">
<div class="body" role="main">
<section id="upgrading-seiscomp">
<span id="tutorials-upgrade"></span><h1>Upgrading SeisComP<a class="headerlink" href="#upgrading-seiscomp" title="Permalink to this heading"></a></h1>
<section id="updating-upgrading-seiscomp">
<span id="tutorials-upgrade"></span><h1>Updating/Upgrading SeisComP<a class="headerlink" href="#updating-upgrading-seiscomp" title="Permalink to this heading"></a></h1>
<p>You will …</p>
<ul class="simple">
<li><p>Upgrade a SeisComP system</p></li>
<li><p>Update/Upgrade a SeisComP system</p></li>
<li><p>Migrate a SeisComP3 system to a newer SeisComP version</p></li>
</ul>
<p>Pre-requisites for this tutorial:</p>
<ul class="simple">
<li><p>Tutorial on <a class="reference internal" href="postinstall.html#tutorials-postinstall"><span class="std std-ref">installation</span></a> and SeisComP previously installed</p></li>
<li><p><a class="reference internal" href="../installation.html#installation"><span class="std std-ref">Documentation of installation</span></a></p></li>
<li><p>Tutorial on <a class="reference internal" href="postinstall.html#tutorials-postinstall"><span class="std std-ref">installation</span></a> and <cite>SeisComP</cite>
previously installed</p></li>
</ul>
<p>Afterwards/Results/Outcomes:</p>
<ul class="simple">
@@ -91,72 +93,38 @@
<hr class="docutils" />
<section id="background">
<h2>Background<a class="headerlink" href="#background" title="Permalink to this heading"></a></h2>
<p>Installing a new SeisComP <a class="reference internal" href="#tutorials-upgrade-versions"><span class="std std-ref">release version</span></a>
is typically simple and the step described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Upgrade</span></a>
can be applied. <strong>More actions</strong> are required when</p>
<p>Updating/upgrading <cite>SeisComP</cite> to a higher
<a class="reference internal" href="../installation.html#installation-versions"><span class="std std-ref">release version</span></a> is typically simple and the
steps described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a> can be applied.
<strong>More actions</strong> are required when</p>
<ul class="simple">
<li><p>Upgrading the major version of SeisComP as described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Upgrade</span></a>.</p></li>
<li><p>Upgrading the major version of SeisComP as described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a>.</p></li>
<li><p>Upgrading <a class="reference internal" href="#tutorials-upgrade-v4"><span class="std std-ref">from SeisComP3 to SeisComP in version 4.0.0. or higher</span></a>.</p></li>
<li><p>Upgrading <a class="reference internal" href="#tutorials-upgrade-seedlink"><span class="std std-ref">from SeisComP3 Jakarta-2018.327 or older to Jakarta-2020.330 or
SeisComP in version 4 or higher</span></a>.</p></li>
</ul>
<section id="seiscomp-versions">
<span id="tutorials-upgrade-versions"></span><h3>SeisComP versions<a class="headerlink" href="#seiscomp-versions" title="Permalink to this heading"></a></h3>
<p>SeisComP has <a class="reference internal" href="../history.html#history"><span class="std std-ref">developed over time</span></a>. The versions can be distinguished
by the name of the release:</p>
<ul>
<li><p><strong>SeisComP since version 4.0.0</strong> uses release version numbers such as <em>5.2.1</em>
where</p>
<ul class="simple">
<li><p>5: major version with changes in API and database schema version, new features,
bug fixed, optimizations,</p></li>
<li><p>2: minor version with new features, bug fixed, optimizations,</p></li>
<li><p>1: patch number with bug fixes, optimizations.</p></li>
</ul>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>When increasing the major version number, an upgrade of
the database is required.</p>
</div>
</li>
<li><p><strong>SeisComP3</strong> uses release versions, names, numbers and patch numbers.</p>
<p>Full example: <em>SeisComP3-jakarta-2020.330.02</em></p>
<ul class="simple">
<li><p>3: release version</p></li>
<li><p>jakarta: release name</p></li>
<li><p>2020.330: release number</p></li>
<li><p>02: patch number</p></li>
</ul>
<p>Names are adjusted depending on changes in source code:</p>
<ul class="simple">
<li><p><strong>Release version:</strong> major changes in module groups, functionality, concepts, data model.
Example: SeisComp3 is SeisComP in version 3.0
in comparison to version 2.5 the GUIs were introduced.</p></li>
<li><p><strong>Release name:</strong> major changes in functionality, concepts, data model.
Example: with SeisComP3-Seattle the new user friendly configuration GUI <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>
was introduced.</p></li>
<li><p><strong>Release number:</strong> changes in data model version and/or major changes in applications and optimizations.
The numbers include the year and the day of the year of the software release.
Example: Jakarta-2018.327</p></li>
<li><p><strong>Patch number:</strong> optimizations of applications without changes in the data model version.</p></li>
</ul>
</li>
</ul>
<section id="upgrade-vs-update">
<h3>Upgrade vs. update<a class="headerlink" href="#upgrade-vs-update" title="Permalink to this heading"></a></h3>
<p>Here we understand that <em>upgrades</em> increase the major release version number
while <em>updates</em> only increase the minor version or the patch number, see section
<a class="reference internal" href="../installation.html#installation-versions"><span class="std std-ref">SeisComP Versions</span></a>.</p>
</section>
<section id="upgrade-seiscomp-on-multiple-machines">
<h3>Upgrade SeisComP on multiple machines<a class="headerlink" href="#upgrade-seiscomp-on-multiple-machines" title="Permalink to this heading"></a></h3>
<section id="upgrading-multiple-machines">
<h3>Upgrading multiple machines<a class="headerlink" href="#upgrading-multiple-machines" title="Permalink to this heading"></a></h3>
<p>Applications can only connect to a messaging system that runs with a database
in an equal or lower data base schema version. In distributed <cite>SeisComP</cite> systems
one machine host the messaging system and the database and all other machines
are connected to this messaging or are running independently, the <cite>SeisComP</cite>
installation on the machine operating the messaging is always updated last.</p>
in an equal or lower data base schema version. However, upgrading <cite>SeisComP</cite> to a
higher major release version typically increases the database scheme version.
Therefore, in distributed <cite>SeisComP</cite> systems where one machine hosts the messaging
system and the database and all other machines are connected to this messaging,
the <cite>SeisComP</cite> installation on the machine operating the messaging is always
upgraded last.</p>
<p><strong>Example:</strong> A distributed system includes a processing system with the
messaging system and database and a GUI work station connected to the processing
system:</p>
<ol class="arabic simple">
<li><p>Upgrade the GUI work station</p></li>
<li><p>Upgrade the processing system, take actions to
<a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">upgrade the database version</span></a>.</p></li>
<li><p><a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Upgrade</span></a> the GUI work station</p></li>
<li><p><a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Upgrade</span></a> the processing system, take actions
to <a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">upgrade the database version</span></a>.</p></li>
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
@@ -166,79 +134,39 @@ system:</p>
</div>
</div>
</section>
</section>
<section id="package-download">
<span id="tutorials-upgrade-download"></span><h2>Package Download<a class="headerlink" href="#package-download" title="Permalink to this heading"></a></h2>
<p>Get the SeisComP package in the latest version or older ones from gempa GmbH or
from the download website of <span id="id1">Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH [<a class="reference internal" href="../references.html#id257" title="Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH. The SeisComP seismological software package. GFZ Data Services. 2008. URL: https://www.seiscomp.de, doi:10.5880/GFZ.2.4.2020.003.">67</a>]</span>.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>gempa provides <span id="id2"><em>gsm - gempa software management tool</em> [<a class="reference internal" href="../references.html#id129" title="gsm - gempa software management tool. gempa solution. URL: https://data.gempa.de/packages/Public/gsm/.">29</a>]</span> for convenient and consistent download and
installation of SeisComP and other packages.</p>
</div>
<span id="tutorials-upgrade-download"></span><h3>Package download<a class="headerlink" href="#package-download" title="Permalink to this heading"></a></h3>
<p>Get and install the <cite>SeisComP</cite> package in the any available version from
<span id="id1"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id147" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de.">31</a>]</span> or from the download website of <span id="id2">Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH [<a class="reference internal" href="../references.html#id290" title="Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH. The SeisComP seismological software package. GFZ Data Services. 2008. URL: https://www.seiscomp.de, doi:10.5880/GFZ.2.4.2020.003.">76</a>]</span> as described
in section <a class="reference internal" href="../installation.html#installation-packages"><span class="std std-ref">Installation of Packages</span></a>.</p>
</section>
<section id="documentation-of-changes">
<span id="tutorials-upgrade-changelog"></span><h2>Documentation of Changes<a class="headerlink" href="#documentation-of-changes" title="Permalink to this heading"></a></h2>
<p>The important novelties, optimizations and changes that are available after upgrading
are documented in the change log which can be read
<a class="reference external" href="https://www.seiscomp.de/doc/base/changelog.html">online</a>.
It is recommend to read the change log before taking further actions.</p>
<p>The details can also be found locally in the file</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span><span class="nv">$SEISCOMP_ROOT</span>/share/doc/seiscomp/CHANGELOG
</pre></div>
</div>
<p>which is integrated in the <a class="reference internal" href="../changelog.html#sc-changelog"><span class="std std-ref">documentation</span></a> or accessible
from the <em>Docs</em> panel in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.</p>
<span id="tutorials-upgrade-changelog"></span><h3>Documentation of changes<a class="headerlink" href="#documentation-of-changes" title="Permalink to this heading"></a></h3>
<p>The important novelties, optimizations and changes that are available after
upgrading are documented in the Changelog which is part of this documentation
and which can also be accessed through the <em>Docs</em> panel of <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.
The installed locally installed file is
<code class="file docutils literal notranslate"><span class="pre">$SEISCOMP_ROOT/share/doc/seiscomp/CHANGELOG</span></code>
The Changelog can also be read
<a class="reference external" href="https://www.seiscomp.de/doc/base/changelog.html">online</a> but care should be
take that the version number matches your.´</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>New features are regularly advertised and described in detail on the
<a class="reference external" href="https://www.gempa.de/news/">News website of gempa GmbH</a> and on the
<span id="id3"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id256" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">24</a>]</span>.</p>
<p>New major release with the features are regularly advertised and described in
detail on the <a class="reference external" href="https://www.gempa.de/news/">News website of gempa GmbH</a> and
on the <span id="id3"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id289" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">26</a>]</span>.</p>
</div>
</section>
<section id="normal-upgrade">
<span id="tutorials-upgrade-normal"></span><h2>Normal Upgrade<a class="headerlink" href="#normal-upgrade" title="Permalink to this heading"></a></h2>
<p>The normal upgrade including upgrading the major version of SeisComP takes only
a few steps:</p>
<ol class="arabic">
<li><p><a class="reference internal" href="#tutorials-upgrade-download"><span class="std std-ref">Download</span></a> the SeisComP package.</p></li>
<li><p>Stop all SeisComP modules:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>stop
</pre></div>
</div>
</li>
<li><p>Install the new packages.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Users of external, e.g., <cite>gempa</cite> modules must ensure that these external
modules match the SeisComP release version if they depend on SeisComP
libraries.</p>
</div>
</li>
<li><p>Test the database schema version and update bindings</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
</pre></div>
</div>
<p><a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">Upgrade the database schema version</span></a> if
mismatches are reported.</p>
</li>
<li><p>After a successful upgrade, start all modules again and observe the status:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>start
seiscomp<span class="w"> </span>status<span class="w"> </span>started
</pre></div>
</div>
</li>
</ol>
</section>
<section id="upgrade-database-schema-version">
<span id="tutorials-upgrade-db"></span><h2>Upgrade database schema version<a class="headerlink" href="#upgrade-database-schema-version" title="Permalink to this heading"></a></h2>
<p>When installing a new SeisComP release with a higher major version number,
upgrading the database may be required. The database version will be tested and
the required actions will be shown when executing:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
<span id="tutorials-upgrade-db"></span><h3>Upgrade database schema version<a class="headerlink" href="#upgrade-database-schema-version" title="Permalink to this heading"></a></h3>
<p>When upgrading <cite>SeisComP</cite> to a higher major version number as set out in section
<a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a>, upgrading the database schema is typically
required, too. The database version will be tested and the required actions will
be reported when executing:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config**Special<span class="w"> </span><span class="k">case</span>:**
</pre></div>
</div>
<p>or when pressing the Update Configuration button in scconfig.
<p>or when pressing the Update Configuration button in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.
An upgrade from version SeisComP3 jakarta-2017.334 to SeisComP in version 5.1.0
will give, e.g.:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
@@ -253,13 +181,24 @@ INFO:<span class="w"> </span>checking<span class="w"> </span>DB<span class="w">
<span class="w"> </span>*<span class="w"> </span>migration<span class="w"> </span>to<span class="w"> </span>the<span class="w"> </span>current<span class="w"> </span>version<span class="w"> </span>is<span class="w"> </span>required.<span class="w"> </span>apply<span class="w"> </span>the<span class="w"> </span>following
<span class="w"> </span>scripts<span class="w"> </span><span class="k">in</span><span class="w"> </span>exactly<span class="w"> </span>the<span class="w"> </span>given<span class="w"> </span>order:
<span class="w"> </span>*<span class="w"> </span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_10_to_0_11.sql
<span class="w"> </span>*<span class="w"> </span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql
error:<span class="w"> </span>updating<span class="w"> </span>configuration<span class="w"> </span><span class="k">for</span><span class="w"> </span>scmaster<span class="w"> </span>failed
<span class="w"> </span>*<span class="w"> </span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>l
</pre></div>
</div>
<p>The shown migration scripts can be used directly as given and in the given order:</p>
<dl class="simple">
<dt><a href="#id4"><span class="problematic" id="id5">**</span></a>Special case:<a href="#id6"><span class="problematic" id="id7">**</span></a>ocalhost &lt; /home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql</dt><dd><p>error: updating configuration for scmaster failed</p>
</dd>
</dl>
<p>The shown migration scripts can be used directly as given and in the given
order but you need to first stop all modules writing to or deleting objects from
the database such as <a class="reference internal" href="../../apps/scmaster.html#scmaster"><span class="std std-ref">scmaster</span></a>, <a class="reference internal" href="../../apps/scdb.html#scdb"><span class="std std-ref">scdb</span></a>, <a class="reference internal" href="../../apps/scardac.html#scardac"><span class="std std-ref">scardac</span></a> or
<a class="reference internal" href="../../apps/scdbstrip.html#scdbstrip"><span class="std std-ref">scdbstrip</span></a> running on the same or any connected machine, e.g.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>stop<span class="w"> </span>scmaster
</pre></div>
</div>
<p><strong>Special case:</strong>
Thereafter, apply the migration according to your database:</p>
<ul>
<li><p>MySQL / MariaDB:</p>
<li><p>MySQL/MariaDB:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_10_to_0_11.sql
mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql
</pre></div>
@@ -273,31 +212,81 @@ psql<span class="w"> </span>-U<span class="w"> </span>sysop<span class="w"> </sp
</li>
</ul>
<p>Using the migration scripts provides a more user friendly way than copying the
lines of MySQL code from the changelog. In future versions we might add the option
lines of MySQL code from the changelog which was practise in past SeisComP3
versions. In future versions we might add the option
to automatically run the migrations.</p>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>Upgrading the database make take some time. Do no interrupt the process!
During this time, the <cite>SeisComP</cite> messaging system is unavailable causing a downtime of the system.</p>
During this time, the <cite>SeisComP</cite> messaging system is unavailable causing a
downtime of the system.</p>
</div>
<p>After applying the migration scripts the database should be at the correct version.
Test again with:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
</pre></div>
</div>
<p>After successfully upgrading the database continue your previous upgrade procedure.</p>
<p>After successfully upgrading the database continue your previous upgrade
procedure.</p>
</section>
<section id="seiscomp3-to-version-4">
<span id="tutorials-upgrade-v4"></span><h2>SeisComP3 to version &gt;=4<a class="headerlink" href="#seiscomp3-to-version-4" title="Permalink to this heading"></a></h2>
<p>SeisComP in version 4 has some major differences to SeisComP3 which require adjustments.
The main differences are in the <a class="reference internal" href="#sec-tutorials-upgrading-path"><span class="std std-ref">directories of the SeisComP installation</span></a>
</section>
<section id="normal-update-upgrade">
<span id="tutorials-upgrade-normal"></span><h2>Normal Update/Upgrade<a class="headerlink" href="#normal-update-upgrade" title="Permalink to this heading"></a></h2>
<p>Normal updates/upgrades of the major version of <cite>SeisComP</cite> takes only a few steps:</p>
<ol class="arabic">
<li><p>If you are tracking your <cite>SeisComP</cite> installation using <strong class="program">git</strong>
(recommended), ensure all previous changes are committed and the installation
is clean.</p></li>
<li><p>Stop all SeisComP modules:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>stop
</pre></div>
</div>
</li>
<li><p>Download and install the <cite>SeisComP</cite> package as described in section
<a class="reference internal" href="../installation.html#installation-packages"><span class="std std-ref">Installation of Packages</span></a>.</p></li>
<li><p>Understand the Changelog of the installed <cite>SeisComP</cite> as described in section
<a class="reference internal" href="#tutorials-upgrade-changelog"><span class="std std-ref">Documentation of changes</span></a>.</p></li>
<li><p>Infrequently configuration parameters require changes which
are documented in the Changelog. You may also scan your configuration for
deprecated or obsolete configuration parameters or values using
<a class="reference external" href="https://data.gempa.de/packages/Public/tools/">gempa-checkSCconfig.py</a>
provided by <span id="id8"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id147" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de.">31</a>]</span>. Apply changes accordingly.</p></li>
<li><p>The software dependencies may have changed after upgrading. Install them as
described in section <a class="reference internal" href="../installation.html#software-dependencies"><span class="std std-ref">Software Dependencies</span></a>.</p></li>
<li><p>Test the database schema version and update bindings</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
</pre></div>
</div>
<p><a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">Upgrade the database schema version</span></a> if
mismatches are reported. The mismatch reports will also give the upgrade
instructions. Repeat <em>seiscomp update-config</em> after upgrading the database
schema version.</p>
<p><strong>Background:</strong> When upgrading the major <cite>SeisComP</cite> version you
typically need to upgrade the database scheme version.</p>
</li>
<li><p>After a successful update/upgrade, start all modules again and observe the
status:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>start
seiscomp<span class="w"> </span>status<span class="w"> </span>started
</pre></div>
</div>
</li>
<li><p>If you are tracking your <cite>SeisComP</cite> installation using <strong class="program">git</strong>
(recommended), commit all changes.</p></li>
</ol>
</section>
<section id="upgrading-from-seiscomp3">
<span id="tutorials-upgrade-v4"></span><h2>Upgrading from SeisComP3<a class="headerlink" href="#upgrading-from-seiscomp3" title="Permalink to this heading"></a></h2>
<p>SeisComP in version &gt;=4 has major differences to SeisComP3 which require
adjustments. The main differences are in the
<a class="reference internal" href="#sec-tutorials-upgrading-path"><span class="std std-ref">directories of the SeisComP installation</span></a>
and the <a class="reference internal" href="#sec-tutorials-upgrading-messaging"><span class="std std-ref">messaging system</span></a>.
The changes and the required actions are explained below. They must be considered
in addition to the steps set out in section <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Upgrade</span></a>.</p>
in addition to the steps set out in section <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a>.</p>
<section id="files-and-directories">
<span id="sec-tutorials-upgrading-path"></span><h3>Files and directories<a class="headerlink" href="#files-and-directories" title="Permalink to this heading"></a></h3>
<p>With <strong>SeisComP3</strong> all the default installation typically required all modules and configurations
in the directories</p>
<p>With <strong>SeisComP3</strong> all the default installation typically required all modules
and configurations in the directories</p>
<ul class="simple">
<li><p>seiscomp3/ , typically $HOME/seiscomp3 or /opt/seiscomp3/</p></li>
<li><p>$HOME/.seiscomp3/</p></li>
@@ -419,13 +408,13 @@ new groups in the configuration of queues</p>
</pre></div>
</div>
</li>
<li><p>Set groups per queue in <a class="reference internal" href="../../apps/scmaster.html#confval-queues.-name.groups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">queues.$name.groups</span></code></a>,
<li><p><strong>Special case:</strong> Set groups per queue in <a class="reference internal" href="../../apps/scmaster.html#confval-queues.-name.groups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">queues.$name.groups</span></code></a>,
ignoring groups in <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a></p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">queues.production.groups</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">L1PICK, L1LOCATION, AMPLITUDE, PICK, LOCATION, MAGNITUDE, FOCMECH, EVENT, QC, PUBLICATION, GUI, INVENTORY, ROUTING, CONFIG, LOGGING, IMPORT_GROUP, SERVICE_REQUEST, SERVICE_PROVIDE</span>
</pre></div>
</div>
</li>
<li><p>Set groups in <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a></p>
<li><p><strong>Special case:</strong> Set groups in <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a></p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">defaultGroups</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">L1PICK, L1LOCATION, AMPLITUDE, PICK, LOCATION, MAGNITUDE, FOCMECH, EVENT, QC, PUBLICATION, GUI, INVENTORY, ROUTING, CONFIG, LOGGING, IMPORT_GROUP, SERVICE_REQUEST, SERVICE_PROVIDE</span>
</pre></div>
</div>
@@ -434,9 +423,9 @@ ignoring groups in <a class="reference internal" href="../../apps/scmaster.html#
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>When setting groups in the queues all groups configured in
<a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> will be ignored unless <cite>${defaultGroups}</cite> is used.
Add all groups from <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> to the queues to keep the
default groups.</p>
<a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> will be ignored unless <cite>${defaultGroups}</cite> is
used. Add all groups from <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> to the queues to
keep the default groups.</p>
</div>
</li>
<li><p>Add the interface name, currently only <em>dbstore</em> is supported. Example for
@@ -490,9 +479,8 @@ is <em>production</em>, e.g.</p>
</section>
<section id="seedlink">
<h3>Seedlink<a class="headerlink" href="#seedlink" title="Permalink to this heading"></a></h3>
<p>When upgrading from SeisComp3 Jakrata-2018.327 or older and using <a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a>,
consider the sections <a class="reference internal" href="#tutorials-upgrade-seedlink"><span class="std std-ref">SeedLink buffer</span></a> and
<a class="reference internal" href="#tutorials-proc-seedlink"><span class="std std-ref">SeedLink stream processor</span></a>.</p>
<p>When upgrading from SeisComp3 in version Jakrata-2018.327 or older and using
<a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a>, consider the section <a class="reference internal" href="#tutorials-upgrade-2018-327"><span class="std std-ref">Upgrading From SeisComP3 &lt;= Jakarta-2018.327</span></a>.</p>
</section>
<section id="automatic-module-check">
<h3>Automatic module check<a class="headerlink" href="#automatic-module-check" title="Permalink to this heading"></a></h3>
@@ -509,8 +497,8 @@ modules automatically during computer startup, then the startup script must be
adjusted.</p>
</section>
</section>
<section id="upgrade-from-seiscomp3-jakarta-2018-327-or-before">
<h2>Upgrade From SeisComP3 Jakarta-2018.327 or Before<a class="headerlink" href="#upgrade-from-seiscomp3-jakarta-2018-327-or-before" title="Permalink to this heading"></a></h2>
<section id="upgrading-from-seiscomp3-jakarta-2018-327">
<span id="tutorials-upgrade-2018-327"></span><h2>Upgrading From SeisComP3 &lt;= Jakarta-2018.327<a class="headerlink" href="#upgrading-from-seiscomp3-jakarta-2018-327" title="Permalink to this heading"></a></h2>
<section id="seedlink-buffer">
<span id="tutorials-upgrade-seedlink"></span><h3>SeedLink buffer<a class="headerlink" href="#seedlink-buffer" title="Permalink to this heading"></a></h3>
<p>In SeisComP3 prior to Jakarta-2020.330 two stations with the same
@@ -576,7 +564,7 @@ grep<span class="w"> </span>-A<span class="w"> </span><span class="m">2</span><s
<span class="w"> </span><span class="nv">net</span><span class="o">=</span><span class="s2">&quot;&quot;</span>
<span class="w"> </span><span class="k">while</span><span class="w"> </span><span class="nb">read</span><span class="w"> </span>a<span class="w"> </span>b<span class="w"> </span>c<span class="p">;</span><span class="w"> </span><span class="k">do</span>
<span class="w"> </span><span class="k">case</span><span class="w"> </span><span class="nv">$a</span><span class="w"> </span><span class="k">in</span>
<span class="w"> </span>--<span class="o">)</span><span class="w"> </span><span class="k">break</span><span class="p">;;</span>
<span class="w"> </span>--<span class="o">)</span><span class="w"> </span><span class="k">break</span><span class="p">;;</span>tutorials_upgrade_seedlink
<span class="w"> </span>name<span class="o">)</span><span class="w"> </span><span class="nb">eval</span><span class="w"> </span><span class="nv">sta</span><span class="o">=</span><span class="nv">$c</span><span class="p">;;</span>
<span class="w"> </span>network<span class="o">)</span><span class="w"> </span><span class="nb">eval</span><span class="w"> </span><span class="nv">net</span><span class="o">=</span><span class="nv">$c</span><span class="p">;;</span>
<span class="w"> </span><span class="k">esac</span>
@@ -625,8 +613,8 @@ was used. This means when upgrading:</p>
data is generated (<a class="reference internal" href="../../apps/seedlink.html#confval-sources.chain.channels.unpack"><code class="xref std std-confval docutils literal notranslate"><span class="pre">sources.chain.channels.unpack</span></code></a>).</p>
</div>
</section>
<section id="id4">
<h4>Background<a class="headerlink" href="#id4" title="Permalink to this heading"></a></h4>
<section id="id9">
<h4>Background<a class="headerlink" href="#id9" title="Permalink to this heading"></a></h4>
<p>A stream processor is an object defined in XML, which is used to create MiniSEED
from raw data and optionally downsample the data. What is the difference between
attaching a stream processor to station and plugin instance?</p>
@@ -681,17 +669,17 @@ LH* and VH* and the other one producing BN* and so on.</p>
<div>
<h3><a href="../../index.html">Table of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Upgrading SeisComP</a><ul>
<li><a class="reference internal" href="#">Updating/Upgrading SeisComP</a><ul>
<li><a class="reference internal" href="#background">Background</a><ul>
<li><a class="reference internal" href="#seiscomp-versions">SeisComP versions</a></li>
<li><a class="reference internal" href="#upgrade-seiscomp-on-multiple-machines">Upgrade SeisComP on multiple machines</a></li>
<li><a class="reference internal" href="#upgrade-vs-update">Upgrade vs. update</a></li>
<li><a class="reference internal" href="#upgrading-multiple-machines">Upgrading multiple machines</a></li>
<li><a class="reference internal" href="#package-download">Package download</a></li>
<li><a class="reference internal" href="#documentation-of-changes">Documentation of changes</a></li>
<li><a class="reference internal" href="#upgrade-database-schema-version">Upgrade database schema version</a></li>
</ul>
</li>
<li><a class="reference internal" href="#package-download">Package Download</a></li>
<li><a class="reference internal" href="#documentation-of-changes">Documentation of Changes</a></li>
<li><a class="reference internal" href="#normal-upgrade">Normal Upgrade</a></li>
<li><a class="reference internal" href="#upgrade-database-schema-version">Upgrade database schema version</a></li>
<li><a class="reference internal" href="#seiscomp3-to-version-4">SeisComP3 to version &gt;=4</a><ul>
<li><a class="reference internal" href="#normal-update-upgrade">Normal Update/Upgrade</a></li>
<li><a class="reference internal" href="#upgrading-from-seiscomp3">Upgrading from SeisComP3</a><ul>
<li><a class="reference internal" href="#files-and-directories">Files and directories</a></li>
<li><a class="reference internal" href="#software-dependencies">Software dependencies</a></li>
<li><a class="reference internal" href="#system-variables">System variables</a></li>
@@ -703,11 +691,11 @@ LH* and VH* and the other one producing BN* and so on.</p>
<li><a class="reference internal" href="#system-daemon">System daemon</a></li>
</ul>
</li>
<li><a class="reference internal" href="#upgrade-from-seiscomp3-jakarta-2018-327-or-before">Upgrade From SeisComP3 Jakarta-2018.327 or Before</a><ul>
<li><a class="reference internal" href="#upgrading-from-seiscomp3-jakarta-2018-327">Upgrading From SeisComP3 &lt;= Jakarta-2018.327</a><ul>
<li><a class="reference internal" href="#seedlink-buffer">SeedLink buffer</a></li>
<li><a class="reference internal" href="#seedlink-stream-processor">SeedLink stream processor</a><ul>
<li><a class="reference internal" href="#chain-plugin">chain plugin</a></li>
<li><a class="reference internal" href="#id4">Background</a></li>
<li><a class="reference internal" href="#id9">Background</a></li>
</ul>
</li>
</ul>
@@ -746,7 +734,7 @@ LH* and VH* and the other one producing BN* and so on.</p>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.