Mup deploy killed on DO drops, but errors in the logs :(

Even just redistributing a previously successfully deployed application does not work. I tracked mup logs -f on a separate terminal during deployment, but there was nothing there. It does not seem to have even reached the actual deployment phase. I have Node 0.10.31 and Meteor 1.0. Does anyone else run into this problem or know how to solve 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 that I get are related to bots, but according to my previous publication in SO , these errors do not occur during deployment and should not be a problem.

0
source share
1 answer

It turns out that updating from a drop of $ 5 / mo, 500 MB to a drop of $ 10 / month, 1 GB solved the problem. Earlier, I looked at a memory problem with a drop of $ 5 using memory swap , but it seems the run has run out. However, it would be nice to have errors in the logs to point me in the right direction.

+1
source

Source: https://habr.com/ru/post/1202452/


All Articles