Ran meteor update to 1.4.3.1, now cannot deploy app

I have been building an app on Meteor 1.2.1, with Blaze, and have deployed to Digital Ocean. Today, I ran meteor update to 1.4.3.1. The app will still run localhost but I can no longer deploy.

When I run mupx deploy, I get the following errors. I haven’t made any other changes to my code aside from updating the Meteor version, so I don’ t understand how there is a syntax error, unless it is in Meteor itself:

Started TaskList: Deploy app '<appname>' (linux)
[104.236.197.201] - Uploading bundle
[104.236.197.201] - Uploading bundle: SUCCESS
[104.236.197.201] - Sending environment variables
[104.236.197.201] - Sending environment variables: SUCCESS
[104.236.197.201] - Initializing start script
[104.236.197.201] - Initializing start script: SUCCESS
[104.236.197.201] - Invoking deployment process
[104.236.197.201] - Invoking deployment process: SUCCESS
[104.236.197.201] - Verifying deployment
[104.236.197.201] x Verifying deployment: FAILED
        
        -----------------------------------STDERR-----------------------------------
        WARN package.json meteor-dev-bundle@0.0.0 No description
        npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
        npm WARN package.json meteor-dev-bundle@0.0.0 No README data
        npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server)
        => Starting meteor app on port:80
        
        /bundle/bundle/programs/server/mini-files.js:74
        const unicodeNormalizePath = (path) => {
                                             ^
        SyntaxError: Unexpected token >
            at Module._compile (module.js:439:25)
            at Object.Module._extensions..js (module.js:474:10)
            at Module.load (module.js:356:32)
            at Function.Module._load (module.js:312:12)
            at Module.require (module.js:364:17)
            at require (module.js:380:17)
            at Object.<anonymous> (/bundle/bundle/programs/server/boot.js:9:13)
            at Module._compile (module.js:456:26)
            at Object.Module._extensions..js (module.js:474:10)
            at Module.load (module.js:356:32)
         
        => Redeploying previous version of the app
         
        -----------------------------------STDOUT-----------------------------------
        
        To see more logs type 'mup logs --tail=50'
        
        ----------------------------------------------------------------------------

When I run mupx logs -f, I get the following (multiple times). I’ve only ever added packages through meteor add <package> so not sure about the npm errors below.

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file      : settings.json

[104.236.197.201] npm WARN deprecated This version of npm lacks support for important features,
[104.236.197.201] npm WARN deprecated such as scoped packages, offered by the primary npm
[104.236.197.201] npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
[104.236.197.201] npm WARN deprecated latest stable version. To upgrade to npm@2, run:
[104.236.197.201] npm WARN deprecated 
[104.236.197.201] npm WARN deprecated   npm -g install npm@latest-2
[104.236.197.201] npm WARN deprecated 
[104.236.197.201] npm WARN deprecated To upgrade to the latest stable version, run:
[104.236.197.201] npm WARN deprecated 
[104.236.197.201] npm WARN deprecated   npm -g install npm@latest
[104.236.197.201] npm WARN deprecated 
[104.236.197.201] npm WARN deprecated (Depending on how Node.js was installed on your system, you
[104.236.197.201] npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
[104.236.197.201] npm WARN deprecated on Windows, run them from an Administrator prompt.)
[104.236.197.201] npm WARN deprecated 
[104.236.197.201] npm WARN deprecated If you're running the version of npm bundled with
[104.236.197.201] npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
[104.236.197.201] npm WARN deprecated will be bundled with a version of npm@2, which has some small
[104.236.197.201] npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
[104.236.197.201] npm WARN deprecated semver behavior.
[104.236.197.201] npm WARN package.json meteor-dev-bundle@0.0.0 No description
[104.236.197.201] npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
[104.236.197.201] npm WARN package.json meteor-dev-bundle@0.0.0 No README data
[104.236.197.201] 
[104.236.197.201] > fibers@1.0.15 install /bundle/bundle/programs/server/node_modules/fibers
[104.236.197.201] > node build.js || nodejs build.js
[104.236.197.201] 
[104.236.197.201] make: Entering directory `/bundle/bundle/programs/server/node_modules/fibers/build'
[104.236.197.201]   CXX(target) Release/obj.target/fibers/src/fibers.o
[104.236.197.201]   CXX(target) Release/obj.target/fibers/src/coroutine.o
[104.236.197.201]   CC(target) Release/obj.target/fibers/src/libcoro/coro.o
[104.236.197.201]   SOLINK_MODULE(target) Release/obj.target/fibers.node
[104.236.197.201]   SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished
[104.236.197.201]   COPY Release/fibers.node
[104.236.197.201] make: Leaving directory `/bundle/bundle/programs/server/node_modules/fibers/build'
[104.236.197.201] Installed in `/bundle/bundle/programs/server/node_modules/fibers/bin/linux-x64-11/fibers.node`
[104.236.197.201] npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server)
[104.236.197.201] ansi-regex@0.2.1 node_modules/ansi-regex
[104.236.197.201] 
[104.236.197.201] ansi-styles@1.1.0 node_modules/ansi-styles
[104.236.197.201] 
[104.236.197.201] escape-string-regexp@1.0.5 node_modules/escape-string-regexp
[104.236.197.201] 
[104.236.197.201] chalk@0.5.1 node_modules/chalk
[104.236.197.201] 
[104.236.197.201] has-ansi@0.1.0 node_modules/has-ansi
[104.236.197.201] 
[104.236.197.201] strip-ansi@0.3.0 node_modules/strip-ansi
[104.236.197.201] 
[104.236.197.201] supports-color@0.2.0 node_modules/supports-color
[104.236.197.201] 
[104.236.197.201] eachline@2.3.3 node_modules/eachline
[104.236.197.201] 
[104.236.197.201] type-of@2.0.1 node_modules/type-of
[104.236.197.201] 
[104.236.197.201] amdefine@1.0.1 node_modules/amdefine
[104.236.197.201] 
[104.236.197.201] meteor-promise@0.8.0 node_modules/meteor-promise
[104.236.197.201] 
[104.236.197.201] asap@2.0.5 node_modules/asap
[104.236.197.201] 
[104.236.197.201] underscore@1.5.2 node_modules/underscore
[104.236.197.201] 
[104.236.197.201] source-map-support@0.3.2 node_modules/source-map-support
[104.236.197.201] 
[104.236.197.201] semver@4.1.0 node_modules/semver
[104.236.197.201] 
[104.236.197.201] promise@7.1.1 node_modules/promise
[104.236.197.201] 
[104.236.197.201] source-map@0.1.32 node_modules/source-map
[104.236.197.201] 
[104.236.197.201] fibers@1.0.15 node_modules/fibers
[104.236.197.201] => Starting meteor app on port:80
[104.236.197.201] 
[104.236.197.201] /bundle/bundle/programs/server/mini-files.js:74
[104.236.197.201] const unicodeNormalizePath = (path) => {
[104.236.197.201]                                      ^
[104.236.197.201] SyntaxError: Unexpected token >
[104.236.197.201]     at Module._compile (module.js:439:25)
[104.236.197.201]     at Object.Module._extensions..js (module.js:474:10)
[104.236.197.201]     at Module.load (module.js:356:32)
[104.236.197.201]     at Function.Module._load (module.js:312:12)
[104.236.197.201]     at Module.require (module.js:364:17)
[104.236.197.201]     at require (module.js:380:17)
[104.236.197.201]     at Object.<anonymous> (/bundle/bundle/programs/server/boot.js:9:13)
[104.236.197.201]     at Module._compile (module.js:456:26)
[104.236.197.201]     at Object.Module._extensions..js (module.js:474:10)
[104.236.197.201]     at Module.load (module.js:356:32)

Has anyone ever seen these errors? This is the first app I have ever built so it this is far outside my skill level.

For now, I just created a new project with Meteor 1.2.1 and copied in my files.

I found this issue that seems to address the problem I was having. It recommends moving away from mupx.

I updated from the beta to the full release and am now getting this error:

=> Started proxy.                             
=> Started MongoDB.                           
/Users/mattmacpherson/.meteor/packages/templating-compiler/.1.2.15.17an6zz++os+web.browser+web.cordova/plugin.compileTemplatesBatch.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:177
      throw error;
      ^

Error: ENFILE: file table overflow, scandir '/Users/mattmacpherson/Documents/Websites/example/node_modules/npm/node_modules/validate-npm-package-license'
    at Error (native)
    at Object.fs.readdirSync (fs.js:808:18)
    at Object.wrapper (/tools/fs/files.js:1535:35)
    at readDirectory (/tools/fs/watch.js:271:26)
    at Watcher._fireIfDirectoryChanged (/tools/fs/watch.js:410:23)
    at /tools/fs/watch.js:662:12
    at Array.forEach (native)
    at Function._.each._.forEach (/Users/mattmacpherson/.meteor/packages/meteor-tool/.1.4.3_1.4ehsmf++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
    at Watcher._checkDirectories (/tools/fs/watch.js:651:7)
    at new Watcher (/tools/fs/watch.js:359:10)
    at setupClientWatcher (/tools/runners/run-app.js:786:23)
    at [object Object]._.extend._runOnce (/tools/runners/run-app.js:797:7)
    at [object Object]._.extend._fiber (/tools/runners/run-app.js:876:28)
    at /tools/runners/run-app.js:403:12

Seems unrelated to your error though. I’m not using mup/mupx.

I had some other errors when i updated to meteor 1.4.3.1

Thought it was from meteor. But i had a bugged npm package that i added just before updating.

Removing it fixed my problem.

I am also facing the same problem with meteor 1.4.3.2

Deleted =====================================

Ran into this problem when migrating my app from 1.2 to 1.5. Did you find a solution to this? I would like to keep my mupx setup, if possible. If there’s a fork of mupx that’s working better, however, I’d be happy to switch to that.

Problem could be: in docker image.
Meteor 1.3 and older using kadirahq/meteord dockar image and later version of meteor is using abernix/meteord:base so remove docker container and docker image and deploy.

It should work after that.

Thanks. I switched to the latest mup branch, and everything is working now.

1 Like

Updated from 1.3 to 1.5 as well, I mup logs not working at all.