centos7系统部署docker因为sytemtd-journald一直占用CPU、内存导致系统宕机?

四台linux系统部署docker,其中一台机器总是过阵子就宕机,必须手动硬启动才能恢复。通过跟踪系统资源发现rsyslogd占用内存越来越多,最后确认是由于docker中system-journal一直写内存导致。网上的资料说是没有创建/var/log/journal目录导致。docker不太熟悉,请教大神如何处理问题(修改journald.conf配置文件改成none不写入日志不是根本办法)
问题服务器上:
/run/log/journal
/run/systemd/journal
/var/lib/docker/overlay2/fc4c5960b3edf7759fedbdd735a346654785479fe2dd68410523abf65d983a29/diff/var/log/journal
/var/lib/docker/overlay2/cf288e27279753f85b0bda454d84e6c699786816a666ad7991a931e964f00833/diff/var/log/journal
/var/lib/docker/overlay2/6b47ce1d2bd89913666eaf08d9a6e7cfbe77930acd32291003dbc66940408426/diff/var/log/journal
/var/lib/docker/overlay2/8ee0eadeae2efc7df1c72f8688e46807eb20f98c5567145403670bddc92138b0/diff/var/log/journal
/var/lib/docker/overlay2/74a37fb541b18341ddfaeb5cc0b87813b53129bfc3bef18d1e8d9573f0b4ce43/diff/var/log/journal
/var/lib/docker/overlay2/7b45e1b704bd4d9b9dfd9991a429daa0c193f173d7f4461944fd126b883984cd/diff/var/log/journal
/var/lib/docker/overlay2/7b45e1b704bd4d9b9dfd9991a429daa0c193f173d7f4461944fd126b883984cd/merged/var/log/journal
/var/lib/docker/overlay2/ec227e219df208fa40f6698c7b1210a432e2680d0c762f481497ec6e9dfefc1a/diff/var/log/journal
/var/lib/docker/overlay2/61be57b3ba9845c16b81b7ae3ea947ecb11ba9e7861f6b855762e45d7ea611ab/diff/var/log/journal
/var/lib/docker/overlay2/c4b59c5a1aafb61ace6eb132305cebc243d763a93a0c7ae9a92a6f07f0b8fc55/diff/var/log/journal
/var/lib/docker/overlay2/c4b59c5a1aafb61ace6eb132305cebc243d763a93a0c7ae9a92a6f07f0b8fc55/merged/var/log/journal
/var/lib/docker/overlay2/6baf35cc22b8c6e4386de24817323f643d873bf49f7a9e66214dc0df78ba6943/diff/var/log/journal
/var/lib/docker/overlay2/0ab345325e174243fec2f96d074d728ed11b260c5eb0f2c85e9b8f592c85a774/diff/var/log/journal
/var/lib/docker/overlay2/0ab345325e174243fec2f96d074d728ed11b260c5eb0f2c85e9b8f592c85a774/merged/var/log/journal
/var/lib/docker/overlay2/bed9f6e86eac638b79b1ee73a82bb34ddfda0302b858f75d5f1ef66d4aeb8eed/diff/var/log/journal
/var/lib/docker/overlay2/00b0f6f97f74dfaaf6059b00bc344b01e7759d7eea45cc89c873dd2053fbbcd9/diff/var/log/journal
/var/lib/docker/overlay2/7c9f75eaadd83220d7c63172ccb55db26be6ce4feb7ffa4142252079d67b26d8/diff/var/log/journal
/var/lib/docker/overlay2/a92c3fbbb773f05efaec233c8b87a181ecef8324d63a80172192625217a384ba/diff/var/log/journal
/var/lib/docker/overlay2/ceb97590a3350559ff496e303c6420ccdaf64816919fa3d5db11ee9668668378/diff/var/log/journal
/var/lib/docker/overlay2/e0c2136194664e825444b2c1d46e13fa92e6d76f4f027832cac2eb29d1553b40/diff/var/log/journal
/var/lib/docker/overlay2/c308d1c157eb1e5156344570b3b89e366ba8919cced95d2665482d7bb2e110ed/diff/var/log/journal
/var/lib/docker/overlay2/0160bc26c799d8bb0a2d3901e66cc8e85428a875c92ce1cd6b8ada39dede5475/diff/var/log/journal
/var/lib/docker/overlay2/4692a8c1d14af4868962c54d10b7fff4ba10c7d91320edb0224372b52a1d4c54/diff/var/log/journal
/var/lib/docker/overlay2/8d5106ada17e2077c49955c6f380895372416bc20e18386372aac8608cf3e4e1/diff/var/log/journal
。。。。。好多这东西

其他服务器上:

/run/log/journal
/run/systemd/journal
/var/lib/docker/devicemapper/mnt/cba80506ba20e116ac412f885d2c7e64cbf6094e6d23f043d30628f0b9ef0e8b/rootfs/var/log/journal
/var/lib/docker/devicemapper/mnt/e80d39b379e46657d4bf694209f18db8695857bd427f44661c74bf509a1a35bf/rootfs/var/log/journal
/var/lib/docker/devicemapper/mnt/2015fe6945ec145b86d3d744badd6f414a5689ccb2311d81bc173365da20eb49/rootfs/var/log/journal
/var/lib/docker/volumes/mongo_config_data/_data/journal
/var/lib/docker/volumes/mongo_shard1_data/_data/journal

参与8

1同行回答

zp_ccczp_ccc高级技术主管国内某金融科技公司
你在docker.service中增加了--log-driver=journald或者运行docker时指定了: docker run --log-driver=journald ?显示全部

你在docker.service中增加了--log-driver=journald
或者运行docker时指定了: docker run --log-driver=journald ?

收起
互联网服务 · 2019-07-30
浏览2817

提问者

hufeng719
系统工程师某钢铁企业
擅长领域: 数据库存储服务器

相关问题

相关资料

相关文章

问题状态

  • 发布时间:2019-07-30
  • 关注会员:3 人
  • 问题浏览:3687
  • 最近回答:2019-07-30
  • X社区推广