Lines Matching refs:error

159 Each command sent by a client may be answered with an error string
160 from the server. These error strings come in three types:
166 - "CLIENT_ERROR <error>\r\n"
168   means some sort of client error in the input line, i.e. the input
169   doesn't conform to the protocol in some way. <error> is a
170   human-readable error string.
172 - "SERVER_ERROR <error>\r\n"
174   means some sort of server error prevents the server from carrying
175   out the command. <error> is a human-readable error string. In cases
178   close the connection after sending the error line. This is the only
182 In the descriptions of individual commands below, these error lines
261   parse "noreply" option reliably.  In this case it may send the error
278 because of an error. This normally means that the
361 incr/decr commands return an error (memcached <= 1.2.6 treated the
719 because of an error.
745 - c: returns the CAS value on successful storage. Will return 0 on error, but
1649 If an error happens, it will return:
1651 STAT sizes_status error\r\n
1756 | conn_swallow   | Discarding excess input, e.g., after an error has         |
1776 |                                |          | encountered an OpenSSL error   |
1779 |                                |          | seen a fatal TLS protocol error|
1821 adjustments of the cache memory limit. It returns "OK\r\n" or an error (unless
1869 b) executing a shell command. If either one is successful, an error is