[SAC] [OSGeo] #2851: patch update on matrix

#2851: patch update on matrix
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Keywords:
---------------------------+---------------------------------------
Been a while since patch updates
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2851&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2851: patch update on matrix
---------------------------+----------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+----------------------------------------
Changes (by robe):

* status: new => closed
* resolution: => fixed

Comment:

I kept the current /etc/matrix-synapse/log.yaml.

changes in case we want to apply them

{{{

--- /etc/matrix-synapse/log.yaml 2022-09-21 15:17:55.934755168
+0000
+++ /etc/matrix-synapse/log.yaml.dpkg-new 2022-11-22
11:14:55.000000000 +0000
@@ -6,7 +6,7 @@
  # Synapse also supports structured logging for machine readable logs
which can
  # be ingested by ELK stacks. See [2] for details.
  #
-# [1]: https://docs.python.org/3.7/library/logging.config.html
#configuration-dictionary-schema
+# [1]: https://docs.python.org/3/library/logging.config.html
#configuration-dictionary-schema
  # [2]: https://matrix-
org.github.io/synapse/latest/structured_logging.html

  version: 1
@@ -62,13 +62,6 @@
          # information such as access tokens.
          level: INFO

- twisted:
- # We send the twisted logging directly to the file handler,
- # to work around https://github.com/matrix-
org/synapse/issues/3471
- # when using "buffer" logger. Use "console" to log to stderr
instead.
- handlers: [file]
- propagate: false
-
  root:
      level: INFO

Configuration file '/etc/matrix-synapse/log.yaml'

}}}
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2851#comment:1&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2851: patch update on matrix
---------------------------+----------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+----------------------------------------
Comment (by robe):

Rebooting seems to have made it not able to get a new ip.

I suspect something amiss with ufw firewall conflicting with lxd which I
have seen before, though usually not until I upgraded to ubuntu 22.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2851#comment:2&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2851: patch update on matrix
---------------------------+----------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+----------------------------------------
Comment (by robe):

Adding these rules to osgeo3 host seems to have fixed

{{{
https://discuss.linuxcontainers.org/t/lxd-bridge-doesnt-work-with-ipv4
-and-ufw-with-nftables/10034/17

sudo ufw allow in on lxdbr0
sudo ufw route allow in on lxdbr0
}}}

I'll update ansible scripts to include those
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2851#comment:3&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.