taoeffect
commented
7 years ago Now it's doing:
[2017/09/18 00:47:31] [ warn] [msgpack2json] unknown msgpack type 876228640
[2017/09/18 00:47:31] [ warn] [msgpack2json] unknown msgpack type 876228640
[2017/09/18 00:47:31] [ warn] [msgpack2json] unknown msgpack type 876228640
[2017/09/18 00:47:31] [ warn] [msgpack2json] unknown msgpack type 876228640
[2017/09/18 00:47:31] [ warn] [msgpack2json] unknown msgpack type 876228640It seems to be caused by the output of the mariadb service, which has a Dockerfile of:
FROM localhost:5000/customalpine
RUN apk --update add mariadb mariadb-client && rm -f /var/cache/apk/*
VOLUME /var/lib/mysql
EXPOSE 3306
COPY configs/ /etc/mysql/
COPY scripts/docker-entrypoint.sh /usr/local/bin
ENTRYPOINT ["/usr/local/bin/docker-entrypoint.sh"]Where docker-entrypoint.sh is:
#!/bin/sh
MYSQL_DATADIR=${MYSQL_DATADIR:-"/var/lib/mysql"}
if [ -d "/run/mysqld" ]; then
echo "[i] MySQL directory already present, skipping creation"
else
echo "[i] mysqld not found, creating...."
mkdir -p /run/mysqld
chown -R mysql:mysql /run/mysqld
echo 'Initializing database'
mkdir -p "$MYSQL_DATADIR/mysql"
chown -R mysql:mysql $MYSQL_DATADIR
mysql_install_db --user=mysql --datadir="$MYSQL_DATADIR" --rpm
echo 'Database initialized'
tfile=`mktemp`
[ -f "$tfile" ] || echo "failed to mktemp!" && exit 1
cat << EOF > $tfile
DELETE FROM mysql.user WHERE user NOT IN ('mysql.sys', 'mysqlxsys', 'root') OR host NOT IN ('localhost');
SET PASSWORD FOR 'root'@'localhost'=PASSWORD('${MYSQL_ROOT_PASSWORD}');
GRANT ALL ON *.* TO 'root'@'localhost' WITH GRANT OPTION;
DROP DATABASE IF EXISTS test;
FLUSH PRIVILEGES;
EOF
/usr/bin/mysqld --user=mysql --bootstrap --verbose=1 --datadir="$MYSQL_DATADIR" < $tfile
rm -f "$tfile"
fi
exec /usr/bin/mysqld --user=mysql --console --datadir="$MYSQL_DATADIR"And configs contains configs/my.cnf:
[mysqld]
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
symbolic-links = 0
# Custom config should go here
!includedir /etc/mysql/conf.d/And configs/conf.d/docker.cnf:
[mysqld]
skip-host-cache
skip-name-resolveI find it so strange that it wasn't doing this yesterday but now it's doing it every time and I can't get it to stop.
edsiper
marcbachmann
I have no idea what's going on.
In the span of a few seconds fluent-bit generated a 16M log file consisting of:
Am using Docker version
17.06.2-ce, build cec0b72, with fluent-bit versionv0.12.2.My dedicated container for logs contains this:
The config file contains this:
The
/home/unpriv/logs/fluent-bit.logis the file containing the 16M worth of spammed msgpack2json messages.The docker-compose.yml contains this:
It wasn't doing this before. No idea why it's happening now.