deploying a liberty war file to bluemix liberty gives error 400 - ibm-cloud

After creating a WAR file using maven successfully, I tried uploading the WAR file to Liberty on Bluemix. I used the following command:
cf push wallet -p ./wallet-service/target/wallet-service-1.1-SNAPSHOT.war
Creating app wallet in org irazabal#us.ibm.com / space jax-rs as irazabal#us.ibm.com...
Got following response:
"OK
Creating route wallet.mybluemix.net...
FAILED
Server error, status code: 400, error code: 210003, message: The host is taken: wallet"
What does that mean and more importantly, how do you fix it?

The above error message means the hostname wallet is taken. You are assigned a hostname on a shared domain of mybluemix.net. You can fix this issue by choosing a unique name. You can keep the name of the app to be wallet but choose a unique hostname with the following command.
cf push wallet -n somethingunique -p ./wallet-service/target/wallet-service-1.1-SNAPSHOT.war
The -n argument allows to give a hostname to the app.
Additionally, you can point your own domain to Bluemix and use that with your app.

Related

bluemix delivery pipeline fails with server error

I created a new application in a new (empty) space and when I try to deploy it, it fails with this error:
Server error, status code: 400, error code: 210003, message: The host
is taken: IoT-DEMO-POC
You need to use a different route because the host is taken. See http://iot-demo-poc.mybluemix.net/
You can get a random route if you run the push command with --random-route
cf push --random-route
You can also open the manifest.yml file and change the host parameter if there is one or the application name. The route needs to be unique.

Error when deploying nodeBB application on Bluemix. How to fix it and deploy successfully?

I want to deploy NodeBB on Bluemix using Compose for Redis service. I follow the setup instructions at https://docs.nodebb.org/en/latest/installing/os/osx-mavericks.html
But when I push the app to Bluemix the application fails to start. I get an error. Please refer to link below.
Error on pushing nodeBB on Bluemix
However the nodeBB application runs fine on my local macbook.
How to resolve this error.Please let me know how to deploy nodeBB on Bluemix successfully?
The error indicates the public/uploads/sounds folder is not found on the staged application. It is not getting pushed along with the other application files.
This folder is used by the nodeBB application to copy sound files at runtime. To make sure that the empty public folder is pushed to Bluemix create a .cfignore file. Add the following line to it
!/public
The following errors can prevent the nodeBB application to run on Bluemix.
1) If the credential to Compose for Redis is not setup correctly OR the Compose of Redis is unavailable in Bluemix
For the Redis connection to setup properly create a Compose for Redis service in Bluemix. Then Copy the Redis credentials from the service credentials as shown below.
{
"db_type": "redis",
"name": "bmix_dal_yp_94747ceb_7c86_4319_b7be_88c2e9c829eb",
"uri_cli": "redis-cli -h sl-us-dal-9-portal.0.dblayer.com -p PORT -a PASSWORD”,
"deployment_id": "583e1bea52de460017000124",
"uri": "redis://admin: PASSWORD#sl-us-dal-9-portal.0.dblayer.com:PORT”
}
PORT represents Redis port number and PASSWORD represents Redis password
Use the credentials to update the config.json correctly when you run command ./nodebb setup [ on Unix or Mac]
Make sure Compose for Redis service is up and running. Otherwise you will get connection errors from the nodebb application when you start it.
2) If the port that the nodebb application can listen on Bluemix is not updated to app.js before pushing the application to Bluemix then it will cause the application to fail to start on Bluemix.
Update
nconf.set('port', urlObject.port || nconf.get('port') || nconf.get('PORT') || (nconf.get('PORT_ENV_VAR') ? nconf.get(nconf.get('PORT_ENV_VAR')) : false) || 4567);
TO
nconf.set('port', process.env.VCAP_APP_PORT || urlObject.port || nconf.get('port') || nconf.get('PORT') || (nconf.get('PORT_ENV_VAR') ? nconf.get(nconf.get('PORT_ENV_VAR')) : false) || 4567);
3) Make sure that the application runs on the local machine without any errors before pushing it to the Bluemix. Command : ./nodebb start OR node app.js
The instruction to setup and run nodeBB on local can be found here ttps://docs.nodebb.org/en/latest/installing/os/osx-mavericks.html

Bluemix dashboard: Unable to update route (BXNUI0030E)

This error seems like a Bluemix internal error to me.
I try to add another route using the new Bluemix dashboard to one of my liberty apps and the error message I get is:
BXNUI0030E: The 'xxxxxx.au-syd.mybluemix.net' route wasn't mapped to
the 'xxxxx-arya' app because a problem occurred contacting Cloud
Foundry. Try again later. If you see this message again, go to the
Bluemix status page to check whether a service or component has an
issue. If the problem continues, click the Account and Support icon in
the top menu bar, click Get help, and search for help or get support.
The error message is not clear to identify cause of the problem. The message just tells Cloud Foundry command behind Web interface failed to create map-route, but it didn't tell what exactly happen. Please run below commands to know what happened during creating map-route and fix the problem;
Login into the space by cfcli;
cf login -a api.au-syd.bluemix.net -u -p -o -s
List all routes in the space and make sure the app or the map-route are there;
cf routes
Create map-route by command;
cf map-route APPNAME au-syd.mybluemix.net --hostname NEW-HOSTNAME
Check error message and fix the problem
*) Most common problem is duplicate map-route name if the hostname used in in other spaces. Please contact Bluemix Support with your new hostname if you cannot find the hostname in your organizations.

SQLDB status code 500

I received a FAILED Server error, status code: 500, error code: 10001,
message: Service broker error : {"description"=>"Service Broker provisioned at this url state is not operational 10002"} message, when trying to create a new SQLDB service instance.
What is the issue?
I was able to confirm that there was a brief issue earlier with the "Free" plan but it has since been resolved.
I was able to create a service successfully from the CF command line:
$ cf create-service sqldb sqldb_free randalstTestSQLDB515
Creating service randalstTestSQLDB515 in org johndoe#myemail.com /
space dev as johndoe#myemail.com...
OK
Try to create the service from the command line using the following syntax:
$ cf create-service sqldb sqldb_small mySQLDB
where
The first attribute sqldb is the service name.
The second attribute is the plan, either sqldb_small, sqldb_free, or sqldb_premium.
The last attribute mySQLDB is the unique name that you are giving to this service instance.

"no such host" mesage while site is deployed on moovapp.com domain

I have done a sample project based on blog.moovdemos.com to test the moovweb solution.
After testing it on on local system I deployed the project on moovweb cloud. I have learnt that one need to own the domain to be able to access it from internet. However, as per documentation, it is still available within moovapp.com domain.
While I am trying to access my site through moovapp.com domain I get moovweb warning page as below
Warning: the webpage you are attempting to access is a Moovweb
Remixed™ version of mshruthijanardhan14047.blog.moovdemos.com. Should
you choose to continue, Moovweb is not responsible for the contents of
this webpage.
[Agree and continue] [Decline]
However, on chossing [Agree and continue] I get following message instead of site page
Failed to establish a connection with upstream (dial tcp: lookup
[muser1234].blog.moovdemos.com: no such host)
please help me what is wrong here?
It looks like you have a misconfigured config.json file in your project.
On the right-hand side of the first "host_map" value, you will need to put the upstream domain 'blog.moovdemos.com'. You currently have it set to [muser1234].blog.moovdemos.com. This domain does not exist; that is why you are getting the "dial tcp: lookup ... no such host" error.
The correct setting should look like:
"host_map": [
"$.blog.moovdemos.com => blog.moovdemos.com"
]
Hope that helps.