On a fresh install of PCF Dev, after logging in:
cf create-service p-rabbitmq standard my_rabbitmq
Showing info of service my_rabbitmq in org system / space system as admin...
name: my_rabbitmq
service: p-rabbitmq
bound apps:
tags:
plan: standard
description: RabbitMQ is a robust and scalable high-performance multi-protocol messaging broker.
documentation:
dashboard: https://rabbitmq-management.local.pcfdev.io/#/login/mu-3ea7453d-7cff-44bd-b7a7-ce0290d9b4d6-v509qlipcuhnu6relaeuat49ca/25849257198976921347999121731293969259
Showing status of last operation from service my_rabbitmq...
status: create succeeded
message:
started: 2018-01-05T01:48:17Z
updated: 2018-01-05T01:48:17Z
When I go to the management dashboard url, the browser displays the following error:
404 Not Found: Requested route ('rabbitmq-management.local.pcfdev.io')
does not exist.
How can I get the RabbitMQ Management Dashboard to be installed and respond?
The only fix I found was installing an earlier version of PCF Dev. This solved the issue.
For more details check this thread on Github.
Related
I am trying the learn OpenShift Origin, and was going through the Getting Started example. I did all steps prior to creating a new application that combines a builder image for Node.js. I can see I have configured the docker registry using oc adm registry.
But in the build logs I see an error as
Pushing image 172.30.134.94:5000/test/nodejs-ex:latest ...
Registry server Address:
Registry server User Name: serviceaccount
Registry server Email: serviceaccount#example.org
Registry server Password: <>
error: build error: Failed to push image: Get https://172.30.134.94:5000/v1/_ping: http: server gave HTTP response to HTTPS client
and the build fails.
What could be the possible issue. Is it some port I have not opened or something? I would really appreciate if someone can share some insight on this and on what I may be doing wrong to get things to work
Thanks
There was a fault in the setting up of insecure registries. Fixed it and things started working.
i build spinnaker using docker-compose follow here
but it always redirect to localhost, how can i fix this.
e.g.
http://localhost:8084/auth/redirect?to=http%3A%2F%2F192.168.99.100%3A9000%2F%23%2Finfrastructure
i set the host:0.0.0.0 in spinnaker-local.yml and configured deck apache2 with proxyPreserve=On, it's not working.
where is the configuration about 'redirect'?
All containers running well but fiat gets error mesages, like this:
WARN 1 --- [ecutionAction-1] c.n.s.fiat.roles.UserRolesSyncer : [] User permission sync failed. Server status is DOWN. Trying again in 10000 ms. Cause:(Provider: DefaultServiceAccountProvider) retrofit.RetrofitError: unexpected url: front50/serviceAccounts
i'm sure set fiat false, is this matter?
thanks.
The docker-compose link project is not available anymore. That deployment type is not supported anymore.
The easiest way i suggest for people to get started quick is by using Armory Open source Minnaker. It runs on top of a K3S small cluster and contains a functional spinnaker deployment.
Great way to get started.
I tried the debian local deployment and it failed all the time.
Enjoy your CD operations.
I get the following error on restarting the cloudera management service in a docker container:quickstart:latest, i had restarted after an error showed service monitor not running:
Mar 15, 8:45:43.760 AM ERROR com.cloudera.cmon.firehose.Main
Failed to start Firehose
java.io.IOException: Unknown version of the versioned LevelDB store.
at com.cloudera.cmon.tstore.leveldb.LDBUtils.openVersionedDB(LDBUtils.java:253)
at com.cloudera.cmon.tstore.leveldb.LDBPartitionMetadataStore.<init>(LDBPartitionMetadataStore.java:139)
at com.cloudera.cmon.tstore.leveldb.LDBPartitionMetadataStore.<init>(LDBPartitionMetadataStore.java:133)
at com.cloudera.cmon.tstore.leveldb.LDBPartitionMetadataStore.createInPartitionMetadataSubdirectory(LDBPartitionMetadataStore.java:119)
at com.cloudera.cmon.tstore.leveldb.LDBPartitionManager.createLDBPartitionManager(LDBPartitionManager.java:193)
at com.cloudera.cmon.firehose.LDBWorkDetailsTable.<init>(LDBWorkDetailsTable.java:90)
at com.cloudera.cmon.firehose.LDBWorkDetailsStore.<init>(LDBWorkDetailsStore.java:67)
at com.cloudera.cmon.firehose.LDBWorkStoreFactory.createYarnWorkDetailsStore(LDBWorkStoreFactory.java:139)
at com.cloudera.cmon.firehose.Firehose.<init>(Firehose.java:222)
at com.cloudera.cmon.firehose.Main.main(Main.java:515)
Also following is shown in the cloudera.quickstart dashboard:
Unable to issue query: the Service Monitor is not running
This is a common error found in cloudera docker container booted on a single node
I solved it by removing the old /var/lib/cloudera-service-monitor.
My Node Red application in IBM BlueMix is repeatedly crashing - once an hour - with no real error message other than "exited with status: 1."
How can I troubleshoot this issue?
Is there someone from IBM BlueMix support that monitors this that could take a look?
I looked at my logs and there's nothing in there that really says what's going on.
Edit per requests:
The regular log for "OUT/ERR" is scrolling so fast with HTTPD logs that I can't get it to copy/paste. Filtering to "ERR" Channel the only thing I see is below. I believe this is an error which occurs during deploy when the application restarts.
[App/0] ERR js-bson: Failed to load c++ bson extension, using pure JS version
My Node Red application is gathering data from Wink, LIFX, and other IoT services and compiles them together into a Freeboard dashboard.
Caught crash on screenshot here -- not enough cred to post images so it'll only post as a link
The zlib error was fixed in the 0.13.2 Node-RED release (that shipped 19/02/16).
If you re-stage your application is should pick up the new version of Node-RED
You can re-stage the application using the cf command line management application:
cf restage <app name>
I have installed MobileFirst 6.3 appcenter console, worklight console successfully, they are operating fine on Tomcat/7.0.57. However when I try to install Operational Analytics, the documentation has the following
http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.installconfig.doc/monitor/c_op_analytics_installation_tomcat.html
I am using tomcat manager http://localhost:8080/html to deploy the war files. logging in as manager, with the manager-gui role.
worklight-analytics.war - deployed with no issues
when I select the worklight-analytics-service.war file and deploy in the GUI, it throws a blank page first, indicating "connection error", and when I refresh the page, on the status bar in Tomcat manager GUI, I get this message - "FAIL - Tried to use command /upload via a GET request but POST is required";
Please provide some direction on what I need to do get this fixed. I am not sure If I have provided all required information - please bear with me and ask, if anything relevant (obviously I can't figure out what is relevant yet) is required to debug.
So I was able to reproduce your error and I saw this in the logs:
java.lang.IllegalStateException:
org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException:
the request was rejected because its size (57353297) exceeds the
configured maximum (52428800)
It looks like by default, the web UI will only upload WARs of size 50MB or smaller. The analytics service WAR file is larger than this, so that is why this is failing. I was able to increase the limit by modifying the following lines in
/webapps/manager/WEB-INF/web.xml
<max-file-size>100000000</max-file-size>
<max-request-size>100000000</max-request-size>
This will increase the limit to 100MB. After I did this, I was able to successfully deploy the service WAR.
Just as a heads up, once you get the WAR deployed, you'll be presented with the login page. You'll need a tomcat user with the 'worklightadmin' role in order to get past the login screen.
The worklight-analytics-service WAR file does not have a user interface. It is simply referenced by the worklight-analytics WAR file. When both WARs have been deployed, can you see the analytics console? And does data load just fine? If so, then everything is fine. There is only an issue if you are unable to use the user interface provided by the worklight-analytics WAR file.