What is causing the following log message in server logs every second: background worker \"azure_mise_service_worker\" (PID 1638153) exited with exit code 1

Question

What is causing the following log message in server logs every second: background worker \"azure_mise_service_worker\" (PID 1638153) exited with exit code 1

Darryl Schmidt 41

I'm seeing the following message in the azure flexible server for postgres server log every second. Wondering what is causing this and how to resolve:

2025-09-26 14:00:13.057 UTC [7-1856349] @ app= LOG: background worker "azure_mise_service_worker" (PID 1638148) exited with exit code 1

2025-09-26 14:00:14.101 UTC [7-1856351] @ app= LOG: background worker "azure_mise_service_worker" (PID 1638149) exited with exit code 1

Kalyani Kondavaradala 3,310 Reputation points Microsoft External Staff Moderator

2025-09-26T15:44:47.6566667+00:00
Hi Darryl Schmidt,

Greetings for the day!

This kind of message typically indicates that the worker is experiencing issues and exit code 1 suggests a generic error.

Here are a few steps you can take to troubleshoot the issue:

Check Resource Utilization: Ensure that your server has enough resources (CPU, memory) available. High resource usage can cause background workers to fail.

View Detailed Logs: Check the detailed logs of the Postgres server to see if there are more messages or reasons specified around the time these exit codes appear. Look for any potential error messages or relevant information prior to the worker exiting.

Investigate Configurations: Review the settings and configurations of the Azure Postgres server, especially any recent changes that might affect the background worker’s functionality. Ensure that required extensions or configs are properly set up.

Look for Known Issues: Check the Azure Service Health dashboard for any ongoing incidents or maintenance that might impact the functionality of the Postgres service on Azure.

Update or Restart the Service: Sometimes, just restarting the Postgres service can clear transient issues.

Meanwhile could you also please provide the details over the private messaging to investigate further.

Thanks!

Kalyani

Answer accepted by question author

1 additional answer

Your answer

Kalyani Kondavaradala 3,310 Reputation points Microsoft External Staff Moderator

2025-09-26T15:44:47.6566667+00:00

Hi Darryl Schmidt,

Greetings for the day!

This kind of message typically indicates that the worker is experiencing issues and exit code 1 suggests a generic error.

Here are a few steps you can take to troubleshoot the issue:

Check Resource Utilization: Ensure that your server has enough resources (CPU, memory) available. High resource usage can cause background workers to fail.

View Detailed Logs: Check the detailed logs of the Postgres server to see if there are more messages or reasons specified around the time these exit codes appear. Look for any potential error messages or relevant information prior to the worker exiting.

Investigate Configurations: Review the settings and configurations of the Azure Postgres server, especially any recent changes that might affect the background worker’s functionality. Ensure that required extensions or configs are properly set up.

Look for Known Issues: Check the Azure Service Health dashboard for any ongoing incidents or maintenance that might impact the functionality of the Postgres service on Azure.

Update or Restart the Service: Sometimes, just restarting the Postgres service can clear transient issues.

Meanwhile could you also please provide the details over the private messaging to investigate further.

Thanks!

Kalyani

Answer 1

Mahesh Kurva 9,650 Microsoft External Staff Moderator

Hi Darryl Schmidt,

Greetings!!

Initially the issue was log message in server logs every second: background worker "azure_mise_service_worker" (PID 1638153) exited with exit code.

After checking with the internal team, issue was resloved.

Thank you!

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Mahesh Kurva 9,650 Reputation points Microsoft External Staff Moderator

2025-10-21T10:47:16.15+00:00

Hi Darryl Schmidt,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Darryl Schmidt 41 Reputation points

2025-10-21T14:25:25.82+00:00

It was helpful to me that the issue was resolved, but it doesn't answer the other questions I had about whether I could have resolved this myself and what the exact issue was and if it will occur again when I build my next managed postgres cluster.
Mahesh Kurva 9,650 Reputation points Microsoft External Staff Moderator

2025-10-21T15:14:59.1133333+00:00

Hi Darryl Schmidt,

Glad to hear the issue has been resolved. We're requesting the RCA for this matter, and once we receive it, I'll provide a detailed explanation.

Thank you!

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Hello Darryl Schmidt,

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

I understand that you found background worker "azure_mise_service_worker" (PID 1638153) exited with exit code 1.

This is a platform-level component failure requiring systematic diagnostics before any restart actions, with immediate Azure Support via your Azure Portal escalation being the primary resolution path for persistent occurrences.

Though, I will escalate from here, however before restarting:

-- Check for blocking issues before any restart
SELECT pid, usename, datname, query, state, wait_event_type, wait_event 
FROM pg_stat_activity 
WHERE state = 'active' AND query != '<IDLE>'
ORDER BY query_start DESC;

https://free.blessedness.top/en-us/azure/postgresql/flexible-server/concepts-monitoring#blocking-sessions

Implement log analysis:

Azure Portal > PostgreSQL Server > Server Logs
Filter timeframe 15 minutes BEFORE first occurrence
Search patterns: "mise", "worker", "OOM", "connection refused"

Check Azure metrics correlation:

CPU utilization spikes ≥95%
Memory pressure indicators
Storage IOPs/throughput limits

https://free.blessedness.top/en-us/azure/postgresql/flexible-server/howto-configure-and-access-logs

Validate the resources:

-- Critical resource checks
SELECT 
    schemaname,
    relname,
    n_dead_tup as dead_tuples,
    n_live_tup as live_tuples,
    last_autovacuum
FROM pg_stat_user_tables 
WHERE n_dead_tup > 1000000
ORDER BY n_dead_tup DESC;

https://free.blessedness.top/en-us/azure/postgresql/flexible-server/how-to-maintenance

Then, you can perform safe restart procedure:

Ensure recent backup exists
Check Azure Service Health for regional issues
Schedule during maintenance window

   # 1. Drain connections gracefully
   # 2. Azure Portal → Overview → Restart (Forced = No)
   # 3. Monitor restart progress via Azure Activity Log

https://free.blessedness.top/en-us/azure/postgresql/flexible-server/how-to-restart-server

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.

Share via

What is causing the following log message in server logs every second: background worker \"azure_mise_service_worker\" (PID 1638153) exited with exit code 1

1 additional answer

Your answer