container-test-run-service-postgresql
checks.aarch64-linux.postgresql
· build #1234
· raw
1build01: building bwpj1wifva5pnjp8xbll8j8hfk3p1yr9-container-test-run-service-postgresql.drv2Machine state will be reset. To keep it, pass --keep-machine-state3start all VLans4(finished: start all VLans, in 0.01 seconds)5Initializing machine ID from random generator.6Test will time out and terminate in 3600.0 seconds7run the VM test script8additionally exposed symbols:9 machine,10 vlan1,11 start_all, test_script, machines, machines_qemu, machines_nspawn, vlans, driver, log, os, create_machine, subtest, run_tests, join_all, retry, serial_stdout_off, serial_stdout_on, polling_condition, BaseMachine, QemuMachine, NspawnMachine, t, debug, dump_machine_ssh12start all VMs13machine: systemd-nspawn running (pid 51)14machine: Waiting for journal at /build/vm-state-machine/var/log/journal...15(finished: start all VMs, in 0.00 seconds)16machine: waiting for unit postgresql17nixos-nspawn(machine): TAP vde-tap1 not found; container will be isolated from VDE18nixos-nspawn(machine): A common reason for this is that /dev/net is not available in the Nix sandbox. Try adding /dev/net to extra-sandbox-paths.19Note: in a future version of systemd-nspawn the default set of permitted socket address families will be restricted to AF_INET, AF_INET6 and AF_UNIX. Use --restrict-address-families= to configure the set of permitted socket address families, or set RestrictAddressFamilies= in a .nspawn file.20░ Spawning container machine on /build/vm-state-machine.21machine # No journal files were found.22machine # No journal boot entry found for the specified boot (+0).23machine # No journal files were found.24machine # No journal boot entry found for the specified boot (+0).25machine # No journal boot entry found for the specified boot (+0).26machine # [902103.837628] machine systemd-journald[73]: Journal started27machine # [902103.837686] machine systemd-journald[73]: Runtime Journal (/run/log/journal/1b7020254d5841cb944038b9854414c5) is 8M, max 2.5G, 2.4G free.28machine # [902103.840152] machine systemd[1]: Finished Apply Kernel Variables.29machine # [902103.851743] machine systemd[1]: Finished Create Static Device Nodes in /dev gracefully.30machine # [902103.864614] machine systemd[1]: Starting Flush Journal to Persistent Storage...31machine # [902103.865388] machine systemd[1]: Starting Network Name Resolution...32machine # [902103.866018] machine systemd[1]: Starting Create Static Device Nodes in /dev...33machine # [902103.874777] machine systemd-journald[73]: Time spent on flushing to /var/log/journal/1b7020254d5841cb944038b9854414c5 is 1.143ms for 7 entries.34machine # [902103.874777] machine systemd-journald[73]: System Journal (/var/log/journal/1b7020254d5841cb944038b9854414c5) is 8M, max 4G, 3.9G free.35machine # [902103.888046] machine systemd[1]: Finished Create Static Device Nodes in /dev.36machine # [902103.888563] machine systemd[1]: Reached target Preparation for Local File Systems.37machine # [902103.888671] machine systemd[1]: Reached target Local File Systems.38machine # [902103.889374] machine systemd[1]: Listening on Boot Loader Control Service Socket.39machine # [902103.889422] machine systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container40machine # [902103.890315] machine systemd[1]: Starting Save Transient machine-id to Disk...41machine # [902103.890348] machine systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys42machine # [902104.004415] machine systemd[1]: Finished Firewall.43machine # [902104.005013] machine systemd[1]: Reached target Preparation for Network.44machine # [902104.005307] machine systemd[1]: Listening on Network Management Resolve Hook Socket.45machine # [902104.006717] machine systemd[1]: Starting Network Management...46machine # [902104.650849] machine systemd-networkd[176]: Failed to increase receive buffer size for general netlink socket, ignoring: Operation not permitted47machine # [902104.650937] machine systemd-networkd[176]: Failed to increase receive buffer size for nftables netlink socket, ignoring: Operation not permitted48machine # [902104.659799] machine systemd-networkd[176]: /etc/systemd/network/99-ethernet-default-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.49machine # [902104.659956] machine systemd-networkd[176]: /etc/systemd/network/99-wireless-client-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.50machine # [902104.660143] machine systemd-networkd[176]: lo: Link UP51machine # [902104.660145] machine systemd-networkd[176]: lo: Gained carrier52machine # [902104.660319] machine systemd-networkd[176]: eth1: Configuring with /etc/systemd/network/40-eth1.network.53machine # [902104.660997] machine systemd-networkd[176]: eth1: Link UP54machine # [902104.661098] machine systemd[1]: Started Network Management.55machine # [902104.661204] machine systemd-networkd[176]: eth1: Gained carrier56machine # [902104.662484] machine systemd[1]: Starting Enable Persistent Storage in systemd-networkd...57machine # [902104.777440] machine systemd[1]: Finished Flush Journal to Persistent Storage.58machine # [902104.779249] machine systemd[1]: Starting Create System Files and Directories...59machine # [902104.781584] machine systemd[1]: Finished Enable Persistent Storage in systemd-networkd.60machine # [902104.828875] machine systemd-tmpfiles[182]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted61machine # [902104.829068] machine systemd-tmpfiles[182]: fchmod() of /var/log/journal failed: Operation not permitted62machine # [902104.829192] machine systemd-tmpfiles[182]: fchmod() of /var/log/journal/1b7020254d5841cb944038b9854414c5 failed: Operation not permitted63machine # [902104.829379] machine systemd-tmpfiles[182]: fchmod() of /run/log/journal failed: Operation not permitted64machine # [902104.843507] machine systemd[1]: Finished Create System Files and Directories.65machine # [902104.857973] machine systemd[1]: Starting Rebuild Journal Catalog...66machine # [902104.858968] machine systemd[1]: Starting Record System Boot/Shutdown in UTMP...67machine # [902104.890290] machine systemd-resolved[104]: Positive Trust Anchors:68machine # [902104.890308] machine systemd-resolved[104]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d69machine # [902104.890312] machine systemd-resolved[104]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b1670machine # [902104.890348] machine systemd-resolved[104]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test71machine # [902104.891145] machine systemd-resolved[104]: Using system hostname 'machine'.72machine # [902104.892738] machine systemd[1]: Started Network Name Resolution.73machine # [902104.892837] machine systemd[1]: Reached target Network.74machine # [902104.927369] machine systemd[1]: Finished Record System Boot/Shutdown in UTMP.75machine # [902104.938133] machine systemd[1]: Finished Rebuild Journal Catalog.76machine # [902104.939461] machine systemd[1]: Starting Update is Completed...77machine # [902104.951907] machine systemd[1]: Finished Update is Completed.78machine # [902104.952121] machine systemd[1]: Reached target System Initialization.79machine # [902104.952216] machine systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container80machine # [902104.952260] machine systemd[1]: Started Daily Cleanup of Temporary Directories.81machine # [902104.952282] machine systemd[1]: Reached target Timer Units.82machine # [902104.952418] machine systemd[1]: Listening on D-Bus System Message Bus Socket.83machine # [902104.952557] machine systemd[1]: Listening on Nix Daemon Socket.84machine # [902104.952662] machine systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.85machine # [902104.952684] machine systemd[1]: Reached target Socket Units.86machine # [902104.952721] machine systemd[1]: Reached target Basic System.87machine # [902104.954006] machine systemd[1]: Starting Import lastlog data into lastlog2 database...88machine # [902104.955227] machine systemd[1]: Starting Name Service Cache Daemon (nsncd)...89machine # [902104.956616] machine systemd[1]: Starting PostgreSQL Server...90machine # [902104.958210] machine systemd[1]: Starting D-Bus System Message Bus...91machine # [902104.975514] machine systemd[1]: Finished Import lastlog data into lastlog2 database.92machine # [902106.114243] machine nsncd[192]: Nov 13 16:23:30.065 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"93machine # [902105.115266] machine systemd[1]: Started Name Service Cache Daemon (nsncd).94machine # [902105.115367] machine systemd[1]: Reached target Host and Network Name Lookups.95machine # [902105.115459] machine systemd[1]: Reached target User and Group Name Lookups.96machine # [902106.113708] machine systemd[1]: Starting User Login Management...97machine # [902106.115217] machine systemd[1]: Starting Permit User Sessions...98machine # [902106.160591] machine systemd[1]: Finished Permit User Sessions.99machine # [902106.161901] machine systemd[1]: Started Console Getty.100machine # [902106.161957] machine systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0101machine # [902106.161985] machine systemd[1]: Reached target Login Prompts.102machine # [902106.237562] machine dbus-broker-launch[194]: Looking up NSS user entry for 'systemd-timesync'...103machine # [902106.238590] machine dbus-broker-launch[194]: NSS returned no entry for 'systemd-timesync'104machine # [902106.238590] machine dbus-broker-launch[194]: Invalid user-name in /nix/store/qx5zrkhli1458iznk70900l58rd7zndq-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"105machine # [902106.239315] machine systemd[1]: Started D-Bus System Message Bus.106machine # [902106.248105] machine dbus-broker-launch[194]: Ready107machine # [902106.336155] machine systemd-networkd[176]: eth1: Gained IPv6LL108machine # [902106.512225] machine postgresql-pre-start[224]: The files belonging to this database system will be owned by user "postgres".109machine # [902106.512225] machine postgresql-pre-start[224]: This user must also own the server process.110machine # [902106.512578] machine postgresql-pre-start[224]: The database cluster will be initialized with locale "en_US.UTF-8".111machine # [902106.512578] machine postgresql-pre-start[224]: The default database encoding has accordingly been set to "UTF8".112machine # [902106.512578] machine postgresql-pre-start[224]: The default text search configuration will be set to "english".113machine # [902106.512578] machine postgresql-pre-start[224]: Data page checksums are enabled.114machine # [902106.512578] machine postgresql-pre-start[224]: fixing permissions on existing directory /var/lib/postgresql/18 ... ok115machine # [902106.906554] machine systemd-logind[212]: New seat seat0.116machine # [902106.906973] machine systemd[1]: Started User Login Management.117machine # [902106.909296] machine systemd[1]: Starting linger-users.service...118machine # [902106.957417] machine systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available119machine # [902106.957484] machine systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available120machine # [902106.957520] machine systemd[1]: linger-users.service: Deactivated successfully.121machine # [902106.957790] machine systemd[1]: Finished linger-users.service.122machine # [902107.920520] machine postgresql-pre-start[224]: creating subdirectories ... ok123machine # [902107.921162] machine postgresql-pre-start[224]: selecting dynamic shared memory implementation ... posix124machine # [902107.949418] machine postgresql-pre-start[224]: selecting default "max_connections" ... 100125machine # [902107.982449] machine postgresql-pre-start[224]: selecting default "shared_buffers" ... 128MB126machine # [902108.432227] machine postgresql-pre-start[224]: selecting default time zone ... UTC127machine # [902108.432227] machine postgresql-pre-start[224]: creating configuration files ... ok128machine # [902108.804842] machine postgresql-pre-start[224]: running bootstrap script ... ok129machine # [902110.041726] machine postgresql-pre-start[224]: performing post-bootstrap initialization ... ok130machine: still waiting for container 'machine' to reach ready state...131machine # [902111.899759] machine postgresql-pre-start[224]: syncing data to disk ... ok132machine # [902111.899759] machine postgresql-pre-start[224]: initdb: warning: enabling "trust" authentication for local connections133machine # [902111.899759] machine postgresql-pre-start[224]: initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.134machine # [902111.899759] machine postgresql-pre-start[224]: Success. You can now start the database server using:135machine # [902111.899759] machine postgresql-pre-start[224]: pg_ctl -D /var/lib/postgresql/18 -l logfile start136machine # [902114.132226] machine postgres[239]: [239] LOG: starting PostgreSQL 18.6 on aarch64-unknown-linux-gnu, compiled by clang version 21.1.8, 64-bit137machine # [902114.135373] machine postgres[239]: [239] LOG: listening on IPv6 address "::1", port 5432138machine # [902114.135373] machine postgres[239]: [239] LOG: listening on IPv4 address "127.0.0.1", port 5432139machine # [902114.327709] machine postgres[239]: [239] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432"140machine # [902114.974220] machine postgres[249]: [249] LOG: database system was shut down at 2026-11-13 16:23:34 GMT141machine # [902115.738786] machine postgres[239]: [239] LOG: database system is ready to accept connections142machine # [902117.693556] machine postgresql-post-start[262]: CREATE ROLE143machine # [902119.724346] machine postgresql-post-start[267]: CREATE DATABASE144machine # [902119.731259] machine systemd[1]: Started PostgreSQL Server.145machine # [902119.733100] machine systemd[1]: Starting PostgreSQL Setup Scripts...146machine: still waiting for container 'machine' to reach ready state...147machine # [902120.484449] machine systemd[1]: Finished PostgreSQL Setup Scripts.148machine # [902120.485311] machine systemd[1]: Reached target PostgreSQL.149machine # [902120.485605] machine systemd[1]: Reached target Multi-User System.150machine: still waiting for container 'machine' to reach ready state...151machine: still waiting for container 'machine' to reach ready state...152machine: still waiting for container 'machine' to reach ready state...153machine: still waiting for container 'machine' to reach ready state...154machine: still waiting for container 'machine' to reach ready state...155machine: still waiting for container 'machine' to reach ready state...156machine: still waiting for container 'machine' to reach ready state...157machine # [902193.960894] machine systemd[1]: systemd-machine-id-commit.service: start operation timed out. Terminating.158machine: still waiting for container 'machine' to reach ready state...159machine: still waiting for container 'machine' to reach ready state...160machine: still waiting for container 'machine' to reach ready state...161machine: still waiting for container 'machine' to reach ready state...162machine: still waiting for container 'machine' to reach ready state...163machine: still waiting for container 'machine' to reach ready state...164machine: still waiting for container 'machine' to reach ready state...165machine: still waiting for container 'machine' to reach ready state...166machine: still waiting for container 'machine' to reach ready state...167machine # [902284.210912] machine systemd[1]: systemd-machine-id-commit.service: State 'stop-sigterm' timed out. Killing.168machine # [902284.211012] machine systemd[1]: systemd-machine-id-commit.service: Killing process 120 (systemd-machine) with signal SIGKILL.169machine # [902284.211063] machine systemd[1]: systemd-machine-id-commit.service: Failed to read pids.max for control group /system.slice/systemd-machine-id-commit.service, ignoring: No data available170machine: still waiting for container 'machine' to reach ready state...171machine: still waiting for container 'machine' to reach ready state...172machine: still waiting for container 'machine' to reach ready state...173machine: still waiting for container 'machine' to reach ready state...174machine: still waiting for container 'machine' to reach ready state...175machine: still waiting for container 'machine' to reach ready state...176machine: still waiting for container 'machine' to reach ready state...177machine: still waiting for container 'machine' to reach ready state...178machine: still waiting for container 'machine' to reach ready state...179machine # [902374.210983] machine systemd[1]: systemd-machine-id-commit.service: Processes still around after SIGKILL. Ignoring.180machine: still waiting for container 'machine' to reach ready state...181machine: still waiting for container 'machine' to reach ready state...182machine: still waiting for container 'machine' to reach ready state...183machine: still waiting for container 'machine' to reach ready state...184machine # [902415.073560] machine postgres[247]: [247] LOG: checkpoint starting: time185machine: still waiting for container 'machine' to reach ready state...186machine: still waiting for container 'machine' to reach ready state...187machine: still waiting for container 'machine' to reach ready state...188machine: still waiting for container 'machine' to reach ready state...189machine: still waiting for container 'machine' to reach ready state...190machine # [902464.460891] machine systemd[1]: systemd-machine-id-commit.service: State 'final-sigterm' timed out. Killing.191machine # [902464.460972] machine systemd[1]: systemd-machine-id-commit.service: Killing process 120 (systemd-machine) with signal SIGKILL.192machine # [902464.461016] machine systemd[1]: systemd-machine-id-commit.service: Failed to read pids.max for control group /system.slice/systemd-machine-id-commit.service, ignoring: No data available193machine: still waiting for container 'machine' to reach ready state...194machine: still waiting for container 'machine' to reach ready state...195machine: still waiting for container 'machine' to reach ready state...196machine: still waiting for container 'machine' to reach ready state...197machine: still waiting for container 'machine' to reach ready state...198machine: still waiting for container 'machine' to reach ready state...199machine: still waiting for container 'machine' to reach ready state...200machine: still waiting for container 'machine' to reach ready state...201machine: still waiting for container 'machine' to reach ready state...202machine: (finished: waiting for unit postgresql, in 453.28 seconds)203machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -c 'CREATE TABLE test (id serial PRIMARY KEY);' test204machine # [902554.461043] machine systemd[1]: systemd-machine-id-commit.service: Processes still around after final SIGKILL. Entering failed mode.205machine # [902554.461070] machine systemd[1]: systemd-machine-id-commit.service: Failed with result 'timeout'.206machine # [902554.461272] machine systemd[1]: systemd-machine-id-commit.service: Unit process 120 (systemd-machine) remains running after unit stopped.207machine # [902554.461786] machine systemd[1]: Failed to start Save Transient machine-id to Disk.208machine # [902554.462536] machine systemd[1]: Startup finished in 7min 32.087s.209machine # [902554.462682] machine systemd[1]: systemd-machine-id-commit.service: Consumed 1.329s CPU time over 7min 30.571s wall clock time.210machine # [902554.628571] machine runuser[290]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)211machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -c 'CREATE TABLE test (id serial PRIMARY KEY);' test, in 0.90 seconds)212machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'INSERT INTO test DEFAULT VALUES;'213machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'INSERT INTO test DEFAULT VALUES;', in 0.03 seconds)214machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'SELECT * FROM test;'215machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'SELECT * FROM test;', in 0.02 seconds)216machine: must succeed: install -d -m 0755 /var/backup/postgres/test217machine: (finished: must succeed: install -d -m 0755 /var/backup/postgres/test, in 0.01 seconds)218machine: must succeed: install -m 0644 /dev/null /var/backup/postgres/test/pg-dump219machine: (finished: must succeed: install -m 0644 /dev/null /var/backup/postgres/test/pg-dump, in 0.01 seconds)220machine: must succeed: pre-backup-test221machine: (finished: must succeed: pre-backup-test, in 0.09 seconds)222machine: must succeed: stat -c '%a %U %G' /var/backup/postgres223machine: (finished: must succeed: stat -c '%a %U %G' /var/backup/postgres, in 0.01 seconds)224machine: must succeed: stat -c '%a %U %G' /var/backup/postgres/test225machine: (finished: must succeed: stat -c '%a %U %G' /var/backup/postgres/test, in 0.01 seconds)226machine: must succeed: stat -c '%a %U %G' /var/backup/postgres/test/pg-dump227machine: (finished: must succeed: stat -c '%a %U %G' /var/backup/postgres/test/pg-dump, in 0.01 seconds)228machine: must fail: runuser -u nobody -- cat /var/backup/postgres/test/pg-dump229cat: /var/backup/postgres/test/pg-dump: Permission denied230machine: (finished: must fail: runuser -u nobody -- cat /var/backup/postgres/test/pg-dump, in 0.01 seconds)231machine: must succeed: chmod 0700 /var/backup232machine: (finished: must succeed: chmod 0700 /var/backup, in 0.01 seconds)233machine: must fail: runuser -u postgres -- cat /var/backup/postgres/test/pg-dump234cat: /var/backup/postgres/test/pg-dump: Permission denied235machine: (finished: must fail: runuser -u postgres -- cat /var/backup/postgres/test/pg-dump, in 0.01 seconds)236machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'INSERT INTO test DEFAULT VALUES;'237machine # [902555.513651] machine runuser[290]: pam_unix(runuser:session): session closed for user postgres238machine # [902555.528280] machine runuser[293]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)239machine # [902555.543855] machine runuser[293]: pam_unix(runuser:session): session closed for user postgres240machine # [902555.554702] machine runuser[296]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)241machine # [902555.565238] machine runuser[296]: pam_unix(runuser:session): session closed for user postgres242machine # [902555.602914] machine runuser[305]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)243machine # [902555.672480] machine runuser[305]: pam_unix(runuser:session): session closed for user postgres244machine # [902555.712561] machine runuser[312]: pam_unix(runuser:session): session opened for user nobody(uid=65534) by (uid=0)245machine # [902555.715837] machine runuser[312]: pam_unix(runuser:session): session closed for user nobody246machine # [902555.732385] machine runuser[315]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)247machine # [902555.735603] machine runuser[315]: pam_unix(runuser:session): session closed for user postgres248machine # [902555.747062] machine runuser[317]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)249machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'INSERT INTO test DEFAULT VALUES;', in 0.94 seconds)250machine: must succeed: postgres-db-restore-command-test251machine # [902556.670451] machine runuser[317]: pam_unix(runuser:session): session closed for user postgres252machine # [902556.698136] machine runuser[322]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)253machine # [902556.709369] machine runuser[322]: pam_unix(runuser:session): session closed for user postgres254machine # [902556.716350] machine runuser[327]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)255machine # [902556.727453] machine runuser[327]: pam_unix(runuser:session): session closed for user postgres256machine # [902556.731159] machine runuser[331]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)257machine # [902558.544215] machine postgres[247]: [247] LOG: checkpoint complete: wrote 532 buffers (3.2%), wrote 3 SLRU buffers; 1 WAL file(s) added, 0 removed, 0 recycled; write=141.373 s, sync=0.202 s, total=143.471 s; sync files=21, longest=0.201 s, average=0.010 s; distance=4610 kB, estimate=4610 kB; lsn=0/1C19B20, redo lsn=0/1BE6A68258machine # [902558.933944] machine postgres[247]: [247] LOG: checkpoint starting: immediate force wait259machine # [902559.019359] machine postgres[247]: [247] LOG: checkpoint complete: wrote 2 buffers (0.0%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.475 s; sync files=3, longest=0.001 s, average=0.001 s; distance=204 kB, estimate=4169 kB; lsn=0/1C19BF0, redo lsn=0/1C19B98260machine # [902559.035182] machine runuser[331]: pam_unix(runuser:session): session closed for user postgres261machine # [902559.039981] machine runuser[334]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)262machine: (finished: must succeed: postgres-db-restore-command-test, in 2.93 seconds)263machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -At -c 'SELECT count(*) FROM test;'264machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -At -c 'SELECT count(*) FROM test;', in 0.02 seconds)265machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'INSERT INTO test DEFAULT VALUES;'266machine # [902559.597364] machine runuser[334]: pam_unix(runuser:session): session closed for user postgres267machine # [902559.610992] machine runuser[338]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)268machine # [902559.622191] machine runuser[338]: pam_unix(runuser:session): session closed for user postgres269machine # [902559.632467] machine runuser[341]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)270machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -c 'INSERT INTO test DEFAULT VALUES;', in 0.98 seconds)271machine: must succeed: post-restore-test272machine # [902560.596496] machine runuser[341]: pam_unix(runuser:session): session closed for user postgres273machine # [902560.622952] machine runuser[346]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)274machine # [902560.633880] machine runuser[346]: pam_unix(runuser:session): session closed for user postgres275machine # [902560.640244] machine runuser[351]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)276machine # [902560.651242] machine runuser[351]: pam_unix(runuser:session): session closed for user postgres277machine # [902560.654877] machine runuser[355]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)278machine # [902560.665144] machine postgres[247]: [247] LOG: checkpoint starting: immediate force wait279machine # [902563.923087] machine postgres[247]: [247] LOG: checkpoint complete: wrote 6 buffers (0.0%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 1 recycled; write=1.404 s, sync=0.014 s, total=3.258 s; sync files=7, longest=0.011 s, average=0.002 s; distance=4379 kB, estimate=4379 kB; lsn=0/2060880, redo lsn=0/2060828280machine # [902563.977981] machine runuser[355]: pam_unix(runuser:session): session closed for user postgres281machine # [902563.983986] machine runuser[358]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)282machine: (finished: must succeed: post-restore-test, in 3.75 seconds)283machine: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -At -c 'SELECT count(*) FROM test;'284machine: (finished: must succeed: runuser -u postgres -- /run/current-system/sw/bin/psql -d test -At -c 'SELECT count(*) FROM test;', in 0.02 seconds)285(finished: run the VM test script, in 463.04 seconds)286machine # [902564.350650] machine runuser[358]: pam_unix(runuser:session): session closed for user postgres287machine # [902564.362057] machine runuser[362]: pam_unix(runuser:session): session opened for user postgres(uid=71) by (uid=0)288machine # [902564.372542] machine runuser[362]: pam_unix(runuser:session): session closed for user postgres289test script finished in 719.25s290cleanup291kill NspawnMachine (pid 51)292(finished: cleanup, in 0.16 seconds)