ate:130 stopping service postgresql
but according to postgresql-setup logs, template1 is instead in UTF-8.
Can you please double check it attaching the output of:
sudo -u postgres psql --list
>
>
> *Von:* Simone Tiraboschi [mailto:stira...@redhat.com]
> *Gesendet:* Dienstag, 31. Ju
etup log file?
> Thanks, Sven
>
>
>
>
>
>
>
> *Von:* Sven Achtelik [mailto:sven.achte...@eps.aero]
> *Gesendet:* Montag, 30. Juli 2018 14:00
> *An:* Simone Tiraboschi
> *Cc:* users
> *Betreff:* [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
>
>
Hi Sven,
to test I created a new VM with a new hostname and fake IP
addresses in /etc/hosts for the oVirt hosts/nodes so it won't interfere with
the real hosts. I then did a full restore from backup and an engine rename.
This leaves you with oVirt system but the no storage or hosts.
t.dumpEnvironment:869 ENV DIALOG/answerFileContent=str:'# OTOPI
> answer file, generated by human dialog
>
> [environment:default]
>
>
>
> SELINUX_LEVEL_REQUESTED=
>
> HISTCONTROL=ignoredups
>
> SHLVL=1
>
> HOME=/root
>
> LOGNAME=root
>
> SSH_
Von: Simone Tiraboschi [mailto:stira...@redhat.com]
Gesendet: Montag, 30. Juli 2018 09:19
An: Sven Achtelik
Cc: Yedidyah Bar David ; users ; Gobinda Das
Betreff: Re: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
On Fri, Jul 27, 2018 at 9:27 AM Sven Achtelik
>
> XDG_RUNTIME_DIR=/run/user/0
>
> _=/usr/bin/env
>
>
>
>
>
>
>
> *Von:* Simone Tiraboschi [mailto:stira...@redhat.com]
> *Gesendet:* Donnerstag, 26. Juli 2018 12:42
> *An:* Sven Achtelik
> *Cc:* Yedidyah Bar David ; users ;
> Gobinda Das
> *Betref
Juli 2018 09:31
An: p.stanifo...@leedsbeckett.ac.uk; users@ovirt.org
Betreff: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
Hi Paul,
I only used the automatic update from oVirt. I'll look through the older post
if I can do something with this information.
Thanks, Sven
Juli 2018 18:04
An: users@ovirt.org
Betreff: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
Hi Sven,
maybe it's dependant on the order of the upgrade, did you update
postgres or let the oVirt do it?
The manual method was to update the template0 template1 an
: Yedidyah Bar David ; users ; Gobinda Das
Betreff: Re: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
On Wed, Jul 25, 2018 at 1:23 PM Sven Achtelik
mailto:sven.achte...@eps.aero>> wrote:
Hi Simone,
if I use the same command as you did I get the following information:
[root
Hi Sven,
maybe it's dependant on the order of the upgrade, did you update
postgres or let the oVirt do it?
The manual method was to update the template0 template1 and postgres databases.
https://www.mail-archive.com/users@ovirt.org/msg47888.html
Regards,
Paul S.
___
> Do you need any other values ?
>
>
>
> Thanks,
>
> Sven
>
>
>
>
>
> *Von:* Simone Tiraboschi [mailto:stira...@redhat.com]
> *Gesendet:* Dienstag, 24. Juli 2018 15:47
> *An:* Sven Achtelik ; Yedidyah Bar David <
> d...@redhat.com>
> *Cc:
]
Gesendet: Mittwoch, 25. Juli 2018 13:17
An: p.stanifo...@leedsbeckett.ac.uk; users@ovirt.org
Betreff: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
Hi Paul,
I'm trying with the latest packages, 4.2.5. How would I manually change those
encodings ?
Thanks,
Sven
-Ursprüng
t.org
Betreff: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues
Hi Sven,
I had a problem with SQL_ASCII and had to change them manually on
our test upgrade system but one of the later 4.2 versions did it as part of the
upgrade for Postgres, which version of 4.2 are you tryi
grade from 4.1 to 4.2 failing - SQL Issues
Hi,
it seams still pretty close to
https://bugzilla.redhat.com/show_bug.cgi?id=1528371 although that one was on
lc_collate and this on encoding.
Adding also Didi.
I just double check on a system of mine upgrade from 4.1 to 4.2 and template1
is still on UT
Hi Sven,
I had a problem with SQL_ASCII and had to change them manually on
our test upgrade system but one of the later 4.2 versions did it as part of the
upgrade for Postgres, which version of 4.2 are you trying to upgrade to?
Regards,
Paul S.
__
Hi,
it seams still pretty close to
https://bugzilla.redhat.com/show_bug.cgi?id=1528371 although that one was
on lc_collate and this on encoding.
Adding also Didi.
I just double check on a system of mine upgrade from 4.1 to 4.2 and
template1 is still on UTF8.
[root@enginevm tmp]# sudo -u postgres
Hi Sven,
I think you need to use same encoding.The error clearly says your dump
encoding is "UTF8" and the new database encoding is "SQL_ASCII"
As per I know PostgreSQL does not convert encoding from one type to another
during restore.
Can you please check what's the current encoding configured?
17 matches
Mail list logo
