Sign transaction error: session not found

[Zimbakin]

• Trezor Model T
• firmware 2.3.4
• Trezor suite 20.12.1
• Mac OS

Sending from Account 1 P2SH address to newly created Account 2 with new P2SH address returns error:
Sign transaction error: session not found
Trezor model T freezes.

[prusnak]

Try different USB cable, different port, etc.

This is not a bug in Suite, but in communication with the device.

[matejcik]

could also be a Bridge problem.
this forum user reports same problem: https://forum.trezor.io/t/sign-transaction-error-session-not-found-aug-29-2021-12-28/2463

in that case, using web suite + webusb resolved the problem

[petrkr]

Hello,
recently I get similar problem with Trezor One on huge transactions which took long to sign.

Suite: 21.12.2
Bridge: 31 (same issue on 29)
FW One: 1.10.4 (same issue on 1.10.3)

EDIT: I can confirm WebUSB (thrught web based suite) works fine. So it's just in bridge

most recent interesing log from verbose bridge calls during signature:

[154.545347 : 12:00:45] POST /call/4
[154.545398 : 12:00:45] [server/api/api.go 196 server/api.(*api).call] start
[154.545425 : 12:00:45] [core/core.go 568 core.(*Core).Call] checking other call on same session
[154.545438 : 12:00:45] [core/core.go 574 core.(*Core).Call] checking other call on same session done
[154.545451 : 12:00:45] [core/core.go 599 core.(*Core).Call] before actual logic
[154.545462 : 12:00:45] [core/core.go 607 core.(*Core).writeDev] decodeRaw
[154.545474 : 12:00:45] [core/core.go 659 core.(*Core).decodeRaw] readAll
[154.545483 : 12:00:45] [core/core.go 661 core.(*Core).decodeRaw] decodeString
[154.545494 : 12:00:45] [core/core.go 681 core.(*Core).decodeRaw] returning
[154.545504 : 12:00:45] [core/core.go 613 core.(*Core).writeDev] writeTo
[154.545512 : 12:00:45] [wire/v1.go 25 wire.(*Message).WriteTo] start
[154.545521 : 12:00:45] [wire/v1.go 39 wire.(*Message).WriteTo] actually writing
[154.545532 : 12:00:45] [usb/libusb.go 555 usb.(*LibUSBDevice).Write] write start
[154.545542 : 12:00:45] [usb/libusb.go 505 usb.(*LibUSBDevice).readWrite] start
[154.545551 : 12:00:45] [usb/libusb.go 507 usb.(*LibUSBDevice).readWrite] checking closed
[154.545564 : 12:00:45] [usb/libusb.go 515 usb.(*LibUSBDevice).readWrite] actual interrupt transport
[154.546128 : 12:00:45] [usb/libusb.go 519 usb.(*LibUSBDevice).readWrite] single transfer done
[154.546144 : 12:00:45] [usb/libusb.go 535 usb.(*LibUSBDevice).readWrite] single transfer successful
[154.546158 : 12:00:45] [core/core.go 619 core.(*Core).readDev] readFrom
[154.546171 : 12:00:45] [wire/v1.go 76 wire.ReadFrom] start
[154.546183 : 12:00:45] [usb/libusb.go 569 usb.(*LibUSBDevice).Read] read start
[154.546195 : 12:00:45] [usb/libusb.go 505 usb.(*LibUSBDevice).readWrite] start
[154.546208 : 12:00:45] [usb/libusb.go 507 usb.(*LibUSBDevice).readWrite] checking closed
[154.546221 : 12:00:45] [usb/libusb.go 515 usb.(*LibUSBDevice).readWrite] actual interrupt transport
[154.547112 : 12:00:45] [usb/libusb.go 519 usb.(*LibUSBDevice).readWrite] single transfer done
[154.547125 : 12:00:45] [usb/libusb.go 535 usb.(*LibUSBDevice).readWrite] single transfer successful
[154.547135 : 12:00:45] [wire/v1.go 96 wire.ReadFrom] actual reading started
[154.547144 : 12:00:45] [wire/v1.go 119 wire.ReadFrom] actual reading finished
[154.547154 : 12:00:45] [core/core.go 625 core.(*Core).readDev] encoding back
[154.547163 : 12:00:45] [core/core.go 691 core.(*Core).encodeRaw] start
[154.547172 : 12:00:45] [core/core.go 601 core.(*Core).Call] after actual logic
127.0.0.1 - - [29/Dec/2021:12:00:45 +0100] "POST /call/4 HTTP/1.1" 200 92
[154.547189 : 12:00:45] 127.0.0.1 - - [29/Dec/2021:12:00:45 +0100] "POST /call/4 HTTP/1.1" 200 92

