Обсуждение: Not able to connect specific database
Hi team,
I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.
Kindly help
Вложения
Am 05.11.23 um 14:11 schrieb Kumar Rajesh:
Hi team,I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.Kindly help
When including text from a terminal window to a post, please don't add a graphical screenshot, but copy & paste the text itself!
It seems that your database cluster is broken. I'm afraid you will have to restore your backup.
Regards,
Holger
-- Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Вложения
You have some kind of corruption. You didn't tell us what version you are using. For me, that file being missing just causes FATAL, not PANIC. I don't know why it would be different for you.
If you shutdown the database and then start it back up with the -P option to 'postgres' of "-o -P" for 'pg_ctl', then you should be able to connect to the database and do a REINDEX SYSTEM. This should fix the problem. Then you can shut it down and start it up again without the special option.
However, once you have some kind of corruption there is no telling how much other corruption you also have. Why would just this one file happen to be missing?
Cheers,
Jeff
Postgres 15
On Mon, 6 Nov 2023, 03:04 Jeff Janes, <jeff.janes@gmail.com> wrote:
You have some kind of corruption. You didn't tell us what version you are using. For me, that file being missing just causes FATAL, not PANIC. I don't know why it would be different for you.If you shutdown the database and then start it back up with the -P option to 'postgres' of "-o -P" for 'pg_ctl', then you should be able to connect to the database and do a REINDEX SYSTEM. This should fix the problem. Then you can shut it down and start it up again without the special option.However, once you have some kind of corruption there is no telling how much other corruption you also have. Why would just this one file happen to be missing?Cheers,Jeff
We are also using patronictl crunchy data for ha and pgbackrest for automatic backup..
Should I simply stop and then start using pg_ctl command
On Mon, 6 Nov 2023, 05:53 Rajesh Kumar, <rajeshkumar.dba09@gmail.com> wrote:
Postgres 15On Mon, 6 Nov 2023, 03:04 Jeff Janes, <jeff.janes@gmail.com> wrote:You have some kind of corruption. You didn't tell us what version you are using. For me, that file being missing just causes FATAL, not PANIC. I don't know why it would be different for you.If you shutdown the database and then start it back up with the -P option to 'postgres' of "-o -P" for 'pg_ctl', then you should be able to connect to the database and do a REINDEX SYSTEM. This should fix the problem. Then you can shut it down and start it up again without the special option.However, once you have some kind of corruption there is no telling how much other corruption you also have. Why would just this one file happen to be missing?Cheers,Jeff
Hola,
Para mi tienes un problema con el sistema operativo Linux donde vive el PG , es posible que uno de tus discos no esté montado ( o se haya desmontado por alguna razón) llenado, o el clúster no esté detectando el storage donde se guardan los archivos base de PostgreSQL.
Yo consultaría si la VM tiene algún problema antes de proceguir... Y si te dicen que no lo hay , bueno... Reinicia el server .
Eso, espero te ayude
Saludos
El dom., 5 de noviembre de 2023 9:41 p. m., Rajesh Kumar <rajeshkumar.dba09@gmail.com> escribió:
We are also using patronictl crunchy data for ha and pgbackrest for automatic backup..Should I simply stop and then start using pg_ctl commandOn Mon, 6 Nov 2023, 05:53 Rajesh Kumar, <rajeshkumar.dba09@gmail.com> wrote:Postgres 15On Mon, 6 Nov 2023, 03:04 Jeff Janes, <jeff.janes@gmail.com> wrote:You have some kind of corruption. You didn't tell us what version you are using. For me, that file being missing just causes FATAL, not PANIC. I don't know why it would be different for you.If you shutdown the database and then start it back up with the -P option to 'postgres' of "-o -P" for 'pg_ctl', then you should be able to connect to the database and do a REINDEX SYSTEM. This should fix the problem. Then you can shut it down and start it up again without the special option.However, once you have some kind of corruption there is no telling how much other corruption you also have. Why would just this one file happen to be missing?Cheers,Jeff
Le 05/11/2023 à 14:11, Kumar Rajesh a écrit :
Hi team,I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.Kindly help
I wonder if you are running your database into a container which also contains your data, making data disappear when restarting the container...
S.
--
Dr Stéphane Schildknecht
Contact régional PostgreSQL pour l'Europe francophone
+33 617 11 37 42
How to solve this then?
On Wed, 8 Nov, 2023, 4:05 PM SAS, <sas.postgresql@gmail.com> wrote:
Le 05/11/2023 à 14:11, Kumar Rajesh a écrit :Hi team,I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.Kindly helpI wonder if you are running your database into a container which also contains your data, making data disappear when restarting the container...
S.
--Dr Stéphane SchildknechtContact régional PostgreSQL pour l'Europe francophone+33 617 11 37 42
Le 08/11/2023 à 11:43, Rajesh Kumar a écrit :
How to solve this then?On Wed, 8 Nov, 2023, 4:05 PM SAS, <sas.postgresql@gmail.com> wrote:Le 05/11/2023 à 14:11, Kumar Rajesh a écrit :Hi team,I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.Kindly helpI wonder if you are running your database into a container which also contains your data, making data disappear when restarting the container...
S.
You don't give enough information to be helped.
--
Dr Stéphane Schildknecht
Contact régional PostgreSQL pour l'Europe francophone
+33 617 11 37 42
I am using postgres 15.2 version on a openshift container platform.
We recently upgraded the openshift version. Did not have any problem in staging and then upgraded in production also.
After which, in in cluster we r having around 10 dbs. Out of which I tried to connect one db using \c dbname...9dbs I am able to connect. But this one particular db, when I tried to connect , it throws an error "PANIC: could not open critical system index 2662". That's the story..please let me know if any additional information required.
On Wed, 8 Nov 2023, 20:05 SAS, <sas.postgresql@gmail.com> wrote:
Le 08/11/2023 à 11:43, Rajesh Kumar a écrit :How to solve this then?On Wed, 8 Nov, 2023, 4:05 PM SAS, <sas.postgresql@gmail.com> wrote:Le 05/11/2023 à 14:11, Kumar Rajesh a écrit :Hi team,I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.Kindly helpI wonder if you are running your database into a container which also contains your data, making data disappear when restarting the container...
S.
You don't give enough information to be helped.
--Dr Stéphane SchildknechtContact régional PostgreSQL pour l'Europe francophone+33 617 11 37 42
La falla se presenta al conectar esa base en particular o en las 9 restantes (dijistes que tienes 10 bases)
Saludos
Erik R. Serrano Saavedra
Ingeniero de Sistemas Informáticos
Data Base Administrator
El mié, 8 nov 2023 a las 17:31, Rajesh Kumar (<rajeshkumar.dba09@gmail.com>) escribió:
I am using postgres 15.2 version on a openshift container platform.We recently upgraded the openshift version. Did not have any problem in staging and then upgraded in production also.After which, in in cluster we r having around 10 dbs. Out of which I tried to connect one db using \c dbname...9dbs I am able to connect. But this one particular db, when I tried to connect , it throws an error "PANIC: could not open critical system index 2662". That's the story..please let me know if any additional information required.On Wed, 8 Nov 2023, 20:05 SAS, <sas.postgresql@gmail.com> wrote:Le 08/11/2023 à 11:43, Rajesh Kumar a écrit :How to solve this then?On Wed, 8 Nov, 2023, 4:05 PM SAS, <sas.postgresql@gmail.com> wrote:Le 05/11/2023 à 14:11, Kumar Rajesh a écrit :Hi team,I am not able to connect to one specific database and receiving error " PANIC:could not open critical system index 2662" as attached in picture . But I am able to connect other remaining database in samee instance.Kindly helpI wonder if you are running your database into a container which also contains your data, making data disappear when restarting the container...
S.
You don't give enough information to be helped.
--Dr Stéphane SchildknechtContact régional PostgreSQL pour l'Europe francophone+33 617 11 37 42