I am using pike release of openstack and ceilometer version 2.9.0 and keystone v3.
$ceilometer meter-list gives HTTP 404 Not Found error
$gnocchi metric list --> HTTP 401
$openstack metric list ---> lists the meters (works) . However in yaml file(for autoscaling) I am unable to get metrics using type OS:Ceilometer::Alarm
How to go about it, please guide. Is there any workaround for the issue I am facing?
Related
I have a spark (version 2.2.0) cluster with 7 nodes and url spark://master:7077. I setup Apache Zeppelin 0.7.2 on the master node using the following configuration:
zeppelin.env.sh
export JAVA_HOME=/usr/local/java/jdk1.8.0_144
export SPARK_HOME=/usr/local/spark-2.2.0
export MASTER=spark://master:7077
export ZEPPELIN_PORT=8082
In zeppelin-site.xml I changed zeppelin.server.port from 8080 to 8082, also tried with other ports like 8090, 8091.
After starting zeppelin when I try to access web UI using master:8082 I got the following error but zeppelin status shows it is running:
HTTP ERROR: 500
Problem accessing /. Reason: javax.servlet.HttpServletRequest.isAsyncStarted()Z
I checked the logs and found that java.lang.NoSuchMethodError:javax.servlet.HttpServletRequest.isAsyncStarted()Z
OPTIONS http://localhost:9000/api/chat/ 404 (Not Found)
XMLHttpRequest cannot load http://localhost:9000/api/chat/. Response for preflight has invalid HTTP status code 404
https://www.playframework.com/documentation/2.5.x/CorsFilter has details on enabling CORS for Play (which is Lagom is built on). To handle the OPTIONS you may need to do something like:
.withAutoAcl(true)
.withServiceAcls(
ServiceAcl.methodAndPath(Method.OPTIONS, "/foo")
)
https://groups.google.com/forum/#!msg/lagom-framework/dtYN_1Ds4SQ/gT-BGPuCAQAJ is a lagom-framework list discussion thread with more details.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Preflighted_requests has an explanation of why your browser is sending an OPTIONS request to begin with.
The metadata for the current exact maven artifact which provides CORS for Play is this:
<metadata>
<groupId>com.typesafe.play</groupId>
<artifactId>filters-helpers_2.12</artifactId>
<versioning>
<latest>2.6.0-M2</latest>
<release>2.6.0-M2</release>
<versions>
<version>2.6.0-M1</version>
<version>2.6.0-M2</version>
</versions>
<lastUpdated>20170310220437</lastUpdated>
</versioning>
</metadata>
While trying to appcfg.py update myProject, my endpoints failed to update. Here is part of the trace:
09:36 PM Failed to update Endpoints configuration. The app returned an error when the Google Cloud Endpoints server attempted to communicate with it.
09:36 PM See the deployment troubleshooting documentation for more information: https://developers.google.com/appengine/docs/python/endpoints/test_deploy#troubleshooting_a_deployment_failure
09:36 PM Ignoring Endpoints failure and proceeding with update.
I tried to check the logs at http://localhost:8080/_ah/spi/BackendService.getApiConfigs, but terminal produces the following error:
#endpoints.api(name='EventsAPI', version='v1')
AttributeError: 'module' object has no attribute 'api'
INFO 2016-03-18 02:01:37,742 module.py:787] default: "GET /_ah/spi/BackendService.getApiConfigs HTTP/1.1" 500 -
Here is my code:
import endpoints
from protorpc import messages
from protorpc import message_types
from protorpc import remote
package = 'Events'
#endpoints.api(name='EventsAPI', version='v1')
class EventsAPI(remote.Service):
# insert lots of endpoint methods
APPLICATION = endpoints.api_server([EventsAPI])
I am following this tutorial. Where did I go wrong?
There is a problem with the endpoints' name. The name EventsAPI is invalid; changing it to eventsapi fixed this issue.
For reference, as outlined in the endpoint definitions.
The name value: Must begin with lowercase.
from google.appengine.api import urlfetch
totango_url = "https://sdr.totango.com/pixel.png"
totango_url2 = "https://app.totango.com/images/accounts-users.png"
result = urlfetch.fetch(totango_url, validate_certificate=None )
print result.status_code
In production , request to totango_url logs indicate (with no error_detail) :
DownloadError: Unable to fetch URL: https://sdr.totango.com/pixel.gif
i ran this curl command. works fine from local setup , for both the https totango urls
curl -v "https://sdr.totango.com/pixel.gif"
curl -v "https://app.totango.com/images/accounts-users.png"
The ssl certificates are valid and same for both urls.
using the urlfetch.fetch on both urls also returns 200 from my (local) datastore console.
However , the urlfetch.fetch calls to https://sdr.totango.com/pixel.png fails with the above error
Also , i ran the same code in the google cloud playground tweaking the sample app-engine application and seem to get a 200 response for totango_url2 while it returns a 500 for totango_url. Both have the same ssl certificate , i think.
is there some ip whitelisting /firewall issue that app-engine in production that i need to take care of?
This sounds more like an issue on the remote side. If you're able to fetch that image from one place but not another, that speaks to the remote site doing some sort of filtering, possibly by IP address.
I'm trying to deploy a build from jenkins using the artifactory invocation of gradle plugin and get a an HTTP error 302, going through the log looks like there's a checksum problem that cannot be skipped:
13:35:41.463 [DEBUG] [org.jfrog.gradle.plugin.artifactory.task.BuildInfoBaseTask] Failed checksum deploy of checksum '8d80bb7f1bf2f0457baa3ad7379348c5ecbf2535' with statusCode: 302
13:35:41.466 [DEBUG] [org.apache.http.impl.conn.SingleClientConnManager] Get connection for route HttpRoute[{}->http://artifactory.edegem.eu.thmulti.com]
....
13:35:41.470 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnectionOperator] Connecting
13:35:41.503 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnection] Receiving response: HTTP/1.1 302 Found
Any clue?
Thanks a lot.
302 is a status code for redirects, which means that your Artifactory is not located at 'http://artifactory.edegem.eu.thmulti.com' but in some other location. Browser follows the redirect to the new place (that's the reason you can browse Artifactory under this URL), but Artifactory networking is not. Please verify the 'real' location of Artifactory and point your Jenkins plugin to it.