mysql.go:411: Response from unknown transaction about beats

[packetb-old]

You can start the agent in foreground and add some debug information like this:

packetbeat -e -c /etc/packetbeat/packetbeat.conf -d "mysql"

If you can record a short trace and send it to us, we can also check what's wrong as well as add it to our set of automatic tests. Thanks!

[ekw]

I am also getting this. But when I start in foreground as indicated above, I don't get any extra debug information:

 # packetbeat -e -c /etc/packetbeat/packetbeat.conf -d "mysql"
 publish.go:342: INFO Using http://192.168.1.1:9200 as publisher
 publish.go:343: INFO Using index pattern [packetbeat-]YYYY.MM.DD
 publish.go:353: INFO No agent name configured, using hostname 'XXXXXXXXX'
 procs.go:93: INFO Local IP addresses are: [127.0.0.1 192.168.1.1]
 mysql.go:411: WARN Response from unknown transaction. Ignoring.
 mysql.go:411: WARN Response from unknown transaction. Ignoring.
 mysql.go:411: WARN Response from unknown transaction. Ignoring.
 mysql.go:411: WARN Response from unknown transaction. Ignoring.

[sammcj]

@ekw Are you using SSL by any chance? See #48

[ekw]

@sammcj No, I'm not using SSL.

[packetb-old]

@ekw Sorry for following late on this. Would it possible to send us a short trace created as explained in http://packetbeat.com/docs/troubleshooting.html#recording-a-trace Thanks!

[packetb-old]

This is likely a dup of #54, but waiting for the trace to confirm.

[ekw]

@packetbeat Does tcpdump record the mysql passwords? I'd like to, but I'm not sure I can send a dump of my staging or production environment if it has this info. And Packetbeat isn't configured to run on my local dev environment.

[packetb-old]

Most likely it will contain only a hash of the password, but the trace could also contain other sensitive data, so best is to look into it with Wireshark before sending. Since this is likely the same issue as #54 you could also wait until our release next week and simply check if the problem is not already solved. Thanks.

[packetb-old]

Closing this one because release 0.3.2, which likely fixes this, is now available. Please reopen if this is not the case.

[Regala]

Hi,

it seems this issue still exists?

root@x/home/x # packetbeat -e -c /etc/packetbeat/packetbeat.conf -d "mysql,mysqldetailed"
output_elasticsearch.go:58: INFO [ElasticsearchOutput] Using Elasticsearch http://x.com:8080
output_elasticsearch.go:59: INFO [ElasticsearchOutput] Using index pattern [packetbeat-]YYYY.MM.DD
output_elasticsearch.go:60: INFO [ElasticsearchOutput] Topology expires after 15s
publish.go:264: WARN No output is defined to store the topology. The server fields might not be filled.
publish.go:276: INFO No agent name configured, using hostname 'x'
geolite.go:59: INFO Loaded GeoIP data from: /usr/share/GeoIP/GeoIP.dat
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:349: WARN Postgresql Message too short. 4E (length=1). Wait for more.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:822: WARN Response from unknown transaction. Ignoring.
pgsql.go:546: WARN Postgresql Message too short (length=2). Wait for more.

Using packetbeat 0.5.0.

[tsg]

This can have multiple causes. Since it's about postgres, could it be SSL? See #48

If not, it would be great if you could send us a trace, see the "Recording a trace" section from here: http://packetbeat.com/docs/troubleshooting.html

[Regala]

Right! Yes, that's probably it. Thanks :-)

[adelbot]

Is it possible to have the http timeout with sp�cial error code ?

Alain

Post-scriptum La Poste

Ce message est confidentiel. Sous reserve de tout accord conclu par
ecrit entre vous et La Poste, son contenu ne represente en aucun cas un
engagement de la part de La Poste. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee prealablement. Si vous
n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur.