Invalid timestamp buffer

[egalano]

    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:27:36)
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:85:28)
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:173:35)
    at Server._handler (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/server.js:140:26)
    at Socket.Server._socket.on (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/server.js:50:14)
    at Socket.emit (events.js:182:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)
RangeError: Invalid timestamp buffer :0167f757d38f
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:27:36)
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:85:28)
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:173:35)
    at Server._handler (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/server.js:140:26)
    at Socket.Server._socket.on (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/server.js:50:14)
    at Socket.emit (events.js:182:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)
RangeError: Invalid timestamp buffer :0167f758bdae
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:27:36)
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:85:28)
    at Object.decode (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/message.js:173:35)
    at Server._handler (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/server.js:140:26)
    at Socket.Server._socket.on (/root/devp2p-network/node_modules/ethereumjs-devp2p/lib/dpt/server.js:50:14)
    at Socket.emit (events.js:182:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)```

[kshinn]

Is this a bug with the library and how it is interpreting certain client's messages?

[egalano]

Maybe. That last example in the log 0167f758bdae is 1546043047342 which as a unix timestamp is a few digits too many. I'd want to enable debug logging on the dht logger and see what the full message looks like. Maybe a specific client version is using the wrong timestamp format.