# Getting warning message on Pmm2.7

**URL:** <https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865>\
**Category:** PMM 2.x\
**Tags:** pmm\
**Created:** [August 7, 2020, 4:40am UTC](https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865 "2020-08-07T04:40:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gajendra](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/gajendra/32/44_2.png) [@Gajendra](https://forums.percona.com/u/Gajendra)\
**Post date:** [August 7, 2020, 4:40am UTC](https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865/1 "2020-08-07T04:40:13Z")

</div>

Hi Team,  
We are monitoring mongoDb 4.2 by pmm2 but few warning messages are coming in log&nbsp;  
  
couldn’t retrieve data from cursor connection(127.0.0.1:27017[-99]) incomplete read of message header: read tcp 127.0.0.1:36222-\>127.0.0.1:27017: i/o timeout #033[33m\*\*\*D#033[0m=/agent\_id/13fc7034-704c-4b66-be5e-e165f50480e2 #033[33mcomponent#033[0m=agent-builtin #033[33mdb#033[0m=bob-qa4 #033[33mtype#033[0m=qan\_mongodb\_profiler\_agent  
  
Please have a look  
Thanks

---

<div class="post-metadata">

**Author:** ![steve.hoffman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/steve.hoffman/32/66_2.png) [@steve.hoffman](https://forums.percona.com/u/steve.hoffman)\
**Post date:** [August 17, 2020, 12:35pm UTC](https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865/2 "2020-08-17T12:35:08Z")

</div>

I saw a similar message once when I was playing with Mongo as a container instead of a bare install (I had disabled the firewall to allow me to register the exporter and then later rebooted and the rule wasn’t made permanent so started blocking connection).&nbsp; Looks like this is the local pmm-admin agent trying to connect for QAN data and getting denied but I’d expect to see similar entries for the mongo\_exporter trying to scrape as well.&nbsp; Are you able to upgrade to 2.9.1?&nbsp; Getting client and server at the latest version would at least rule out something that’s already been fixed in the last few releases.&nbsp;&nbsp;

---

<div class="post-metadata">

**Author:** ![Gajendra](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/gajendra/32/44_2.png) [@Gajendra](https://forums.percona.com/u/Gajendra)\
**Post date:** [August 20, 2020, 2:14am UTC](https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865/3 "2020-08-20T02:14:31Z")

</div>

Hi Steve,  
i upgraded pmm to 2.91 but still we are having same error .  
  
Agent ID: /agent\_id/6892b59a-e570-4d51-9ef6-d1bf9833df17Node ID : /node\_id/21d567c4c-1d1d-4733-a1ab-70d4118b454a  
PMM Server:&nbsp; &nbsp; &nbsp; &nbsp; URL&nbsp; &nbsp; : [https://pmm-server-ip:443/&nbsp](https://pmm-server-ip:443/&nbsp); &nbsp; &nbsp; &nbsp; Version: 2.9.1  
PMM Client:&nbsp; &nbsp; &nbsp; &nbsp; Connected&nbsp; &nbsp; &nbsp; &nbsp; : true&nbsp; &nbsp; &nbsp; &nbsp; Time drift&nbsp; &nbsp; &nbsp; &nbsp;: 1.476634ms&nbsp; &nbsp; &nbsp; &nbsp; Latency&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 1.073369ms&nbsp; &nbsp; &nbsp; &nbsp; pmm-admin version: 2.9.1&nbsp; &nbsp; &nbsp; &nbsp; pmm-agent version: 2.9.1Agents:&nbsp; &nbsp; &nbsp; &nbsp; /agent\_id/6e732314-fbe8-432e-b6d3-2e5ae5c2c31d node\_exporter Running&nbsp; &nbsp; &nbsp; &nbsp; /agent\_id/70a55aa4-e80b-4bbc-a4f7-eb676b5d6d3 mongodb\_profiler\_agent Running&nbsp; &nbsp; &nbsp; &nbsp; /agent\_id/d330b911-5cb4-4adf-8d53-1260ee501f14 mongodb\_exporter Running

---

<div class="post-metadata">

**Author:** ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)\
**Post date:** [February 22, 2021, 12:40pm UTC](https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865/4 "2021-02-22T12:40:44Z")

</div>

Hi @Gajendra  
Even I saw this error but after re-adding the service, it’s gone. later I don’t see the same issue.  
Can you try same?

Try the following,

- remove pmm2-client and directory ‘/usr/local/percona/pmm2’

- install pmm2-client version again (same as pmm server version)

- and add instance in monitoring again.

---

<div class="post-metadata">

**Author:** ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)\
**Post date:** [April 23, 2021, 10:25am UTC](https://forums.percona.com/t/getting-warning-message-on-pmm2-7/7865/5 "2021-04-23T10:25:55Z")

</div>

Seen a similar issue with 2.16.0 Here is the bug report: [[PMM-6912] mongodb\_exporter\_qan hung due server overload - Percona JIRA](https://jira.percona.com/browse/PMM-6912)
