Diagnosing problems and troubleshooting

If you experience any problems while setting up your network, we are here to help. Logs created by the nodes will help us classify any problems and suggest solutions. The log levels used are info, debug, and trace. This section outlines how to diagnose and solve some problems that you may encounter:

Problem: Failed reading: Your input is either malformed or not hex encoded:

--tx-in f5296e996940b1c81f781594293d423b4250a454f5832b0740a923f74460d34#1 \
--tx-out $(cat payment2.addr)+100000000 \
--tx-out $(cat payment.addr)+899832033 \
--ttl 335000 --fee 167965 \
--out-file tx001.raw
malformed or not hex encoded: 

Diagnosis: tx-in is not a valid UTXO

Solution: Make sure that you are using a correct UTXO. You can query this with:

 --address $(cat payment.addr) \
 --testnet-magic 42

Problem: ExpiredUTxO

> --tx-file tx001.signed \
> --testnet-magic 42

Diagnosis: TTL has already passed.

Solution: Look at pfUTXOttl and pfUTXOcurrentSlot. Current Slot is ahead of UTXOttl.

Build a new transaction with a TTL (time to live) higher than Current Slot. As a rule of thumb, you will need between 300-500 slots to build, sign, and submit the transaction.

Problem: ValueNotConservedUTxO

> --tx-file tx001.signed \
> --testnet-magic 42

Diagnosis: Value not Conserved: (Input UTXO ≠ Fee + Amount sent + Change)

Solution: Check that output amount is equal to input amount

Problem: BadInputsUTxO

--tx-file tx001.signed \
--testnet-magic 42

Diagnosis: Bad UTXO transaction index

Solution: Verify the UTXO transaction index using:

 --address $(cat payment.addr) \
 --testnet-magic 42
7f1d95ce599c84064c61903c0b1334c826b55c48a1.... 1      1000000000000

We encourage you to share your ideas and suggestions on our dedicated support page so that we can create a library of solutions and support for the tasks that you need to perform.

Last updated: May 1, 2020 08:00 UTC