Benutzer-Werkzeuge

Webseiten-Werkzeuge


know-how:linux

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
know-how:linux [2024/03/19 21:38] – [gvm - openvas] ccknow-how:linux [2024/03/20 12:44] (aktuell) – [gvm - openvas] cc
Zeile 1062: Zeile 1062:
  
 <code> <code>
-Did you upgrade your postgresql cluster to 16 like the instructions said to when the update came in? 
  
-pg_dropcluster 16 main --stop +root@pentest:~# pg_lsclusters  
-pg_upgradecluster 15 main+Ver Cluster Port Status Owner    Data directory              Log file 
 +15  main    5432 online postgres /var/lib/postgresql/15/main /var/log/postgresql/postgresql-15-main.log 
 +16  main    5433 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16-main.log 
 + 
 +root@pentest:~# pg_dropcluster 16 main --stop 
 + 
 +root@pentest:~# pg_upgradecluster 15 main 
 + 
 + 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Stopping old cluster... 
 +Restarting old cluster with restricted connections... 
 +Notice: extra pg_ctl/postgres options given, bypassing systemctl for start operation 
 +Creating new PostgreSQL cluster 16/main ... 
 +/usr/lib/postgresql/16/bin/initdb -D /var/lib/postgresql/16/main --auth-local peer --auth-host scram-sha-256 --no-instructions --encoding UTF8 --lc-collate en_GB.UTF-8 --lc-ctype en_GB.UTF-8 --locale-provider libc 
 +The files belonging to this database system will be owned by user "postgres"
 +This user must also own the server process. 
 + 
 +The database cluster will be initialized with locale "en_GB.UTF-8"
 +The default text search configuration will be set to "english"
 + 
 +Data page checksums are disabled. 
 + 
 +fixing permissions on existing directory /var/lib/postgresql/16/main ... ok 
 +creating subdirectories ... ok 
 +selecting dynamic shared memory implementation ... posix 
 +selecting default max_connections ... 100 
 +selecting default shared_buffers ... 128MB 
 +selecting default time zone ... Europe/Vienna 
 +creating configuration files ... ok 
 +running bootstrap script ... ok 
 +performing post-bootstrap initialization ... ok 
 +syncing data to disk ... ok 
 + 
 +Copying old configuration files... 
 +Copying old start.conf... 
 +Copying old pg_ctl.conf... 
 +Starting new cluster... 
 +Notice: extra pg_ctl/postgres options given, bypassing systemctl for start operation 
 +Running init phase upgrade hook scripts ... 
 + 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Roles, databases, schemas, ACLs... 
 +WARNING:  database "postgres" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +WARNING:  database "gvmd" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +WARNING:  database "postgres" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 + set_config  
 +------------ 
 +  
 +(1 row) 
 + 
 + set_config  
 +------------ 
 +  
 +(1 row) 
 + 
 + set_config  
 +------------ 
 +  
 +(1 row) 
 + 
 + set_config  
 +------------ 
 +  
 +(1 row) 
 + 
 +Fixing hardcoded library paths for stored procedures... 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Upgrading database template1... 
 +WARNING:  database "template1" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Fixing hardcoded library paths for stored procedures... 
 +WARNING:  database "gvmd" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Upgrading database gvmd... 
 +WARNING:  database "gvmd" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Fixing hardcoded library paths for stored procedures... 
 +WARNING:  database "postgres" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Upgrading database postgres... 
 +WARNING:  database "postgres" has a collation version mismatch 
 +DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.37. 
 +HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 
 +Stopping target cluster... 
 +Stopping old cluster... 
 +Disabling automatic startup of old cluster... 
 +Starting upgraded cluster on port 5432... 
 +Running finish phase upgrade hook scripts ... 
 +vacuumdb: processing database "gvmd": Generating minimal optimizer statistics (1 target) 
 +vacuumdb: processing database "postgres": Generating minimal optimizer statistics (1 target) 
 +vacuumdb: processing database "template1": Generating minimal optimizer statistics (1 target) 
 +vacuumdb: processing database "gvmd": Generating medium optimizer statistics (10 targets) 
 +vacuumdb: processing database "postgres": Generating medium optimizer statistics (10 targets) 
 +vacuumdb: processing database "template1": Generating medium optimizer statistics (10 targets) 
 +vacuumdb: processing database "gvmd": Generating default (full) optimizer statistics 
 +vacuumdb: processing database "postgres": Generating default (full) optimizer statistics 
 +vacuumdb: processing database "template1": Generating default (full) optimizer statistics 
 + 
 +Success. Please check that the upgraded cluster works. If it does, 
 +you can remove the old cluster with 
 +    pg_dropcluster 15 main 
 + 
 +Ver Cluster Port Status Owner    Data directory              Log file 
 +15  main    5433 down   postgres /var/lib/postgresql/15/main /var/log/postgresql/postgresql-15-main.log 
 +Ver Cluster Port Status Owner    Data directory              Log file 
 +16  main    5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16-main.log 
 + 
 +root@pentest:~# pg_dropcluster 15 main 
 + 
 +root@pentest:~# pg_lsclusters  
 +Ver Cluster Port Status Owner    Data directory              Log file 
 +16  main    5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16-main.log 
 </code> </code>
  
know-how/linux.txt · Zuletzt geändert: 2024/03/20 12:44 von cc