Meteor throws errors on initial run - meteor

I've read multiple questions that are similar to the issue but none of their answers have fixed my problem. Here is a link to the other questions/answers that I've tried.
Creating meteor project throws error
meteor create project failing
I really appreciate the help determining why meteor does not work on 2 of my machines. It's running fine on my laptop. I've tried uninstalling/reinstalling meteor and node. I'm running command line in admin mode. I'm totally stuck here.
My issue/error is:
C:\Users\dbaccus\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.window
s.x86_64\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
throw error;
^
Error: EBUSY: resource busy or locked, symlink 'C:\Users\dbaccus\AppData\Local\.
meteor\packages\babel-compiler\7.1.1\npm\node_modules\#babel\plugin-transform-ob
ject-super' -> 'c:\Users\dbaccus\Documents\GitHub\simple-todos\.meteor\local\.bu
ild441417.build\programs\.build716012.server\npm\node_modules\meteor\babel-compi
ler\node_modules\#babel\plugin-transform-object-super'
at Object.fs.symlinkSync (fs.js:1014:18)
at Object.wrapper (C:\tools\fs\files.js:1607:35)
at symlinkWithOverwrite (C:\tools\fs\files.js:543:11)
at walk (C:\tools\isobuild\builder.js:526:9)
at optimisticReaddir.forEach.item (C:\tools\isobuild\builder.js:621:11)
at Array.forEach (<anonymous>)
at walk (C:\tools\isobuild\builder.js:532:34)
at optimisticReaddir.forEach.item (C:\tools\isobuild\builder.js:621:11)
at Array.forEach (<anonymous>)
at walk (C:\tools\isobuild\builder.js:532:34)
at Builder._copyDirectory (C:\tools\isobuild\builder.js:670:5)
at Builder.copyNodeModulesDirectory (C:\tools\isobuild\builder.js:426:17)
at C:\tools\isobuild\bundler.js:2317:17
at Function._.each._.forEach (C:\Users\dbaccus\AppData\Local\.meteor\package
s\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\underscor
e\underscore.js:87:22)
at JsImage.write (C:\tools\isobuild\bundler.js:2276:7)
at ServerTarget.write (C:\tools\isobuild\bundler.js:2548:13)
at C:\tools\isobuild\bundler.js:2701:30
at Object.keys.forEach.name (C:\tools\isobuild\bundler.js:2836:9)
at Array.forEach (<anonymous>)
at C:\tools\isobuild\bundler.js:2826:26
at C:\tools\isobuild\bundler.js:3167:22
at C:\tools\utils\buildmessage.js:271:13
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89
:14)
at C:\tools\utils\buildmessage.js:264:29
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89
:14)
at C:\tools\utils\buildmessage.js:262:18
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89
:14)
at C:\tools\utils\buildmessage.js:253:23
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89
:14)
at Object.capture (C:\tools\utils\buildmessage.js:252:19)
at bundle (C:\tools\isobuild\bundler.js:3000:31)
at files.withCache (C:\tools\isobuild\bundler.js:2947:32)
at Object.withCache (C:\tools\fs\files.js:1710:12)
at Object.exports.bundle (C:\tools\isobuild\bundler.js:2947:16)
at Profile.run (C:\tools\runners\run-app.js:579:36)
at Function.run (C:\tools\tool-env\profile.js:490:12)
at bundleApp (C:\tools\runners\run-app.js:578:34)
at AppRunner._runOnce (C:\tools\runners\run-app.js:622:35)
at AppRunner._fiber (C:\tools\runners\run-app.js:880:28)
at C:\tools\runners\run-app.js:408:12

Related

Cannot start up existing Meteor application

I have an existing Meteor app that appears to have crashed today. I re-ran meteor in terminal and it proceeds to run meteor but it’s not picking up correct db we are using in mongodb. When I run
MONGO_URL=mongodb://dbuser:dbpass#127.0.0.1/db meteor run it proceeds to build the application but then exits with a code:8. Then it just loops back to creating the application again and selecting package versions. Then when I visit our URL in the browser for the site, I’m getting the following error:
“It looks like you are trying to access MongoDB over HTTP on the native driver port.”
Not sure how to get this app back up and running so any help/suggestions would be appreciated. So short story is we had this running yesterday but then it crashed and now I can’t get the app running again. The db is intact and the collection we use is present in the db. The app code for meteor is all in place. I’m just having problems starting up the app again. The app is hosted in AWS CentOS server running Apache.
Detailed error that I'm seeing when trying to run the app:
/dev_bundle/server-lib/node_modules/fibers/future.js:245
W20171114-03:34:08.618(0)? (STDERR) throw(ex);
W20171114-03:34:08.618(0)? (STDERR) ^
W20171114-03:34:08.618(0)? (STDERR) TypeError: Object #<Object> has no method 'describe'
W20171114-03:34:08.618(0)? (STDERR) at app/server/packages/npm-container/package.js:4:9
W20171114-03:34:08.619(0)? (STDERR) at app/server/packages/npm-container/package.js:25:3
W20171114-03:34:08.619(0)? (STDERR) at /var/www/mongo-parcc-user/parcc-meteor/.meteor/local/build/programs/server/boot.js:222:10
W20171114-03:34:08.619(0)? (STDERR) at Array.forEach (native)
W20171114-03:34:08.619(0)? (STDERR) at Function._.each._.forEach (/root/.meteor/packages/meteor-tool/.1.1.3.115udz9++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)
W20171114-03:34:08.619(0)? (STDERR) at /var/www/mongo-parcc-user/parcc-meteor/.meteor/local/build/programs/server/boot.js:117:5
=> Exited with code: 8

