# Enabling postgresql module in Metricbeat causes crash **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [March 22, 2019, 9:50am UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467 "2019-03-22T09:50:52Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![aswinm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aswinm/32/42578_2.png) [@aswinm](https://discuss.elastic.co/u/aswinm)\ **Post date:** [March 22, 2019, 9:50am UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/1 "2019-03-22T09:50:52Z")
I recently installed Metricbeat on a windows server 2016 and enabled apache and Postgresql modules. After almost a day after this my Postgres crashed with an error `no buffer space available`. I had to reboot the system to get it fixed then and in another 12 hours it crashed again. When I inspected the connections in TCPView, I could see a lot of connections between Metricbeat and Postgres and it kept growing. So I disabled the Postgres module and it was all back to normal. Is there a setting I can limit the number of connections between the 2? ---
**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\ **Post date:** [March 22, 2019, 9:58am UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/2 "2019-03-22T09:58:11Z")
Hi, That sounds like a bug in Metricbeat. Which version are you using? Did you customize the settings for the postgresql module? ---
**Author:** ![aswinm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aswinm/32/42578_2.png) [@aswinm](https://discuss.elastic.co/u/aswinm)\ **Post date:** [March 22, 2019, 10:00am UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/3 "2019-03-22T10:00:48Z")
Thanks for the quick response. I am using Metricbeat 6.6.2. I did not customise anything related to the postgresql module. I downloaded Metricbeat, enabled the modules and started the service ---
**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\ **Post date:** [March 22, 2019, 3:14pm UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/4 "2019-03-22T15:14:57Z")
I'm trying to reproduce the issue, stay tuned. ---
**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\ **Post date:** [March 22, 2019, 5:15pm UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/5 "2019-03-22T17:15:40Z")
I could reproduce it but couldn't come up with a fix, so I created an bug report: > ---
**Author:** ![aswinm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aswinm/32/42578_2.png) [@aswinm](https://discuss.elastic.co/u/aswinm)\ **Post date:** [March 22, 2019, 6:22pm UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/6 "2019-03-22T18:22:12Z")
Great.. Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 19, 2019, 6:22pm UTC](https://discuss.elastic.co/t/enabling-postgresql-module-in-metricbeat-causes-crash/173467/7 "2019-04-19T18:22:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.