arunoda / meteor-up-legacy

Production Quality Meteor Deployments
MIT License
2.26k stars 394 forks source link

Mupx Verifying deployment: Fibers Erro #684

Open felipesmendes opened 9 years ago

felipesmendes commented 9 years ago

I was using mupx and then went to a new deploy got the error bellow as it tried to re- run Setup and reconfig , does anyone have any idea of the cause and solution?

    -----------------------------------STDERR-----------------------------------
    g directory `/bundle/bundle/programs/server/node_modules/fibers/build'
    Installed in `/bundle/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node`
    ansi-regex@0.2.1 node_modules/ansi-regex

    ansi-styles@1.1.0 node_modules/ansi-styles

    escape-string-regexp@1.0.3 node_modules/escape-string-regexp

    chalk@0.5.1 node_modules/chalk

    supports-color@0.2.0 node_modules/supports-color

    strip-ansi@0.3.0 node_modules/strip-ansi

    has-ansi@0.1.0 node_modules/has-ansi

    eachline@2.3.3 node_modules/eachline

    type-of@2.0.1 node_modules/type-of

    amdefine@1.0.0 node_modules/amdefine

    asap@2.0.3 node_modules/asap

    meteor-promise@0.4.8 node_modules/meteor-promise

    underscore@1.5.2 node_modules/underscore

    promise@7.0.4 node_modules/promise

    source-map-support@0.3.2 node_modules/source-map-support

    semver@4.1.0 node_modules/semver

    source-map@0.1.32 node_modules/source-map

    fibers@1.0.5 node_modules/fibers
    => Starting meteor app on port:80

    => Redeploying previous version of the app

    -----------------------------------STDOUT-----------------------------------

    To see more logs type 'mup logs --tail=50'

    ----------------------------------------------------------------------------
felipesmendes commented 9 years ago

I tried to run docker attach in mongo image and got this erro:

2015-10-01T16:17:47.927+0000 I JOURNAL [initandlisten] journal dir=/data/db/journal 2015-10-01T16:17:47.927+0000 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed 2015-10-01T16:17:47.927+0000 I JOURNAL [initandlisten] 2015-10-01T16:17:47.927+0000 E JOURNAL [initandlisten] Insufficient free space for journal files 2015-10-01T16:17:47.928+0000 I JOURNAL [initandlisten] Please make at least 3379MB available in /data/db/journal or use --smallfiles 2015-10-01T16:17:47.928+0000 I JOURNAL [initandlisten] 2015-10-01T16:17:47.928+0000 I STORAGE [initandlisten] exception in initAndListen: 15926 Insufficient free space for journals, terminating 2015-10-01T16:17:47.928+0000 I CONTROL [initandlisten] now exiting 2015-10-01T16:17:47.928+0000 I NETWORK [initandlisten] shutdown: going to close listening sockets... 2015-10-01T16:17:47.928+0000 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock 2015-10-01T16:17:47.928+0000 I NETWORK [initandlisten] shutdown: going to flush diaglog... 2015-10-01T16:17:47.928+0000 I NETWORK [initandlisten] shutdown: going to close sockets... 2015-10-01T16:17:47.929+0000 I STORAGE [initandlisten] shutdown: waiting for fs preallocator... 2015-10-01T16:17:47.929+0000 I STORAGE [initandlisten] shutdown: final commit... 2015-10-01T16:17:47.929+0000 I STORAGE [initandlisten] shutdown: closing all files... 2015-10-01T16:17:47.929+0000 I STORAGE [initandlisten] closeAllFiles() finished 2015-10-01T16:17:47.929+0000 I CONTROL [initandlisten] dbexit: rc: 100

I have free space in the machine, how can I solve this?

MasterJames commented 9 years ago

Looks like it says...

Please make at least 3379MB available in /data/db/journal or use --smallfiles

Something like this I think

mongod --config /etc/mongodb.conf --smallFiles