Blocking issue on Azure Postgres Flexible 17 with the background worker azure_mise_service_worker

Question

Blocking issue on Azure Postgres Flexible 17 with the background worker azure_mise_service_worker

Ioana Teodorescu 45

Hello,

We started to deploy Azure Postgres Flexible servers using the recent version 17. We are observing recurrent log messages (every second !) generated by the postmaster backend with the following content : LOG: background worker "azure_mise_service_worker" (PID xxx) exited with exit code 1

The servers seem to be functional, we can create databases, users, structures, import from dumps and export the data. But the logs are flooded with these messages and we consider this is a blocking issue for any environments (dev / testing / production).

Here is the exact version of our 17 version servers :
PostgreSQL 17.6 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.2.0, 64-bit

Similar servers (same sku, sizing and configuration) in version 16 don't have the issue.

What is the reason / impact of this log ? I saw the similar question here, but we are not facing any resource stress issue at all. These servers have no activity, we just deployed them. Are there any particular incompatibilities of the 17 version with the compute / storage layers ?

PostgreSQL 17 has been GA since July 2025, but fresh installation unusable due to crash loop every second. Version 16 works fine, only version 17 affected. This is a blocking issue for our production deployment.

Thanks in advance for your help

Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-10T17:21:15.57+00:00

Hi Ioana Teodorescu,

Thank you for reaching on Microsoft Q&A!

From your description you are saying that this issue only happening on V17 not on V16, everything is working as expected, you are able to create database, users, structures and import from dumps but logs spamming by showing this "background worker "azure_mise_service_worker" (PID xxx) exited with exit code 1", please correct me if my understanding is wrong.

Can you please confirm the status of the server and have you tried restarting the server?

can you please share the logs of the server and region so that we can investigate further.

Thanks!

Kalyani
Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-14T11:37:52.6966667+00:00

Hi Ioana Teodorescu,

Can you please check private messaging and confirm.

Answer accepted by question author

1 additional answer

Your answer

Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-10T17:21:15.57+00:00

Hi Ioana Teodorescu,

Thank you for reaching on Microsoft Q&A!

From your description you are saying that this issue only happening on V17 not on V16, everything is working as expected, you are able to create database, users, structures and import from dumps but logs spamming by showing this "background worker "azure_mise_service_worker" (PID xxx) exited with exit code 1", please correct me if my understanding is wrong.

Can you please confirm the status of the server and have you tried restarting the server?

can you please share the logs of the server and region so that we can investigate further.

Thanks!

Kalyani
Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-14T11:37:52.6966667+00:00

Hi Ioana Teodorescu,

Can you please check private messaging and confirm.

Answer 1

Kalyani Kondavaradala 3,235 Microsoft External Staff Moderator

Hi Ioana Teodorescu,

following up on discussion initially you have faced the issue is only happening on V17 not on V16, everything is working as expected, you are able to create database, users, structures and import from dumps but logs spamming by showing this "background worker "azure_mise_service_worker" (PID xxx) exited with exit code 1".

Since the issue appeared to be on the backend, we reached out to the internal team and shared all the necessary details and context. They confirmed that the server is no longer visible from the backend, and as you mentioned over private messaging, it was deleted in accordance with your project standards.

As we have seen similar issue faced by other customer. The fix taken by the team is they have disabled the aad_disable_mise component from the backend.

I hope this has been helpful.

Kindly consider upvoting and accept the answer if the provided information helpful. It will help other community members who are facing similar issues, please feel free to post your queries in Microsoft Q&A if you have any in future.

Thanks!

Kalyani

Ioana Teodorescu 45 Reputation points

2025-10-15T06:36:24.05+00:00

Hello,

Thank you for your answer and all the provided details.

Does this mean that if we reconsider ramping up V17 PG servers in the future, we'll have to have the internal team to disable the aad_disable_mise component as well ? This cannot be a long-term solution, servers are created / destroyed automatically, we cannot handle them manually / individually. Do you have any official documentation about this component (aad_disable_mise), the behavior it might trigger, the consequences of disabling it (looks like it is related to Azure AD, so it may be problematic for certain use cases) ?

Before reconsidering PG V17 for our platform, we need to understand the root cause of this problem and either fix it on our side (if it is a configuration / sizing / compatibility matter) or wait for the official fix from MS / Azure teams.

What is the internal team conclusion about this : is it considered as a bug / abnormal behavior ? If yes, will there be a fix for this issue on the long run and do you have an approximative time frame for such a fix ?

Thank you again for helping us going to the bottom of this and completely clarify the picture.
Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-16T09:29:55.76+00:00

Hi Ioana Teodorescu,

We currently have limited access to the product background, but I’ll take this request to the PG team for further review. Please note that there might be some delay, as they are currently engaged with development tasks. I will make sure to update you when I receive any response from them regarding your request.

In the meantime, please rest assured, if you face any challenges or get stuck while using Azure services, you can always reach out to us on Microsoft Q&A. We’re more happy to assist you! I truly appreciate your understanding and patience.

Thanks!

Kalyani
Ioana Teodorescu 45 Reputation points

2025-10-16T10:23:58.53+00:00

Hello,

Thanks a lot for the provided support, looking forward to get news about all this.
Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-16T10:44:20.4533333+00:00

Sure, thank you for your patience and understanding.
Ioana Teodorescu 45 Reputation points

2025-10-22T05:59:51.3+00:00

Hello,
I got notified that you added a privaye message but I'm no longer able to see them (the private messages button is missing despite the fact that i'm authenticated and connected with my own profile).
Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-22T08:27:13.6933333+00:00

Hi Ioana Teodorescu,

No worries I am just informing the updates on the process, As conveyed earlier i reached out the Product team, I am still waiting for Pg response. Will keep you posted
Kalyani Kondavaradala 3,235 Reputation points Microsoft External Staff Moderator

2025-10-29T12:27:27.6633333+00:00

Hi Ioana Teodorescu,

We got response from product team, they confirmed that its product bug.

This appears to be a known product issue, and our team is actively working on resolving it. While there isn’t an exact ETA available yet.

You can approach to Microsoft Q&A for faster resolution if you have observed this in future, Product team has the temporary fix as conveyed earlier in the answer.

I hope this helps, please consider upvoting and accepting the Answer so that it will help others who are facing similar challenges.

Thanks!

Kalyani
Ioana Teodorescu 45 Reputation points

2025-10-30T06:20:39.3333333+00:00

Thanks for the feedback and sorry to hear there is no ETA yet.

Regrads,

Ioana.

Answer 2

Hello oana Teodorescu,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are having issue on Azure Postgres Flexible 17 with the background worker azure_mise_service_worker.

This is a confirmed platform-level issue affecting PostgreSQL 17.6 on Azure Flexible Server. The azure_mise_service_worker is crashing every second, causing log flooding and raising production reliability concerns. Microsoft has not yet provided a fix, and the only viable workaround is to use PostgreSQL 16 until the issue is resolved.

I will advise you to open a critical Azure Support Ticket via your Azure Portal or use [Priority Customer Support](https://free.blessedness.top/en-us/azure/azure-portal/supportability/priority-community-support

) (PCS).

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Ioana Teodorescu 45 Reputation points

2025-10-11T06:10:17.41+00:00

Hello @Sina Salam ,
Thank you for the quick answer. If this is a known problem, could you please provide some official link / documentation which track down the issue ?
Thanks again and best regards

Share via

Blocking issue on Azure Postgres Flexible 17 with the background worker azure_mise_service_worker

1 additional answer

Your answer