Thank you, Andreas.
I've had a checkered history with pg_upgradecluster; the last upgrade (to
22.04LTS, PG14) worked fine, if I remember correctly, but all other post-LTS
upgrades failed for me.
Is it possible that setting a non-default password for user postgres might
cause a problem? - the on
So I'm coming to this bug with fresh eyes.
Inspecting your attachments, it looks like you had postgresql-12
installed, from 20.04 (focal)?
Example:
Start-Date: 2024-09-21 12:36:44
Commandline: /usr/sbin/synaptic
Requested-By: mbm (1000)
Purge: postgresql-12:amd64 (12.11-0ubuntu0.20.04.1), postg
1)
The LTS upgrade creates an empty cluster for the new postgresql version:
pg_lsclusters
This empty cluster first needs to be removed:
pg_dropcluster 16 main --stop
Then:
pg_upgradecluster 14 main
On my main pc, that last command collapsed with error - see bug #2078494
On the standby pc (an older
Hello Bernard,
Let me take a step back and try to understand where we are right now.
1) Could you please post a step-by-step with the *exact* commands you
issued?
2) I believe we've asked this before, but just in case: can you
reproduce this bug in a clean environment? If yes, can you please
pr
Yes, on my stand-by pc I can still re-run the upgrade process - I didn't get
round to installing the databases manually!
Currently, pg_lsclusters shows
14 main 5432 down ...
16 main 5433 online
and psql -p 5433 shows no role for me ... as noted above.
So yes, I'll be happy to provide any i
** Changed in: postgresql-16 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081996
Title:
After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
T
Hello Bernard,
I'm so sorry for the delay, but the bug probably didn't show up again in
our triage because it remained "incomplete" after your last comments.
Did you finally recreate the databases manually? Or there is still a
chance that you could provide any other info to continue with the
debu
** Changed in: postgresql-16 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081996
Title:
After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
T
Sorry - after a lot more searching, I retract comment #8.
Most advice on upgrading PG versions refers to 'sudo pg_ctl {stop|start}'
Some advices refer to 'sudo service postgresql {stop|start}'
Very few refer to the *systemd* command 'sudo systemctl {status|start|stop}
postgresql',
and equally v
It might be relevant that pg_ctl is not in any PATH (not mine, nor sudo, nor
postgres), on either of my PCs.
The command is found only in /usr/lib/postgresql/*/bin/pg_ctl
Attempts to run [sudo] pg_ctl status result in
Command 'pg_ctl' not found, did you mean:
command 'dg_ctl' from deb drogon (1
1
Yes, the databases I expected to be transferred are in the MAIN cluster, so
*should* have been set up in the new 'postgresql-16' main cluster; and
pg_upgradecluster *should* have changed the ports set for the '14' and '16'
instances. Neither happened.
2
pg_upgradecluster gave me problems af
Thanks for the additional logs.
Looking at your attached pg_upgradecluster.OUT I see what you mean that
it looks like it succeeded in porting the 'postgres' and 'template1'
databases, but presumably you expected another database(s) to upgrade?
Are those databases included in the 'main' cluster? I
** Changed in: postgresql-16 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081996
Title:
After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
T
(1) Those two fatal errors result from an attempt to verify the (apparently
not unsuccessful) pg_upgradecluster by psql access to the database 'simas'.
They originate after pg_upgradecluster had terminated.
(2) There are no known customised config files for postgresql on the
system.
(3) I can'
Hello,
Thanks for providing the requested information. Looking at the
postgresql-16-main.log file, I see the following excerpt which caught my
attention:
2024-09-21 15:51:05.322 BST [5823] mbm@simas FATAL: role "mbm" does not exist
2024-09-21 15:53:46.720 BST [5784] LOG: checkpoint starting: t
** Attachment added: "upgradeclusterINFO.gz contains (a) the screen output
pasted into pg_upgradecluster.OUT, (b) apt/term.log, (c) apt/history.log,
(d) postgresql/postgresql-14-main.log.1, and (e) postgresql-16-main.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/208199
pg_upgradecluster.OUT doesn't appear to be included in the APPORT.info
file you attached; that doesn't appear to include log data at all.
I'm not sure what data would help Athos the most, so hopefully he can
follow up, but I would suggest maybe attaching these:
/var/log/apt/term.log*
/var/log/apt
** Attachment added: "Generated on standby pc using apport-cli --save
APPORT.info"
https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2081996/+attachment/5821830/+files/APPORT.info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
18 matches
Mail list logo
