Difference between revisions of "Error"
From Obyte Wiki
m (added wikilink) |
(→huh?: changed note) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
| could not send payment: precommit callback failed || smart wallet containing committed funds that only the counter-party can now spend | | could not send payment: precommit callback failed || smart wallet containing committed funds that only the counter-party can now spend | ||
|- | |- | ||
| − | | could not send payment: authentifier verification failed || smart contract conditions not fulfilled | + | | could not send payment: authentifier verification failed || [[smart contract]] conditions not fulfilled |
|- | |- | ||
| could not send payment: known bad || if you try a bad send repeatedly | | could not send payment: known bad || if you try a bad send repeatedly | ||
| Line 31: | Line 31: | ||
| unable to find parents; failed to find compatible parents: no deep units || witness error, such as (user) swapping out two at once | | unable to find parents; failed to find compatible parents: no deep units || witness error, such as (user) swapping out two at once | ||
|- | |- | ||
| − | | Syncing -- | + | | Syncing -- __ private payments left (Android) || probably a connection problem |
| + | |- | ||
| + | | Uncaught exception: Error: Error: SQLITE_ERROR: no such index: outputsIsSerial SELECT unit, message_index, sequence FROM outputs INDEXED BY outputsIsSerial JOIN units USING(unit) WHERE outputs.is_serial IS NULL AND units.is_stable=1 AND is_spent=0 || Likely due to restoring a full backup on a new wallet when the original full backup was an older wallet version. Try downloading a legacy wallet to restore and send funds to the new version | ||
|} | |} | ||
Latest revision as of 07:05, 15 May 2019
Error messages in the wallet and (maybe) how to fix them.
Contents
huh?
Table information collection in progress. Please contact @slackjore with any info.
| Error message | Notes |
|---|---|
| could not send payment: bad signature at path r | look under the table |
| could not send payment: precommit callback failed | smart wallet containing committed funds that only the counter-party can now spend |
| could not send payment: authentifier verification failed | smart contract conditions not fulfilled |
| could not send payment: known bad | if you try a bad send repeatedly |
| could not create payment proposal: No bytes to pay fees | so send bytes to wallet |
| connect to light vendor failed [socket closed] | firewall? turn off Tor? (light vendor = hub) |
| ??? | incoming payment not confirmed yet, so wait another 5 minutes or so |
| [internal] connection closed | maybe non-functioning hub: change to another hub |
| unable to verify the first certificate | ??? |
| too many messages, try sending a smaller amount [of blackbytes] | send smaller amounts |
| on login “Uncaught exception: Error: message encrypted to unknown key, device" | don't click ok; right click > "inspect" > delete the window in the html code ; restart |
| unable to find parents; failed to find compatible parents: no deep units | witness error, such as (user) swapping out two at once |
| Syncing -- __ private payments left (Android) | probably a connection problem |
| Uncaught exception: Error: Error: SQLITE_ERROR: no such index: outputsIsSerial SELECT unit, message_index, sequence FROM outputs INDEXED BY outputsIsSerial JOIN units USING(unit) WHERE outputs.is_serial IS NULL AND units.is_stable=1 AND is_spent=0 | Likely due to restoring a full backup on a new wallet when the original full backup was an older wallet version. Try downloading a legacy wallet to restore and send funds to the new version |
Comments
tonych [10:43 AM 2017-06-14 #helpdesk]:
Bad signature at path r is a mysterious bug that affected a few users in the past but there is no clarity about its nature. Are you on android, did you send any payments from this wallet before? any other unusual actions with this wallet?
