mat1010 opened a new issue, #10892: URL: https://github.com/apache/trafficserver/issues/10892
We are running Trafficserver 9.2.3 and ran into an issue where trafficserver reached the maximum amount of stats and records which is set by [`maxRecords`](https://docs.trafficserver.apache.org/appendices/command-line/traffic_server.en.html#cmdoption-traffic_server-m). The reason for this is that we are also running podman containers on the same server. Every new container and every restart of a container causes a change of the virtual network interfaces. A new container get's a new interface and a restarted container removes it's current interfaces and gets a new one, with a new name. Every interface creates new records ``` plugin.system_stats.net.vethfb0aaa00.speed 10000 plugin.system_stats.net.vethfb0aaa00.collisions 0 plugin.system_stats.net.vethfb0aaa00.multicast 0 plugin.system_stats.net.vethfb0aaa00.rx_bytes 71171126 plugin.system_stats.net.vethfb0aaa00.rx_compressed 0 plugin.system_stats.net.vethfb0aaa00.rx_crc_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_dropped 0 plugin.system_stats.net.vethfb0aaa00.rx_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_fifo_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_frame_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_length_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_missed_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_nohandler 0 plugin.system_stats.net.vethfb0aaa00.rx_over_errors 0 plugin.system_stats.net.vethfb0aaa00.rx_packets 983190 plugin.system_stats.net.vethfb0aaa00.tx_aborted_errors 0 plugin.system_stats.net.vethfb0aaa00.tx_bytes 133071338 plugin.system_stats.net.vethfb0aaa00.tx_carrier_errors 0 plugin.system_stats.net.vethfb0aaa00.tx_compressed 0 plugin.system_stats.net.vethfb0aaa00.tx_dropped 0 plugin.system_stats.net.vethfb0aaa00.tx_errors 0 plugin.system_stats.net.vethfb0aaa00.tx_fifo_errors 0 plugin.system_stats.net.vethfb0aaa00.tx_heartbeat_errors 0 plugin.system_stats.net.vethfb0aaa00.tx_packets 1912343 plugin.system_stats.net.vethfb0aaa00.tx_window_errors 0 ``` This would not be an issue if we either could purge the records, not only the values, from time to time (without restarting trafficserver), or the creation of new stats would just not be possible anymore with a corresponding log message. Unfortunately once the value of `maxRecords` is reached the trafficserver segfaults and does not recover by itself since the `traffic_manager` process is not getting killed so `systemd` is not able to handle it with the `restart=on-failure` directive. Is this a known issue, or is this the expected bevahiour? Is it save to increase the `maxRecords` limit to a huge number? What might be the drawbacks? I attached the crashlogs from systemd and trafficserver [systemd.log](https://github.com/apache/trafficserver/files/13517384/systemd.log) [crash-2023-11-28-164715.log](https://github.com/apache/trafficserver/files/13517399/crash-2023-11-28-164715.log) Thanks in advance -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
