-
Notifications
You must be signed in to change notification settings - Fork 493
Error Codes
Lex Berezhny edited this page Jul 30, 2018
·
12 revisions
Proposal for consistent error codes across the entire lbrynet API.
Code | Name |
---|---|
1xx | Daemon start other CLI command Failures (non-recoverable) |
10x | Meta error codes not presented by lbrynet itself but from apps trying to interact with lbrynet . |
100 | Cannot find the lbrynet command. |
101 | Permission denied trying to execute lbrynet command. |
102 | Executing lbrynet command does not produce any result. |
103 | Executing lbrynet produces a result that is not normal (eg. a segfault). |
11x | Enough of lbrynet was able to start to determine external factors causing eventual startup failure. |
110 | Out of disk space. |
111 | Out of RAM. |
12x | 120-129 Internal factors preventing lbrynet from bootstrapping itself. |
120 | Incompatible version of Python. |
121 | Incompatible version of some library. |
13x | 130-139 configuration errors |
130 | Cannot write configuration file. (When writing the default config fails on startup, such as due to permission issues.) |
131 | Cannot find provided configuration file. (Can't open the config file user provided via command line args.) |
132 | Failed to parse the configuration file. (Includes the syntax error / line number to help user fix it.) |
133 | Configuration file is missing setting that has no default / fallback. |
134 | Configuration file has setting set to an invalid value. |
14x | 140-149 executing commands |
140 | Command does not exist. |
141 | Command is deprecated. |
142 | Invalid arguments for command. |
2xx | Networking |
201 | Not internet connection. |
202 | Router does not support UPnP. |
210 | Failed connecting to a lbryumx server. (Should normally not need to be handled higher up as lbrynet will retry other servers.) |
211 | Failed connecting to all known lbryumx servers. (Will need to bubble up and require user to do something.) |
212 | lbryumx droppped our connection. (Maybe we were being bad?) |
213 | Disconnected from lbryumx server due to suspicious responses. (SPV failed to validate, etc) |
214 | Disconnected from lbryumx server due to unresponsiveness. |
215 | 215-229 TBD lbryumx connectivity errors. |
230 | 230-249 P2P / blob download errors. |
250 | 250 - 299 TBD DHT errors. |
3xx | Blockchain |
300 | Transaction rejected, unknown reason. |
301 | Transaction rejected, fees too low. |
310 | Not enough LBC to cover the transaction, even after all UTXOs reach 6 confirmations. |
311 | Not enough LBC to cover the transaction, will be enough after some more confirmations. |
330 | Channel signing key not found. |
331 | Channel signing key is out of date. (For example, channel was updated but you don't have the updated key.) |
4xx | Blobs |
400 | Blob not found. |