Here maybe ?

[154.547251 : 12:00:45] [core/core.go 590 core.(*Core).Call.func4] detected request close context canceled, auto-release


[154.547266 : 12:00:45] [core/core.go 359 core.(*Core).release] session 4
[154.547275 : 12:00:45] [core/core.go 368 core.(*Core).release] bus close
[154.547281 : 12:00:45] [usb/libusb.go 436 usb.(*LibUSBDevice).Close] storing d.closed
[154.547288 : 12:00:45] [usb/libusb.go 444 usb.(*LibUSBDevice).Close] canceling previous transfers
[154.547295 : 12:00:45] [usb/libusb.go 453 usb.(*LibUSBDevice).Close] finishing read queue
[154.547302 : 12:00:45] [usb/libusb.go 498 usb.(*LibUSBDevice).finishReadQueue] transfer
POST /call/4
[154.551047 : 12:00:45] POST /call/4
[154.551112 : 12:00:45] [server/api/api.go 196 server/api.(*api).call] start
[154.551148 : 12:00:45] [server/api/api.go 277 server/api.(*api).respondError] Returning error: session not found
127.0.0.1 - - [29/Dec/2021:12:00:45 +0100] "POST /call/4 HTTP/1.1" 400 30
[154.551227 : 12:00:45] 127.0.0.1 - - [29/Dec/2021:12:00:45 +0100] "POST /call/4 HTTP/1.1" 400 30
POST /release/4
[154.563856 : 12:00:45] POST /release/4
[154.563904 : 12:00:45] [server/api/api.go 154 server/api.(*api).release] start
[154.563921 : 12:00:45] [core/core.go 359 core.(*Core).release] session 4
[154.563934 : 12:00:45] [core/core.go 363 core.(*Core).release] session not found
[154.563948 : 12:00:45] [server/api/api.go 277 server/api.(*api).respondError] Returning error: session not found
127.0.0.1 - - [29/Dec/2021:12:00:45 +0100] "POST /release/4 HTTP/1.1" 400 30
[154.563976 : 12:00:45] 127.0.0.1 - - [29/Dec/2021:12:00:45 +0100] "POST /release/4 HTTP/1.1" 400 30
[154.597499 : 12:00:45] [usb/libusb.go 458 usb.(*LibUSBDevice).Close] releasing interface
[154.597547 : 12:00:45] [usb/libusb.go 477 usb.(*LibUSBDevice).Close] low level close
[154.597573 : 12:00:45] [usb/libusb.go 479 usb.(*LibUSBDevice).Close] done

[prusnak]

Thanks, reopening

[mroz22]

I have also found a similar, maybe related, case trezor/connect#948

[STew790]

I tried to reproduce this issue in the recent version of Suite (22.1.1 e7262e5) but I wasn't successful yet. Nonetheless, I will be monitoring this issue and as soon as I find something, I will add it here.

[STew790]

I tried to reproduce this issue throughout the past month on various versions of Suite and I wasn't successful.
Let us know if you get this issue again, please.
Closing (could not reproduce).

[petrkr]

Problem still persist on latest suite, trezord and Trezor One firmware

Trezor suite: 22.5.2
Trezord (bridge) used from suite bundle: v2.0.31 (rev 5f53132)
Trezor one FW: 1.11.1

When trying to sign huge UTXO input TX, trezor session not found occurres.

I can provide some debugging cooperation. I do not know why it is this closed if is NOT fixed yet... It is really problem if you can not send transaction and you have to send by smaller parts which you have to again merge (so you are able to send higher amount).

More testing:
Web suite (https://suite.trezor.io/web) on WebUSB (trezord is shutdown) - Works
Web suite with trezord - causes session not found, but not so often and only on really huge inputs
Suite AppImage with trezord (regardless if bundle version or own systemd version) - causes session not found almost on every bigger transaction

I logged communication between trezord by wireshark, but nothing much I can see there.. Only POST 200, and then two POST will return "400 Bad request" with payload "Session not found".

So probably better logging of trezord is needed to investigate this.

[petrkr]

Well I probably found something what can be connected with it...

There is some long request to bridge (/listen) which hangs response for like 30 secods (or maybe until some /calls or /release are called? Did not checked code well yet.

In closer filter you can see this response came after 30 sec to the client...

Maybe those asynchronous calls can be reason? I will check something like parallel requests from electron. And something like re-use connections (now I can see it reopen new TCP connection for every call)