Azure Database for PostgreSQL flexible server stuck in restart status

Question

Azure Database for PostgreSQL flexible server stuck in restart status

Alex 20

Hi,

My Azure Database for PostgreSQL flexible server has the storage full (100%) and no connection to it is working. I tried to restart it and "The server is currently in 'restarting' state" for more than 1 day.

I'd like to set the storage size to bigger size but I cannot because the Compute+Storage menu is greyed out.

I tried using the azCli to stop/restart/start, restore from Azure Portal, but always getting InternalServerError. Same with Terraform apply with bigger storage, but it errors: "Server <pgsql-server-name> is busy with other operations. Please try later".

How can I add storage to make it start correctly?

NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-10-09T05:30:53.1466667+00:00

@Alex
Thank you for the question and for using Microsoft Q&A platform.
I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.
Alex 20 Reputation points

2024-10-09T06:50:09.9233333+00:00

Hi Nikhila,

I'd like for you to be able to understand why this happens and address it, because I've seen plenty of these same posts/tickets here on the Azure Community and the only resolution was the support ticket.

I was even thinking about Restore to new-name-server, Delete original-name-server, Restore again to original-name-server.

But the restore was not working, so the only option here is deleting the original-name-server. In this case, will the original-name be available for reuse?

Look forward for your reply
Alex 20 Reputation points

2024-10-15T13:04:31.0633333+00:00

Solved via a support case, by freeing up some space by Microsoft internal tech team to clear the transaction, making the server to come back online.

Answer accepted by question author

0 additional answers

Your answer

NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-10-09T05:30:53.1466667+00:00

@Alex
Thank you for the question and for using Microsoft Q&A platform.
I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.
Alex 20 Reputation points

2024-10-09T06:50:09.9233333+00:00

Hi Nikhila,

I'd like for you to be able to understand why this happens and address it, because I've seen plenty of these same posts/tickets here on the Azure Community and the only resolution was the support ticket.

I was even thinking about Restore to new-name-server, Delete original-name-server, Restore again to original-name-server.

But the restore was not working, so the only option here is deleting the original-name-server. In this case, will the original-name be available for reuse?

Look forward for your reply
Alex 20 Reputation points

2024-10-15T13:04:31.0633333+00:00

Solved via a support case, by freeing up some space by Microsoft internal tech team to clear the transaction, making the server to come back online.

Answer 1

RahulRandive 10,506

Hi @Alex

If the storage is full, the server may not have enough space to roll back or roll forward active transactions, causing it to become stuck in this state. Backend intervention is required to restore server availability, and you'll need to open a support case to resolve the issue.

Deleting the server and attempting to recreate it with the same name is risky, as there is no guarantee that the name will be released, allowing you to reuse it. I believe this poses a potential risk.

Thank You!

Alex 20 Reputation points

2024-10-10T13:44:26.38+00:00

Mail sent. Thanks
RahulRandive 10,506 Reputation points

2024-10-15T13:03:55.2+00:00

Hi Alex,
I worked with you offline to bring the server back. Thank you for your patience.

Please don't forget to close the thread by marking the answer.

Thank You!
Alex 20 Reputation points

2024-10-15T13:07:38.0333333+00:00

Just to let others know, he Microsoft internal tech team has addressed the issue of the system being stuck due to full storage. They cleared some space internally, which enabled the transactions to be processed and brought the Postgresql Flexible server back online.

Thank you Rahul

Share via

Azure Database for PostgreSQL flexible server stuck in restart status

0 additional answers

Your answer