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.
Related
I would like to clone a WordPress site that is already in VersionPress to a new server.
The instructions are generally only listed for cloning on the current server. I have one server dedicated to Dev and another for Production
I tried the following command line:
wp vp clone
--name=sitename
--ssh=username#site.school.edu
--path=/var/www/html/folder
--url=https://site.school.edu/destination
--dbname=mydb
--dbuser=myuser
--dbpass=mypass
--dbhost=xxx.xxx.xxx.xxx
--dbprefix=wp-
--force
However after I login to the remote ssh server, I get this error:
Fatal error: Call to undefined function apply_filters() in /var/www/html/atwiki/wp-includes/load.php on line 317
Error: Cannot connect over SSH using provided configuration.
Any ideas?
Here's a blog post on how to achieve that today. We will have a more polished way in the future.
I am setting up a phabricator server and i am observing the below issue, both from my diffusion repository Status window and the daemons.log file
Error updating working copy: Command failed with error #128!
COMMAND
git log --format='%H%x01%P%x01%ct' --all --
STDOUT
(empty)
STDRR
fatal: bad default revision 'HEAD'
After reading on this issue, i figured out that this is a common issue with bare repositories without first commits. So i tried committing from my local system through repository http URI, but it is returning a 500 exception.
below is the error message i pulled out from phabricator database:
$ select * from phabricator_repository.repository_pullevent;
500 | {"response.message":"Error 1: sudo: a password is required\n"}
Can any one help me out to understand the issues from repository_pullevents and daemons.log file.
thanks in advance!
i resolved the problem with sudo, by changing the user running apache and adding the symlink created for git-http-backened in sudoers for the apache user.
and the problem with repository bad HEAD revision was resolved by making the first commit from a client machine.
I am having issues while restarting YARN service. It keeps failing with errors shown in the logs below. YARN was working fine until last week and then the below error messages started to pop up all of a sudden.
Tried restarting YARN/JOB history server. Nothing worked. Kindly help to alleviate this issue.
Thanks,
Vinoth
Error starting JobHistoryServer
java.lang.IllegalAccessError: tried to access class org.apache.hadoop.mapred.JobACLsManager from class org.apache.hadoop.mapreduce.v2.hs.HistoryFileManager
at org.apache.hadoop.mapreduce.v2.hs.HistoryFileManager.serviceInit(HistoryFileManager.java:503)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.mapreduce.v2.hs.JobHistory.serviceInit(JobHistory.java:94)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
at org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.serviceInit(JobHistoryServer.java:145)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.launchJobHistoryServer(JobHistoryServer.java:222)
at org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.main(JobHistoryServer.java:232)
Are you working in a pseudo environment?
Also not clear what command you are using to restart.
You can try the below command to restart :
sudo service hadoop-master stop
sudo service hadoop-master start
-Senthil
When I try to install error messages, it fails to download. I get error messages like this:
[error] Server access Error: java.security.cert.CertificateException: No subject alternative DNS name matching repo.scala-sbt.org found. url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-pgp/scala_2.10/sbt_0.13/0.8.3/ivys/ivy.xml
I can confirm, when accessing via my browser, that the certificate installed for the domain repo.scala-sbt.org is actually the certificate for repo.typesafe.com, and this seems to be the source of the error. It doesn't appear to be a DNS issue as http://repo.scala-sbt.org/ (insecure) works.
Please see https://github.com/sbt/sbt/issues/2125 for the workarounds. Specifically "http" should not be used.
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
Edit: This issue is now resolved. No workarounds should be required.
As a temporary workaround, add the file ~/.sbt/0.13/plugins/temp.sbt with the following contents:
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
You'll still see the error, but sbt will be able to find the dependency for which it is searching when accessing https://dl.bintray.com/sbt/sbt-plugin-releases directly (the place to which repo.scala-sbt.org presently redirects).
Upgrading nss package on CentOS worked for me.
sudo yum upgrade nss
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.