I have install jboss-fuse on linux centos and runt it. But management console is not reachable.
I have found some relevant documentation on redhat's website and followed the steps.
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Using_the_Management_Console/files/FMCUGAccess.html
In that document it is said fabric-webui is to be installed. So I have run this command;
"profile-edit --features fabric-webui fabric"
But, An error occured during the installation. I found this exception in 'karaf.log' file.
2015-06-17 20:02:02,255 | ERROR | agent-3-thread-1 | DeploymentAgent
| .fabric8.agent.DeploymentAgent$2 255 | 60 - io.fabric8.fabric-agent
- 1.0.0.redhat-379 | Unable to update agent org.osgi.service.resolver.ResolutionException: Unable to resolve
dummy/0.0.0: missing requirement [dummy/0.0.0] osgi.identity;
osgi.identity=fabric-webui; type=karaf.feature; version=0 at
org.apache.felix.resolver.Candidates.populateResource(Candidates.java:285)[60:io.fabric8.fabric-agent:1.0.0.redhat-379]
at
org.apache.felix.resolver.Candidates.populate(Candidates.java:153)[60:io.fabric8.fabric-agent:1.0.0.redhat-379]
at
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:148)[60:io.fabric8.fabric-agent:1.0.0.redhat-379]
at
io.fabric8.agent.DeploymentBuilder.resolve(DeploymentBuilder.java:226)[60:io.fabric8.fabric-agent:1.0.0.redhat-379]
at
io.fabric8.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:521)[60:io.fabric8.fabric-agent:1.0.0.redhat-379]
at
io.fabric8.agent.DeploymentAgent$2.run(DeploymentAgent.java:252)[60:io.fabric8.fabric-agent:1.0.0.redhat-379]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_72]
at
java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_72]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_72]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_72]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_72]
I have checked the continer list and result is shown below.
[id] [version] [connected] [profiles]
[provision status] root* 1.0 true
fabric, fabric-ensemble-0000-1, jboss-fuse-full error -
org.osgi.service.resolver.ResolutionException: Unable to resolve
dummy/0.0.0: missing requir
Can this problem be caused because maven has not configured yet ? Fuse use maven to collect dependencies but I haven't configured maven yet.
The problem is resolved.
It seems the logs and management console access problems are irrelevant.
The problem was firewall and we are able to access management console after stopping the firewall.
systemctl stop firewalld
Also, It seems maven is not required for accessing to management console after installation.
Related
I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.
we are a group of french students in networks, and we need to get openstack working for a school project. We are curently facing an issue while installing keystone. After following the official openstack guide, when trying the service, we get the following error:
[root#localhost ~]# openstack project create --domain default --description "Service Project" service
Failed to discover available identity versions when contacting http://controller:5000/v3. Attempting to parse version from URL.
Unable to establish connection to http://controller:5000/v3/auth/tokens: HTTPConnectionPool(host='controller', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f60f19af9d0>: Failed to establish a new connection: [Errno -2] Nom ou service inconnu',))
tail /var/log/keystone/keystone.log
2019-10-03 14:24:35.943 4778 WARNING keystone.access_rules_config.backends.json [-] No config file found for access rules, application credential access rules will be unavailable.: IOError: [Errno 2] No such file or directory: '/etc/keystone/access_rules.json'
We are installing the stein version
Does anyone know how to solve the problem? We can include some others log if needed. We are two who tried and get the same error.
Thanks for any help! :)
Well, the error is self explanatory.
You are missing a config file which governs access to openstack endpoints.
You can use copy it from unittest cases and put in /etc/keystone folder.
For your convenience here is url to file:
https://fossies.org/linux/misc/openstack/keystone-15.0.0.tar.gz/keystone-15.0.0/keystone/tests/unit/config_files/access_rules.json?m=t
I'm trying to install aodh. I am following this tutorial - https://docs.openstack.org/aodh/stein/install/install-ubuntu.html
When I run this command
aodh alarm list
I'm getting following error.
<html>
<head>
<title>503 Service Unavailable</title>
</head>
<body>
<h1>503 Service Unavailable</h1>
The server is currently unavailable. Please try again at a later time.<br /><br />
The Keystone service is temporarily unavailable.
</body>
</html> (HTTP 503) (Request-ID: req-9f8035a5-e324-4e2f-b3f0-037b68f88d1a)
Even though the error says keystone is unavailable, I highly suspect that already there was some problem with aodh installation.
From the aodh link above, I in the final step, it says:
Restart the Alarming services:
# service aodh-api restart
# service aodh-evaluator restart
# service aodh-notifier restart
# service aodh-listener restart
When I tried this
service aodh-api restart
I got following error
Failed to restart aodh-api.service: Unit aodh-api.service not found.
Moreover in step 2 of above link
Source the admin credentials to gain access to admin-only CLI commands:
$ . admin-openrc
Since, I was unable to find admin-openrc, I skipped that step.
So, I am thinking probably aodh installation didn't go well. Hence the aforementioned error in 'aodh alarm list' command.
Other commands like 'nova list' etc are running fine
Can someone please help in figuring out, what could be going wrong?
Install aodh component as plugin during devstack installation.
https://ask.openstack.org/en/question/116895/how-to-configure-devstack-with-ceilometer-gnocchi-and-aodh-components/
Recently, I encountered this problem, which has been answered on the official website.
https://docs.openstack.org/aodh/latest/contributor/install/index.html
Default, API is provided by apache2 wsgi.
But in my environment, this method can not successfully.
Another method, remove aodh apache2 wsgi, and create aodh-api service.
this method success.
I installed cloudify3.4 according to the cloudify DOCS. When I install the manager, and executed like this:
# cfy bootstrap --install-plugins -p openstack-manager-blueprint.yaml -i openstack-manager-blueprint-inputs.yaml
an error occurred:
[ERROR] Bootstrap failed! (Workflow failed: Task failed 'neutron_plugin.floatingip.create' -> Expected exactly one object of type network with match {'name': u'178d7438-ca18-4df6-a5d0-dd11a53155a5'} but there are 0)
I have already installed
"cloudify_openstack_plugin-1.4-py27-none-linux_x86_64-centos-Core.wgn"
"cloudify_openstack_plugin-1.4-py27-none-linux_x86_64-redhat-Maipo.wgn"
So, how to solve this error?
Thank you to everyone who helped me!
In Cloudify version 3.4, the Cloudify manager can only be installed (bootstrapped) on either CentOS 7.x or RHEL 7.x.
See more details :
http://docs.getcloudify.org/3.4.0/manager/prerequisites/
FYI: There are no limitations in host agents.
That means that once the Cloudify manager is alive, it will enable you to deploy anything on every operating system.
I am getting below error while installing informatica 8.6:
****use the error below and catalina.out and node.log in the server/tomcat/logs directory on the current machine to get more information. Select Retry to continue the installation.
STDOUT: Installing the service '"Informatica Services 8.6.0"' on node 'node01_geettika4912'...
Using CURRENT_DIR: C:\Informatica\PowerCenter8.6.0\server\tomcat\bin
Using INFA_HOME: C:\Informatica\PowerCenter8.6.0
The service '"Informatica Services 8.6.0"' has been installed.
STDERR: The filename, directory name, or volume label syntax is incorrect.
The service name is invalid.
More help is available by typing NET HELPMSG 2185.**
EXITCODE: 2**
I am getting this error after the successful creation of domain.
Please help me in resolving this error.
Thanks!
Run services.msc to get a list of all the services.
Click properties on the service you want, there you can see the "service name" and the "display name".
The service name is what you need to use with the net command. Check if Informatica Services 8.6.0 is in the list.