pinpoint-c-agent: [StreamServerLayer.py:68] peer error:[Errno 104] Connection reset by peer

I’m running a PHP cron job on Kubernetes which ending with the following trace:

[pinpoint] [1] [1]#55 pinpoint_end_trace Done!
--
  | [pinpoint] [1] [1]#128 add clues:330:20765.640625 KB
  | [pinpoint] [1] [1]this span:({"E":12325,"FT":1500,"S":1610711645350,"appid":"sid.ping-lost","appname":"sid","calls":[{"E":34,"S":142,"calls":[{"E":5,"S":165,"clues":["-1:SHOW FULL COLUMNS FROM `audit_entry`","21:SHOW FULL COLUMNS FROM `audit_entry`"],"dst":"mysql:host=uat.fr;port=3306;dbname=sid-uat","name":"yii\\db\\Command::internalExecute","stp":"2101"}],"clues":["-1:fetchAll","21:SHOW FULL COLUMNS FROM `audit_entry`"],"dst":"mysql:host=uat.fr;port=3306;dbname=sid-uat","name":"yii\\db\\Command::queryInternal","stp":"2101"},{"E":9,"S":178,"calls":[{"E":8,"S":179,"clues":["-1:SELECT\n    `kcu`.`CONSTRAINT_NAME` AS `constraint_name`,\n    `kcu`.`COLUMN_NAME` AS `column_name`,\n    `kcu`.`REFERENCED_TABLE_NAME` AS `referenced_table_name`,\n    `kcu`.`REFERENCED_COLUMN_NAME` AS `referenced_column_name`\nFROM `information_schema`.`REFERENTIAL_CONSTRAINTS` AS `rc`\nJOIN `information_schema`.`KEY_COLUMN_USAGE` AS `kcu` ON\n    (\n        `kcu`.`CONSTRAINT_CATALOG` = `rc`.`CONSTRAINT_CATALOG` OR\n        (`kcu`.`CONSTRAINT_CATALOG` IS NULL AND `rc`.`CONSTRAINT_CATALOG` IS NULL)\n    ) AND\n    `kcu`.`CONSTRAINT_SCHEMA` = `rc`.`CONSTRAINT_SCHEMA` AND\n    `kcu`.`CONSTRAINT_NAME` = `rc`.`CONSTRAINT_NAME`\nWHERE `rc`.`CONSTRAINT_SCHEMA` = database() AND `kcu`.`TABLE_SCHEMA` = database()\nAND `rc`.`TABLE_NAME` = 'audit_entry' AND `kcu`.`TABLE_NAME` = 'audit_entry'","21:SELECT\n    `kcu`.`CONSTRAINT_NAME` AS `constraint_name`,\n    `kcu`.`COLUMN_NAME` AS `column_name`,\n    `kcu`.`REFERENCED_TABLE_NAME` AS `referenced_table_name`,\n    `kcu`.`REFERENCED_COLUMN_NAME` AS `referenced_column_name`\nFROM `information_schema`.`REFERENTIAL_CONSTRAINTS` AS `rc`\nJOIN `information_schema`.`KEY_COLUMN_USAGE` AS `kcu` ON\n    (\n        `kcu`.`CONSTRAINT_CATALOG` = `rc`.`CONSTRAINT_CATALOG` OR\n        (`kcu`.`CONSTRAINT_CATALOG` IS NULL AND `rc`.`CONSTRAINT_CATALOG` IS NULL)\n    ) AND\n    `kcu`.`CONSTRAINT_SCHEMA` = `rc`.`CONSTRAINT_SCHEMA` AND\n    `kcu`.`CONSTRAINT_NAME` = `rc`.`CONSTRAINT_NAME`\nWHERE `rc`.`CONSTRAINT_SCHEMA` = database() AND `kcu`.`TABLE_SCHEMA` = database()\nAND `rc`.`TABLE_NAME` = 'audit_entry' AND `kcu`.`TABLE_NAME` = 'audit_entry'"],"dst":"mysql:host=uat..fr;port=3306;dbname=sid-uat","name":"yii\\db\\Command::internalExecute","stp":"2101"}],"clues":["-1:fetchAll","21:SELECT\n    `kcu`.`CONSTRAINT_NAME` AS `constraint_name`,\n    `kcu`.`COLUMN_NAME` AS `column_name`,\n    `kcu`.`REFERENCED_TABLE_NAME` AS `referenced_table_name`,\n    `kcu`.`REFERENCED_COLUMN_NAME` AS `referenced_column_name`\nFROM `information_schema`.`REFERENTIAL_CONSTRAINTS` AS `rc`\nJOIN `information_schema`.`KEY_COLUMN_USAGE` AS `kcu` ON\n    (\n        `kcu`.`CONSTRAINT_CATALOG` = `rc`.`CONSTRAINT_CATALOG` OR\n        (`kcu`.`CONSTRAINT_CATALOG` IS NULL AND `rc`.`CONSTRAINT_CATALOG` IS NULL)\n    ) AND\n    `kcu`.`CONSTRAINT_SCHEMA` = `rc`.`CONSTRAINT_SCHEMA` AND\n    `kcu`.`CONSTRAINT_NAME` = `rc`.`CONSTRAINT_NAME`\nWHERE `rc`.`CONSTRAINT_SCHEMA` = database() AND `kcu`.`TABLE_SCHEMA` = database()\nAND `rc`.`TABLE_NAME` = 'audit_entry' AND `kcu`.`TABLE_NAME` = 'audit_entry'"],"dst":"mysql:host=uat..fr;port=3306;dbname=sid-uat","name":"yii\\db\\Command::queryInternal","stp":"2101"},{"E":12031,"S":206,"calls":[{"E":185,"S":210,"calls":[{"E":18,"EXP":"Redis error: ERR This instance has cluster support disabled\nRedis command was: CLUSTER INFO","S":221,"calls":[{"E":15,"S":221,"calls":[{"E":2,"S":234,"calls":[{"E":0,"S":234,"name":"yii\\redis\\Connection::open"},{"E":2,"S":234,"name":"yii\\redis\\Connection::sendCommandInternal","stp":"1501"}],"clues":["-1:SELECT 3"],"name":"yii\\redis\\Connection::executeCommand","stp":"1501"}],"dst":"tcp://uat.fr:6379, database=3","name":"yii\\redis\\Connection::open","stp":"8200"},{"E":3,"EXP":"Redis error: ERR This instance has cluster support disabled\nRedis command was: CLUSTER INFO","S":236,"name":"yii\\redis\\Connection::sendCommandInternal","stp":"1501"}],"clues":["-1:CLUSTER INFO "],"name":"yii\\redis\\Connect
  | [pinpoint] [1] [1]agent try to connect:(tcp:pinpoint-collector-agent:8181)
  | [pinpoint] [1] [1]#128 pinpoint_end_trace Done!

On collector agent which is pinpoint-collector-agent:8181 v0.4.1, I’ve got the following:

[2021-01-15 11:54:17,683] [30] [INFO] [StreamServerLayer.py:141] new connect fd:8
[2021-01-15 11:54:17,683] [30] [DEBUG] [FrontAgent.py:90] send hello:8 len:59
[2021-01-15 11:54:17,684] [30] [DEBUG] [StreamServerLayer.py:97] send 59
[2021-01-15 11:54:17,704] [30] [WARNING] [StreamServerLayer.py:68] peer error:[Errno 104] Connection reset by peer
[2021-01-15 11:54:17,705] [30] [WARNING] [StreamServerLayer.py:168]  client:8 disconnected
[2021-01-15 11:54:17,705] [30] [DEBUG] [StreamServerLayer.py:74] close client:8(('10.131.0.1', 51576))

And not trace is sent to the UI.