You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FluntBit was running as a pod in the k8s, I use it to collect logs from some log files.
Sometimes it crashed, after some debug I found maybe it due to the special charactor in the log content.
To Reproduce
the log generator script is normal like this:
#!/bin/bashshow_help() {
echo"Usage: $0 [NUM_LINES]"echo"If NUM_LINES is not provided, it will default to print 100 lines of logs."echo"NUM_LINES should be a positive integer representing the number of log lines to print."exit 1
}
if [ $#-gt 1 ];then
show_help
fiif [ -z"$1" ];then
LOG_LINES=100
elseif [[ "$1"=~ ^[0-9]+$ ]];then
LOG_LINES=$1elseecho"Error: The parameter should be a positive integer."
show_help
fifi
NODE_IP=$(hostname | awk '{print $1}')
POD_NAME=${POD:-"unknown-pod"}
extra_info="This is extra info for log line. Some more details here heiheihheiheihheiheiheiheiheiheiheiheiheiheiheiheiheiheiheiheihei."for((i =0; i < LOG_LINES; i++));do
TIMESTAMP=$(date +"%Y-%m-%d")echo"$TIMESTAMP | Node IP: $NODE_IP | Count: $i | $extra_info"
sleep 2
done
most of the logs is normal.
before fluent-bit crashed, the last log shows there are lots of 'NUL' where should be normal string charactor ('This is extra info for log line. Some more d').
the original logs file is big i cannot attach it here.
Screenshots
And i can not find any '0000' when i vim the log file by setting :%!xxd
Bug Report
Describe the bug
FluntBit was running as a pod in the k8s, I use it to collect logs from some log files.
Sometimes it crashed, after some debug I found maybe it due to the special charactor in the log content.
To Reproduce
the log generator script is normal like this:
most of the logs is normal.
before fluent-bit crashed, the last log shows there are lots of 'NUL' where should be normal string charactor ('This is extra info for log line. Some more d').
the original logs file is big i cannot attach it here.
Screenshots
And i can not find any '0000' when i vim the log file by setting
:%!xxd
Your Environment
# kubectl version Client Version: v1.28.4-r0-28.0.5 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.28.6-r0-28.0.39.7
Additional context
The text was updated successfully, but these errors were encountered: