We are trying to integrate Flyway with our Spring Boot apps. Its working fine for bunch of services but for one service it always brings up all pods except one (we have 3 replica pods for K8s). Weird thing is that in the logs nothing is available, even we enabled DEBUG for our app but application logs only shows Flyway Community Edition 5.2.4 by Boxfuse. We have been trying to trouble shoot this issue but without any logs its almost impossible to do the root cause analysis. There are no errors/exceptions in the logs and logs just hangs after logging above Flyway version log. Also for most of the time, some pods comes up fine while other (mostly 1 out of 3) just hangs and once noticed it becomes healthy after 40 mins or so. Not sure what is going on as went through lot of documentation without any luck.
We are using following versions.
Spring Boot: 2.1.6
Flyway DB: 5.2.4
Postgress: 42.2.5
Any pointers are appreciated.
Related
I have a droplet in Digital Ocean with Ubuntu 20.04 and a .NET Core web application that connects to Mongo.
My deployment workflow is the following:
I work locally with Visual Studio and release my app to a folder.
Then I connect to my server through FTP and drag the content of my folder to /var/www/myapp
Secrets are managed by Azure (it took me a lot of time to set this up).
A service runs the app and restarts it if needed.
The web server is Nginx
Everything works fine, nothing new so far. However, I'd like to automate each deployment and I found GitLab can run a pipeline to help me achieve that. The problem is I don't understand how to set this up correctly since I've seen there are more partes involved, such as Docker and Kubernetes, and I feel a bit overwhelmed.
Do I need to "dockerize" my application, database, etc.? If I want to add Angular as the client side, do I need to dockerize it as well or it goes in the same container as the .NET Core app?
Do I need Kubernetes? If so, why?
What would be the most straightforward and recommended way of achieving a CI/CD for my app?
It took me a lot of effort to deploy to my Linux server and I'm afraid I can destroy something in production.
I would really appreciate any help.
I had Application Insights running smoothly on an Azure Web App via the AI SDK, reporting to an AI instance hosted in Azure.
The only niggle was it didn't show detailed dependancy diagnostics, according to this page this was because I was using the SDK only, I needed to "Instrument your web app on the server", which looking at the docs can't be done if you already have an instance of AI running....helpful!
Reluctantly I deleted the AI instance, stripped the SDK from my code so I was starting fresh, and followed the steps, however as soon as I finished the process in the previous link my website broke and now responds to every single request (MVC5 and Web API) with an empty 404 request
The AI status page is showing green ticks for everything, and I can't discern anything from diagnostic log dump from KUDO or manage to remotely debug the site.
Deleting the AI extension under Web App -> Extensions in the Azure portal and then restarting the web app fixes the problem.
I've run out of ideas on how to fix this, is there anything else I can do to get to the bottom of the problem?
To fix this problem, delete the following 2 files from your web app's (or slot's) filesystem:
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation32\ProductionBreakpoints_x86.config
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation64\ProductionBreakpoints_x64.config
You can do this easily through Kudu.
Edit: Apparently this is/was an issue with the ProductionBreakpoints interacting with precompiled views. Microsoft has informed me a fix should be out within the next couple days. The version of Application Insights extension I have now that is still broken is 2.4.6 - I will post the "fixed" version when I can confirm it.
Edit 2: Confirmed this is fixed in 2.4.7 which is out now.
After following the Meteorjs instructions and successfully creating an app, the deployment step failed. I am familiar with the developer account and the normal procedure. The Error being provided is stating that I have unauthorized access to Galaxy and that I am attempting to deploy on it (this is the paid cloud service of Meteor released recently and not the testing cloud service of Meteor.com for developers). I am not understanding why this redirection is occurring. It would be helpful to point out the issue. The name of the app being deployed follows the format appname.meteor.com. Please also note that
The developer-account dependency was installed
The app was created through the Meteorjs dashboard
I was also logged in from the console prior to deploying
Thanks in advance
I would like some clarity on the process you're attempting, however meteor killed free hosting in March of 2016 (three months ago at the time of this post).
This post explains the details of MDG cancelling that service.
This means there is no longer a testing cloud service, which seems like what you're attempting to deploy to (can't tell as you've given no specifics on your process), there is only Galaxy.
I am hosting a website on Azure Websites, and starting around 10AM CST today, I have been unable to deploy for the following reason
Web deployment task failed. (Could not connect to the remote computer ("waws-prod-chX-XXX.publish.azurewebsites.windows.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)
On top of that the site keeps giving a 502 gateway error (after 5 minutes), BUT the Azure dashboard shows everything is up: http://www.windowsazure.com/en-us/support/service-dashboard/
I use the Standard Mode on a Small VM which I share between 3 other sites, the other sites are all fine, and I can publish to them, just not this one. They all have the same web deployment server.
In my case I experienced the same error, and did not see anything wrong in the console. Then right as the hour turned over, I was able to do it again.
There must be some setting that only allows X number of WebDeploy resources to be used per hour.
I'm currently running Azure SDK 1.6 and am having troubles starting the Azure instance locally without debugging.
It's hanging on "Starting the roles for the application in the Windows Azure compute emulator ..." step.
Strangely enough when I hit Debug, the project starts.
Additionally the project does not pick up any HTML/CSS/Code changes when I run in debug mode.
Has anyone else encountered this issue and/or have a solution?
I've seen this:
http://social.msdn.microsoft.com/Forums/nl-NL/windowsazuredevelopment/thread/ad362016-16f6-459a-8022-9307aa5f910e
and this:
http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/05dbf84c-4929-40b4-82b2-f7747227d541
But both do not seem to resolve the issue.