Protocol Error Opcode 01
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or
Github Memcached
posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss memcached protocol Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only
Libmemcached
takes a minute: Sign up Protocol Error in memcached up vote 0 down vote favorite I'm kind of new to memcached so I may be missing something obvious. I'm running memcached 1.4.24 on OS X 10.10 in a VM with the following options: memcached -p 11211 -U 0 -B binary -vv -U 0 disables UDP. I'm interacting with memcached from a C# 4.5 project running on Windows (the host OS) using the EnyimMemcached client. I'm storing binary data in memcached (keys are plain strings of course). While some documents are stored and retrieved fine, many aren't, and I'm seeing lots of errors in the memcached output. Here is a typical example: <27 Read binary protocol data: <27 0x80 0x00 0x01 0x00 <27 0x00 0x00 0x00 0x00 <27 0x00 0x00 0x01 0x00 <27 0x00 0x00 0x00 0x17 <27 0x00 0x00 0x00 0x00 <27 0x00 0x00 0x00 0x00 >27 Writing an error: Invalid arguments >27 Writing bin response: >27 0x81 0x00 0x00 0x00 >27 0x00 0x00 0x00 0x04 >27 0x00 0x00 0x00 0x11 >27 0x00 0x00 0x00 0x17 >27 0x00 0x00 0x00 0x00 >27 0x00 0x00 0x00 0x00 Protocol error (opcode 00), close connection 27 <27 connection closed. What do these errors mean, and could be causing them? FWIW, I've also tried with memcached 1.4.5 on Windows but I have the exact same problem. c# memcached share|improve this question edited Jan 18 at 15:30 asked Jan 18 at 13:32 Francois Beaune 6512832 Seems like it could be due to keys being too long? Would that cause protocol errors? –Francois Beaune Jan 18 at 15:01 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Browse other questions tagged c# memcached or ask your own question. asked 9 months ago viewed 39 times Blog Stack Overflow Podcas
(BRM) error locations, classes, and codes. For information about troubleshooting BRM, including examples of error messages that use these error codes, see Chapter 17, "Resolving Problems in Your BRM System". Interpreting BRM Error Codes When a BRM process has a problem, its log file displays an error message that often includes: Error location; for example, location=
Inc. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may https://docs.datastax.com/en/drivers/python/3.4/_modules/cassandra/protocol.html not use this file except in compliance with the License. https://www.wireshark.org/lists/wireshark-dev/200804/msg00217.html # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, protocol error # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. from __future__ import absolute_import # to enable import io from stdlib from collections import namedtuple import logging import socket from protocol error opcode uuid import UUID import six from six.moves import range import io from cassandra import type_codes, DriverException from cassandra import (Unavailable, WriteTimeout, ReadTimeout, WriteFailure, ReadFailure, FunctionFailure, AlreadyExists, InvalidRequest, Unauthorized, UnsupportedOperation, UserFunctionDescriptor, UserAggregateDescriptor, SchemaTargetType) from cassandra.marshal import (int32_pack, int32_unpack, uint16_pack, uint16_unpack, int8_pack, int8_unpack, uint64_pack, header_pack, v3_header_pack) from cassandra.cqltypes import (AsciiType, BytesType, BooleanType, CounterColumnType, DateType, DecimalType, DoubleType, FloatType, Int32Type, InetAddressType, IntegerType, ListType, LongType, MapType, SetType, TimeUUIDType, UTF8Type, VarcharType, UUIDType, UserType, TupleType, lookup_casstype, SimpleDateType, TimeType, ByteType, ShortType) from cassandra.policies import WriteType from cassandra.cython_deps import HAVE_CYTHON, HAVE_NUMPY from cassandra import util log = logging.getLogger(__name__) class NotSupportedError(Exception): pass class InternalError(Exception): pass ColumnMetadata = namedtuple("ColumnMetadata", ['keyspace_name', 'table_name', 'name', 'type']) MIN_SUPPORTED_VERSION = 1 MAX_SUPPORTED_VERSION = 4 HEADER_DIRECTION_TO_CLIENT = 0x80 HEADER_DIRECTION_MASK = 0x80 COMPRESSED_FLAG = 0x01 TRACING_FLAG = 0x02 CUSTOM_PAYLOAD_FLAG = 0x04 WARNING_FLAG = 0x08 _message_types_by_opcode = {} _UNSET_VALUE = object() def register_class(cls): _message_types_by_opcode[cls.opcode] = cls def get_registered_classes(): return _message_types_by_opcode.copy() class _RegisterMessageType(ty
Wireshark-dev: Re: [Wireshark-dev] Wireshark decoding error- protocol DNS - section Flags for A Date Index Thread Index Other Months All Mailing Lists Date Prev Date Next Thread Prev Thread Next From: "Luis EG Ontanon" <[emailprotected]> Date: Fri, 11 Apr 2008 16:51:31 +0200 Hi, Thanks for the detailed report and traces (traces are always very appreciated). You better open a bug in http://bugs.wireshark.org that way we do keep track of this. Or else we risk just loosing track of it. Thanks, Luis On Fri, Apr 11, 2008 at 12:29 PM, März, Frank <[emailprotected]> wrote: > > > > Hello Wireshark Expert, > > I think I have found a problem within Wireshark while decoding two bits > within the DNS protocol. The problem can be seen in all Wireshark version I > tried up to 1.0.0 on several OS. Wireshark fails to decode the Flags section > for the bit AD and CD. > > Details are in: > > RFC2535 - 6.1 The AD and CD Header Bits > > 1 1 1 1 1 1 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > | ID | > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > |QR| Opcode |AA|TC|RD|RA| Z|AD|CD| RCODE | > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > | QDCOUNT | > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > | ANCOUNT | > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > | NSCOUNT | > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > | ARCOUNT | > +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ > > > This is the trace in text format: > > > > > No. Time Source Destination Protocol > Info > > 50 41.833438 193.254.142.169 213.162.74.3 DNS > Standard query A web.mnc007.mcc232.gprs > > > > Frame 50 (93 bytes on wire, 93 bytes captured) > > Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst: > 69:31:65:74:68:34 (69:31:65:74:68:34) > > Internet Protocol, Src: 193.254.142.169 (