Hi there,
we recently installed Packetbeat on one of our PostgreSQL-Servers. Basicly it works. It sends things to Elasticsearch and created the Dashboards in Kibana. But in the PGSQL-Performace Dashboard it tells us that about 40% of all requests are errors. And this can definitely not be true as the log of the Postgresql-Server does not tell us anything like this. We are talking about like 500 Errors per Seccond. The Events which are detected as Errors have "Error" as State, but no PGSQL-Errormessage or Errorcode. The Source of the error-Queries are different hosts and can be Select, Insert, Whatever. Additionaly the Log of Packetbeat is spamed with these messages below. Maybe there is some kind of conenction to the irrational high error-rate?
2018-07-26T14:17:04.497+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:04.501+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:04.502+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=43, i=12
2018-07-26T14:17:04.504+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:04.702+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=182, i=2
2018-07-26T14:17:04.702+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:04.767+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:04.768+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:04.834+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:05.513+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:05.854+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.854+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.854+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.854+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.855+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.855+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.855+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.855+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.855+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:05.856+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:06.466+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:07.351+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=21, i=7
2018-07-26T14:17:07.418+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=184, i=2
2018-07-26T14:17:08.103+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:08.375+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:08.381+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:08.381+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:08.382+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:08.441+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
2018-07-26T14:17:08.778+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=34, i=6
2018-07-26T14:17:08.778+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:08.779+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 116
2018-07-26T14:17:08.780+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:08.780+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=34, i=6
2018-07-26T14:17:08.781+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:08.846+0200 ERROR pgsql/parse.go:531 Pgsql invalid column_length=4294967295, buffer_length=34, i=6
2018-07-26T14:17:08.847+0200 WARN pgsql/parse.go:501 Pgsql parser expected data message, but received command of type 110
2018-07-26T14:17:09.188+0200 WARN pgsql/parse.go:633 Pgsql parser expected extended query message, but received command of type 80
The monitored Network-Interface is configured like this:
packetbeat.interfaces.device: ens192
packetbeat.interfaces.snaplen: 1500
packetbeat.interfaces.type: af_packet
packetbeat.interfaces.buffer_size_mb: 512
Can anybody give us any hints why this is happening?
We are using Packetbeat 6.3.2, Elasticsearch and Kibana 6.3.1, Postgresql 10.4 and Debian 9.4.
Greetings Marco