I am following this tutorial (using meteor on modulus) to test telescope app and how the deploy works
I am getting this error :
Unable to connect to any application instances.
And this is the log:
/mnt/data/1/node_modules/fibers/future.js:245
throw(ex);
^ TypeError: Cannot read property 'name' of undefined
at app/server/migrations.js:469:43
at [object Object]._.extend.forEach (packages/mongo/mongo_driver.js:965:1)
at [object Object].Cursor.(anonymous function) [as forEach] (packages/mongo/mongo_driver.js:812:1)
at Object.migrationsList.updateUserNames (app/server/migrations.js:462:14)
at runMigration (app/server/migrations.js:45:52)
at app/server/migrations.js:10:5
at Array.forEach (native)
at Function..each..forEach (packages/underscore/underscore.js:105:1)
at Meteor.methods.removeMigration.Migrations.remove.name (app/server/migrations.js:9:5)
at /mnt/data/1/programs/server/boot.js:229:5 [2015-04-09T22:31:49.395Z] Failed to start application.
Thank you !!
This is a common issue when you don't redeploy the application after the first step.
run this 2 commands.
modulus project restart
modulus deploy
NOTE be sure the URL don't have any blank space either.
From step three of the tutorial,
The Meteor app is not quite ready yet and the logs will show errors. We have to deploy first in order to receive a URL for Meteor's required environment variables.
Have you goen through and correctly defined all of the environment variables?
Related
I have a long JINJA2 file used to deploy Elastic application over a set of servers.
The Ansible task to deploy the application is working fine, but task to deploy the application config file is failing and returning the error message below:
fatal: [HOSTNAME.ACME.COM] =>
{'msg': "TypeError: argument of type 'StrictUndefined' is not iterable", 'failed': True}
I really believe that there is an error in the JINJA2 file, but was not able to find it out so far.
Could someone help me?
Thanks.
We have generated jHipster project using "yo jHipster" which runs fine locally.
Now, we want to deploy the application to AWS using Elastic Beanstalk.
I have tried deploying the WAR file generated for the jHipster project using the Elastic Beanstalk console, however, it fails to launch the application.
Then I came across a sub project of jHipster to generate the application for AWS directly. e.g. yo jHipster:aws
But I am getting the following error while running it. Any pointers to investigate this issue further please?
yo jhipster:aws
events.js:141
throw er; // Unhandled 'error' event
^
TypeError: Cannot read property 'toLowerCase' of undefined
at module.exports.AwsGenerator.extend.initializing.checkDatabase (/usr/local/lib/node_modules/generator-jhipster/aws/index.js:23:37)
at Object. (/usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/base.js:436:25)
at /usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-generator/node_modules/run-async/index.js:24:25
at /usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/base.js:446:8
at processImmediate [as _immediateCallback] (timers.js:383:17)
Is it possible to deploy a Single Page App project build using grunt to IIS using MSDeploy from TeamCity? The project is not any kind of Visual Studio solution and doesn't get built using MSBuild.
My Command parameters which are not working are:
-source:package='%teamcity.build.checkoutDir%\Dist.%build.number%.zip' -dest:auto,computerName="%system.MsDeployServiceUrl%",userName="%system.UserName%",password="%system.Password%",authtype="basic",includeAcls="False"
-verb:sync -setParamFile:"%teamcity.build.checkoutDir%\Dist.%build.number%.zip.SetParameters.xml"
-AllowUntrusted -setParam:"IIS Web Application Name"="%system.WebSiteName%" -verbose
The error I am getting is:
[11:47:31][Step 3/3] Error Code: ERROR_EXCEPTION_WHILE_CREATING_OBJECT
[11:47:31][Step 3/3] More Information: Object of type 'package' and
path 'D:\TeamCity\buildAgent\work\e2b0015b49d87e90\Dist.30.zip' cannot
be created. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT.
[11:47:31][Step 3/3] Error: The Zip package
'D:\TeamCity\buildAgent\work\e2b0015b49d87e90\Dist.30.zip' could not
be loaded. [11:47:31][Step 3/3] Error: Could not find file
'D:\TeamCity\buildAgent\work\e2b0015b49d87e90\Dist.30.zip'.
[11:47:31][Step 3/3] Error count: 1. [11:47:31][Step 3/3] Process
exited with code -1 [11:47:31][Step 3/3] Step Deploy (Command Line)
failed
My build process is working as I end up with the correct artefacts, I just don't seem to be able to deploy my generated artefacts using MSDeploy
This is a screenshot of my artefacts:
I managed to get this working by changing my parameters to the following:
-source:iisapp='%teamcity.build.checkoutDir%\dist' -dest:iisapp='C:\www\xxxx-website',computerName="%system.MsDeployServiceUrl%",userName="%system.UserName%",password="%system.Password%",authtype="basic",includeAcls="False"
-verb:sync -AllowUntrusted -verbose
And changing my user to an admin user rather than an IIS user. Note use of iisapp - the key was to read the MSDeploy api using msdeploy -help
FYI - a good test is to use the intended command against msdeploy.exe in console and check output errors then push command into teamcity when it's working.
I created a grunt and gulp plugin to do just what you are looking to do. gulp-mswebdeploy-package and grunt-mswebdeploy-package will create a ms webdeploy package from any folder and do not require your build to be running on windows.
https://www.npmjs.com/package/gulp-mswebdeploy-package
https://www.npmjs.com/package/grunt-mswebdeploy-package
I want to develop a new cartridge for my own use. I use OpenShift Cartridge Development Kit to start my work. My building script is written in .openshift/action_hooks/build and it can be successfully executed.
But when I tried to use the command displayed on the homepage of the CDK project - "rhc create-app mynewcart http://##YOUR-DOMAIN##/manifest/##YOUR-COMMIT-ID##" - to create an app, I got the following error: "Unable to complete the requested operation due to: An invalid exit code (1) was returned from the server ex-std-node161.prod.rhcloud.com. This indicates an unexpected problem during the
execution of your request."
How can I trace the progress of deploying and find out where is the code that caused the problem? Is there any log file available for me to analyse?
Use the --debug option when running the command and you'll get much more detailed output:
rhc create-app mynewcart http://##YOUR-DOMAIN##/manifest/##YOUR-COMMIT-ID## --debug
While trying to login using the Meteor packages accounts-facebook and accounts-google, I'm getting an OAuth handler exception. Packages accounts-twitter appears to work fine and logs in perfectly. I haven't written any code, this is right out of the box using the accounts-ui package
The front end simply says "Internal Server Error" in red text, and the Meteor stack trace is the following:
Exception in oauth request handler [Error: failed]
Exception while invoking method 'login' Error: failed
at Request.Meteor.http.call [as _callback] (app/packages/http/httpcall_server.js:117:19)
at Request.init.self.callback (/usr/lib64/meteor/lib/node_modules/request/main.js:122:22)
at Request.EventEmitter.emit (events.js:96:17)
at Request.<anonymous> (/usr/lib64/meteor/lib/node_modules/request/main.js:654:16)
at Request.EventEmitter.emit (events.js:123:20)
at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer (/usr/lib64/meteor/lib/node_modules/request/main.js:616:14)
at IncomingMessage.EventEmitter.emit (events.js:123:20)
at IncomingMessage._emitEnd (http.js:366:10)
at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23)
at CleartextStream.socketOnData (http.js:1366:20)
I'm running the Meteor app on my own infrastructure with a working domain name. Any idea what's going on?
I had the same issue, and it turned out my service was not configured correctly, specifically I had the wrong Facebook app secret. Go into your mongo shell and check your meteor_accounts_loginServiceConfiguration to ensure it's set up correctly.
Start up Meteor, then go into the mongo shell via meteor mongo
Then type 'db.meteor_accounts_loginServiceConfiguration.find()' to show the documents in that collection. Now check your Facebook document to ensure it matches the app you created on Facebook exactly.
I did this and everything worked immediately.
Sorry for that. Our error reporting in these cases sucked. A fix is coming out in the soon-to-be-released Meteor 0.6.2.