I'm using Cloudify 2.7 with OpenStack Icehouse.
I have deployed with success a tomcat service.
In the Cloudify log, I see:
WARNING [org.cloudifysource.usm.tail.RollingFileReader] - In RollingFileReader: file not found
Can someone help me to understand the meaning of the error?
Thanks.
The Cloudify RollingFileReader is explained here:
https://github.com/CloudifySource/cloudify/blob/master/USM/src/main/java/org/cloudifysource/usm/tail/RollingFileReader.java
In this case, it means that Cloudify was expecting a log file to be created, but none was found. This is probably not a critical error.
Note that Cloudify 2 has reached End-of-Life. You should consider moving to Cloudify 3
Related
Trying to compile Corda from scratch. I cloned version 4.3 from Github. Details and error codes below.I am using Oracle java version 1.8. I have asked this question on slack as well but didn't find anyone who has faced this issue before.
Task :node-api-tests:test
net.corda.nodeapitests.internal.crypto.X509UtilitiesTest > create valid server certificate chain FAILED
java.security.cert.CertificateException at X509UtilitiesTest.kt:166
net.corda.nodeapitests.internal.crypto.X509UtilitiesTest > create valid self-signed CA certificate FAILED
java.security.cert.CertificateException at X509UtilitiesTest.kt:131
46 tests completed, 2 failed
Task :node-api-tests:test FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ‘:node-api-tests:test’.
So it looks like you're trying to build Corda's source code. Most of the time you really won't need to do this. I'd recommend instead just taking a look at the Corda samples as they use gradle which will download the jars and compile the samples for you.
Here's a link to some of those sample repo's so you can try building off of them.
https://github.com/corda/samples-kotlin
https://github.com/corda/samples-java
All of them compile and run the same way so it shouldn't be too difficult to get running.
./gradlew deployNodes
and then
./build/nodes/runnodes
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 have a problem to deploy EJB and WAR modules at the same time in NetBeans 8.2 on GlassFish 4.1.1. The following message is shown:
[[ Exception Occurred :Error occurred during deployment: Exception while preparing the app : Could not resolve a persistence unit corresponding to the persistence-context-ref-name [ejb.NewMessage/em] in the scope of the module called [TestEJB-ejb]. Please verify your application.. Please see server.log for more details.]]
When I checked server.log file of GlassFish server, I faced with the following erreor message:
[2018-07-28T12:59:45.406+0430] [glassfish 4.1] [SEVERE] [] [javax.enterprise.system.core] [tid: _ThreadID=427 _ThreadName=admin-listener(7)] [timeMillis: 1532766585406] [levelValue: 1000] [[
Exception while preparing the app : Could not resolve a persistence unit corresponding to the persistence-context-ref-name [ejb.NewEntityFacade/em] in the scope of the module called [TestEJB-ejb]. Please verify your application.]]
Is there any solution for that?
Thanks for your help.
If you did not start to create your app or if you did not choose your programming framework, you can switch to Java Spring with less headache!
Read the first paragraph of the following link:
https://en.wikipedia.org/wiki/Spring_Framework
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 have a written a very simple blueprint.yaml to install the MongoDB on a VM. When I am trying to upload the blueprint it gives me below error:
"An error occurred on the server: 400: Invalid blueprint - provider_context CONTEXT not found"
I am using following:
1. Cloudify CLI and Manager version: 3.3
2. It is successfully validated but issue comes while uploading blueprint.
3. I am using the embedded Nodecellar application blueprint
Any kind of help is appreciated.
Thanks,
Sanjiv
In most cases you will receive this error because you have a very large file in the same directory of the blueprint.
Please look for large files and move them from the blueprint directory or sub-directory's
Best,
Jonathan
This is fixed. Issue was with the manager bootstrap process.