OriginTrail
Error while sending telemetry data: Maximum call stack size exceeded
Issue description
I'm receiving errors in the log by the node failing to send telemetry data.
Expected behavior
Logs sent without an error
Actual behavior
Receive error in the log
Specifications
- Node version: v14.18.2
- Platform: Ubuntu 20.04.4 LTS
- Node wallet: 0x0014517F7761AE488892ECaA13Bd0Fa1cD441920
- Node libp2p identity: QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L
Contact details
- Email: [email protected]
Error logs
[2022-03-07 12:18:13] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmXzmTqVT3TPUtTz4dBDN5NWSABqnX9rKXCG9WCLXMfEaM
[2022-03-07 12:18:13] INFO: Telemetry hub module initialized successfully, using ot-telemetry-collector package(s)
[2022-03-07 12:18:13] INFO: Network API module enabled on port 9000
[2022-03-07 12:18:13] INFO: Enabling network protocol: /store
[2022-03-07 12:18:13] INFO: Enabling network protocol: /resolve
[2022-03-07 12:18:13] INFO: Enabling network protocol: /search
[2022-03-07 12:18:13] INFO: Enabling network protocol: /search/result
[2022-03-07 12:18:13] INFO: Enabling network protocol: /search/assertions
[2022-03-07 12:18:13] INFO: Enabling network protocol: /search/assertions/result
[2022-03-07 12:18:13] INFO: Service API module enabled, server running on port 8900
[2022-03-07 12:18:15] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmQ2X7nCArENLdtVzSqiW1qqYisvH86PMhqY3UXCbexX7a
[2022-03-07 12:18:18] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmZAoaMb7ZAphUPLhRsrv3Q3h5rmbzMPtbzmcJJELqg1Vj
[2022-03-07 12:18:20] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmdujPXsuifXgeTcECjWj5XQHbhk4o3PcARMA2GfsVoVjs
[2022-03-07 12:18:23] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L discovered QmSpebDCY9RTDauQHDh9TtrqUJ6MDSWiWzenypeRpeGKwN
... bunch of same debug logs ...
[2022-03-07 12:19:08] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmSd5LAHC9HBg1bX1WYoNqrVuGtbkj1v4my8ayu315PTji
[2022-03-07 12:19:13] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmYUnJvmnoWjweLhM5aa4m1dxT71WjPHSvLgJ1GCnnJmt4
[2022-03-07 12:19:13] INFO: Replay pending/started commands from the database...
[2022-03-07 12:19:13] INFO: Checking for new updates...
[2022-03-07 12:19:13] INFO: Started sending telemetry data
[2022-03-07 12:19:18] USERLVL: OT-Node is alive...
[2022-03-07 12:19:21] ERROR: Error while sending telemetry data to Telemetry hub: Maximum call stack size exceeded. undefined
[2022-03-07 12:19:21] USERLVL: Found error will be reported to Telemetry: SendingDataTelemetryError
[2022-03-07 12:19:30] INFO: Receiving message from QmRhjycgGW4LqpireRZHMpmLhsSETNJRqMxVuUoBHpdQXC to QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L: event=/search;
[2022-03-07 12:19:30] INFO: Sending response from QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L to QmRhjycgGW4LqpireRZHMpmLhsSETNJRqMxVuUoBHpdQXC: event=/search;
[2022-03-07 12:19:30] USERLVL: Started measuring execution of handle search command
[2022-03-07 12:19:30] USERLVL: Finished measuring execution of handle search command
[2022-03-07 12:19:30] INFO: Sending message from QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L to QmRhjycgGW4LqpireRZHMpmLhsSETNJRqMxVuUoBHpdQXC: event=/search/result;
[2022-03-07 12:19:36] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmTq6UZrwcAaTnvYU9x2CbHfe6aywJWpEHFom8RfYAgMMn
[2022-03-07 12:19:47] DEBUG: Node QmdiRGM7dJmhfcFUwSJR3q9HJ6GedXpT8R3TBQPn6Gyb3L connected to QmPgM2scGGKfxoDRaBZqh2n8VJaTJyfZJSnkxjuaSFp976
Thanks for reporting @Alko89
So for everyone who are experiencing this issue, right now solution is to take a look at active.log file in /logs directory. Check the size of the file by running the next commands from ot-node directory:
cd logs
ls -lh | grep active.log
If you see that file is too big (more then 20MB), then you should delete it and restart the node systemctl restart otnode
Yep, my log size was 1.7 GB :laughing: I removed all logs and it seems to be fixed now :+1:
This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.
Thank you, OriginTrail Team