Updating meteor from 1.4.3.2 to 1.5 causes a build error with ecmascript package on MacOS

I have updated meteor for the project to 1.5 and have done the following:
ran meteor update
reinstalled node_modules
ran meteor reset
The relevant github issue
The error message is:
While processing files with ecmascript (for target web.browser): /tools/isobuild/compiler-plugin.js:376:52: Cannot read property 'id' of null
at InputFile.resolve (/tools/isobuild/compiler-plugin.js:376:52)
at InputFile._require (/tools/isobuild/compiler-plugin.js:386:25)
at InputFile.require (/tools/isobuild/compiler-plugin.js:380:17)
at requireWithPrefix (packages/babel-compiler.js:428:32)
at requireWithPath (packages/babel-compiler.js:357:14)
at resolveHelper (packages/babel-compiler.js:330:22)
at packages/babel-compiler.js:306:19
at Array.forEach (native)
at walkHelper (packages/babel-compiler.js:305:22)
at walkBabelRC (packages/babel-compiler.js:295:7)
at resolveHelper (packages/babel-compiler.js:333:11)
at packages/babel-compiler.js:306:19
at Array.forEach (native)
at walkHelper (packages/babel-compiler.js:305:22)
at walkBabelRC (packages/babel-compiler.js:295:7)
at BabelCompiler.BCp._inferHelper (packages/babel-compiler.js:380:3)
at BabelCompiler.BCp._inferFromPackageJson (packages/babel-compiler.js:268:17)
at BabelCompiler.BCp.inferExtraBabelOptions (packages/babel-compiler.js:237:10)
at BabelCompiler.BCp.processOneFileForTarget (packages/babel-compiler.js:166:10)
at BabelCompiler.<anonymous> (packages/babel-compiler.js:109:26)
at Array.forEach (native)
at BabelCompiler.BCp.processFilesForTarget (packages/babel-compiler.js:108:14)

Meteor 1.3 - running meteor test throws AssertionError: "undefined" === false

