docker中的gitlab:***缓冲区检测到的***:终止Xargs:尾巴:由信号终止6
我在从13.8.8升级到13.9.7(docker中的CE版本)时遇到了问题,日志崩溃了:
...
...
==> /var/log/gitlab/gitlab-rails/api_json.log.1-2022030300.backup <==
==> /var/log/gitlab/gitlab-rails/exceptions_json.log.1-2022042000.backup <==
==> /var/log/gitlab/gitlab-rails/exceptions_json.log.1-2021110700.backup <==
==> /var/log/gitlab/gitlab-rails/production_json.log.1-2021121100.backup <==
*** buffer overflow detected ***: terminated
xargs: tail: terminated by signal 6
然后,我依次升级到15.0.2-CE,但是日志持续存在的问题。我遵循了升级计划,等待所有迁移的结束,进行了a gitlab-ctl重新配置,但不幸的是,没有任何帮助。
gitlab-ctl status
run: gitaly: (pid 11302) 411s; run: log: (pid 321) 2106s
run: gitlab-kas: (pid 11324) 411s; run: log: (pid 523) 2094s
run: gitlab-workhorse: (pid 11355) 411s; run: log: (pid 907) 2048s
run: logrotate: (pid 11381) 410s; run: log: (pid 273) 2119s
run: nginx: (pid 11387) 410s; run: log: (pid 994) 2042s
run: postgresql: (pid 11421) 409s; run: log: (pid 372) 2101s
run: puma: (pid 11434) 408s; run: log: (pid 781) 2060s
run: redis: (pid 11441) 408s; run: log: (pid 290) 2113s
run: sidekiq: (pid 11526) 403s; run: log: (pid 824) 2054s
run: sshd: (pid 11532) 403s; run: log: (pid 30) 2132s
I have problem when upgrading from 13.8.8 to 13.9.7 (ce version in docker), logs are crashing like that:
...
...
==> /var/log/gitlab/gitlab-rails/api_json.log.1-2022030300.backup <==
==> /var/log/gitlab/gitlab-rails/exceptions_json.log.1-2022042000.backup <==
==> /var/log/gitlab/gitlab-rails/exceptions_json.log.1-2021110700.backup <==
==> /var/log/gitlab/gitlab-rails/production_json.log.1-2021121100.backup <==
*** buffer overflow detected ***: terminated
xargs: tail: terminated by signal 6
Then I successively upgraded to 15.0.2-ce but the problem with the logs persisted. I followed the upgrade plan, waited for the end of all migrations, did a gitlab-ctl reconfigure, but unfortunately nothing helped.
gitlab-ctl status
run: gitaly: (pid 11302) 411s; run: log: (pid 321) 2106s
run: gitlab-kas: (pid 11324) 411s; run: log: (pid 523) 2094s
run: gitlab-workhorse: (pid 11355) 411s; run: log: (pid 907) 2048s
run: logrotate: (pid 11381) 410s; run: log: (pid 273) 2119s
run: nginx: (pid 11387) 410s; run: log: (pid 994) 2042s
run: postgresql: (pid 11421) 409s; run: log: (pid 372) 2101s
run: puma: (pid 11434) 408s; run: log: (pid 781) 2060s
run: redis: (pid 11441) 408s; run: log: (pid 290) 2113s
run: sidekiq: (pid 11526) 403s; run: log: (pid 824) 2054s
run: sshd: (pid 11532) 403s; run: log: (pid 30) 2132s
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
好吧,这对我有用:
然后重新启动gitlab容器
Okay, that works for me:
and then restart gitlab container