0

I am having a strange problem. My error logs in old releases grow to gigabytes with in minutes of deployments. What is strange, is that the releases that grow are the old ones, normally the oldest one. Below is the error that fills the log:

[2016-09-22 01:14:48] production.ERROR: ErrorException: include(/home/forge/.../releases/20160922002617/vendor/composer/../bugsnag/bugsnag/src/Report.php): failed to open stream: No such file or directory in /home/forge/.../releases/20160922002617/vendor/composer/ClassLoader.php:414

It repeats multiple times per second until I restart the server. I am thinking, that maybe Envoyer isn't restarting a process that is in progress when it switches to a new release. I am not sure where to start on figuring out how I might be able to fix this. I am guessing I need to build something in to the Envoyer "Deployment Hooks".

Has anyone encountered this? Or give me advice on how I might be able ti fix it?

4

1 回答 1

0

在与 Taylor 交谈后,确定我有旧的 Queue 作品在删除的版本中运行,这导致了大量的日志。我已经在我的嵌入过程中添加了一个队列重启脚本,它似乎已经解决了这个问题。现在,在激活版本后,所有队列都将重新启动。

于 2016-09-24T20:12:56.510 回答