Is this what you’re looking for ?

HOSTNAME=ovirt-engine
SELINUX_ROLE_REQUESTED=
TERM=xterm
SHELL=/bin/bash
HISTSIZE=1000
SSH_CLIENT=10.1.50.14 50688 22
SELINUX_USE_CURRENT_RANGE=
SSH_TTY=/dev/pts/1
USER=root
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36:
SSH_AUTH_SOCK=/tmp/ssh-FoWxJtonlt/agent.14076
MAIL=/var/spool/mail/root
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
PWD=/root
LANG=en_US
SELINUX_LEVEL_REQUESTED=
HISTCONTROL=ignoredups
SHLVL=1
HOME=/root
LOGNAME=root
SSH_CONNECTION=
LESSOPEN=||/usr/bin/lesspipe.sh %s
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 <sven.achte...@eps.aero>
Cc: Yedidyah Bar David <d...@redhat.com>; users <users@ovirt.org>; Gobinda Das 
<go...@redhat.com>
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 
<sven.achte...@eps.aero<mailto:sven.achte...@eps.aero>> wrote:
Hi Simone,

if I use the same command as you did I get the following information:

[root@ovirt-engine ~]# sudo -u postgres scl enable rh-postgresql95 -- psql 
--list
could not change directory to "/root": Permission denied
                                              List of databases
         Name         |        Owner         | Encoding  |   Collate   |    
Ctype    |   Access privileges
----------------------+----------------------+-----------+-------------+-------------+-----------------------
engine               | engine               | UTF8      | en_US.UTF-8 | 
en_US.UTF-8 |
 ovirt_engine_history | ovirt_engine_history | UTF8      | en_US.UTF-8 | 
en_US.UTF-8 |
 postgres             | postgres             | SQL_ASCII | C           | C      
     |
 template0            | postgres             | SQL_ASCII | C           | C      
     | =c/postgres          +
                      |                      |           |             |        
     | postgres=CTc/postgres

The issue is just there on postgres and template0.
According to inidb documentation:
https://www.postgresql.org/docs/9.5/static/app-initdb.html

-E encoding
--encoding=encoding

Selects the encoding of the template database. This will also be the default 
encoding of any database you create later, unless you override it there. The 
default is derived from the locale, or SQL_ASCII if that does not work.

It will fall back to SQL_ASCII if there was an error getting the locale.

Can you please share the output of env on the shell there you executed 
engine-setup?



template1            | postgres             | UTF8      | en_US.utf8  | 
en_US.utf8  |
(5 rows)

As I’m not a DB admin, I don’t really know how go about these encodings. I 
restored the current system from a 4.1.7 Backup to a 4.1.9 image and all went 
well.

Do you need any other values ?

Thanks,
Sven


Von: Simone Tiraboschi [mailto:stira...@redhat.com<mailto:stira...@redhat.com>]
Gesendet: Dienstag, 24. Juli 2018 15:47
An: Sven Achtelik <sven.achte...@eps.aero<mailto:sven.achte...@eps.aero>>; 
Yedidyah Bar David <d...@redhat.com<mailto:d...@redhat.com>>
Cc: users <users@ovirt.org<mailto:users@ovirt.org>>; Gobinda Das 
<go...@redhat.com<mailto:go...@redhat.com>>
Betreff: Re: [ovirt-users] Re: Upgrade 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 UTF8.

[root@enginevm tmp]# sudo -u postgres scl enable rh-postgresql95 -- psql --list
                                             List of databases
         Name         |        Owner         | Encoding |   Collate   |    
Ctype    |   Access privileges
----------------------+----------------------+----------+-------------+-------------+-----------------------
 engine               | engine               | UTF8     | en_US.UTF-8 | 
en_US.UTF-8 |
 ovirt_engine_history | ovirt_engine_history | UTF8     | en_US.UTF-8 | 
en_US.UTF-8 |
 postgres             | postgres             | UTF8     | en_US.UTF-8 | 
en_US.UTF-8 |
 template0            | postgres             | UTF8     | en_US.UTF-8 | 
en_US.UTF-8 | =c/postgres          +
                      |                      |          |             |         
    | postgres=CTc/postgres
 template1            | postgres             | UTF8     | en_US.UTF-8 | 
en_US.UTF-8 | postgres=CTc/postgres+
                      |                      |          |             |         
    | =c/postgres
(5 rows)


So the point is why the upgrade process is trying to force SQL_ASCII.
Can you please share your env variable values?

On Tue, Jul 24, 2018 at 2:57 PM Gobinda Das 
<go...@redhat.com<mailto:go...@redhat.com>> wrote:
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?

On Tue, Jul 24, 2018 at 5:00 PM, Sven Achtelik 
<sven.achte...@eps.aero<mailto:sven.achte...@eps.aero>> wrote:
Hi All,

I’m still struggling to upgrade from 4.1 to 4.2 and the root cause seems to be 
the SQL upgrade. I installed my 4.1.9 with the engine appliance image and 
restored a DB to it. My Upgrade to 4.2 is failing with the errors below:
--------------------------------
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is the install user                  ok
Checking database connection settings                       ok
Checking for prepared transactions                          ok
Checking for reg* system OID user data types                ok
Checking for contrib/isn with bigint-passing mismatch       ok
Checking for invalid "line" user columns                    ok
Creating dump of global objects                             ok
Creating dump of database schemas
  engine
  ovirt_engine_history
  postgres
  template1
                                                            ok

encodings for database "template1" do not match:  old "UTF8", new "SQL_ASCII"
Failure, exiting

I tried everything that could do and I also tried to find a solution on google 
to make this work. Could someone with DB knowhow please advise on the next 
steps to resolve this ? I really would like to upgrade somehow.

Thank you,
Sven

_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/H7KQJ4VDGVDBQX6QL2RJ5LLS6I3KHC6I/



--
Thanks,
Gobinda
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/T7AE7KYVIB2SXUZPOGCXAD4WMR4KNMS2/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNSBLRAL5R5LH7KOYGT2FVDWPSWGZYM6/

Reply via email to