# Metricbeat not collecting memory info
**URL:** https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145
**Category:** Beats
**Tags:** metricbeat
**Created:** [March 27, 2017, 2:18pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145 "2017-03-27T14:18:13Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@francopp](https://discuss.elastic.co/u/francopp)
#### Post date: [March 27, 2017, 2:18pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/1 "2017-03-27T14:18:13Z")
After some Swap configuration changes metricbeat stop sending memory info I got any other type but memory info.
About an hour ago we made some changes in our server configuration and now we got this
The changes we made were to just stop using swap memory:
swapoff --all
Then change the fstab file and comment out the swap lines and finally a cache clear:
sync; echo 1 \> /proc/sys/vm/drop\_caches
sync; echo 2 \> /proc/sys/vm/drop\_caches
sync; echo 3 \> /proc/sys/vm/drop\_caches
After this we stop recieving memory part. And before this everything was normal. When I start metricbeat it's sending memory info in JSON but all data comming from memory it's all 0s
---
### Author:  [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [March 27, 2017, 2:43pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/2 "2017-03-27T14:43:38Z")
Are there any errors in the log file?
Are there any error events reported to elasticsearch? You can query for `_exists_:error` on the Discover page in Kibana.
---
### Author:  [@francopp](https://discuss.elastic.co/u/francopp)
#### Post date: [March 27, 2017, 2:49pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/3 "2017-03-27T14:49:30Z")
No errors in the log. Data is coming like this
```auto
{
"@timestamp": "2017-03-27T14:42:08.408Z",
"beat": {
"hostname": "srvsig23logprod",
"name": "srvsig23logprod",
"version": "5.1.2"
},
"metricset": {
"module": "system",
"name": "process",
"rtt": 187062
},
"system": {
"process": {
"cpu": {
"start_time": "2016-05-30T16:36:15.000Z",
"total": {
"pct": 0
}
},
"memory": {
"rss": {
"bytes": 0,
"pct": 0
},
"share": 0,
"size": 0
},
"name": "ksoftirqd/0",
"pgid": 0,
"pid": 4,
"ppid": 2,
"state": "sleeping",
"username": "root"
}
},
"type": "metricsets"
}
```
---
### Author:  [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [March 27, 2017, 3:16pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/4 "2017-03-27T15:16:16Z")
You are showing an event from the `process` metricset (which looks normal BTW). Can you look for events from the memory metricset (`metricset.name:memory`). Are there any events from this metricset that have an error (`metricset.name:memory AND _exists_:error`)?
The memory data is read from `/proc/meminfo` on Linux. What's in that file?
---
### Author:  [@francopp](https://discuss.elastic.co/u/francopp)
#### Post date: [March 27, 2017, 3:33pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/5 "2017-03-27T15:33:04Z")
Yeah, It was just an example of how logs are coming, as normal as always.
No output from the search, also try to filter by metricset.name and look up for memory but no logs since this changes.
This is my output of:
> -bash-4.1$ cat /proc/meminfo
> MemTotal: 132028084 kB
> MemFree: 84576776 kB
> Buffers: 183948 kB
> Cached: 8654160 kB
> SwapCached: 0 kB
> Active: 7526564 kB
> Inactive: 3658672 kB
> Active(anon): 2437912 kB
> Inactive(anon): 29164 kB
> Active(file): 5088652 kB
> Inactive(file): 3629508 kB
> Unevictable: 34746100 kB
> Mlocked: 0 kB
> SwapTotal: 0 kB
> SwapFree: 4 kB
> Dirty: 18980 kB
> Writeback: 0 kB
> AnonPages: 37093272 kB
> Mapped: 181600 kB
> Shmem: 272 kB
> Slab: 583976 kB
> SReclaimable: 469328 kB
> SUnreclaim: 114648 kB
> KernelStack: 19968 kB
> PageTables: 88848 kB
> NFS\_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 66014040 kB
> Committed\_AS: 38544732 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 750196 kB
> VmallocChunk: 34289449660 kB
> HardwareCorrupted: 0 kB
> AnonHugePages: 36560896 kB
> HugePages\_Total: 0
> HugePages\_Free: 0
> HugePages\_Rsvd: 0
> HugePages\_Surp: 0
> Hugepagesize: 2048 kB
> DirectMap4k: 12288 kB
> DirectMap2M: 2011136 kB
> DirectMap1G: 132120576 kB
---
### Author:  [@francopp](https://discuss.elastic.co/u/francopp)
#### Post date: [March 27, 2017, 6:40pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/6 "2017-03-27T18:40:53Z")
There is no information for any problem like this before. Any idea?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 24, 2017, 6:40pm UTC](https://discuss.elastic.co/t/metricbeat-not-collecting-memory-info/80145/7 "2017-04-24T18:40:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.