deploy: 643c0c50c1
This commit is contained in:
erikjohnston
parent
6a2b9facb0
commit
fe73cc6f5a
|
|
@ -1613,6 +1613,39 @@ worker for application service traffic, <strong>it must be stopped</strong> when
|
|||
without any risk of reusing transaction IDs.</p>
|
||||
<p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly,
|
||||
deployments where no applciation services are in use can be upgraded as normal.</p>
|
||||
<details>
|
||||
<summary><b>Recovering from an incorrect upgrade</b></summary>
|
||||
<p>If the database schema is upgraded <em>without</em> stopping the worker responsible
|
||||
for AS traffic, then the following error may be given when attempting to start
|
||||
a Synapse worker or master process:</p>
|
||||
<pre><code>**********************************************************************************
|
||||
Error during initialisation:
|
||||
|
||||
Postgres sequence 'application_services_txn_id_seq' is inconsistent with associated
|
||||
table 'application_services_txns'. This can happen if Synapse has been downgraded and
|
||||
then upgraded again, or due to a bad migration.
|
||||
|
||||
To fix this error, shut down Synapse (including any and all workers)
|
||||
and run the following SQL:
|
||||
|
||||
SELECT setval('application_services_txn_id_seq', (
|
||||
SELECT GREATEST(MAX(txn_id), 0) FROM application_services_txns
|
||||
));
|
||||
|
||||
See docs/postgres.md for more information.
|
||||
|
||||
There may be more information in the logs.
|
||||
**********************************************************************************
|
||||
</code></pre>
|
||||
<p>This error may also be seen if Synapse is <em>downgraded</em> to an earlier version,
|
||||
and then upgraded again to v1.57.0 or later.</p>
|
||||
<p>In either case:</p>
|
||||
<ol>
|
||||
<li>Ensure that the worker responsible for AS traffic is stopped.</li>
|
||||
<li>Run the SQL command given in the error message via <code>psql</code>.</li>
|
||||
</ol>
|
||||
<p>Synapse should then start correctly.</p>
|
||||
</details>
|
||||
<h1 id="upgrading-to-v1560"><a class="header" href="#upgrading-to-v1560">Upgrading to v1.56.0</a></h1>
|
||||
<h2 id="open-registration-without-verification-is-now-disabled-by-default"><a class="header" href="#open-registration-without-verification-is-now-disabled-by-default">Open registration without verification is now disabled by default</a></h2>
|
||||
<p>Synapse will refuse to start if registration is enabled without email, captcha, or token-based verification unless the new config
|
||||
|
|
@ -1636,7 +1669,7 @@ for more information and instructions on how to fix a database with incorrect va
|
|||
<a href="https://packaging.python.org/en/latest/specifications/entry-points/">entry point</a>
|
||||
and no longer exists at the root of Synapse's source tree. If you wish to use
|
||||
<code>synctl</code> to manage your homeserver, you should invoke <code>synctl</code> directly, e.g.
|
||||
<code>synctl start</code> instead of <code>./synctl start</code> or <code>/path/to/synctl start</code>. </p>
|
||||
<code>synctl start</code> instead of <code>./synctl start</code> or <code>/path/to/synctl start</code>.</p>
|
||||
<p>You will need to ensure <code>synctl</code> is on your <code>PATH</code>.</p>
|
||||
<ul>
|
||||
<li>This is automatically the case when using
|
||||
|
|
@ -1678,7 +1711,7 @@ feature has been stabilised and moved from:</p>
|
|||
<p>Formerly, entries in the cache were not evicted regardless of whether they were accessed after storing.
|
||||
This behavior has now changed. By default entries in the cache are now evicted after 30m of not being accessed.
|
||||
To change the default behavior, go to the <code>caches</code> section of the config and change the <code>expire_caches</code> and
|
||||
<code>cache_entry_ttl</code> flags as necessary. Please note that these flags replace the <code>expiry_time</code> flag in the config.<br />
|
||||
<code>cache_entry_ttl</code> flags as necessary. Please note that these flags replace the <code>expiry_time</code> flag in the config.
|
||||
The <code>expiry_time</code> flag will still continue to work, but it has been deprecated and will be removed in the future.</p>
|
||||
<h2 id="deprecation-of-capability-orgmatrixmsc3283"><a class="header" href="#deprecation-of-capability-orgmatrixmsc3283">Deprecation of <code>capability</code> <code>org.matrix.msc3283.*</code></a></h2>
|
||||
<p>The <code>capabilities</code> of MSC3283 from the REST API <code>/_matrix/client/r0/capabilities</code>
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
|
|
@ -233,6 +233,39 @@ worker for application service traffic, <strong>it must be stopped</strong> when
|
|||
without any risk of reusing transaction IDs.</p>
|
||||
<p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly,
|
||||
deployments where no applciation services are in use can be upgraded as normal.</p>
|
||||
<details>
|
||||
<summary><b>Recovering from an incorrect upgrade</b></summary>
|
||||
<p>If the database schema is upgraded <em>without</em> stopping the worker responsible
|
||||
for AS traffic, then the following error may be given when attempting to start
|
||||
a Synapse worker or master process:</p>
|
||||
<pre><code>**********************************************************************************
|
||||
Error during initialisation:
|
||||
|
||||
Postgres sequence 'application_services_txn_id_seq' is inconsistent with associated
|
||||
table 'application_services_txns'. This can happen if Synapse has been downgraded and
|
||||
then upgraded again, or due to a bad migration.
|
||||
|
||||
To fix this error, shut down Synapse (including any and all workers)
|
||||
and run the following SQL:
|
||||
|
||||
SELECT setval('application_services_txn_id_seq', (
|
||||
SELECT GREATEST(MAX(txn_id), 0) FROM application_services_txns
|
||||
));
|
||||
|
||||
See docs/postgres.md for more information.
|
||||
|
||||
There may be more information in the logs.
|
||||
**********************************************************************************
|
||||
</code></pre>
|
||||
<p>This error may also be seen if Synapse is <em>downgraded</em> to an earlier version,
|
||||
and then upgraded again to v1.57.0 or later.</p>
|
||||
<p>In either case:</p>
|
||||
<ol>
|
||||
<li>Ensure that the worker responsible for AS traffic is stopped.</li>
|
||||
<li>Run the SQL command given in the error message via <code>psql</code>.</li>
|
||||
</ol>
|
||||
<p>Synapse should then start correctly.</p>
|
||||
</details>
|
||||
<h1 id="upgrading-to-v1560"><a class="header" href="#upgrading-to-v1560">Upgrading to v1.56.0</a></h1>
|
||||
<h2 id="open-registration-without-verification-is-now-disabled-by-default"><a class="header" href="#open-registration-without-verification-is-now-disabled-by-default">Open registration without verification is now disabled by default</a></h2>
|
||||
<p>Synapse will refuse to start if registration is enabled without email, captcha, or token-based verification unless the new config
|
||||
|
|
@ -256,7 +289,7 @@ for more information and instructions on how to fix a database with incorrect va
|
|||
<a href="https://packaging.python.org/en/latest/specifications/entry-points/">entry point</a>
|
||||
and no longer exists at the root of Synapse's source tree. If you wish to use
|
||||
<code>synctl</code> to manage your homeserver, you should invoke <code>synctl</code> directly, e.g.
|
||||
<code>synctl start</code> instead of <code>./synctl start</code> or <code>/path/to/synctl start</code>. </p>
|
||||
<code>synctl start</code> instead of <code>./synctl start</code> or <code>/path/to/synctl start</code>.</p>
|
||||
<p>You will need to ensure <code>synctl</code> is on your <code>PATH</code>.</p>
|
||||
<ul>
|
||||
<li>This is automatically the case when using
|
||||
|
|
@ -298,7 +331,7 @@ feature has been stabilised and moved from:</p>
|
|||
<p>Formerly, entries in the cache were not evicted regardless of whether they were accessed after storing.
|
||||
This behavior has now changed. By default entries in the cache are now evicted after 30m of not being accessed.
|
||||
To change the default behavior, go to the <code>caches</code> section of the config and change the <code>expire_caches</code> and
|
||||
<code>cache_entry_ttl</code> flags as necessary. Please note that these flags replace the <code>expiry_time</code> flag in the config.<br />
|
||||
<code>cache_entry_ttl</code> flags as necessary. Please note that these flags replace the <code>expiry_time</code> flag in the config.
|
||||
The <code>expiry_time</code> flag will still continue to work, but it has been deprecated and will be removed in the future.</p>
|
||||
<h2 id="deprecation-of-capability-orgmatrixmsc3283"><a class="header" href="#deprecation-of-capability-orgmatrixmsc3283">Deprecation of <code>capability</code> <code>org.matrix.msc3283.*</code></a></h2>
|
||||
<p>The <code>capabilities</code> of MSC3283 from the REST API <code>/_matrix/client/r0/capabilities</code>
|
||||
|
|
|
|||
Loading…
Reference in New Issue