pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedNot able to connect specific database
11+ messages / 6 participants
[nested] [flat]
* Not able to connect specific database
@ 2023-11-05 13:11 Kumar Rajesh <kr97061@gmail.com>
0 siblings, 3 replies; 11+ messages in thread
From: Kumar Rajesh @ 2023-11-05 13:11 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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
Attachments:
[image/jpeg] IMG_20231105_182928.jpg (1.0M, ../../CADc0YLa062mZBbS7BqEhq5KkF_jW5H_2k1GUAMsxQCfLTSsT5w@mail.gmail.com/3-IMG_20231105_182928.jpg)
download | view image
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-05 14:50 Holger Jakobs <holger@jakobs.com>
parent: Kumar Rajesh <kr97061@gmail.com>
2 siblings, 0 replies; 11+ messages in thread
From: Holger Jakobs @ 2023-11-05 14:50 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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
Attachments:
[application/pgp-signature] OpenPGP_signature (202B, ../../748fe073-34e2-0517-07e2-3f613b808271@jakobs.com/3-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-05 21:34 Jeff Janes <jeff.janes@gmail.com>
parent: Kumar Rajesh <kr97061@gmail.com>
2 siblings, 1 reply; 11+ messages in thread
From: Jeff Janes @ 2023-11-05 21:34 UTC (permalink / raw)
To: Kumar Rajesh <kr97061@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-06 00:23 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: Jeff Janes <jeff.janes@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: Rajesh Kumar @ 2023-11-06 00:23 UTC (permalink / raw)
To: Jeff Janes <jeff.janes@gmail.com>; +Cc: Kumar Rajesh <kr97061@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
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
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-06 00:40 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: Rajesh Kumar @ 2023-11-06 00:40 UTC (permalink / raw)
To: Jeff Janes <jeff.janes@gmail.com>; +Cc: Kumar Rajesh <kr97061@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
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 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
>>
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-08 00:42 Erik Serrano <eserranos@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 0 replies; 11+ messages in thread
From: Erik Serrano @ 2023-11-08 00:42 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Jeff Janes <jeff.janes@gmail.com>; Kumar Rajesh <kr97061@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
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 command
>
> On Mon, 6 Nov 2023, 05:53 Rajesh Kumar, <rajeshkumar.dba09@gmail.com>
> wrote:
>
>> 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
>>>
>>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-08 10:35 SAS <sas.postgresql@gmail.com>
parent: Kumar Rajesh <kr97061@gmail.com>
2 siblings, 1 reply; 11+ messages in thread
From: SAS @ 2023-11-08 10:35 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-08 10:43 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: SAS <sas.postgresql@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: Rajesh Kumar @ 2023-11-08 10:43 UTC (permalink / raw)
To: SAS <sas.postgresql@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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 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
>
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-08 14:35 SAS <sas.postgresql@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: SAS @ 2023-11-08 14:35 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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 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.
>
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-08 20:31 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: SAS <sas.postgresql@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: Rajesh Kumar @ 2023-11-08 20:31 UTC (permalink / raw)
To: SAS <sas.postgresql@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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 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.
>>
>
> 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
>
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Not able to connect specific database
@ 2023-11-09 11:47 Erik Serrano <eserranos@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 0 replies; 11+ messages in thread
From: Erik Serrano @ 2023-11-09 11:47 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: SAS <sas.postgresql@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
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 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.
>>>
>>
>> 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
>>
>>
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2023-11-09 11:47 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-11-05 13:11 Not able to connect specific database Kumar Rajesh <kr97061@gmail.com>
2023-11-05 14:50 ` Holger Jakobs <holger@jakobs.com>
2023-11-05 21:34 ` Jeff Janes <jeff.janes@gmail.com>
2023-11-06 00:23 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-06 00:40 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-08 00:42 ` Erik Serrano <eserranos@gmail.com>
2023-11-08 10:35 ` SAS <sas.postgresql@gmail.com>
2023-11-08 10:43 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-08 14:35 ` SAS <sas.postgresql@gmail.com>
2023-11-08 20:31 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-09 11:47 ` Erik Serrano <eserranos@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox