-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pgsql.go:275: WARN Postgresql Message too short. 53 (length=1). Wait for more. #46
Comments
I've find why: my postgresql use ssl communication. you should not use ssl=true in postgresql.conf to make it work. |
wow, the fix should never be to disable SSL! hope that wasn't in production... |
tsg
pushed a commit
that referenced
this issue
May 27, 2015
tsg
pushed a commit
that referenced
this issue
Dec 2, 2015
Contains: * getting started guide * migration from LSF guide * configuration file options reference * CLI options reference Squashed from commits by Ruflin, Monica Sarbu and myself. See #46.
ruflin
pushed a commit
to ruflin/beats
that referenced
this issue
Dec 2, 2015
Implement coverage with gotestcover
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Jan 6, 2016
Bumped nightlies version to 1.2
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Jan 20, 2016
tsg
added a commit
to tsg/beats
that referenced
this issue
Jan 20, 2016
Implement coverage with gotestcover
paylm
pushed a commit
to paylm/beats
that referenced
this issue
Mar 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have postgresql running and a packetbeat agent.
packetbeat -e -c /etc/packetbeat/packetbeat.conf -d "pgsql"
give me this output : pgsql.go:275: WARN Postgresql Message too short. 53 (length=1). Wait for more.
Do i have to do something posgresql configuration ?
The text was updated successfully, but these errors were encountered: