alibaba/canal · error · IOException

Unexpected packet with field_count= + body[0]

Error message

Unexpected packet with field_count= + body[0]

What it means

During sendRegisterSlave() the server's response packet started with a negative first byte that is not -1 (0xff). Canal only knows how to interpret 0xff as an ErrorPacket; any other negative field_count is treated as a malformed/unexpected response, and an IOException is thrown with the raw byte value. This indicates a protocol-level surprise rather than a clean MySQL error.

Source

Thrown at parse/src/main/java/com/alibaba/otter/canal/parse/inbound/mysql/MysqlConnection.java:341

        byte[] cmdBody = cmd.toBytes();

        logger.info("Register slave {}", cmd);

        HeaderPacket header = new HeaderPacket();
        header.setPacketBodyLength(cmdBody.length);
        header.setPacketSequenceNumber((byte) 0x00);
        PacketManager.writePkg(connector.getChannel(), header.toBytes(), cmdBody);

        header = PacketManager.readHeader(connector.getChannel(), 4);
        byte[] body = PacketManager.readBytes(connector.getChannel(), header.getPacketBodyLength());
        assert body != null;
        if (body[0] < 0) {
            if (body[0] == -1) {
                ErrorPacket err = new ErrorPacket();
                err.fromBytes(body);
                throw new IOException("Error When doing Register slave:" + err.toString());
            } else {
                throw new IOException("Unexpected packet with field_count=" + body[0]);
            }
        }
    }

    private void sendBinlogDump(String binlogfilename, Long binlogPosition) throws IOException {
        BinlogDumpCommandPacket binlogDumpCmd = new BinlogDumpCommandPacket();
        binlogDumpCmd.binlogFileName = binlogfilename;
        binlogDumpCmd.binlogPosition = binlogPosition;
        binlogDumpCmd.slaveServerId = this.slaveId;
        byte[] cmdBody = binlogDumpCmd.toBytes();

        logger.info("COM_BINLOG_DUMP with position:{}", binlogDumpCmd);
        HeaderPacket binlogDumpHeader = new HeaderPacket();
        binlogDumpHeader.setPacketBodyLength(cmdBody.length);
        binlogDumpHeader.setPacketSequenceNumber((byte) 0x00);
        PacketManager.writePkg(connector.getChannel(), binlogDumpHeader.toBytes(), cmdBody);
        connector.setDumping(true);
    }

View on GitHub (pinned to 87be50e876)

Solutions

1. Inspect the field_count value in the message to identify the packet type (0xfe = EOF, etc.) and cross-check against your MySQL/MariaDB version.
2. Verify network path integrity — proxies, SSL terminators, or load balancers between canal and the DB can corrupt the handshake.
3. Ensure the MySQL server version is supported and that no other client interfered with the socket; reconnect and reproduce.
4. If reproducible only on one server variant, report it with the exact byte value and server version.

try {
    connection.dump(journalName, position, coprocessor);
} catch (IOException e) {
    if (e.getMessage() != null && e.getMessage().contains("Unexpected packet with field_count=")) {
        logger.error("Protocol-level unexpected response during register slave; verify MySQL version and network path", e);
    }
    throw e;
}

When it happens

Trigger: The byte immediately following the 4-byte packet header is negative (>= 0x80) but not 0xff — e.g. 0xfe (EOF packet) or 0x80..0xfd returned where an OK packet was expected after COM_REGISTER_SLAVE.

Common situations: Server/client protocol version mismatch, a proxy or man-in-the-middle mangling the replication stream, an older/newer MySQL variant that responds differently to slave registration, or a connection that was silently closed and the read picked up garbage bytes.

Related errors

• Error When doing Register slave: + err.toString()
• Received error packet: errno = {}, sqlstate = {} errmsg = {}
• Unexpected response {} while fetching binlog: packet #{}, le
• command : show variables like 'server_id' has an error!
• command : ' + showSql + ' has an error!

AI-assisted analysis of alibaba/canal@87be50e876 (2026-08-14). Data as JSON: /api/errors/68769dd81ff2984a. Report an issue: GitHub.