Skip to content
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.

Sign up for GitHub

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

Jump to bottom

need help to debug why Packetbeat not capturing postgresql #123

Closed
harshamadala opened this issue Apr 27, 2015 · 6 comments · Fixed by #24826
Closed

need help to debug why Packetbeat not capturing postgresql #123

harshamadala opened this issue Apr 27, 2015 · 6 comments · Fixed by #24826

Comments

@harshamadala
Copy link

Can anyone help me how to debug why packetbeat not capturing postgresql packets.

I tried running packetbeat -e -d "pgsql" and it keep on giving below logs
"pgsql.go:472: WARN Postgresql Message too short (length=1). Wait for more.
pgsql.go:630: DBG Message not complete, but sending to the next layer
pgsql.go:723: WARN Response from unknown transaction. Ignoring."

Somewhere before I read that this is because of preparedstatements, but even commands which I ran in psql are not begin captured by packetbeat. Is there any way to debug what is the issue?

Thanks
@harshamadala harshamadala changed the title Packetbeat not capturing postgresql need help to debug why Packetbeat not capturing postgresql Apr 27, 2015
@harshamadala
Copy link
Author

Configuration using:
device = "any"
[protocols.pgsql]
ports = [5432]
[procs.monitored.pgsql]
cmdline_grep = "postgres"

@tsg
Copy link
Contributor

tsg commented Apr 27, 2015

You might have encryption on? See #90

@tsg
Copy link
Contributor

tsg commented Apr 27, 2015

Sorry, this is the ticket I wanted to link to: #46

@harshamadala
Copy link
Author

Thanks for quick response.

We have encryption off. And I am getting
"pgsql.go:723: WARN Response from unknown transaction. Ignoring." continuously.
Is this because of prepared statements? How to debug this?

@tsg
Copy link
Contributor

tsg commented Apr 28, 2015

Best would be to create a small trace, like this one:

tcpdump -i any -s0 -w"trace.pcap" "port 5432"

And send it to us at info@packetbeat.com. We can than figure it out if it's because of prepared statements or something else.

@tsg
Copy link
Contributor

tsg commented Apr 28, 2015

Thanks for the trace, indeed, it's using "unnamed prepared statements". You can see them showing up in wireshark as "T/D/C/Z".

Closing this one as a duplicate of #78. We'll try to figure out a solution.

@tsg tsg closed this as completed Apr 28, 2015
@tsg tsg added the duplicate label Apr 28, 2015
ruflin added a commit that referenced this issue Dec 2, 2015
@ruflin
Merge pull request #123 from urso/enh/testsuite-go1.5
f9b9bf6 
testsuite go1.5
tsg added a commit that referenced this issue Dec 2, 2015
@tsg
Merge pull request #123 from ruflin/nightlies-link
5dd6574 
Add link to nightlies
monicasarbu added a commit that referenced this issue Dec 2, 2015
@monicasarbu
Merge pull request #123 from tsg/docs_version
7f37775 
Set docs version
tsg pushed a commit to tsg/beats that referenced this issue Jan 20, 2016
@ruflin
Merge pull request elastic#123 from urso/enh/testsuite-go1.5
0a62d03 
testsuite go1.5
@ycombinator ycombinator mentioned this issue Feb 7, 2020
Merged
1 task
@sayden sayden mentioned this issue Jul 13, 2020
Closed
3 tasks
@narph narph mentioned this issue Sep 1, 2020
Merged
6 tasks
@kaiyan-sheng kaiyan-sheng mentioned this issue Oct 28, 2020
Merged
6 tasks
@narph narph mentioned this issue Dec 9, 2020
Merged
6 tasks
@aleksmaus aleksmaus mentioned this issue Mar 30, 2021
Merged
1 task
@andrewkroh andrewkroh mentioned this issue Jun 30, 2021
Merged
3 tasks
@narph narph mentioned this issue Sep 21, 2021
Merged
6 tasks
@narph narph mentioned this issue Nov 10, 2021
Merged
6 tasks
@belimawr belimawr mentioned this issue Apr 7, 2022
Closed
6 tasks
@ishleenk17 ishleenk17 mentioned this issue Jul 18, 2022
Closed
6 tasks
pierrehilbert added a commit that referenced this issue Aug 4, 2023
@pierrehilbert
Changelog: adding 8.7.0 and 8.7.1 to release-notes.html (#36237)
2ac0c9d 
<!-- Type of change
Please label this PR with one of the following labels, depending on the
scope of your change:
- Bug
- Enhancement
- Breaking change
- Deprecation
- Cleanup
- Docs
-->

## Proposed commit message

<!-- Mandatory
Explain here the changes you made on the PR.

Please explain:

- WHAT: patterns used, algorithms implemented, design architecture,
message processing, etc.
- WHY:  the rationale/motivation for the changes

This text will be pasted into the squash dialog when the change is
committed and will be
a long term historical record of the change to help future contributors
understand the
change, please help them by making it clear and comprehensive, they may
be you.

If the commit title is adequate to describe both of these things, The
text here may be omitted
or replaced with "See title". The title of the PR will be used as the
commit message title when
the merge is made and the "See title" marker will be removed if present.

The text here and the PR title will be subject to the PR review process.
-->

We forgot to modify `libbeat/docs/release.asciidoc` we added changelog
on the 8.8 branch.
The changelog content was already present.
 
## Checklist

<!-- Mandatory
Add a checklist of things that are required to be reviewed in order to
have the PR approved

List here all the items you have verified BEFORE sending this PR. Please
DO NOT remove any item, striking through those that do not apply. (Just
in case, strikethrough uses two tildes. ~~Scratch this.~~)
-->
- [x] I have made corresponding changes to the documentatio

## Related issues

<!-- Recommended
Link related issues below. Insert the issue link or reference after the
word "Closes" if merging this should automatically close it.

- Closes #123
- Relates #123
- Requires #123
- Superseds #123
-->
- Relates #35580
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@tsg @harshamadala