aboutsummaryrefslogtreecommitdiff
path: root/gnu-taler-error-codes
diff options
context:
space:
mode:
authorChristian Grothoff <grothoff@gnunet.org>2024-02-10 11:33:14 +0100
committerChristian Grothoff <grothoff@gnunet.org>2024-02-10 11:33:14 +0100
commit4728c9e60ce121f439b3db30cc08f06ff0beff71 (patch)
treee24734e4fdbf5b18e6f5f4e8a6990b5ab747496f /gnu-taler-error-codes
parent06b19cd6f11396e11b95e5480e4b07897f3663e7 (diff)
downloadgana-4728c9e60ce121f439b3db30cc08f06ff0beff71.tar.gz
gana-4728c9e60ce121f439b3db30cc08f06ff0beff71.zip
more error message review
Diffstat (limited to 'gnu-taler-error-codes')
-rw-r--r--gnu-taler-error-codes/registry.rec49
1 files changed, 25 insertions, 24 deletions
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec
index 1428077..bc429fd 100644
--- a/gnu-taler-error-codes/registry.rec
+++ b/gnu-taler-error-codes/registry.rec
@@ -102,27 +102,28 @@ HttpStatus: 400
102 102
103Value: 24 103Value: 24
104Name: GENERIC_PAYTO_URI_MALFORMED 104Name: GENERIC_PAYTO_URI_MALFORMED
105Description: The payto:// URI provided by the client is malformed. 105Description: The payto:// URI provided by the client is malformed. Check that you are using the correct syntax as of RFC 8905 and/or that you entered the bank account number correctly.
106HttpStatus: 400 106HttpStatus: 400
107 107
108Value: 25 108Value: 25
109Name: GENERIC_PARAMETER_MISSING 109Name: GENERIC_PARAMETER_MISSING
110Description: A required parameter in the request was missing. 110Description: A required parameter in the request was missing. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
111HttpStatus: 400 111HttpStatus: 400
112 112
113Value: 26 113Value: 26
114Name: GENERIC_PARAMETER_MALFORMED 114Name: GENERIC_PARAMETER_MALFORMED
115Description: A parameter in the request was malformed. 115Description: A parameter in the request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
116HttpStatus: 400 116HttpStatus: 400
117 117
118Value: 27 118Value: 27
119Name: GENERIC_RESERVE_PUB_MALFORMED 119Name: GENERIC_RESERVE_PUB_MALFORMED
120Description: The reserve public key given as part of a /reserves/ endpoint was malformed. 120Description: The reserve public key was malformed.
121HttpStatus: 400 121HttpStatus: 400
122FIXME: Fold with 26?
122 123
123Value: 28 124Value: 28
124Name: GENERIC_COMPRESSION_INVALID 125Name: GENERIC_COMPRESSION_INVALID
125Description: The body in the request could not be decompressed by the server. 126Description: The body in the request could not be decompressed by the server. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
126HttpStatus: 400 127HttpStatus: 400
127 128
128# Circumstantial client-side protocol problems (30-39) 129# Circumstantial client-side protocol problems (30-39)
@@ -130,17 +131,17 @@ HttpStatus: 400
130 131
131Value: 30 132Value: 30
132Name: GENERIC_CURRENCY_MISMATCH 133Name: GENERIC_CURRENCY_MISMATCH
133Description: The currency involved in the operation is not acceptable for this backend. 134Description: The currency involved in the operation is not acceptable for this server. Check your configuration and make sure the currency specified for a given service provider is one of the currencies supported by that provider.
134HttpStatus: 400 135HttpStatus: 400
135 136
136Value: 31 137Value: 31
137Name: GENERIC_URI_TOO_LONG 138Name: GENERIC_URI_TOO_LONG
138Description: The URI is longer than the longest URI the HTTP server is willing to parse. 139Description: The URI is longer than the longest URI the HTTP server is willing to parse. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
139HttpStatus: 414 140HttpStatus: 414
140 141
141Value: 32 142Value: 32
142Name: GENERIC_UPLOAD_EXCEEDS_LIMIT 143Name: GENERIC_UPLOAD_EXCEEDS_LIMIT
143Description: The body is too large to be permissible for the endpoint. 144Description: The body is too large to be permissible for the endpoint. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
144HttpStatus: 413 145HttpStatus: 413
145 146
146 147
@@ -174,37 +175,37 @@ HttpStatus: 403
174 175
175Value: 50 176Value: 50
176Name: GENERIC_DB_SETUP_FAILED 177Name: GENERIC_DB_SETUP_FAILED
177Description: The service failed initialize its connection to the database. 178Description: The service failed initialize its connection to the database. The system administrator should check that the service has permissions to access the database and that the database is running.
178HttpStatus: 500 179HttpStatus: 500
179 180
180Value: 51 181Value: 51
181Name: GENERIC_DB_START_FAILED 182Name: GENERIC_DB_START_FAILED
182Description: The service encountered an error event to just start the database transaction. 183Description: The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
183HttpStatus: 500 184HttpStatus: 500
184 185
185Value: 52 186Value: 52
186Name: GENERIC_DB_STORE_FAILED 187Name: GENERIC_DB_STORE_FAILED
187Description: The service failed to store information in its database. 188Description: The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
188HttpStatus: 500 189HttpStatus: 500
189 190
190Value: 53 191Value: 53
191Name: GENERIC_DB_FETCH_FAILED 192Name: GENERIC_DB_FETCH_FAILED
192Description: The service failed to fetch information from its database. 193Description: The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
193HttpStatus: 500 194HttpStatus: 500
194 195
195Value: 54 196Value: 54
196Name: GENERIC_DB_COMMIT_FAILED 197Name: GENERIC_DB_COMMIT_FAILED
197Description: The service encountered an error event to commit the database transaction (hard, unrecoverable error). 198Description: The service encountered an unrecoverable error trying to commit a transaction to the database. The system administrator should check that the database is running and review the service logs.
198HttpStatus: 500 199HttpStatus: 500
199 200
200Value: 55 201Value: 55
201Name: GENERIC_DB_SOFT_FAILURE 202Name: GENERIC_DB_SOFT_FAILURE
202Description: The service encountered an error event to commit the database transaction, even after repeatedly retrying it there was always a conflicting transaction. (This indicates a repeated serialization error; should only happen if some client maliciously tries to create conflicting concurrent transactions.) 203Description: The service encountered an error event to commit the database transaction, even after repeatedly retrying it there was always a conflicting transaction. This indicates a repeated serialization error; it should only happen if some client maliciously tries to create conflicting concurrent transactions. It could also be a sign of a missing index. Check if you are using the latest available version and/or file a report with the developers.
203HttpStatus: 500 204HttpStatus: 500
204 205
205Value: 56 206Value: 56
206Name: GENERIC_DB_INVARIANT_FAILURE 207Name: GENERIC_DB_INVARIANT_FAILURE
207Description: The service's database is inconsistent and violates service-internal invariants. 208Description: The service's database is inconsistent and violates service-internal invariants. Check if you are using the latest available version and/or file a report with the developers.
208HttpStatus: 500 209HttpStatus: 500
209 210
210 211
@@ -212,17 +213,17 @@ HttpStatus: 500
212 213
213Value: 60 214Value: 60
214Name: GENERIC_INTERNAL_INVARIANT_FAILURE 215Name: GENERIC_INTERNAL_INVARIANT_FAILURE
215Description: The HTTP server experienced an internal invariant failure (bug). 216Description: The HTTP server experienced an internal invariant failure (bug). Check if you are using the latest available version and/or file a report with the developers.
216HttpStatus: 500 217HttpStatus: 500
217 218
218Value: 61 219Value: 61
219Name: GENERIC_FAILED_COMPUTE_JSON_HASH 220Name: GENERIC_FAILED_COMPUTE_JSON_HASH
220Description: The service could not compute a cryptographic hash over some JSON value. 221Description: The service could not compute a cryptographic hash over some JSON value. Check if you are using the latest available version and/or file a report with the developers.
221HttpStatus: 500 222HttpStatus: 500
222 223
223Value: 62 224Value: 62
224Name: GENERIC_FAILED_COMPUTE_AMOUNT 225Name: GENERIC_FAILED_COMPUTE_AMOUNT
225Description: The service could not compute an amount. 226Description: The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
226HttpStatus: 500 227HttpStatus: 500
227 228
228 229
@@ -230,32 +231,32 @@ HttpStatus: 500
230 231
231Value: 70 232Value: 70
232Name: GENERIC_PARSER_OUT_OF_MEMORY 233Name: GENERIC_PARSER_OUT_OF_MEMORY
233Description: The HTTP server had insufficient memory to parse the request. 234Description: The HTTP server had insufficient memory to parse the request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
234HttpStatus: 500 235HttpStatus: 500
235 236
236Value: 71 237Value: 71
237Name: GENERIC_ALLOCATION_FAILURE 238Name: GENERIC_ALLOCATION_FAILURE
238Description: The HTTP server failed to allocate memory. 239Description: The HTTP server failed to allocate memory. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
239HttpStatus: 500 240HttpStatus: 500
240 241
241Value: 72 242Value: 72
242Name: GENERIC_JSON_ALLOCATION_FAILURE 243Name: GENERIC_JSON_ALLOCATION_FAILURE
243Description: The HTTP server failed to allocate memory for building JSON reply. 244Description: The HTTP server failed to allocate memory for building JSON reply. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
244HttpStatus: 500 245HttpStatus: 500
245 246
246Value: 73 247Value: 73
247Name: GENERIC_CURL_ALLOCATION_FAILURE 248Name: GENERIC_CURL_ALLOCATION_FAILURE
248Description: The HTTP server failed to allocate memory for making a CURL request. 249Description: The HTTP server failed to allocate memory for making a CURL request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
249HttpStatus: 500 250HttpStatus: 500
250 251
251Value: 74 252Value: 74
252Name: GENERIC_FAILED_TO_LOAD_TEMPLATE 253Name: GENERIC_FAILED_TO_LOAD_TEMPLATE
253Description: The backend could not locate a required template to generate an HTML reply. 254Description: The backend could not locate a required template to generate an HTML reply. The system administrator should check if the resource files are installed in the correct location and are readable to the service.
254HttpStatus: 500 255HttpStatus: 500
255 256
256Value: 75 257Value: 75
257Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE 258Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE
258Description: The backend could not expand the template to generate an HTML reply. 259Description: The backend could not expand the template to generate an HTML reply. The system administrator should investigate the logs and check if the templates are well-formed.
259HttpStatus: 500 260HttpStatus: 500
260 261
261 262