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
Related
I got this error when installing MoonMail follow the default instructions. It's seem that the installation guide is out of date. Do you have any ideas how to solve this problem?
Serverless: WARNING: This variable is not defined: sendCampaignTopicARN
Serverless: WARNING: This variable is not defined: sendEmailsTopicARN
Serverless: WARNING: This variable is not defined: sentEmailsTopicARN
Serverless: WARNING: This variable is not defined: projectBucket
/Users/michael/.node/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: [AttachSenderTopic, PrecompileCampaignTopic, SentEmailsTable, SendCampaignTopic, PrecompileEmailTopic, AttachRecipientsTopic, ClicksStream, SentEmailsTopic, CampaignsTable, TemplatesTable, FreeUsersSendEmailQueue, UsersTable, IamRoleLambda, AttachListRecipientsTopic, StaticDataBucket, UnsubscribedRecipientTopic, LinksTable, UpdateListImportStatusTopic, EmailAdminsTopic, ListsTable, EmailNotificationsTopic, AttachRecipientsCountTopic, OpensStream, UpdateCampaignTopic, SendEmailsTopic, RecipientsImportS3Bucket, ReportsTable].
In order to deploy the project, you've got to define all those variables in the appropriate s-variables-*.json file. Besides, the issue could be somewhere else. I suggest you to go to the CloudFormation web console and check the events history for the MoonMail stack, it provides more information and better understanding about why it errored than the serverless CLI.
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)
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?
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