I have connected to an AWS instance which was set up for MarkLogic using the AWS Systems Manager. I am trying to start the MarkLogic Server, but I am receiving the following error response:
Set configuration: JAVA_HOME="/usr/lib/jvm/jre-1.8.0-openjdk-1.8.0.252.b09-2.amzn2.0.1.x86_64"
Set configuration: MARKLOGIC_MDB_TYPE=""
Set configuration: AWS_REGION="ap-southeast-2"
Set configuration: AWS_DEFAULT_REGION="ap-southeast-2"
Set configuration: MARKLOGIC_ZONE="ap-southeast-2a"
Initialize Configuration.
AWS Region: ap-southeast-2, ZONE: ap-southeast-2a. INSTANCE: i-08c0992c858711a67
Instance is not managed
Waiting for device mounted to come online : /dev/nvme1n1
Volume /dev/sdf has failed to attach - aborting
Warning: ec2-startup did not complete successfully
Check the error logs for details
Starting MarkLogic: [FAILED]
This was the output on the log for mlcmd:
"2020-08-17 02:10:26,821 0 INFO [main] shell.Shell - xmlsh initialize
"2020-08-17 02:10:26,952 131 INFO [main] builtin.log - loading init.xsh
"2020-08-17 02:10:27,102 281 INFO [main] builtin.log - initializing mlcmd
"2020-08-17 02:10:27,103 282 INFO [main] builtin.log - loading /var/local/mlcmd.conf
"2020-08-17 02:10:27,297 476 TRACE [main] mlcmd.trace - init-config: exit-status: 1 args: Not loading mdb functions - not a managed cluster
"2020-08-17 02:10:27,299 478 TRACE [main] mlcmd.trace - complete init.xsh: exit-status: 1 args:
"2020-08-17 02:10:27,299 478 INFO [main] builtin.log - runing init-config.xsh
"2020-08-17 02:10:27,942 0 INFO [main] shell.Shell - xmlsh initialize
"2020-08-17 02:10:28,042 100 INFO [main] builtin.log - loading init.xsh
"2020-08-17 02:10:28,173 231 INFO [main] builtin.log - initializing mlcmd
"2020-08-17 02:10:28,174 232 INFO [main] builtin.log - loading /var/local/mlcmd.conf
"2020-08-17 02:10:28,387 445 TRACE [main] mlcmd.trace - ec2-startup: exit-status: 1 args: Not loading mdb functions - not a managed cluster
"2020-08-17 02:10:28,389 447 TRACE [main] mlcmd.trace - complete init.xsh: exit-status: 1 args:
How do I resolve this issue?
If there is more required information, do let me know and I will try to get it
It appears that you are attempting to start a self-managed instance/cluster, while the Managed Cluster feature has not been disabled.
The MarkLogic Managed Cluster feature is the recommended way to deploy a MarkLogic Cluster on AWS so it is enabled by default. Managed clusters are meant to be deployed using the MarkLogic CloudFormation Templates.
Deploying MarkLogic on EC2 Using CloudFormation
The Managed Cluster feature reduces the amount of work necessary to setup the initial cluster, and creates an Auto Scaling Group that will automatically re-launch an instance that gets terminated, and when MarkLogic starts on the new instance, it will remount the associated EBS data drive.
CloudFormation Template Overview
If you wish to have a self-managed cluster, then you will need to create an /etc/marklogic.conf file to disable the feature at startup.
AWS Configuration Variables
Best Practice Editing MarkLogic Server Environment Variables
I would recommend reviewing the following guide, as it details using both the Managed Cluster feature, as well as self-managed clusters.
MarkLogic Server on Amazon Web Services (AWS) Guide
I've been struggling AWS-Elastic Beanstalk problems.
The other day, I appended some gems into Gemfile and then used eb deploy.
(Maybe the gem is whenever? or bcrypt? Sorry not sure)
It didn't work correctly on my deployment. The results are below.
ERROR: [Instance: i-452520da] Command failed on instance. Return code: 10 Output: /opt/elasticbeanstalk/hooks/appdeploy/post/10_reload_cron.sh: line 3: cd: HOME not set
Could not locate Gemfile or .bundle/ directory.
Hook /opt/elasticbeanstalk/hooks/appdeploy/post/10_reload_cron.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
ERROR: Unsuccessful command execution on instance id(s) 'i-452520da'. Aborting the operation.
ERROR: Failed to deploy application.
Here's eb-activity.log.
[2016-08-28T01:51:16.844Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployEnactHook] : Completed activity. Result:
Successfully execute hooks in directory /opt/elasticbeanstalk/hooks/appdeploy/enact.
[2016-08-28T01:51:16.844Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook] : Starting activity...
[2016-08-28T01:51:16.844Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook/01_create_pids.sh] : Starting activity...
[2016-08-28T01:51:17.044Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook/01_create_pids.sh] : Completed activity.
[2016-08-28T01:51:17.044Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook/10_reload_cron.sh] : Starting activity...
[2016-08-28T01:51:17.242Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook/10_reload_cron.sh] : Activity execution failed, because: /opt/elasticbeanstalk/hooks/appdeploy/post/10_reload_cron.sh: line 3: cd: HOME not set
Could not locate Gemfile or .bundle/ directory (ElasticBeanstalk::ExternalInvocationError)
caused by: /opt/elasticbeanstalk/hooks/appdeploy/post/10_reload_cron.sh: line 3: cd: HOME not set
Could not locate Gemfile or .bundle/ directory (Executor::NonZeroExitStatus)
[2016-08-28T01:51:17.242Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook/10_reload_cron.sh] : Activity failed.
[2016-08-28T01:51:17.243Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1/AppDeployPostHook] : Activity failed.
[2016-08-28T01:51:17.243Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147/AppDeployStage1] : Activity failed.
[2016-08-28T01:51:17.243Z] INFO [20749] - [Application update app-ed0b6-160828_104745#147] : Completed activity. Result:
Application update - Command CMD-AppDeploy failed
[2016-08-28T01:52:38.630Z] INFO [2486] - [CMD-TailLogs] : Starting activity...
[2016-08-28T01:52:38.630Z] INFO [2486] - [CMD-TailLogs/AddonsBefore] : Starting activity...
How could I eliminate this problem? Thanks in advance.
I can work out this problem.
The thing is "/opt/elasticbeanstalk/hooks/appdeploy/post/10_reload_cron.sh".
So I deleted this file by using .ebextensions/some.sh
I'm trying to install GhostScript 9.10 on Elastic Beanstalk because currently only Ghostscript 8.70 is available via yum packages.
The installation is working via SSH on the EC2 instance but the configuration file is always failing and I don't understand whats the reason.
Here is my .ebextensions configuration file:
commands:
01_admin_rights:
command: "sudo su"
02_get_gs:
command: "curl -O http://downloads.ghostscript.com/public/old-gs-releases/ghostscript-9.10.tar.gz"
03_extract_gs:
command: "tar -xzf ghostscript-9.10.tar.gz"
04_cd_gs:
command: "cd ghostscript-9.10"
05_configure_gs:
command: "bash configure"
06_install_gs:
command: "make install"
07_so_gs:
command: "make so"
08_reboot:
command: "reboot"
And here goes the elastic beanstalk error log part:
[2016-06-21T12:22:52.720Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 01_admin_rights] : Starting activity...
[2016-06-21T12:22:52.757Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 01_admin_rights] : Completed activity.
[2016-06-21T12:22:52.757Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 02_get_gs] : Starting activity...
[2016-06-21T12:22:53.524Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 02_get_gs] : Completed activity. Result:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 33.6M 100 33.6M 0 0 49.2M 0 --:--:-- --:--:-- --:--:-- 49.2M
[2016-06-21T12:22:53.524Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 03_extract_gs] : Starting activity...
[2016-06-21T12:22:55.066Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 03_extract_gs] : Completed activity.
[2016-06-21T12:22:55.066Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 04_cd_gs] : Starting activity...
[2016-06-21T12:22:55.069Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 04_cd_gs] : Completed activity.
[2016-06-21T12:22:55.070Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 05_configure_gs] : Starting activity...
[2016-06-21T12:22:55.073Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 05_configure_gs] : Activity execution failed, because: bash: configure: No such file or directory
(ElasticBeanstalk::ExternalInvocationError)
[2016-06-21T12:22:55.073Z] INFO [24703] - [Application update Come on #15#25/AppDeployStage0/EbExtensionPreBuild/Infra-EmbeddedPreBuild/prebuild_2__Staging/Command 05_configure_gs] : Activity failed.
I understand that the command 5 is failing because the file doesn't exist. However when I'm doing the steps manually via SSH the file exists and all commands can be executed in this order.
What do I miss?
EDIT:
I played around with the configure argument and tried:
/bin/bash: ./configure
./configure
bash ./configure
All arguments fail with the same error "No such file or directory."
If I connect via SSH and enter one of the configure commands then it works without any issues.
Anybody knows whats going on here?
I think this could be because separate commands don't keep the environment or the current directory consistent between them. One of your commands is cd, but I don't think the changed directory persists to the next command. Try combining all commands into one, like this:
command: |
cd directory
./configure
Also, ebextensions run as root, so you may not need the sudo su in the beginning.
I am trying deploy a simple docker container through Elastic Beanstalk but I am getting Docker container quit unexpectedly error. Not sure what is wrong here. Thanks in advance for the help.
Dockerrun.aws.json:
{
"AWSEBDockerrunVersion": "1",
"Image": {
"Name": "janedoe/image",
"Update": "true"
},
"Ports": [{
"ContainerPort": "10010"
}],
"Volumes": [{
"HostDirectory": "/home/ec2-user/testdocker",
"ContainerDirectory": "/home/ec2-user/testdocker"
}],
"Logging": "/home/ec2-user/testlogs"
}
Dockerfile:
FROM centos:centos6
MAINTAINER janedoe
RUN echo "test"
EXPOSE 10010
Log :
[2016-03-22T22:56:35.034Z] INFO [15895] - [Application update/AppDeployStage0/AppDeployPreHook/03build.sh] : Completed activity.
Result:
centos6: Pulling from library/centos
Digest: sha256:ec1bf627545d77d05270b3bbd32a9acca713189c58bc118f21abd17ff2629e3f
Status: Image is up to date for centos:centos6
Successfully pulled centos:centos6
Sending build context to Docker daemon 4.608 kB
Sending build context to Docker daemon 4.608 kB
Step 1 : FROM centos:centos6
---> ed452988fb6e
Step 2 : MAINTAINER janedoe
---> Running in 8bce7dfb7e59
---> 04de6fffed04
Removing intermediate container 8bce7dfb7e59
Step 3 : RUN echo "test"
---> Running in 36cef1d7c0e5
test
---> c5b3d119184c
Removing intermediate container 36cef1d7c0e5
Step 4 : EXPOSE 10010
---> Running in ea07cbcc1136
---> 45f9b3fe6503
Removing intermediate container ea07cbcc1136
Successfully built 45f9b3fe6503
Successfully built aws_beanstalk/staging-app
[2016-03-22T22:56:35.034Z] INFO [15895] - [Application update/AppDeployStage0/AppDeployPreHook] : Completed activity. Result:
Successfully execute hooks in directory /opt/elasticbeanstalk/hooks/appdeploy/pre.
[2016-03-22T22:56:35.035Z] INFO [15895] - [Application update/AppDeployStage0/EbExtensionPostBuild] : Starting activity...
[2016-03-22T22:56:35.550Z] INFO [15895] - [Application update/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild] : Starting activity...
[2016-03-22T22:56:35.550Z] INFO [15895] - [Application update/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild] : Completed activity.
[2016-03-22T22:56:35.587Z] INFO [15895] - [Application update/AppDeployStage0/EbExtensionPostBuild] : Completed activity.
[2016-03-22T22:56:35.588Z] INFO [15895] - [Application update/AppDeployStage0/InfraCleanEbextension] : Starting activity...
[2016-03-22T22:56:36.107Z] INFO [15895] - [Application update/AppDeployStage0/InfraCleanEbextension] : Completed activity. Result:
Cleaned ebextensions subdirectories from .
[2016-03-22T22:56:36.107Z] INFO [15895] - [Application update/AppDeployStage0] : Completed activity. Result:
Application update - Command CMD-AppDeploy stage 0 completed
[2016-03-22T22:56:36.107Z] INFO [15895] - [Application update/AppDeployStage1] : Starting activity...
[2016-03-22T22:56:36.108Z] INFO [15895] - [Application update/AppDeployStage1/AppDeployEnactHook] : Starting activity...
[2016-03-22T22:56:36.108Z] INFO [15895] - [Application update/AppDeployStage1/AppDeployEnactHook/00run.sh] : Starting activity...
[2016-03-22T22:56:44.157Z] INFO [15895] - [Application update/AppDeployStage1/AppDeployEnactHook/00run.sh] : Activity execution failed, because: 268f1a5e43874771bc6039977e9eb048e704c0b94a5e100a2a9ffbf2d9d7f271
Docker container quit unexpectedly after launch: Docker container quit unexpectedly on Tue Mar 22 22:56:44 UTC 2016:. Check snapshot logs for details. (ElasticBeanstalk::ExternalInvocationError)
caused by: 268f1a5e43874771bc6039977e9eb048e704c0b94a5e100a2a9ffbf2d9d7f271
Docker container quit unexpectedly after launch: Docker container quit unexpectedly on Tue Mar 22 22:56:44 UTC 2016:. Check snapshot logs for details. (Executor::NonZeroExitStatus)
You should use a CMD instead of a RUN on your Dockerfile.
When executing commands in a Dockerfile, you must choose carefully between RUN, CMD and ENTRYPOINT (extracted from the Docker reference):
RUN:
The RUN instruction will execute any commands in a new layer on top of
the current image and commit the results. The resulting committed
image will be used for the next step in the Dockerfile.
CMD:
The main purpose of a CMD is to provide defaults for an executing
container. These defaults can include an executable, or they can omit
the executable, in which case you must specify an ENTRYPOINT
instruction as well.
ENTRYPOINT:
An ENTRYPOINT allows you to configure a container that will run as an
executable.
You should have a deep read to the Docker reference and to the Docker best practices
Apart from that, if you intend to use the volumes you defined in your Dockerrun.aws.json, have in mind what is stated in the AWS documentation:
Do not specify the Image key in the Dockerrun.aws.json file when using
a Dockerfile. .Elastic Beanstalk will always build and use the image
described in the Dockerfile when one is present.
This means that your Dockerrun.aws.json will be ignored, so take care.
It is easier to just see the command prompt output if your run it like
eb create <replace_with_your_env_name/> -vvv
We already have WSO2 ESB 4.6 in production so I'm using ESB 4.6.0 and ELB 2.0.3.
Following the instructions at https://docs.wso2.com/pages/viewpage.action?pageId=26839403 I seem to have successfully installed the ELB. I tried setting up the ESB from scratch (as opposed to using our production instance or config) and started it up, but it isn't joining the cluster, and I'm unable to access the management console at https://mgt.esb.cloud-test.wso2.com:8243/carbon . (In order to keep everything according to the installing instructions, I added elb.wso2.com, mgt.esb.cloud-test-wso2.com, and esb.cloud-test.wso2.com to /etc/hosts as . . .
127.0.0.1 localhost localhost.localdomain elb.wso2.com mgt.esb.cloud-test.wso2.com esb.cloud-test.wso2.com
I haven't installed the ESB worker node yet, but that, the ESB management node, and the ELB will be on the same host for now. I enabled the port offset for the management node.
I confirmed the hostnames and port numbers are correct in the ELB and ESB configurations.
This is the log from starting the ESB management node:
JAVA_HOME environment variable is set to /usr/java/jre1.7.0_17
CARBON_HOME environment variable is set to /opt/app/wso2esb-4.6.0-manager
[2014-12-09 13:37:13,474] INFO - CarbonCoreActivator Starting WSO2 Carbon...
[2014-12-09 13:37:13,476] INFO - CarbonCoreActivator Operating System : Linux 2.6.18-194.el5, amd64
[2014-12-09 13:37:13,476] INFO - CarbonCoreActivator Java Home : /usr/java/jre1.7.0_17
[2014-12-09 13:37:13,476] INFO - CarbonCoreActivator Java Version : 1.7.0_17
[2014-12-09 13:37:13,477] INFO - CarbonCoreActivator Java VM : Java HotSpot(TM) 64-Bit Server VM 23.7-b01,Oracle Corporation
[2014-12-09 13:37:13,477] INFO - CarbonCoreActivator Carbon Home : /opt/app/wso2esb-4.6.0-manager
[2014-12-09 13:37:13,477] INFO - CarbonCoreActivator Java Temp Dir : /opt/app/wso2esb-4.6.0-manager/tmp
[2014-12-09 13:37:13,477] INFO - CarbonCoreActivator User : clowndrugs, en-US, America/Chicago
[2014-12-09 13:37:13,505] WARN - ValidationResultPrinter Open files limit :1024 of the system is below the recommended minimum count :4096
[2014-12-09 13:37:13,522] INFO - AgentHolder Agent created !
[2014-12-09 13:37:13,543] INFO - AgentDS Successfully deployed Agent Client
[2014-12-09 13:37:16,158] INFO - EmbeddedRegistryService Configured Registry in 40ms
[2014-12-09 13:37:16,260] INFO - RegistryCoreServiceComponent Registry Mode : READ-WRITE
[2014-12-09 13:37:17,612] INFO - ClusterBuilder Clustering has been enabled
[2014-12-09 13:37:17,625] INFO - ClusterBuilder Running in application mode
[2014-12-09 13:37:17,626] INFO - ClusterBuilder Clustering configuration management has been enabled
[2014-12-09 13:37:17,627] INFO - ClusterBuilder Clustering state management has been disabled
[2014-12-09 13:37:17,954] INFO - LandingPageWebappDeployer Deployed product landing page webapp: StandardEngine[Catalina].StandardHost[localhost].StandardContext[/home]
[2014-12-09 13:37:18,049] INFO - DeploymentInterceptor Deploying Axis2 service: echo {super-tenant}
[2014-12-09 13:37:18,237] INFO - DeploymentEngine Deploying Web service: Echo.aar - file:/opt/app/wso2esb-4.6.0-manager/repository/deployment/server/axis2services/Echo.aar
[2014-12-09 13:37:18,324] INFO - DeploymentInterceptor Deploying Axis2 service: Version {super-tenant}
[2014-12-09 13:37:18,344] INFO - DeploymentEngine Deploying Web service: Version.aar - file:/opt/app/wso2esb-4.6.0-manager/repository/deployment/server/axis2services/Version.aar
[2014-12-09 13:37:18,607] INFO - DeploymentInterceptor Deploying Axis2 service: echo {super-tenant}
[2014-12-09 13:37:18,700] INFO - DeploymentInterceptor Deploying Axis2 service: Version {super-tenant}
[2014-12-09 13:37:18,795] INFO - ModuleDeployer Deploying module: rampart-1.6.1-wso2v8 - file:/opt/app/wso2esb-4.6.0-manager/repository/deployment/client/modules/rampart-1.6.1-wso2v8.mar
[2014-12-09 13:37:18,798] INFO - ModuleDeployer Deploying module: addressing-1.6.1-wso2v7 - file:/opt/app/wso2esb-4.6.0-manager/repository/deployment/client/modules/addressing-1.6.1-wso2v7.mar
[2014-12-09 13:37:18,803] INFO - TCPTransportSender TCP Sender started
[2014-12-09 13:37:19,992] INFO - DeploymentEngine Deploying Web service: org.wso2.carbon.message.processor -
[2014-12-09 13:37:20,000] INFO - DeploymentEngine Deploying Web service: org.wso2.carbon.message.store -
[2014-12-09 13:37:21,806] INFO - DeploymentInterceptor Deploying Axis2 service: wso2carbon-sts {super-tenant}
[2014-12-09 13:37:21,959] INFO - DeploymentEngine Deploying Web service: org.wso2.carbon.sts -
[2014-12-09 13:37:22,205] INFO - DeploymentEngine Deploying Web service: org.wso2.carbon.tryit -
[2014-12-09 13:37:22,497] INFO - CarbonServerManager Repository : /opt/app/wso2esb-4.6.0-manager/repository/deployment/server/
[2014-12-09 13:37:22,743] INFO - PermissionUpdater Permission cache updated for tenant -1234
[2014-12-09 13:37:22,815] INFO - ServiceBusInitializer Starting ESB...
[2014-12-09 13:37:22,832] INFO - ServiceBusInitializer Initializing Apache Synapse...
[2014-12-09 13:37:22,836] INFO - SynapseControllerFactory Using Synapse home : /opt/app/wso2esb-4.6.0-manager/.
[2014-12-09 13:37:22,836] INFO - SynapseControllerFactory Using synapse.xml location : /opt/app/wso2esb-4.6.0-manager/././repository/deployment/server/synapse-configs/default
[2014-12-09 13:37:22,836] INFO - SynapseControllerFactory Using server name : localhost
[2014-12-09 13:37:22,839] INFO - SynapseControllerFactory The timeout handler will run every : 15s
[2014-12-09 13:37:22,845] INFO - Axis2SynapseController Initializing Synapse at : Tue Dec 09 13:37:22 CST 2014
[2014-12-09 13:37:22,845] INFO - Axis2SynapseController Loading mediator extensions...
[2014-12-09 13:37:22,848] INFO - CarbonSynapseController Loading the mediation configuration from the file system
[2014-12-09 13:37:22,850] INFO - MultiXMLConfigurationBuilder Building synapse configuration from the synapse artifact repository at : ././repository/deployment/server/synapse-configs/default
[2014-12-09 13:37:22,850] INFO - XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
[2014-12-09 13:37:23,075] INFO - SynapseConfigurationBuilder Loaded Synapse configuration from the artifact repository at : ././repository/deployment/server/synapse-configs/default
[2014-12-09 13:37:23,076] INFO - Axis2SynapseController Deploying the Synapse service...
[2014-12-09 13:37:23,078] INFO - Axis2SynapseController Deploying Proxy services...
[2014-12-09 13:37:23,078] INFO - Axis2SynapseController Deploying EventSources...
[2014-12-09 13:37:23,083] INFO - ServerManager Server ready for processing...
[2014-12-09 13:37:23,120] WARN - MediationStatisticsComponent Can't register an observer for mediationStatisticsStore. If you have disabled StatisticsReporter, please enable it in the Carbon.xml
[2014-12-09 13:37:23,177] INFO - RuleEngineConfigDS Successfully registered the Rule Config service
[2014-12-09 13:37:24,407] INFO - HttpsTransportListener HTTPS port : 9444
[2014-12-09 13:37:24,407] INFO - HttpTransportListener HTTP port : 9764
[2014-12-09 13:37:24,408] INFO - TribesClusteringAgent Initializing cluster...
[2014-12-09 13:37:24,423] INFO - TribesClusteringAgent Cluster domain: wso2.esb.domain
[2014-12-09 13:37:24,425] INFO - TribesClusteringAgent Using wka based membership management scheme
[2014-12-09 13:37:24,433] INFO - WkaBasedMembershipScheme Receiver Server Socket bound to:/10.221.90.92:4001
[2014-12-09 13:37:24,535] INFO - WkaBasedMembershipScheme Receiver Server Socket bound to:/10.221.90.92:4001
[2014-12-09 13:37:24,639] INFO - WkaBasedMembershipScheme Could not connect to member 127.0.0.1:4000(wso2.esb.domain)
[2014-12-09 13:37:24,653] INFO - TribesClusteringAgent Local Member 10.221.90.92:4001(wso2.esb.domain)
[2014-12-09 13:37:24,653] INFO - TribesUtil No members in current cluster
[2014-12-09 13:37:24,654] INFO - TribesClusteringAgent Cluster initialization completed.
[2014-12-09 13:37:25,828] INFO - RegistryEventingServiceComponent Successfully Initialized Eventing on Registry
[2014-12-09 13:37:25,943] INFO - JMXServerManager JMX Service URL : service:jmx:rmi://localhost:11112/jndi/rmi://localhost:10000/jmxrmi
[2014-12-09 13:37:25,943] INFO - StartupFinalizerServiceComponent Server : WSO2 Enterprise Service Bus-4.6.0
[2014-12-09 13:37:25,944] INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 17 sec
[2014-12-09 13:37:26,567] INFO - CarbonUIServiceComponent Mgt Console URL : https://mgt.esb.cloud-test.wso2.com:8243/carbon/
The output from the ELB gives lots of these:
[2014-12-09 15:33:44,773] ERROR - TenantAwareLoadBalanceEndpoint No application members available
Is this expected behavior since I have yet set up any services or a worker node? From the instructions, it sounded like I should be able to see the management node's Web console at this point.
try the following changes and see
modify elb.wso2.com in ELB axis2.xml file
modify mgt.esb.cloud-test-wso2.com in ESB axis2.xml file