PostgreSQL 17 and Python 3

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel KC9363 appliance services                                                           < Quit >      Web:https://[2804:710:d0:5:be24:11ff:fea5:a209]Check:https://[2804:710:d0:5:be24:11ff:fea5:a209]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fea5:a209]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fea5:a209 (port 22)PostgreSQL: psql --username=postgres --host=::1PostgreSQL: psql --username=postgres --host=127.0.0.1 Keel Linux Configuration Console KC9363 appliance services                                            < Quit >    Web:https://[2804:710:d0:5:be24:11ff:fea5:a209]Check:https://[2804:710:d0:5:be24:11ff:fea5:a209]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fea5:a209]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fea5:a209 (port 22)PostgreSQL: psql --username=postgres --host=::1PostgreSQL: psql --username=postgres --host=127.0.0.1
Debian GNU/Linux 13 kc9363 tty1
kc9363 login: root
Password:
Keel Linux lnpp 19.0-trixie-amd64
IPv6 Web:  https://[2804:710:d0:5:be24:11ff:fea5:a209]
IPv6 SSH:  root@2804:710:d0:5:be24:11ff:fea5:a209
Welcome to kc9363, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 05:49:52 2026 (UTC+0000)
System load:  10.32             Memory usage:  12.3%
Processes:    41                Swap usage:    0.0%
Usage of /:   14.6% of 7.78GB   Networking not configured
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9363 7.0.14-12-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-12 (2026-08-11T11:05Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel KC9364 appliance services                                                           < Quit >      Web:https://[fd00:218:88:0:c71d:57f7:ab05:83fb]Check:https://[fd00:218:88:0:c71d:57f7:ab05:83fb]/keel-check/Webmin:     https://[fd00:218:88:0:c71d:57f7:ab05:83fb]:12321SSH/SFTP:   root@fd00:218:88:0:c71d:57f7:ab05:83fb (port 22)PostgreSQL: psql --username=postgres --host=::1Web:https://10.218.88.112Check:https://10.218.88.112/keel-check/Webmin:     https://10.218.88.112:12321SSH/SFTP:   root@10.218.88.112 (port 22)PostgreSQL: psql --username=postgres --host=127.0.0.1 Keel Linux Configuration Console KC9364 appliance services                                            < Quit >    Web:https://[fd00:218:88:0:c71d:57f7:ab05:83fb]Check:https://[fd00:218:88:0:c71d:57f7:ab05:83fb]/keel-check/Webmin:     https://[fd00:218:88:0:c71d:57f7:ab05:83fb]:12321SSH/SFTP:   root@fd00:218:88:0:c71d:57f7:ab05:83fb (port 22)PostgreSQL: psql --username=postgres --host=::1Web:https://10.218.88.112Check:https://10.218.88.112/keel-check/Webmin:     https://10.218.88.112:12321SSH/SFTP:   root@10.218.88.112 (port 22)PostgreSQL: psql --username=postgres --host=127.0.0.1
Debian GNU/Linux 13 kc9364 tty1
kc9364 login: root
Password:
Keel Linux lnpp 19.0-trixie-amd64
IPv6 Web:  https://[2804:7f0:9880:6c3:46e:6ffe:6c57:af3d]
IPv6 SSH:  root@2804:7f0:9880:6c3:46e:6ffe:6c57:af3d
IPv4 Web:  https://10.218.88.112
IPv4 SSH:  root@10.218.88.112
Welcome to kc9364, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 05:54:20 2026 (UTC+0000)
System load:  11.25             Memory usage:  10.4%
Processes:    45                Swap usage:    0.0%
Usage of /:   10.2% of 8.00GB   IP address for eth0: 10.218.88.112
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9364 7.0.14-19-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-19 (2026-09-18T07:31Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9363.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9364.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
PostgreSQL Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
PostgreSQL Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********>PostgreSQL role 'postgres' has a password, set on the console (35pgsqlpass); no DB_PASS to log in with, so the catalogue is what was checked
NOTICE:  relation "boot" already exists, skipping
40lnpp-check: the check page reads keel_check as keel-check, a row for kc9363 is in its table
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

********>PostgreSQL role 'postgres' has a password, set on the console (35pgsqlpass); no DB_PASS to log in with, so the catalogue is what was checked
NOTICE:  relation "boot" already exists, skipping
40lnpp-check: the check page reads keel_check as keel-check, a row for kc9364 is in its table
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

Simpleone node, no meshCloud simple    two nodes, failover by hand>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_simple$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 05:50:11 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 05:50:11 INF Calculated device ID(device=TCCFZ7M-NOXJH5O-OEAWZRL-PQXCVTZ-UUASNUJ-3IWUF5Y-652URZX-GEKJXQ5 log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9363)instance.fqdn: unchanged (/etc/hosts maps kc9363 to kc9363.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 8 unit(s) and 8 probe(s) of lnpp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: unchanged (disabled: etcd.service)overlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):done57%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of two (cloud simple).
Primary: the first node. It makes the mesh and invites the replica with a line you copy to it.
Replica: the second node. It joins with that line, and its data follows the primary.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

Simpleone node, no meshCloud simple    two nodes, failover by hand>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_simple$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 05:54:41 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 05:54:41 INF Calculated device ID(device=CLWIMXB-FBCR5KB-372UWNL-TFYI3UY-URPAKVU-QYITZQS-VTAK5K7-3ZABSQ2 log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9364)instance.fqdn: unchanged (/etc/hosts maps kc9364 to kc9364.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 8 unit(s) and 8 probe(s) of lnpp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: unchanged (disabled: etcd.service)overlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):done57%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of two (cloud simple).
Primary: the first node. It makes the mesh and invites the replica with a line you copy to it.
Replica: the second node. It joins with that line, and its data follows the primary.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

Keel Linux - First boot configuration
keel mesh create: making
the mesh...
Keel Linux - First boot configuration
Make the mesh
<  ok  >x
$ keel mesh createcreated the mesh: this node is fd65:ddb3:156::1/64 on wg0, WireGuard on UDP 51820keel mesh invite prints the line that joins the next nodeconfirming the new overlayconfirmed from keel mesh createthe overlay has no peer, so nothing can cross it: keel mesh create confirmed it once the routes to the gatewaysand to the operator's session were found to still leave through the uplinkwg-quick@wg0 enabled: the overlay comes back up at bootthe network change stays; the revert is cancelledmesh: this node holds the mesh's root CA, which signs the database certificates of a cloud simple pairkeel mesh: exit 0, done>Invite a node
This node invites the replica (node 2) into its mesh. Copy the line below to the replica (node 2): paste it into its Join a mesh screen, or run it there as root. It can be used once, until 2026-11-10T06:50:53Z. The line carries the service address of the pair, shown below: this node writes it as its appliance.vip, and the replica takes it from the join. Nobody types it.
Copy this line to the replica (node 2), on one line, as it is. It is a secret: it lets one node join this mesh.
keel mesh join - <<< <invite 1>
VIP: fd65:ddb3:156::ffff:1
Expires: 2026-11-10T06:50:53Z
Press Enter to go on:

Primary  the first node: makes the mesh, invitesReplica  joins the primary; its data follows it
Keel Linux - First boot configuration
Join a mesh
Paste the line that Invite a node shows on the inviting node:
keel mesh join - <<< keel2:...
The token alone (keel2:...) is accepted too. It goes to keel
on its standard input, never on a command line.
<  OK  >         <Cancel>x

<Select>           < Back >
4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fd65:ddb3:156::1/64
VIP: fd65:ddb3:156::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Take the VIP
Waiting for the replica to pair with this node (keel vip pair on the
replica). Then this node applies its description and takes the VIP.
If the replica says it paired and nothing moves here, choose Back
and Take it now.
This node: fd65:ddb3:156::1/64
Member: fd65:ddb3:156::fb34, reached
VIP: fd65:ddb3:156::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1>
== Keel Linux - First boot configuration
Take the VIP
<  ok  >x
$ keel vip promotefd65:ddb3:156::fb34: appliedthis node holds fd65:ddb3:156::ffff:1 at epoch 1, on wg0, taken by the other member of the pair; the other peersare told in the backgroundkeel vip: exit 0, done
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fd65:ddb3:156::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fd65:ddb3:156::1carried here: yesrouted to: no peer$ keel mesh statusthis node: fd65:ddb3:156::1/64 on wg0, WireGuard on UDP 51820mesh identity: 6039235ddce6ed31c56fa2eb161cfcfepublic key: <public key>peers: 1<public key>  fd65:ddb3:156::fb34/128[2804:7f0:9880:6c3:46e:6ffe:6c57:af3d]:51820  handshake 22 s agopending invites: 0etcd: not on this node (installation.mode cloud_simple; etcd runs on cloud advanced members only)vip fd65:ddb3:156::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fd65:ddb3:156::1carried here: yesrouted to: no peer$ keel database statuspair: VIP fd65:ddb3:156::ffff:1; role here primaryother member: fd65:ddb3:156::fb34 (<public key>)the primary's address: fd65:ddb3:156::1dump: none yetserver: primary (runuser -u postgres -- psql --no-psqlrc -At -F-c SELECT type, address, netmask FROM pg_hpg_hba_file_rules WHERE 'replication' = ANY(database): replication is allowed from fd65:ddb3:156::fb34/128)timeline: 1synchronous commit: on, synchronous_standby_names 'FIRST 1 (keel)'74%
>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

the overlay was tested: the inviter's answer over the overlay (invite 9700c934a52d9261) arrived at fd65:ddb3:156::fb34 on wg0, from fd65:ddb3:156::1
wg-quick@wg0 enabled: the overlay comes back up at boot
the network change stays; the revert is cancelled
joined the mesh: this node is fd65:ddb3:156::fb34/64 on wg0
peer: <public key> at fd65:ddb3:156::1, through [2804:710:d0:5:be24:11ff:fea5:a209]:51820
the mesh is up with 2 nodes; etcd starts when a third node joins, because 2 etcd members cannot lose one and keep a majority
vip: fd65:ddb3:156::ffff:1, proposed by the inviter for the pair (appliance.vip on both nodes; keel mesh status --json gives it)
Press Enter to go on: == Keel Linux - First boot configuration
< Yes >< No  >x
Becoming a replica REPLACES the data on this node with a copy of the primary at [fd65:ddb3:156::1].If this server holds any database that is not its own, keel refuses and this console asks once more, namingthem; a Yes there drops them and cannot be undone. Move anything you need elsewhere first.This screen configures THIS node only. It does not create replicas, does not change any other machine, andcannot know what the others are doing. It changes the database server and leaves the network and the TLScertificate alone.Go on and make this node a replica?
Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
$ keel vip pair fd65:ddb3:156::1fd65:ddb3:156::ffff:1 is the VIP of <public key> and<public key>, signed by bothkeel vip: exit 0, done
Keel Linux - First boot configuration
Pair with the primary
Paired. Waiting for the primary to take the VIP: its screen does it
once this node has paired.
This node: fd65:ddb3:156::fb34/64
Member: fd65:ddb3:156::1, reached
VIP: fd65:ddb3:156::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1>
== Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
/etc/keel/instance.yaml: database.server.role: replica$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yamlapply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9364)instance.fqdn: unchanged (/etc/hosts maps kc9364 to kc9364.pop.coop)database.server: make or renew the database certificate for fd65:ddb3:156::fb34 and fd65:ddb3:156::ffff:1,signed by the mesh's root CA (here, or asked of its holder over the members' channel), under the engine's TLSdirectory (etc/mysql/keel-tls or etc/postgresql/keel-tls): donedatabase.server: write /etc/sysctl.d/90-keel-database.conf: both nodes bind the VIP (mode 0644): donedatabase.server: let the server bind the VIP before it carries it (sysctl -q -w net.ipv6.ip_nonlocal_bind=1):donedatabase.server: write etc/postgresql/17/main/conf.d/99-keel-database.conf: a paired node, primary-capable, thepair's hba and TLS, the VIP fd65:ddb3:156::ffff:1 bound (mode 0644): donedatabase.server: write etc/postgresql/17/main/conf.d/98-keel-pair.conf: the pair's synchronous commit and theident map it points at (mode 0644): donedatabase.server: write etc/postgresql/17/main/keel-pg_hba.conf: the pair's authorizations, the peer'scertificate pinned (mode 0644): donedatabase.server: write etc/postgresql/17/main/keel-pg_ident.conf: the peer's certificate CN mapped to thereplication role (mode 0644): donedatabase.server: restart the server, which is the only way these take effect (systemctl restart postgresql):donedatabase.server.replication.allowed_from: ensure the replication slot of the pair exists on the primary (runuser-u postgres -- psql --no-psqlrc --tuples-only --no-align '--field-separator=  ' --set=ON_ERROR_STOP=1, 2 stastatement(s) on standard input): donedatabase.server.replication.allowed_from: ensure the replication role holds the pair's password (runuser -upostgres -- psql --no-psqlrc --tuples-only --no-align '--field-separator=     ' --set=ON_ERROR_STOP=1, 7 statemstatement(s) on standard input): donedatabase.server.replication.allowed_from: ensure the replication role may read the files that pg_rewind reads(runuser -u postgres -- psql --no-psqlrc --tuples-only --no-align '--field-separator= ' --set=ON_ERROR_STOP=1, 1045%
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fd65:ddb3:156::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fd65:ddb3:156::1carried here: norouted to: <public key>$ keel mesh statusthis node: fd65:ddb3:156::fb34/64 on wg0, WireGuard on UDP 51820mesh identity: 6039235ddce6ed31c56fa2eb161cfcfepublic key: <public key>peers: 1<public key>  fd65:ddb3:156::1/128  [2804:710:d0:5:be24:11ff:fea5:a209]:51820handshake 46 s agopending invites: 0etcd: not on this node (installation.mode cloud_simple; etcd runs on cloud advanced members only)vip fd65:ddb3:156::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fd65:ddb3:156::1carried here: norouted to: <public key>$ keel database statuspair: VIP fd65:ddb3:156::ffff:1; role here replicaother member: fd65:ddb3:156::1 (<public key>)the primary's address: fd65:ddb3:156::1dump: none yetserver: replica (runuser -u postgres -- psql --no-psqlrc -At -F-c SELECT pg_is_in_recovery(), (SELECT coucount(*) FROM pg_stat_replication WHERE client_addr IS NOT NULL), current_setting('port'): pg_is_in_recovery()is true)timeline: 172%
>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel KC9365 appliance services                                                           < Quit >      Web:https://[2804:710:d0:5:be24:11ff:fe7e:1491]Check:https://[2804:710:d0:5:be24:11ff:fe7e:1491]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fe7e:1491]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe7e:1491 (port 22)PostgreSQL: psql --username=postgres --host=::1PostgreSQL: psql --username=postgres --host=127.0.0.1 Keel Linux Configuration Console KC9365 appliance services                                            < Quit >    Web:https://[2804:710:d0:5:be24:11ff:fe7e:1491]Check:https://[2804:710:d0:5:be24:11ff:fe7e:1491]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fe7e:1491]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe7e:1491 (port 22)PostgreSQL: psql --username=postgres --host=::1PostgreSQL: psql --username=postgres --host=127.0.0.1
Debian GNU/Linux 13 kc9365 tty1
kc9365 login: root
Password:
Keel Linux lnpp 19.0-trixie-amd64
IPv6 Web:  https://[2804:710:d0:5:be24:11ff:fe7e:1491]
IPv6 SSH:  root@2804:710:d0:5:be24:11ff:fe7e:1491
Welcome to kc9365, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 05:49:55 2026 (UTC+0000)
System load:  10.32             Memory usage:  12.3%
Processes:    41                Swap usage:    0.0%
Usage of /:   14.6% of 7.78GB   Networking not configured
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9365 7.0.14-12-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-12 (2026-08-11T11:05Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel KC9366 appliance services                                                           < Quit >      Web:https://[fd00:218:88:0:fd98:50b6:3a41:f724]Check:https://[fd00:218:88:0:fd98:50b6:3a41:f724]/keel-check/Webmin:     https://[fd00:218:88:0:fd98:50b6:3a41:f724]:12321SSH/SFTP:   root@fd00:218:88:0:fd98:50b6:3a41:f724 (port 22)PostgreSQL: psql --username=postgres --host=::1Web:https://10.218.88.111Check:https://10.218.88.111/keel-check/Webmin:     https://10.218.88.111:12321SSH/SFTP:   root@10.218.88.111 (port 22)PostgreSQL: psql --username=postgres --host=127.0.0.1 Keel Linux Configuration Console KC9366 appliance services                                            < Quit >    Web:https://[fd00:218:88:0:fd98:50b6:3a41:f724]Check:https://[fd00:218:88:0:fd98:50b6:3a41:f724]/keel-check/Webmin:     https://[fd00:218:88:0:fd98:50b6:3a41:f724]:12321SSH/SFTP:   root@fd00:218:88:0:fd98:50b6:3a41:f724 (port 22)PostgreSQL: psql --username=postgres --host=::1Web:https://10.218.88.111Check:https://10.218.88.111/keel-check/Webmin:     https://10.218.88.111:12321SSH/SFTP:   root@10.218.88.111 (port 22)PostgreSQL: psql --username=postgres --host=127.0.0.1
Debian GNU/Linux 13 kc9366 tty1
kc9366 login: root
Password:
Keel Linux lnpp 19.0-trixie-amd64
IPv6 Web:  https://[2804:7f0:9880:6c3:ef5a:9caf:432a:1fda]
IPv6 SSH:  root@2804:7f0:9880:6c3:ef5a:9caf:432a:1fda
IPv4 Web:  https://10.218.88.111
IPv4 SSH:  root@10.218.88.111
Welcome to kc9366, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 05:53:44 2026 (UTC+0000)
System load:  14.25             Memory usage:  9.4%
Processes:    44                Swap usage:    0.0%
Usage of /:   10.2% of 8.00GB   IP address for eth0: 10.218.88.111
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9366 7.0.14-19-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-19 (2026-09-18T07:31Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel Linux Configuration Console  KC9367 appliance services                                                                   < Quit >           Webmin:     https://[2804:710:d0:5:be24:11ff:fe80:888f]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe80:888f (port 22)
Debian GNU/Linux 13 kc9367 tty1
kc9367 login: root
Password:
Keel Linux core 19.0-trixie-amd64
IPv6 SSH:  root@2804:710:d0:5:be24:11ff:fe80:888f
Welcome to kc9367, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 05:56:04 2026 (UTC+0000)
System load:  7.54             Memory usage:  8.9%
Processes:    29               Swap usage:    0.0%
Usage of /:   9.9% of 7.78GB   Networking not configured
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9367 7.0.14-12-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-12 (2026-08-11T11:05Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9365.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9366.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
PostgreSQL Password
Please enter new password for the 'postgres' account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9367.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

********
Keel Linux - First boot configuration
PostgreSQL Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
PostgreSQL Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Simpleone node, no meshCloud simple    two nodes, failover by handCloud simple    two nodes, failover by handCloud advanced  two nodes and a witness, failover by itself>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_advanced$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yamlapply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9367)instance.fqdn: unchanged (/etc/hosts maps kc9367 to kc9367.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 5 unit(s) and 4 probe(s) of core (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: etcd waits for its cluster: it forms at the third cloud advanced member's join, or with keel meshetcd form; nothing is started until thenoverlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):doneapply --system-only: 9 change(s), 0 failed94%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of three (cloud advanced).
Primary: the first node. It makes the mesh and invites the replica, then the witness, each with a line you copy
to it.
Replica: the second node. It joins with the first line, and its data follows the primary.
Witness: the third node, Keel Core on a third site. It joins with the second line and gives etcd its third vote.
It holds no data.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
Witness  Keel Core on a third site: a vote, no data
<Select>

********>PostgreSQL role 'postgres' has a password, set on the console (35pgsqlpass); no DB_PASS to log in with, so the catalogue is what was checked
NOTICE:  relation "boot" already exists, skipping
40lnpp-check: the check page reads keel_check as keel-check, a row for kc9365 is in its table
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

********>PostgreSQL role 'postgres' has a password, set on the console (35pgsqlpass); no DB_PASS to log in with, so the catalogue is what was checked
NOTICE:  relation "boot" already exists, skipping
40lnpp-check: the check page reads keel_check as keel-check, a row for kc9366 is in its table
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

Primary  the first node: makes the mesh, invitesWitness  Keel Core on a third site: a vote, no data
Keel Linux - First boot configuration
Join a mesh
Paste the line that Invite a node shows on the inviting node:
keel mesh join - <<< keel2:...
The token alone (keel2:...) is accepted too. It goes to keel
on its standard input, never on a command line.
<  OK  >         <Cancel>x

Simpleone node, no meshCloud simple    two nodes, failover by handCloud simple    two nodes, failover by handCloud advanced  two nodes and a witness, failover by itself>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_advanced$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 05:50:13 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 05:50:13 INF Calculated device ID(device=KDQQQ7L-3OGIDRV-L55F2F4-OK22COM-GT33JIC-C6PWBKE-IYOU42N-EG6XMQI log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9365)instance.fqdn: unchanged (/etc/hosts maps kc9365 to kc9365.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 9 unit(s) and 9 probe(s) of lnpp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: etcd waits for its cluster: it forms at the third cloud advanced member's join, or with keel meshetcd form; nothing is started until thenoverlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):56%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of three (cloud advanced).
Primary: the first node. It makes the mesh and invites the replica, then the witness, each with a line you copy
to it.
Replica: the second node. It joins with the first line, and its data follows the primary.
Witness: the third node, Keel Core on a third site. It joins with the second line and gives etcd its third vote.
It holds no data.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

Simpleone node, no meshCloud simple    two nodes, failover by handCloud simple    two nodes, failover by handCloud advanced  two nodes and a witness, failover by itself>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_advanced$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 05:54:06 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 05:54:06 INF Calculated device ID(device=RDFOYQV-W5HAM4O-UO6WTT4-KDTWMUP-6HVF62O-MEWIO6J-YTGZZNA-5MSD7AH log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9366)instance.fqdn: unchanged (/etc/hosts maps kc9366 to kc9366.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 9 unit(s) and 9 probe(s) of lnpp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: etcd waits for its cluster: it forms at the third cloud advanced member's join, or with keel meshetcd form; nothing is started until thenoverlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):56%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of three (cloud advanced).
Primary: the first node. It makes the mesh and invites the replica, then the witness, each with a line you copy
to it.
Replica: the second node. It joins with the first line, and its data follows the primary.
Witness: the third node, Keel Core on a third site. It joins with the second line and gives etcd its third vote.
It holds no data.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

<invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1>z<invite 1>z6<invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2>F<invite 2>FA<invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1>5<invite 2><invite 1>5_<invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1>uw<invite 1><invite 1>w<invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2>_P<invite 1><invite 2>P<invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2>D<invite 2>D_<invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2>>Join a mesh
Join a mesh: keel joins this node to the mesh. When the inviting node cannot be reached, keel prints a line keel mesh accept keel1a:... and waits: run that line on the inviting node, or paste it into its Paste accept line screen.
endpoint 2804:710:d0:5:be24:11ff:fe80:888f, found on eth0 (--endpoint overrides it)
confirming over the overlay
confirmed from the inviter's answer over the overlay (invite 3ded05314815de87)
the overlay was tested: the inviter's answer over the overlay (invite 3ded05314815de87) arrived at fd62:ff74:fabb::39fc on wg0, from fd62:ff74:fabb::1
wg-quick@wg0 enabled: the overlay comes back up at boot
the network change stays; the revert is cancelled
joined the mesh: this node is fd62:ff74:fabb::39fc/64 on wg0
peer: <public key> at fd62:ff74:fabb::1, through [2804:710:d0:5:be24:11ff:fe7e:1491]:51820
the mesh has 3 nodes: this node has them all as peers, and the inviter announces this node to the 1 other(s) over the overlay (one offline now learns of it at its next keel mesh sync)
etcd: this node forms with 2 other member(s)
vip: fd62:ff74:fabb::ffff:1, proposed by the inviter for the pair (appliance.vip on both nodes; keel mesh status --json gives it)
Press Enter to go on:
== Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel mesh statusthis node: fd62:ff74:fabb::39fc/64 on wg0, WireGuard on UDP 51820mesh identity: f4d608c4b79a463997f18476e2211e8bpublic key: <public key>peers: 2<public key>  fd62:ff74:fabb::1/128  [2804:710:d0:5:be24:11ff:fe7e:1491]:51820handshake 13 s ago<public key>  fd62:ff74:fabb::b2e9/128[2804:7f0:9880:6c3:ef5a:9caf:432a:1fda]:51820  handshake 1 s agopending invites: 0etcd: 3 voter(s), 0 learner(s)keel-fd62-ff74-fabb--1  fd62:ff74:fabb::1  voter  healthykeel-fd62-ff74-fabb--b2e9  fd62:ff74:fabb::b2e9  voter  healthykeel-fd62-ff74-fabb--39fc  fd62:ff74:fabb::39fc  voter  healthyleader: keel-fd62-ff74-fabb--1etcd: this member's certificate expires 2026-12-10 05:56 UTCvip: none (this node declares no appliance.vip and routes no other pair's)>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

Keel Linux - First boot configuration
keel mesh create: making
the mesh...
Keel Linux - First boot configuration
Make the mesh
<  ok  >x
$ keel mesh createcreated the mesh: this node is fd62:ff74:fabb::1/64 on wg0, WireGuard on UDP 51820keel mesh invite prints the line that joins the next nodeconfirming the new overlayconfirmed from keel mesh createthe overlay has no peer, so nothing can cross it: keel mesh create confirmed it once the routes to the gatewaysand to the operator's session were found to still leave through the uplinkwg-quick@wg0 enabled: the overlay comes back up at bootthe network change stays; the revert is cancelledetcd: this node holds the mesh's root CA; etcd forms when the third cloud advanced member joinskeel mesh: exit 0, done>Invite a node
This node invites the replica (node 2) into its mesh. Copy the line below to the replica (node 2): paste it into its Join a mesh screen, or run it there as root. It can be used once, until 2026-11-10T06:50:48Z. The line carries the service address of the pair, shown below: this node writes it as its appliance.vip, and the replica takes it from the join. Nobody types it.
Copy this line to the replica (node 2), on one line, as it is. It is a secret: it lets one node join this mesh.
keel mesh join - <<< <invite 1>
VIP: fd62:ff74:fabb::ffff:1
Expires: 2026-11-10T06:50:48Z
Press Enter to go on:

Primary  the first node: makes the mesh, invitesReplica  joins the primary; its data follows it
Keel Linux - First boot configuration
Join a mesh
Paste the line that Invite a node shows on the inviting node:
keel mesh join - <<< keel2:...
The token alone (keel2:...) is accepted too. It goes to keel
on its standard input, never on a command line.
<  OK  >         <Cancel>x

4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fd62:ff74:fabb::1/64
etcd: not_formed, voters 0
VIP: fd62:ff74:fabb::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fd62:ff74:fabb::1/64
etcd: not_formed, voters 0
VIP: fd62:ff74:fabb::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fd62:ff74:fabb::1/64
etcd: not_formed, voters 0
VIP: fd62:ff74:fabb::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0>Invite a node
This node invites the witness (node 3, Keel Core) into its mesh. Copy the line below to the witness (node 3, Keel Core): paste it into its Join a mesh screen, or run it there as root. It can be used once, until 2026-11-10T06:54:44Z. The line carries the service address of the pair, shown below: this node writes it as its appliance.vip, and the replica takes it from the join. Nobody types it.
Copy this line to the witness (node 3, Keel Core), on one line, as it is. It is a secret: it lets one node join this mesh.
keel mesh join - <<< <invite 1><invite 2><invite 1><invite 1><invite 2><invite 1>
VIP: fd62:ff74:fabb::ffff:1
Expires: 2026-11-10T06:54:44Z
Press Enter to go on:

VIP: fd62:ff74:fabb::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
< Yes >< No  >x
Becoming a replica REPLACES the data on this node with a copy of the primary at [fd62:ff74:fabb::1].If this server holds any database that is not its own, keel refuses and this console asks once more, namingthem; a Yes there drops them and cannot be undone. Move anything you need elsewhere first.This screen configures THIS node only. It does not create replicas, does not change any other machine, andcannot know what the others are doing. It changes the database server and leaves the network and the TLScertificate alone.Go on and make this node a replica?
Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
$ keel vip pair fd62:ff74:fabb::1fd62:ff74:fabb::ffff:1 is the VIP of <public key> and<public key>, signed by bothetcd: fd62:ff74:fabb::ffff:1: its pair's role is grantedkeel vip: exit 0, done
Keel Linux - First boot configuration
Pair with the primary
Paired. Waiting for the primary to take the VIP: its screen does it
once this node has paired.
This node: fd62:ff74:fabb::b2e9/64
Member: fd62:ff74:fabb::1, reached
Member: fd62:ff74:fabb::39fc, reached
etcd: formed, voters 3
VIP: fd62:ff74:fabb::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1>
== Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
/etc/keel/instance.yaml: database.server.role: replica$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yamlapply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9366)instance.fqdn: unchanged (/etc/hosts maps kc9366 to kc9366.pop.coop)database.server: make or renew the database certificate for fd62:ff74:fabb::b2e9 and fd62:ff74:fabb::ffff:1,signed by the mesh's root CA (here, or asked of its holder over the members' channel), under the engine's TLSdirectory (etc/mysql/keel-tls or etc/postgresql/keel-tls): donedatabase.server: write /etc/sysctl.d/90-keel-database.conf: both nodes bind the VIP (mode 0644): donedatabase.server: let the server bind the VIP before it carries it (sysctl -q -w net.ipv6.ip_nonlocal_bind=1):donedatabase.server: write etc/postgresql/17/main/conf.d/99-keel-database.conf: a paired node, primary-capable, thepair's hba and TLS, the VIP fd62:ff74:fabb::ffff:1 bound (mode 0644): donedatabase.server: write etc/postgresql/17/main/conf.d/98-keel-pair.conf: the pair's synchronous commit and the
ident map it points at (mode 0644): donedatabase.server: write etc/postgresql/17/main/keel-pg_hba.conf: the pair's authorizations, the peer'scertificate pinned (mode 0644): donedatabase.server: write etc/postgresql/17/main/keel-pg_ident.conf: the peer's certificate CN mapped to thereplication role (mode 0644): donedatabase.server: restart the server, which is the only way these take effect (systemctl restart postgresql):donedatabase.server.replication.allowed_from: ensure the replication slot of the pair exists on the primary (runuser-u postgres -- psql --no-psqlrc --tuples-only --no-align '--field-separator=  ' --set=ON_ERROR_STOP=1, 2 stastatement(s) on standard input): donedatabase.server.replication.allowed_from: ensure the replication role holds the pair's password (runuser -upostgres -- psql --no-psqlrc --tuples-only --no-align '--field-separator=     ' --set=ON_ERROR_STOP=1, 7 statemstatement(s) on standard input): donedatabase.server.replication.allowed_from: ensure the replication role may read the files that pg_rewind reads(runuser -u postgres -- psql --no-psqlrc --tuples-only --no-align '--field-separator= ' --set=ON_ERROR_STOP=1, 1050%
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fd62:ff74:fabb::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fd62:ff74:fabb::1carried here: norouted to: <public key>$ keel mesh statusthis node: fd62:ff74:fabb::b2e9/64 on wg0, WireGuard on UDP 51820mesh identity: f4d608c4b79a463997f18476e2211e8bpublic key: <public key>peers: 2<public key>  fd62:ff74:fabb::1/128  [2804:710:d0:5:be24:11ff:fe7e:1491]:51820handshake 41 s ago<public key>  fd62:ff74:fabb::39fc/128[2804:710:d0:5:be24:11ff:fe80:888f]:51820  handshake 34 s agopending invites: 0etcd: 3 voter(s), 0 learner(s)keel-fd62-ff74-fabb--1  fd62:ff74:fabb::1  voter  healthykeel-fd62-ff74-fabb--b2e9  fd62:ff74:fabb::b2e9  voter  healthykeel-fd62-ff74-fabb--39fc  fd62:ff74:fabb::39fc  voter  healthyleader: keel-fd62-ff74-fabb--1etcd: this member's certificate expires 2026-12-10 05:54 UTCvip fd62:ff74:fabb::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fd62:ff74:fabb::1carried here: norouted to: <public key>$ keel database statuspair: VIP fd62:ff74:fabb::ffff:1; role here replica61%
>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the witness (node 3, Keel Core) to join with the line,
checked every 5 s. Back gives a menu: Paste accept line, when the
join printed one (keel mesh accept keel1a:...), or the line again.
This node: fd62:ff74:fabb::1/64
Member: fd62:ff74:fabb::b2e9, reached
etcd: not_formed, voters 0
VIP: fd62:ff74:fabb::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0>
== Keel Linux - First boot configuration
Take the VIP
Waiting for the replica to pair with this node (keel vip pair on the
replica). Then this node applies its description and takes the VIP.
If the replica says it paired and nothing moves here, choose Back
and Take it now.
This node: fd62:ff74:fabb::1/64
Member: fd62:ff74:fabb::b2e9, reached
Member: fd62:ff74:fabb::39fc, reached
e
Vx                                5
<Select>           < Back >x
4             3                         2     >
== Keel Linux - First boot configuration
Take the VIP
<  ok  >x
$ keel vip promotethis node holds fd62:ff74:fabb::ffff:1 at epoch 1, by etcd's lease 7665022954121996616the peers are told in the backgroundvip fd62:ff74:fabb::ffff:1: fd62:ff74:fabb::39fc: appliedvip fd62:ff74:fabb::ffff:1: fd62:ff74:fabb::b2e9: appliedkeel vip: exit 0, done
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fd62:ff74:fabb::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fd62:ff74:fabb::1etcd lease 7665022954121996616carried here: yesrouted to: no peer$ keel mesh statusthis node: fd62:ff74:fabb::1/64 on wg0, WireGuard on UDP 51820mesh identity: f4d608c4b79a463997f18476e2211e8bpublic key: <public key>peers: 2<public key>  fd62:ff74:fabb::b2e9/128[2804:7f0:9880:6c3:ef5a:9caf:432a:1fda]:51820  handshake 25 s ago<public key>  fd62:ff74:fabb::39fc/128[2804:710:d0:5:be24:11ff:fe80:888f]:51820  handshake 30 s agopending invites: 0etcd: 3 voter(s), 0 learner(s)keel-fd62-ff74-fabb--1  fd62:ff74:fabb::1  voter  healthykeel-fd62-ff74-fabb--b2e9  fd62:ff74:fabb::b2e9  voter  healthykeel-fd62-ff74-fabb--39fc  fd62:ff74:fabb::39fc  voter  healthyleader: keel-fd62-ff74-fabb--1etcd: this member's certificate expires 2026-12-10 05:50 UTCvip fd62:ff74:fabb::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fd62:ff74:fabb::1etcd lease 7665022954121996616carried here: yesrouted to: no peer57%>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x