I'm trying to configure the MoonMail source code on AWS by Serverless, but when following the steps on github, it doesn’t work.
According to the information, an error occurred while provisioning the cloud formation:
“ServerlessError: ServerlessError: An error occurred while
provisioning your cloudformation: The following resource(s) failed to
create: [AutomationsTable, AwsMarketplaceNotificationsQueue,
ScheduledEmailsTable, ListExportS3Bucket, PrecompileCampaignTopic,
SentEmailsTable, SendCampaignTopic, PrecompileEmailTopic,
AttachRecipientsTopic, ListSegmentsTable, CampaignsTable,
TemplatesTable, FreeUsersSendEmailQueue, AttachSegmentRecipientsTopic,
UsersTable, EventsBusTopic, IamRoleLambda, AttachListRecipientsTopic,
RecipientsTable, StaticDataBucket, AutomationActionsTable,
ClicksReportTable, PaymentLogsTable, LinksTable,
UpdateListImportStatusTopic, ExpertsTable, EmailAdminsTopic,
ClicksTable, ListsTable, UpdateCampaignTopic, SendEmailsTopic,
OpensTable, OpensReportTable, RecipientsImportS3Bucket, ReportsTable].
. Delete requested by user.”
On CloudFormation no stack is created. I already tried some suggestions that can be found online, mainly on stackOverflow trough the MoonMail tag, but none seemed to work.
Thanks.
Related
I am trying to invoke Azure Batch Rest API to create a pool from ADF.
Below is the Post url I am trying -
https://management.azure.com/subscriptions/a01c19ca-c50f-4be0-904d-xxxxxxxxxxxx/resourceGroups/
sumo-dev-rg/providers/Microsoft.Batch/batchAccounts/sumobatch/pools/testpool?api-version=2021-01-01
testpool above doesn't exist but something that should be created once the RestAPi runs successfully.
However, I am getting the following error code -
Error details
Error code 2108
Troubleshooting guide
Failure type
User configuration issue
Details
{"error":{"code":"InvalidUri","message":"The requested URI does not represent any resource on the server.\nRequestId:b512af12-c1b7-474a-9773-dcf034b07e0e\nTime:2021-07-18T05:57:31.4199546Z","target":"BatchAccount","details":[{"code":"UriPath","message":"/subscriptions/a01c19ca-c50f-4be0-904d-************/resourceGroups/
sumo-dev-rg/providers/Microsoft.Batch/batchAccounts/sumobatch/pools/testpool"}]}}
Source Pipeline poolstart
Any leads will be highly appreciated ?
Thank you Poon. Posting your comment as Answer to help other community members.
Adding the PUT before the URL fixed the issue
When I recreate my VM I got the following error:
Problem occurred during request to Azure services. Cloud provider details: Unable to edit or replace deployment 'VM-Name': previous deployment from '8/20/2019 6:20:33 AM' is still active (expiration time is '8/27/2019 5:17:41 AM'). Please see https://aka.ms/arm-deploy for usage details.
Help me please to understand.
What could be the cause of the error ?
UPDATED:
This deployment has not been started previously.
Prior to this, errors were received during creation:
Azure is not available now. Please Try again later
There were several such errors one at a time and then I got that error related to:
Unable to edit or replace deployment
My assumptions about this.
Tell me, am I right or not ?
I launched the image, then after some time I recreated it.
Creation began, but at that moment the connection with Azure was lost.
Then, when the connection was restored, we tried to make a deployment that was not removed in the previous attempt (because there was no connection with Azure).
As a result, we got such an error.
Does this theory make sense?
exactly what it says, there is another deployment with the same name going on at this time, either change the name of the deployment you are trying to queue or wait for the other deployment to finish\fail
This can also occur if you use Bicep templates for your ARM deployement and multiple modules or resources in the template have the same name:
module fooModule '../modules/foo.bicep' = {
name: 'foo'
}
module barModule '../modules/bar.bicep' = {
name: 'foo'
}
I got the same error initially pipeline was working but when retriggered pipeline took more time so i canceled the deployment and made a fresh rerun it encounters. i think i need wait until that deployment filed.
I am trying to deploy app in Google App Engine and I am getting following error message
ERROR: (gcloud.app.deploy) Error Response: [13] Flex operation
projects/black-tenure-213005/regions/us-east1/operations/379b4ee9-aa45-4681-bf6e-8f4fcc8b93f1
error [INTERNAL] : An internal error occurred while processing task
/appengine-flex-v1/insert_flex_deployment/flex_create_resources>2018-09-27T03:45:41.652Z2073:
500 Internal Server Error { "code" : 500, "errors" : [ {
"debugInfo" : "No backend error mapping found for errorCode: deployment.proto.DeploymentManagerErrorDomain.INTERNAL_ERROR, method:
deploymentmanager.deployments.insert, and location: null. Output will
be 500 Internal Server Error.\n/DeploymentsService.Insert to
[2002:a30:2f16::]:4118 [APPLICATION_ERROR(500)]
com.google.security.data_access. client.DataAccessException:
com.google.net.rpc3.client.RpcClientException:
APPLICATION_ERROR;security.data_access/DataAccessService.RequestTransactDat;java.security.GeneralS
ecurityException: [Policy name: deploymentmanager-transact-dat] client
\"MdbUser = cloud-dm\" is not allowed by the policy;
Please help me regarding this.
Thanks in advance.
As #DazWilkin pointed out, a general issue was affecting the Deployment Manager in GCP. Here's the incident documented in the Google Cloud Status Dashboard. By what I can see from the report, the issue has already been solved.
Errors with code 500 when deploying GAE Flex applications can be linked to the Deployment Manager experiencing issues. Given that the original issue is solved, the GAE Flex deployments should be working normally again.
I got an "500 Internal Server Error - An error occurred while starting the application" after deploying my application: https://iidapp.azurewebsites.net/
I keep finding the following error message but I am unable to find out on msdn websites any information describing how I can specify the SAS URL
INFO: The app was working for a long period and I didn't have to set the SAS URL; I wonder why suddenly Azure is generating exceptions
INFO2: the app works perfectly on my local machine
Any help is welcomed as I couldn't find any solution by reading the related topics on stackoverflow
2017-04-05T18:51:32
System.ApplicationException: The trace listener AzureBlobTraceListener is disabled. ---> System.InvalidOperationException: The SAS URL for the cloud storage account is not specified. Use the environment variable 'DIAGNOSTICS_AZUREBLOBCONTAINERSASURL' to define it.
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.RefreshConfig()
--- End of inner exception stack trace ---
An error was triggered by W3SVC-WP : {app name}02000780
I found out on eventid that the code 02000780 meant that a file was missing
I eventually found out that it was possible to log further information by enabling the stdoulog inside the web.config. Read When a .NET Core Azure App Service won’t start: 502.5 Process Failure
I opened the debug console and found out that a directory wasn't found https://{app_id}.scm.azurewebsites.net/DebugConsole
Voilà! I corrected the code and the app is up and running!
I encounter an error trying to deploy cloud foundry to azure. Below is the stack trace. Any ideas how to resolve it?
Deploying
---------
Director task 7
Deprecation: Ignoring cloud config. Manifest contains 'networks' section.
Started preparing deployment > Preparing deployment. Done (00:00:01)
Error 100: Unable to render instance groups for deployment. Errors are:
- Unable to render jobs for instance group 'cf_z1'. Errors are:
- Unable to render templates for job 'cloud_controller_ng'. Errors are:
- Error filling in template 'cloud_controller_api.yml.erb' (line 131: undefined method `empty?' for 123456:Fixnum)
It seems BOSH is expecting a string for a value in your manifest and you have supplied a number. I'm not sure what version of cloudfoundry you are deploying but looking at cloud_controller_api.yml.erb on line 131, I think you should start by looking at the value for router.route_services_secret in your manifest.