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)
Related
I have been able to run through the following Grails 3 guide for deploying a Grails application to GCP.
https://guides.grails.org/grails-google-cloud/guide/index.html
I've tried to mirror this using my own Grails 4 application but it fails when I try to access it.
appengineDeploy completes successfully but when I try and access the webapp URL, I get a long stacktrace which culminates in the following error;
Failed to instantiate [org.grails.orm.hibernate.HibernateDatastore]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/mysql/cj/api/io/SocketFactory
...
...
Caused by: java.lang.ClassNotFoundException: com.mysql.cj.api.io.SocketFactory
I've been trying all sorts of various versions of the socket factory dependency to try and solve and redeploy but all result in the same error.
I have used various version of the j-6 connector (com.google.cloud.sql:mysql-socket-factory-connector-j-6) and my most recent attempt used the j-8 (1.0.14).
At this point it would be great to even know if what I'm trying is even possible. Java 11 support has been added quite recently and I have made the necessary config adjustments to get my app to deploy, but I cannot then access it.
Upgrading to version 8 of mysql-connector-java in tandem with mysql-socket-factor-connector-j-8 appears to have made this particular issue go away (and moved me to the next).
Dependencies are as follows;
runtime "mysql:mysql-connector-java:8.0.15"
runtime "com.google.cloud.sql:mysql-socket-factory-connector-j-8:1.0.14"
While trying to install MoonMail, I'm running the following command:
sls resources deploy
and I'm getting the following error:
/usr/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:61
fn = function () { throw arg; };
^
ServerlessError: ServerlessError: An error occurred while provisioning your cloudformation: The following resource(s) failed to create: [ScheduledEmailsTable, AttachSenderTopic, SentEmailsTable, SendCampaignTopic, PrecompileEmailTopic, AttachRecipientsTopic, CampaignsTable, TemplatesTable, AttachListRecipientsTopic, RecipientsTable, AutomationActionsTable, ClicksReportTable, UnsubscribedRecipientTopic, LinksTable, ExpertsTable, UpdateUserReputationTopic, EmailNotificationsTopic, OpensStream, UpdateCampaignTopic, OpensTable]. . Delete requested by user.
I've already tried giving the IAM user admin access, unfortunately it didn't help.
Go to your AWS dashboard, CloudFormation section, and select the stack where you're deploying the project. You'll see exactly the error that prevented you from creating the stack, serverless errors are not really descriptive when it comes to CloudFormation
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.
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?
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.