I've just upgraded an existing Meteor 1.2 project to Meteor 1.3 and would like to start using the new "meteor test" function.
However, when I run the command meteor test --driver-package practicalmeteor:mocha I get the output below.
Can anyone point me in the direction on how to narrow down the cause of this. The only related issue I could find was issue #6527 import-scanner - inconsistent lazy loading package files in Meteor 1.3-rc.3, however this is marked as resolved.
Many thanks in advance for any clues!
[[[[[ Tests ]]]]]
=> Started proxy.
=> Started MongoDB.
/home/me/.meteor/packages/coffeescript/.1.0.15.1v9es4z++os+web.browser+web.cordova/plugin.compileCoffeescript.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:116
throw error;
^
AssertionError: "undefined" === false
at ImportScanner._combineFiles (/tools/isobuild/import-scanner.js:154:12)
at /tools/isobuild/import-scanner.js:140:14
at Array.forEach (native)
at ImportScanner.addInputFiles (/tools/isobuild/import-scanner.js:119:11)
at /tools/isobuild/compiler-plugin.js:756:15
at Array.forEach (native)
at Function.computeJsOutputFilesMap (/tools/isobuild/compiler-plugin.js:726:19)
at ClientTarget._emitResources (/tools/isobuild/bundler.js:910:8)
at /tools/isobuild/bundler.js:677:12
at /tools/utils/buildmessage.js:359:18
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:352:34
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:350:23
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at Object.enterJob (/tools/utils/buildmessage.js:324:26)
at ClientTarget.make (/tools/isobuild/bundler.js:668:18)
at /tools/isobuild/bundler.js:2509:14
at /tools/isobuild/bundler.js:2599:20
at Array.forEach (native)
at Function._.each._.forEach (/home/me/.meteor/packages/meteor-tool/.1.3.0_3.61500n++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
at /tools/isobuild/bundler.js:2598:7
at /tools/utils/buildmessage.js:271:13
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:264:29
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:262:18
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:253:23
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at Object.capture (/tools/utils/buildmessage.js:252:19)
at Object.exports.bundle (/tools/isobuild/bundler.js:2490:31)
at /tools/runners/run-app.js:591:36
at Function.run (/tools/tool-env/profile.js:489:12)
at bundleApp (/tools/runners/run-app.js:581:34)
at AppRunner._runOnce (/tools/runners/run-app.js:634:35)
at AppRunner._fiber (/tools/runners/run-app.js:887:28)
at /tools/runners/run-app.js:411:12
By a process of brute force elimination (removing all files from the project and adding them back, one by one!), I discovered that the problem is being triggered by the presence of the bootstrap-settings.json file which is used to manage the bootstrap files generated by the huttonr:bootstrap3 package
I have raised an issue regarding this directly with the project owner: https://github.com/huttonr/bootstrap3/issues/17
In the meantime, as a workaround I have disabled the huttonr:bootstrap3 package and removed the client/stylesheets/bootstrap-settings.json file

Box2d-Web with Meteor

I want to use Box2D-Web with Meteorjs on both client and server side. I used this in nodejs. There was a small configuration that exports Box2D variable, and it was working with nodejs. The additional configuration was
exports.Box2D = Box2D;
at the bottom of the libary.
But I couldn't load it in meteor. I put the Box2D-web under lib directory in my project. But it gives an error and I still don't see what the problem is.
Here is what meteor saying;
W20140106-00:15:03.627(2)? (STDERR) /Users/ahmetdal/workspace/realhaxtmp/.meteor/local/build/programs/server/boot.js:186
W20140106-00:15:03.692(2)? (STDERR) }).run();
W20140106-00:15:03.692(2)? (STDERR) ^
W20140106-00:15:03.692(2)? (STDERR) TypeError: Cannot call method 'write' of undefined
W20140106-00:15:03.693(2)? (STDERR) at Console.log (console.js:53:16)
W20140106-00:15:03.694(2)? (STDERR) at Object.Meteor._debug (packages/meteor/debug.js:41)
W20140106-00:15:03.694(2)? (STDERR) at _.extend.publish (packages/livedata/livedata_server.js:1166)
W20140106-00:15:03.694(2)? (STDERR) at app/server/publications.js:7:12
W20140106-00:15:03.694(2)? (STDERR) at /Users/ahmetdal/workspace/realhaxtmp/.meteor/local/build/programs/server/boot.js:159:61
W20140106-00:15:03.694(2)? (STDERR) at Array.forEach (native)
W20140106-00:15:03.694(2)? (STDERR) at Function._.each._.forEach (/Users/ahmetdal/.meteor/tools/09b63f1ed5/lib/node_modules/underscore/underscore.js:79:11)
W20140106-00:15:03.695(2)? (STDERR) at /Users/ahmetdal/workspace/realhaxtmp/.meteor/local/build/programs/server/boot.js:159:5
There is not error about the Box2D-Web library. I tried to find any alternative meaning for the error but, I could not find anything either.
This error is being occurred when I put the library under lib folder under project root.
I did not put all code of library here. Because it really consists of too many lines of codes.
What additional configration in library can I do to apply it to Meteorjs?
Thank you!
Placing Javascript files like the Box2D-Web library in the lib folder in the root of your project will cause the code to be run on both the client and the server. The error occurs when the library gets run on the server.
To fix this, just place the library file into /client/lib/.

Error: watch EMFILE when putting node_modules in /public

Supposedly, I'm supposed to put node_modules into /public in Meteor. This works fine, up until a point where I get a lot of files in the node_modules directory, and I start getting this error:
Error: watch EMFILE
at errnoException (fs.js:648:11)
at FSWatcher.start (fs.js:675:11)
at Object.watch (fs.js:703:11)
at [object Object]._scan (/usr/local/meteor/app/meteor/run.js:347:12)
at /usr/local/meteor/app/meteor/run.js:362:14
at Array.forEach (native)
at Function.<anonymous> (/usr/local/meteor/app/lib/third/underscore.js:76:11)
at [object Object]._scan (/usr/local/meteor/app/meteor/run.js:361:9)
at /usr/local/meteor/app/meteor/run.js:362:14
at Array.forEach (native)
How should I deal with this?
This command solves it in linux :
sudo sh -c 'echo 8192 > /proc/sys/fs/inotify/max_user_instances'

Resources