Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

process monitor throws warnings on postgresql: Warning: Process 123 disappeared while scanning

See original GitHub issue

process monitor throws warnings on postgresql: Warning: Process 123 disappeared while scanning

process ------- - instance #0 [OK] - instance DataDog/dd-agent#1 [WARNING] Warning: Process 16039 disappeared while scanning Warning: Process 16177 disappeared while scanning Warning: Process 16178 disappeared while scanning Warning: Process 16193 disappeared while scanning Warning: Process 16194 disappeared while scanning Warning: Process 16198 disappeared while scanning

      Warning: Process 15830 disappeared while scanning
      Warning: Process 15844 disappeared while scanning
  - instance DataDog/dd-agent#2 [OK]
  - instance DataDog/dd-agent#3 [OK]
  - instance DataDog/dd-agent#4 [OK]
  - instance DataDog/dd-agent#5 [OK]
  - instance DataDog/dd-agent#6 [OK]
  - instance DataDog/dd-agent#7 [OK]
  - instance DataDog/dd-agent#8 [OK]
  - instance DataDog/dd-agent#9 [OK]
  - Collected 43 metrics, 0 events & 11 service checks

Is is perfectly normal for postgresql to start and stop processes, and I see no reason why datadog would have to complain about that.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Reactions:2
  • Comments:14 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
albertvakacommented, Nov 3, 2020

This warning got removed in https://github.com/DataDog/integrations-core/pull/7045 which was released in Agent versions 6.22 and 7.22, please update your Agents to get the fix 😃 Closing this as done.

1reaction
remhcommented, Jul 1, 2016

Thanks for the feedback @tomazstrukeljdlabs . We could make an option to disable those warnings indeed. Reopening

Read more comments on GitHub >

github_iconTop Results From Across the Web

Warning: Process 123 disappeared while scanning · Issue ...
This bug will cause a DDOS on the logs if you have a big postgresql instance like the one I have, it does...
Read more >
Documentation: 15: 43.9. Errors and Messages - PostgreSQL
Allowed levels are DEBUG , LOG , INFO , NOTICE , WARNING , and EXCEPTION , with EXCEPTION being the default. EXCEPTION raises...
Read more >
Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
Read more >
Postgres Release Notes - All Versions - Bucardo
This is a complete, one-page listing of changes across all Postgres versions. All versions 10 and older are EOL (end of life) and...
Read more >
PostgreSQL Internals (1) - HPE
WARNING: terminating connection because of crash of another server process. DETAIL: The postmaster has commanded this server process to roll ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

Better docs for custom metrics

Next page

Ping integration issues