Closed snow884 closed 1 year ago
Are you able to reproduce this on master w/ a clean install?
Hi @Roasbeef , no this error is not reproducible.
This error seems to occur when I am running tarod for a long time after I send myself an asset.
I almost always get this when I let tarod running over night.
Here is a new log:
[ec2-user@ip-172-31-85-57 ~]$ tarod --network=testnet --debuglevel=debug --lnd.host=localhost:10009 --lnd.macaroonpath=/home/ec2-user/.lnd/data/chain/bitcoin/testnet/admin.macaroon --lnd.tlspath=/home/ec2-user/.lnd/tls.cert --tarodir=/home/ec2-user/.taro --rpclisten=127.0.0.1:10029 --restlisten=127.0.0.1:8089 --batch-minting-interval=1m
2023-01-06 09:26:07.573 [WRN] CONF: open /home/ec2-user/.taro/taro.conf: no such file or directory
2023-01-06 09:26:07.574 [INF] CONF: Opening sqlite3 database at: /home/ec2-user/.taro/data/testnet/taro.db
2023-01-06 09:26:07.578 [INF] CONF: Attempting to establish connection to lnd...
2023-01-06 09:26:07.588 [INF] CONF: lnd connection initialized
2023-01-06 09:26:07.588 [INF] SRVR: Version: 0.1.99-alpha commit=v0.1.1-alpha-93-gddb0e0d, build=production, logging=default, debuglevel=debug
2023-01-06 09:26:07.588 [INF] SRVR: Active network: testnet3
2023-01-06 09:26:07.589 [INF] RPCS: Validating RPC requests based on macaroon at: /home/ec2-user/.taro/data/testnet/admin.macaroon
2023-01-06 09:26:07.589 [INF] RPCS: RPC server listening on 127.0.0.1:10029
2023-01-06 09:26:07.589 [INF] RPCS: gRPC proxy started at 127.0.0.1:8089
2023-01-06 09:26:07.589 [INF] GRDN: Starting ChainPlanter
2023-01-06 09:26:07.589 [INF] GRDN: Retrieved 0 non-finalized batches from DB
2023-01-06 09:26:07.589 [INF] GRDN: Starting asset custodian
2023-01-06 09:26:07.590 [INF] FRTR: Starting ChainPorter
2023-01-06 09:26:07.590 [INF] FRTR: Resuming delivery of 0 pending asset parcels
2023-01-06 09:26:07.590 [INF] RPCS: Starting RPC Server
2023-01-06 09:26:07.590 [INF] SRVR: Taro Daemon fully active!
2023-01-06 09:26:07.591 [INF] GRDN: Gardener for ChainPlanter now active!
2023-01-06 09:26:07.591 [DBG] GRDN: Subscribing to new on-chain transactions
2023-01-06 09:26:07.591 [INF] GRDN: Loading pending inbound asset events
2023-01-06 09:26:07.592 [INF] GRDN: Resuming 1 pending inbound asset events
2023-01-06 09:26:07.593 [ERR] SRVR: Shutting down because error in main method: received critical error from subsystem: error fetching asset proof: sql: no rows in result set
2023-01-06 09:26:07.593 [INF] RPCS: Stopping RPC Server
2023-01-06 09:26:07.593 [INF] SRVR: Shutdown complete
received critical error from subsystem: error fetching asset proof: sql: no rows in result set
Hi @snow884 , do you see any proof files on disk?
@snow884 we're taking a look at this, can you provide the requested info?
Hi @jharveyb ,
Thanks a lot for picking this up.
I am sorry I no longer have access to the environment where the issue occurred.
@dstadulis I cannot provide the info.
The issue seems to be related to neutrino . When I use bitcoind I do not get this error anymore.
Could have been a follow-up error after https://github.com/lightninglabs/taro/issues/228 left the DB in an incomplete state. Or something around Neutrino (which I don't believe we are currently prioritizing to support). So going to close this with the intent to re-open if more people run into this.
My tarod keeps crashing with the error:
This happened after I tried minting an multiple assets in a row using commands that looked like this:
My LND commit hash is: c03de26dc My Taro commit hash is: ddb0e0d
I have built LND using the command:
Executing the commands:
Produces the log: