I want to configure an Oracle Se instance on the elastic beanstalk environment, and I have chosen the oracle-se from the selection box, but the related select option of version and instance class does not be updated.
I have chosen the db.t2.micro (due to free tier usage), and it shows I have selected the db.m1.small. Then, it keeps prompting the error message when I save that configuration.
For example:
Unable to retrieve RDS configuration options.
Configuration validation exception: Invalid option value:
'db.m1.small' (Namespace: 'aws:rds:dbinstance', OptionName:
'DBInstanceClass'): DBInstanceClass db.m1.small not supported for
oracle-se1 db engine.
Sample image with related error message
I have also searched the other stack overflow forum like Unable to add an RDS instance to Elastic Beanstalk, and those forum has stated that AWS has resolved this problem, but it does not work for me.
Related
I am trying to set up a var template in grafana that would allow me to only show ec2 instances with specific ec2 tags. I did find
ec2_instance_attribute(us-east-1, InstanceId, {"tag:app": ["$application"]})
on a grafana community site and i changed it to
ec2_instance_attribute(us-west-2, InstanceId, {"tag:ENV": ["Prod"]})
The tags based off of my ec2 instance tags is and i keep getting a metric error. I tried removing the brackets and tweaking and still can't figure it out. Does anyone know how to create this using this method or another one i haven't thought of?
Your expression should be working. But I had this error also, due to a missing AWS Policy permission. This might be the case for you as well AWS has a default Policy to read CloudWatch data: "CloudWatchReadOnlyAccess ", but creating my own policy as a copy of "CloudWatchReadOnlyAccess" and adding "ec2:DescribeTags" and "ec2:DescribeInstances" made this work for me.
The above answer might be only applicable when you control your access via Roles with Policies.
When trying to create an ECS instance via cli tools I get the error in subject and I can't find what it means. For example:
$ ./aliyun ecs RunInstances --Amount 1 --ImageId m-0xidtg6bbw1s8voux52d --InstanceType ecs.n1.medium --InstanceName Composer-Test-VM-1 --SecurityGroupId sg-0xi4w9isg0p1ytj1qbhf
ERROR: SDK.ServerError
ErrorCode: InvalidResourceType.NotSupported
Recommend:
RequestId: 1B3E65BD-D181-4552-9A58-599FC51924A7
Message: user order resource type [classic] not exists in [random]
I have credentials configured in ~/.aliyun/config.json.
The default region in config is us-east-1, the ImageId and SecurityGroupId are both in the same region.
I tried a few other instance types and either I get the same error message or [classic] is replaced by the prefix of the instance type. This leads me to think I can't create virtual machines from some of these instance types in my region but I have no idea why.
Does anyone know what is causing this specific error or where to find more documentation about it ?
I have found the culprit here. Although not stated (e.g. in --help) the --VSwitchId option is mandatory when specifying a --SecurityGroupId. The VSwitch needs to be in the same availability zone as your security group.
On this link, check out the following documentation under "Description":
For network configuration:
To create an instance in a VPC, you must specify a VPC and a VSwitch. One instance can belong only to one VSwitch.
When you specify VSwitchId, ensure that the security group and VSwitch specified by SecurityGroupId and VSwitchId belong to the same VPC.
If you specify both VSwitchId and PrivateIpAddress, ensure that the private IP address specified by PrivateIpAddress is within the CIDR block of the VSwitch.
PrivateIpAddress is dependent on VSwitchId. You cannot only specify the PrivateIpAddress parameter.
Also Note: The Alibaba Cloud product APIs are divided into RPC API and RESTful API. Most products use RPC style. When you use Alibaba Cloud CLI to call the interface, APIs of different styles have different calling methods.
Check out the following link: https://www.alibabacloud.com/help/doc-detail/110344.htm
Hope this helps!
I have been attempting to install oracle db 12c (both 12.2.0.1 as well as 12.1.0.2) But keep getting errors that I can't figure out. I have gone through AWS's own cloudformation troubleshooting guide along with several forums.
I am getting the following messages in the events log. I have included text below as well as a screen shot of the events for the root stack:
The following resource(s) failed to create: [OracleStack].
Embedded stack arn:aws:cloudformation:us-west-2:007849015507:stack/Oracle-Database-OracleStack-1W5U4RT91JZXT/a1f67bb0-be05-11e9-8c50-02ee71065ed8 was not successfully created: The following resource(s) failed to create: [PrimaryInstance].
I have come accross some info on cloudformation helper scripts and timing out of parameters, but no topic addresses how to correct the problem.
Help is appreciated
I want to create elastic search indexes on neo4j data.
I reffered https://github.com/neo4j-contrib/neo4j-elasticsearch and https://www.youtube.com/watch?v=SJLSFsXgOvA&ab_channel=AnmolAgrawal to create elasticsearch index from neo4j.
But after that, im getting below error in neo4j.log file.
2016-11-08 12:20:09.825+0000 WARN Error updating ElasticSearch No Server is assigned to client to connect
io.searchbox.client.config.exception.NoServerConfiguredException: No Server is assigned to client to connect
at io.searchbox.client.AbstractJestClient$ServerPool.getNextServer(AbstractJestClient.java:132)
at io.searchbox.client.AbstractJestClient.getNextServer(AbstractJestClient.java:81)
at io.searchbox.client.http.JestHttpClient.prepareRequest(JestHttpClient.java:80)
at io.searchbox.client.http.JestHttpClient.executeAsync(JestHttpClient.java:60)
at org.neo4j.elasticsearch.ElasticSearchEventHandler.afterCommit(ElasticSearchEventHandler.java:81)
at org.neo4j.elasticsearch.ElasticSearchEventHandler.afterCommit(ElasticSearchEventHandler.java:27)
at org.neo4j.kernel.internal.TransactionEventHandlers.afterCommit(TransactionEventHandlers.java:149)
at org.neo4j.kernel.internal.TransactionEventHandlers.afterCommit(TransactionEventHandlers.java:47)
at org.neo4j.kernel.impl.api.TransactionHooks.afterCommit(TransactionHooks.java:75)
at org.neo4j.kernel.impl.api.KernelTransactionImplementation.afterCommit(KernelTransactionImplementation.java:541)
at org.neo4j.kernel.impl.api.KernelTransactionImplementation.commit(KernelTransactionImplementation.java:482)
at org.neo4j.kernel.impl.api.KernelTransactionImplementation.close(KernelTransactionImplementation.java:380)
at org.neo4j.server.rest.transactional.TransitionalTxManagementKernelTransaction.commit(TransitionalTxManagementKernelTransaction.java:92)
at org.neo4j.server.rest.transactional.TransactionHandle.closeContextAndCollectErrors(TransactionHandle.java:243)
at org.neo4j.server.rest.transactional.TransactionHandle.commit(TransactionHandle.java:151)
at org.neo4j.server.rest.web.TransactionalService.lambda$executeStatementsAndCommit$29(TransactionalService.java:202)
at com.sun.jersey.core.impl.provider.entity.StreamingOutputProvider.writeTo(StreamingOutputProvider.java:71)
at com.sun.jersey.core.impl.provider.entity.StreamingOutputProvider.writeTo(StreamingOutputProvider.java:57)
at com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:302)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1510)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
How to fix this error or is there any other way to update index if neo4j node's property value changes?
As this is one of the very few page that appears when you search Google for this string, I wanted to post a clear (one that J. Dimeo's answer above alludes to, but is far from specific).
In your graylog config (/etc/graylog/server/server.conf for me), set elasticsearch_discovery_enabled to false, and resart the service.
That's it :)
Are you using AWS ElasticSearch? They do not allow connecting to individual nodes. I read elsewhere (from the AWS team):
"Looking over the logs, it seems that 'i.s.c.config.discovery.NodeChecker' is trying to auto discover and connect to the individual nodes of the cluster. Amazon is continuously working hard on improving the service features but unfortunately, at this moment AWS doesn't allow clients to connect to the individual nodes of the cluster. Instead, you can connect using the URL"
You need to turn off node discovery in the Jest client somehow:
ClientConfig clientConfig = new ClientConfig.Builder("http://localhost:9200").discoveryEnabled(false)
See https://github.com/searchbox-io/Jest/blob/master/jest/README.md#node-discovery-through-nodes-api
I created a custom AMI for use in an Elastic Beanstalk environment as described here. It all works, except for requesting log files from the instances. When using the Console, when I click "Request Logs|Last 100 lines", it show a Loading spinner for a rather long time and then leaves the list of downloadable logs empty.
I already tried enabling all Logging related checkboxes in the EC2Config dialog before creating the AMI, but this did not help.