Mup部署在DO Drop上被杀死，但日志中没有错误:( [英] mup deploy killed on DO droplet but no errors in logs :(

问题描述

即使只是重新部署以前成功部署的应用程序也不起作用.部署时，我在单独的终端上监控了mup logs -f，但是在那里什么也没有显示.看起来它甚至还没有到达实际的部署步骤.我有Node 0.10.31和Meteor 1.0.还有其他人遇到这个问题或知道如何解决吗?

Even just redeploying a previously successfully deployed app doesn't work. I monitored mup logs -f on a separate terminal while deploying, but nothing ever showed up there. Looks like it doesn't even get to the actual deploy step. I have Node 0.10.31 and Meteor 1.0. Is anyone else having this problem or know how to tackle it?

~# mup deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

Building Started: /root/TS
Bundling Error: code=137, error:
-------------------STDOUT-------------------

-------------------STDERR-------------------
bash: line 1: 26400 Killed                  meteor build --directory /tmp/2b45aa84-0ffc-4ece-9cf4-aca8500409c3

实际上，我得到的唯一错误与机器人有关，但根据我的

Actually, the only errors I get relate to bots, but according to my previous posting on SO those errors do not occur during deployment and should not be a problem.

推荐答案

事实证明，从$ 5/mo，500 MB的水滴升级到$ 10/mo，1 GB的水滴可以解决此问题.我之前使用内存交换，但似乎已用完里程.不过，在日志中出现错误以将我指向正确的方向还是很不错的.

It turns out that upgrading from a $5/mo, 500 MB droplet to a $10/mo, 1 GB droplet solved the problem. I previously addressed the memory problem with the $5 droplet using memory swap, but that appears to have run out of mileage. Still, it would have been nice to have errors in the logs to point me in the right directions.

这篇关于Mup部署在DO Drop上被杀死，但日志中没有错误:(的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！