I have enabled Diego for my application in bluemix and verified in command also. But the dashboard still showing the same as DEA . I tried restarted the app and refreshed the dashboard also . Any thoughts ?
You will need to use the command line to migrate an existing app to Diego.
After installing the Diego-enabler CLI plugin, run the command:
$ cf enable-diego APPLICATION_NAME
to migrate to Diego.
To verify that the app was successfully migrated, type the command:
$ cf has-diego-enabled APPLICATION_NAME
If you have done these two steps and the dashboard problem persists, try restaging the application:
$ cf restage APPLICATION_NAME
This is what I did to get rid of the DEA symbol next to my app name.
On January 31, 2017, Apps are scheduled to be automatically updated to the new architecture. Let me know if you are still encountering issues after restaging your application.
maybe u have a check the diego property of from CLI.
cf curl /v2/apps/$(cf app APPLICATION_NAME --guid)
to check the value of diego.
when diego is true, in Dashboard UI, DEA tag should not show out.
and about app not running, maybe have a carefully reviewing to docs, as joe said about "Diego made some changes for the host environment variable"
We have fixed this issue and it should be working now. Currently when apps are migrated from DEA to Diego through cf CLI or web UI, the UI of these apps will update automatically in both dashboard page and app details page.
Related
I have a Meteor App running on a Ubuntu Droplet on Digital Ocean (your basic virtual machine). This app was written by a company that went out of business and left us with nothing.
The database is a MongoDB currently running on IBM Compose. Compose is shutting down in a month and the Database needs to be moved and our App needs to connect to the new database.
I had no issues exporting and creating a MongoDB with all the data on a different server.
I cannot for the life of me figure out where on the live Meteor App server I would change the address of the database connection. There is no simple top level config file where I can change this?? Does anyone out there know where I would do this?
I realize that in the long term I will need to either rewrite or deprecate this aging app, but in the short term the company relies on it and IBM decided to just shut down their Compose service so please help!!
There is mostly the MONGO_URL and MONGO_OPLOG_URL that are configured as environment variable: https://docs.meteor.com/environment-variables.html#MONGO-OPLOG-URL
Now you don't set these within the code but during deployment. If you are running on localhost and want to connect to the external MongoDb you can simply use:
$ MONGO_URL="mongodb://user:password#myserver.com:port" meteor
If you want to deploy the app, you should stick with the docs: https://galaxy-guide.meteor.com/mongodb.html#authentication
If you use MUP then configure the mongo appropriately: https://meteor-up.com/docs.html#mongodb
Edit: If your app was previously deployed using MUP you can try to restore the environment variables from /opt/app-name/config (where app-name is the name of your app) which contains env.list (including all environment variables; thus your MONGO_URL) and start.sh which you can use to recreate the mup.js config.
My app is no longer shown listed under Apps in the Default environment at make.powerapps.com.
When I run Get-AdminPowerApp PowerShell cmdlet against the Default env, the App is listed.
When I run Get-AdminDeletedPowerAppsList, the App is not listed.
When I try to run Set-AdminPowerAppOwner, I receive an error...
Error=;
Message=No permission to the 'SharepointFormApp' application that has ID = '<guid-here>'.;
Internal=System.Net.HttpWebResponse
...but I have permissions on the SharepointList that the App is built on.
How do I troubleshoot and if necessary recover this app?
Try to go to https://admin.powerplatform.microsoft.com/environments, select the default environment and the Power Apps.
This should give you a complete list of apps in the environment.
I have on a few occations found flows that was disappeared this way.
Following the guide over here:
https://sap.github.io/cloud-sdk/docs/java/guides/logging-overview#logging-overview
I am trying to use CF CLI cf set-env command to change the logs levels at runtime.
This commands executes successfully and the log levels are only changed when I do a cf restage srv or cf restart srv. srv is the name of my application.
Is there any alternative where I don't have to stop the cf application and still be able to change the log levels at runtime?
No, I think in order to reload the setting from environment variables a reload is required.
You could instead implement a new endpoint in your application where you set the log level programatically. But that depends on the logging framework you are using. E.g. for Logback this can be done as described here.
We've created a new AppService and successfully deployed our solution backend through docker-compose (preview), but when we update one (or more) image on the registry and we restart the appservice to get docker-compose to get the new version, we get errors of ambiguous network name like this one
InnerException: Docker.DotNet.DockerApiException, Docker API responded with status code=BadRequest, response={"message":"network my_app_service_multi_nw__0 is ambiguous (94 matches found on name)"}
In our docker-compose.yml we don't have any network name specified (since network is a not-supported option)
At the moment, the only solution we found is to delete entirely the appservice and create a new one (WITH A DIFFERENT NAME, also)
What we're doing wrong? Is it possible to prune all unused networks?
We've contacted Microsoft for support, they've told us that it's a known bug and a temporary fix could be changing App Service plan.
Apparently, changing from S1 to B1 fixed the issue for us.
The answer from #Doc is currently not working for us, as scaling up or down the plan does not seem to reset the underling VM. We can't delete the app or change the name, therefore we are currently stuck with this issue...
EDIT: It was not sufficient to change from B2 to S2, but changing from B2 to P1V2 fixed the issue. A hint should be that, when you change the plan, you should see a message at the bottom "Outgoing IP addresses for your app might change", which ensures that your App Service app is actually migrating to a different VM, therefore resetting the Docker configuration.
I got the same issue in local when try to run with Visual Studio and got fixed with following steps.
step 1: List existing networks
docker network ls
Find duplicate network names
Step 2: Remove one network
docker network rm <NETWORK ID>
I want to view the Files and Logs for my Bluemix application, but when I select this from the Overview page for my app, it just shows the message:
BXNUI0045E: Could not retrieve files or logs for the 'XXX' application using instance '0'. See the Troubleshooting topics in the IBM Bluemix Documentation to check service status, review troubleshooting information, or for information about getting help.
I looked at the Troubleshooting topics but found nothing helpful. What is this message trying to tell me, and how can I fix this problem so that I can see Files and Logs for my app?
If your application failed to start or crashed, the Bluemix UI can not be used to retrieve the files and logs. I recommend you use the command line tool.
If the application failed to start or crashed, you can get logs by:
cf logs <appname> --recent
If the application started and running properly, you can view the files (including any logs the server or application writes) by:
cf files <appname>
cf files <appname> <path>