diff options
author | Christian Grothoff <grothoff@gnunet.org> | 2024-02-10 11:33:14 +0100 |
---|---|---|
committer | Christian Grothoff <grothoff@gnunet.org> | 2024-02-10 11:33:14 +0100 |
commit | 4728c9e60ce121f439b3db30cc08f06ff0beff71 (patch) | |
tree | e24734e4fdbf5b18e6f5f4e8a6990b5ab747496f /gnu-taler-error-codes | |
parent | 06b19cd6f11396e11b95e5480e4b07897f3663e7 (diff) | |
download | gana-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.rec | 49 |
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 | ||
103 | Value: 24 | 103 | Value: 24 |
104 | Name: GENERIC_PAYTO_URI_MALFORMED | 104 | Name: GENERIC_PAYTO_URI_MALFORMED |
105 | Description: The payto:// URI provided by the client is malformed. | 105 | Description: 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. |
106 | HttpStatus: 400 | 106 | HttpStatus: 400 |
107 | 107 | ||
108 | Value: 25 | 108 | Value: 25 |
109 | Name: GENERIC_PARAMETER_MISSING | 109 | Name: GENERIC_PARAMETER_MISSING |
110 | Description: A required parameter in the request was missing. | 110 | Description: 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. |
111 | HttpStatus: 400 | 111 | HttpStatus: 400 |
112 | 112 | ||
113 | Value: 26 | 113 | Value: 26 |
114 | Name: GENERIC_PARAMETER_MALFORMED | 114 | Name: GENERIC_PARAMETER_MALFORMED |
115 | Description: A parameter in the request was malformed. | 115 | Description: 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. |
116 | HttpStatus: 400 | 116 | HttpStatus: 400 |
117 | 117 | ||
118 | Value: 27 | 118 | Value: 27 |
119 | Name: GENERIC_RESERVE_PUB_MALFORMED | 119 | Name: GENERIC_RESERVE_PUB_MALFORMED |
120 | Description: The reserve public key given as part of a /reserves/ endpoint was malformed. | 120 | Description: The reserve public key was malformed. |
121 | HttpStatus: 400 | 121 | HttpStatus: 400 |
122 | FIXME: Fold with 26? | ||
122 | 123 | ||
123 | Value: 28 | 124 | Value: 28 |
124 | Name: GENERIC_COMPRESSION_INVALID | 125 | Name: GENERIC_COMPRESSION_INVALID |
125 | Description: The body in the request could not be decompressed by the server. | 126 | Description: 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. |
126 | HttpStatus: 400 | 127 | HttpStatus: 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 | ||
131 | Value: 30 | 132 | Value: 30 |
132 | Name: GENERIC_CURRENCY_MISMATCH | 133 | Name: GENERIC_CURRENCY_MISMATCH |
133 | Description: The currency involved in the operation is not acceptable for this backend. | 134 | Description: 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. |
134 | HttpStatus: 400 | 135 | HttpStatus: 400 |
135 | 136 | ||
136 | Value: 31 | 137 | Value: 31 |
137 | Name: GENERIC_URI_TOO_LONG | 138 | Name: GENERIC_URI_TOO_LONG |
138 | Description: The URI is longer than the longest URI the HTTP server is willing to parse. | 139 | Description: 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. |
139 | HttpStatus: 414 | 140 | HttpStatus: 414 |
140 | 141 | ||
141 | Value: 32 | 142 | Value: 32 |
142 | Name: GENERIC_UPLOAD_EXCEEDS_LIMIT | 143 | Name: GENERIC_UPLOAD_EXCEEDS_LIMIT |
143 | Description: The body is too large to be permissible for the endpoint. | 144 | Description: 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. |
144 | HttpStatus: 413 | 145 | HttpStatus: 413 |
145 | 146 | ||
146 | 147 | ||
@@ -174,37 +175,37 @@ HttpStatus: 403 | |||
174 | 175 | ||
175 | Value: 50 | 176 | Value: 50 |
176 | Name: GENERIC_DB_SETUP_FAILED | 177 | Name: GENERIC_DB_SETUP_FAILED |
177 | Description: The service failed initialize its connection to the database. | 178 | Description: 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. |
178 | HttpStatus: 500 | 179 | HttpStatus: 500 |
179 | 180 | ||
180 | Value: 51 | 181 | Value: 51 |
181 | Name: GENERIC_DB_START_FAILED | 182 | Name: GENERIC_DB_START_FAILED |
182 | Description: The service encountered an error event to just start the database transaction. | 183 | Description: The service encountered an error event to just start the database transaction. The system administrator should check that the database is running. |
183 | HttpStatus: 500 | 184 | HttpStatus: 500 |
184 | 185 | ||
185 | Value: 52 | 186 | Value: 52 |
186 | Name: GENERIC_DB_STORE_FAILED | 187 | Name: GENERIC_DB_STORE_FAILED |
187 | Description: The service failed to store information in its database. | 188 | Description: The service failed to store information in its database. The system administrator should check that the database is running and review the service logs. |
188 | HttpStatus: 500 | 189 | HttpStatus: 500 |
189 | 190 | ||
190 | Value: 53 | 191 | Value: 53 |
191 | Name: GENERIC_DB_FETCH_FAILED | 192 | Name: GENERIC_DB_FETCH_FAILED |
192 | Description: The service failed to fetch information from its database. | 193 | Description: The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs. |
193 | HttpStatus: 500 | 194 | HttpStatus: 500 |
194 | 195 | ||
195 | Value: 54 | 196 | Value: 54 |
196 | Name: GENERIC_DB_COMMIT_FAILED | 197 | Name: GENERIC_DB_COMMIT_FAILED |
197 | Description: The service encountered an error event to commit the database transaction (hard, unrecoverable error). | 198 | Description: 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. |
198 | HttpStatus: 500 | 199 | HttpStatus: 500 |
199 | 200 | ||
200 | Value: 55 | 201 | Value: 55 |
201 | Name: GENERIC_DB_SOFT_FAILURE | 202 | Name: GENERIC_DB_SOFT_FAILURE |
202 | Description: 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.) | 203 | Description: 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. |
203 | HttpStatus: 500 | 204 | HttpStatus: 500 |
204 | 205 | ||
205 | Value: 56 | 206 | Value: 56 |
206 | Name: GENERIC_DB_INVARIANT_FAILURE | 207 | Name: GENERIC_DB_INVARIANT_FAILURE |
207 | Description: The service's database is inconsistent and violates service-internal invariants. | 208 | Description: 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. |
208 | HttpStatus: 500 | 209 | HttpStatus: 500 |
209 | 210 | ||
210 | 211 | ||
@@ -212,17 +213,17 @@ HttpStatus: 500 | |||
212 | 213 | ||
213 | Value: 60 | 214 | Value: 60 |
214 | Name: GENERIC_INTERNAL_INVARIANT_FAILURE | 215 | Name: GENERIC_INTERNAL_INVARIANT_FAILURE |
215 | Description: The HTTP server experienced an internal invariant failure (bug). | 216 | Description: 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. |
216 | HttpStatus: 500 | 217 | HttpStatus: 500 |
217 | 218 | ||
218 | Value: 61 | 219 | Value: 61 |
219 | Name: GENERIC_FAILED_COMPUTE_JSON_HASH | 220 | Name: GENERIC_FAILED_COMPUTE_JSON_HASH |
220 | Description: The service could not compute a cryptographic hash over some JSON value. | 221 | Description: 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. |
221 | HttpStatus: 500 | 222 | HttpStatus: 500 |
222 | 223 | ||
223 | Value: 62 | 224 | Value: 62 |
224 | Name: GENERIC_FAILED_COMPUTE_AMOUNT | 225 | Name: GENERIC_FAILED_COMPUTE_AMOUNT |
225 | Description: The service could not compute an amount. | 226 | Description: The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers. |
226 | HttpStatus: 500 | 227 | HttpStatus: 500 |
227 | 228 | ||
228 | 229 | ||
@@ -230,32 +231,32 @@ HttpStatus: 500 | |||
230 | 231 | ||
231 | Value: 70 | 232 | Value: 70 |
232 | Name: GENERIC_PARSER_OUT_OF_MEMORY | 233 | Name: GENERIC_PARSER_OUT_OF_MEMORY |
233 | Description: The HTTP server had insufficient memory to parse the request. | 234 | Description: 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. |
234 | HttpStatus: 500 | 235 | HttpStatus: 500 |
235 | 236 | ||
236 | Value: 71 | 237 | Value: 71 |
237 | Name: GENERIC_ALLOCATION_FAILURE | 238 | Name: GENERIC_ALLOCATION_FAILURE |
238 | Description: The HTTP server failed to allocate memory. | 239 | Description: 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. |
239 | HttpStatus: 500 | 240 | HttpStatus: 500 |
240 | 241 | ||
241 | Value: 72 | 242 | Value: 72 |
242 | Name: GENERIC_JSON_ALLOCATION_FAILURE | 243 | Name: GENERIC_JSON_ALLOCATION_FAILURE |
243 | Description: The HTTP server failed to allocate memory for building JSON reply. | 244 | Description: 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. |
244 | HttpStatus: 500 | 245 | HttpStatus: 500 |
245 | 246 | ||
246 | Value: 73 | 247 | Value: 73 |
247 | Name: GENERIC_CURL_ALLOCATION_FAILURE | 248 | Name: GENERIC_CURL_ALLOCATION_FAILURE |
248 | Description: The HTTP server failed to allocate memory for making a CURL request. | 249 | Description: 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. |
249 | HttpStatus: 500 | 250 | HttpStatus: 500 |
250 | 251 | ||
251 | Value: 74 | 252 | Value: 74 |
252 | Name: GENERIC_FAILED_TO_LOAD_TEMPLATE | 253 | Name: GENERIC_FAILED_TO_LOAD_TEMPLATE |
253 | Description: The backend could not locate a required template to generate an HTML reply. | 254 | Description: 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. |
254 | HttpStatus: 500 | 255 | HttpStatus: 500 |
255 | 256 | ||
256 | Value: 75 | 257 | Value: 75 |
257 | Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE | 258 | Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE |
258 | Description: The backend could not expand the template to generate an HTML reply. | 259 | Description: 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. |
259 | HttpStatus: 500 | 260 | HttpStatus: 500 |
260 | 261 | ||
261 | 262 | ||