Understanding PostgreSQL installer debug log
Hi Team, Can you please help me to understand the PostgreSQL installer’s debug log. I am installing PostgreSQL in CentOS 7.6 system with PostgreSQL binary ( postgresql-9.6.6-1-linux-x64.run). I am using the below command to install it in unattended mode. ./postgresql-9.6.6-1-linux-x64.run --installer-language en --serviceaccount postgres --servicename postgresqld --datadir "/home/postgres/" --prefix "/home/postgres" --superpassword 1234 --serverport 5432 --debuglevel 4 --debugtrace ./postgresql-debug.log --mode unattended A debug log file postgresql-debug.log is created in the same directory. But it is in some encoded format which I am not able to decode. Here is the first few lines of the debug log. MwSUdmn65MlwA81MDBVmg34ZjlXDReCYnIxjAwgZ15jHp8UXS0OQ2L/a8iph kR7moeATHKE7UkwbqeM1bluAAET0rr2AXwDdQdowNVgI5BYvwz7YBMUd5nsn AgldXNczMw/dSiFsj334+Bb/iOhXuaQo/S0FzyzqFPEqaBHVjPrJv70vdhTD dmHn7vKY/Zo2xZ/eyouLxobkFYdRw2zqX+HAkRpygUNPqHzvy0AJg6Kln8uv GhwphVedsu1buJc7gb2T+1HWqsCXB8jm9LI7GmDvA62sKmgmjxRDMl+UI6UE rn7gbhrc59oI4Wjem2aJK8ufTHuYM+xfXNFc5yY9CtoI4Wjem2aJzo+oIONC gYoZFhKeT1iysdoI4Wjem2aJ8B3Ju++KR9us+PNdpxdCk9oI4Wjem2aJL+bx eZCCp83ng4pRhi+GoQyXnF++cnIKHlx0bVlSX7X7AV8O24BoFwyXnF++cnIK rJUoxqtsZe6URWF1lQj7xgyXnF++cnIKkX2dNd0GKfLyeRPuEuaM1N6/6xVl We are trying to debug an issue with installation at client’s location and before that we are trying to run debug mode as trial. But looks like this cannot be understood. Before going back to client, we would like to understand how to decode the debug log so that we could trace out the issues at client side. Thanks in advance and appreciate your response. Please consider this as a high priority for us. Regards, Ramesh Maddi – DevOPs Lead. Mobigesture
Understanding PostgreSQL installer debug log
Hi Team, Can you please help me to understand the PostgreSQL installer’s debug log. I am installing PostgreSQL in CentOS 7.6 system with PostgreSQL binary ( postgresql-9.6.6-1-linux-x64.run). I am using the below command to install it in unattended mode. ./postgresql-9.6.6-1-linux-x64.run --installer-language en --serviceaccount postgres --servicename postgresqld --datadir "/home/postgres/" --prefix "/home/postgres" --superpassword 1234 --serverport 5432 --debuglevel 4 --debugtrace ./postgresql-debug.log --mode unattended A debug log file postgresql-debug.log is created in the same directory. But it is in some encoded format which I am not able to decode. Here is the first few lines of the debug log. MwSUdmn65MlwA81MDBVmg34ZjlXDReCYnIxjAwgZ15jHp8UXS0OQ2L/a8iph kR7moeATHKE7UkwbqeM1bluAAET0rr2AXwDdQdowNVgI5BYvwz7YBMUd5nsn AgldXNczMw/dSiFsj334+Bb/iOhXuaQo/S0FzyzqFPEqaBHVjPrJv70vdhTD dmHn7vKY/Zo2xZ/eyouLxobkFYdRw2zqX+HAkRpygUNPqHzvy0AJg6Kln8uv GhwphVedsu1buJc7gb2T+1HWqsCXB8jm9LI7GmDvA62sKmgmjxRDMl+UI6UE rn7gbhrc59oI4Wjem2aJK8ufTHuYM+xfXNFc5yY9CtoI4Wjem2aJzo+oIONC gYoZFhKeT1iysdoI4Wjem2aJ8B3Ju++KR9us+PNdpxdCk9oI4Wjem2aJL+bx eZCCp83ng4pRhi+GoQyXnF++cnIKHlx0bVlSX7X7AV8O24BoFwyXnF++cnIK rJUoxqtsZe6URWF1lQj7xgyXnF++cnIKkX2dNd0GKfLyeRPuEuaM1N6/6xVl We are trying to debug an issue with installation at client’s location and before that we are trying to run debug mode as trial. But looks like this cannot be understood. Before going back to client, we would like to understand how to decode the debug log so that we could trace out the issues at client side. Thanks in advance and appreciate your response. Please consider this as a high priority for us. Regards, Ramesh Maddi – DevOPs Lead. Mobigesture
Re: Understanding PostgreSQL installer debug log
Our product is certified along with PostgreSQL 9.6.6 only. We cannot use further version of PostgreSQL at this time in production until it is certified for our product( which is integrated may other components) and is officially released. To elaborate actual issue with client in installing PostgreSQL, it is failing to install on only one client's server RHEL 7.6. Below is the error performing post-bootstrap initialization ... Failed to initialize the database cluster with initdb with the error "invalid byte sequence for encoding "UTF8" Script stderr: FATAL: invalid byte sequence for encoding "UTF8": 0xeb 0x2f 0xdb child process exited with exit code 1 initdb: removing contents of data directory "/home/postgres/9.6/data" Error running /home/postgres/9.6/installer/server/initcluster.sh "postgres" "postgres" "/home/postgres/9.6" "/home/postgres/9.6/data" 5432 DEFAULT: FATAL: invalid byte sequence for encoding "UTF8": 0xeb 0x2f 0xdb child process exited with exit code 1 initdb: removing contents of data directory "/home/postgres/9.6/data" Problem running post-install step. Installation may not complete correctly The database cluster initialisation failed. Problem running post-install step. Installation may not complete correctly The database cluster initialisation failed. Initially we thought the issue would be with client's VMs locale settings. But client's VMs locale is set to en_US.utf8 format which is expected and default for PostgreSQL. This issue is only happening for this client only. With this we are suspecting the issue would be client's OS settings but not sure about what settings need to be modified. In order to further debug the issue, I am adding "debug" options to PostgreSQL EDB installer. But the debug log is fully encoded/encrypted in unknown format. We have client session in early next week. Before that we need to identify the debug steps to resolve the issue. Coming to *Luca's *question, I understand that using Yum/RPM is better way of installation. That would be our future plan. But for this particular issue, we need to identify debug steps. Thanks for your insight. -- Ramesh On Fri, Aug 9, 2019 at 4:33 PM Benedict Holland < benedict.m.holl...@gmail.com> wrote: > Does the problem go away if you install pg11? Are the drives you are > getting your logs from encrypted? > > Thanks, > ~Ben > > On Fri, Aug 9, 2019, 3:17 AM Luca Ferrari wrote: > >> On Fri, Aug 9, 2019 at 8:46 AM Ramesh Maddi >> wrote: >> > ./postgresql-9.6.6-1-linux-x64.run --installer-language en >> --serviceaccount postgres --servicename postgresqld --datadir >> "/home/postgres/" --prefix "/home/postgres" --superpassword 1234 >> --serverport 5432 --debuglevel 4 --debugtrace ./postgresql-debug.log --mode >> unattended >> > >> >> I suspect this is a dump produced by Qt used by EDB installer, maybe >> you should ask support to them for this: >> >> >> 18.8.0 >> Linux 4.18.0-25-generic x86_64 >> >> >> Please note that, my case, I was able to get a dump immediatly because >> the data directory did not exist. Why don't you use at least attended >> mode to see if it is something as trivial as in my case? >> >> Beside, is there a specific reason why you are not using >> distro-specific packages? See the note here >> <https://www.enterprisedb.com/downloads/postgres-postgresql-downloads>. >> Luca >> >> >>
