am new to stackoverflow, and I thought of sharing this regarding an IBM product called APIC.
I did the whole deployment correctly as recommended by IBM on an Ubuntu Environment with mongoDB and MySQL using an AZURE Virtual Machine as Server. Whenever I try to update the schema of the database with the new models, I get an error saying:
Cannot GET /apim/dataSources/partials/dataSourceMigrate.html
Please help or ask me anything in case you need more info, and tell me if it's an error from Azure or IBM or me.
Thanks
This exactly happened to me once, and I contacted IBM for several weeks of give and take, to find out it's a bug on their side, not on the cloud side or your side :)
Check it here: https://stackoverflow.com/a/40016171/4694311
In this case, go back to using strongloop until they get it fixed.
Note that his is a bug on the operating system itself, it works on iOS but that would be useless on cloud.
Related
I recently deployed a Next.js application for a software engineering boot camp. I am using Vercel for hosting the web app. The problem I am having has been spoken about on the internet before. However, I couldn't find much helpful information.
When I look at the real-time logs for my application from my Vercel dashboard, a 504 error gets thrown for multiple API routes I have created. I am aware that Vercel places restrictions on requests depending on the hosting plan someone subscribes to. However, I can't help but wonder if I have overlooked an important step when deploying my application.
When deploying my application, I did the following things:
Connected a session store to my MongoDB database.
Created a password-protected MongoDB Atlas account (credentials are environment variables).
White-listed all IP addresses so that any user can interact with their portion of the database.
I would appreciate help finding out if these errors are my fault and if there is anything I can do about them or if they are solely caused by the restrictions of the "Hobby" plan.
Thank you very much in advance,
-Sam
Screen Shot:
I had a similar issue, turned out, it was just the fact that I did not add the vercel ip addr to the network access page on mongodb so momgodb was blocking vercel from accessing data.
You need to integrate MongoDB in your project on Vercel.
Go to your project settings in Vercel and go to the Integrations tab. Click the Browse Marketplace button and find MongoDb. Click Add Integration button and follow the instructions.
Hope this helps... I know this was asked quite a while ago.
You have to troubleshoot the issue by doing the following
Eliminate the NextJS app out of the equation - Using postman https://www.postman.com/downloads/ - Confirm the output of your API, what is the time the API takes? Given function invocation has a limit, you need to optimize the API to meet the threshold.
If the API times are fine and resolution occurs outside of your app, the next step is to troubleshoot the API route, remove the DB parts and just echo back a success message and check the function invocation time.
If #2 turns out to be the issue, reach out to vercel support - Another option could be hosting it outside and whitelisting the cross domain API ask from your application.
I've been installing our very own ArcGIS Enterprise instance on AWS.
The instance I chose is ArcGIS Enterprise on Ubuntu.
It is important to mention that this installation was conducted without using Cloudbuilder. I know it is a tool that automates the process but I was introduced to it only after I have already started to attack my current instance problems head-on. So, please don't advise me to restart the whole process from scratch using it.
The current status of my instance is that my ArcGIS Server is working. I can access it, upload services and we have already started using it in out Staging environment.
I have authorized all of the software on the server and verified it is licensed. The Portal for ArcGIS is my main problem.
Whenever I try to access it externally(from my office computer) it seems to redirect to the internal IP for some reason, and then times out on that request.
for example typing(from my browser):
https://[dns address]:7443/arcgis/home
redirects to:
https://[internal IP]:7443/arcgis/home
and this times out. (...took too long to respond error)
The funny thing is I can access the portaladmin area.
it's only the portal itself which doesn't work.
Also, another curious thing is that if I type without using the ports, I can access a window but exceptions are thrown in the browser.
For example:
https://[dns address]/arcgis
This will lead to a window where the ArcGIS world icon can be seen but nothing else loads and there are exceptions for "resource not found" 404 on some of the components of this page.
Any ideas? What further information should I include to answer this question?
I've looked everywhere but Esri's documentation is not very forthcoming with examples and information to understand what it is I did wrong.
Also, I don't think this is a ArcGIS software issue. It looks like this might be a proxy issue. Anyone else experienced something like this?
Thanks!
I found the solution.
It was a combination of two problems:
Tomcat that was running the web adaptor service was crashing because of an entirely different and unrelated issue.
The Portal was missing a web adaptor configuration and therefore did not have the WebContext property set with the web adaptor URL.
After fixing both of these problems, I was able to access the portal correctly.
We are using a MariaDB and a MongoDB (single instance) service in the Swisscom App Cloud.
If i try to create a backup with the backup button, it starts to create one, but fails after a few minutes.
Also, if i try to delete the failed entry, the deletion fails as well.
The interface provides no further information about the reason.
This happens for MariaDB as well as for MongoDB.
What could be a possible reason and how am I able to debug this error? Where can I get further information about the error?
screenshot of Portal:
Simon here from the App Cloud Team.
There was an issue in the backend which we fixed this morning, so your backups should now work again.
Sorry for the inconvenience.
I developed a CF CLI plugin for DB backups (MariaDB) in Cloud Foundry, called "cf-mariadb-backup-plugin", that also works in the Swisscom App Cloud. Check it out here, and give it a star. ;-)
If you use such plugin it presents the error message catch directly from the Cloud Foundry API. This might provide you, at least, better reasons on why such actions are failing.
I came across problem of cyclic (deploy-undeploy) deployments to WebSphere 7, where uninstalled application leaves dirty workplace. IBM has a fix (PM20642)for it in cumulative updates starting from 7.0.15, but I see no difference. Orphaned folder for business level app and composition unit are still present after undeployment.I'm using JMX admin client for connectivity to the server.
Anyone has any experience in dealing with this issue?
If you're using IBM's fix and it still fails, I would say open a PMR with IBM to help you investigate. It could be their fix didn't work as they expected or maybe the fix pack was not applied correctly. In either scenario way I would say you may want IBM's support to resolve this issue.
If you only have remote access via JMX, then you could try to use $AdminConfig deleteDocument in wsadmin to remove the files/folders from the configuration repository.
I have installed AppFabric onto Server2012. I checked the prerequisites were installed first and have installed accumulative update 3. I have an instance of SQL Server 2012 installed to SP1 and the OS indicates that all updates have been installed.
When viewing the dashboard I am receiving the error:
Unable to cast object to type
'System.Management.Automation.PSCustomObject' to type
'Microsoft.ApplicationServer.Management.Data.Group...'
I've found minimal information during my google searches, none of which are providing a solution to the problem.
Can anyone help with this?
I had the same issue and found that applying Windows Update KB2932678 (Cumulative update package 5 for Microsoft AppFabric 1.1 for Windows Server) stopped the error from coming up.
EDIT : KB3092423 (Cumulative Update 7) is the latest one I could find, so if you are going to apply an update you might as well apply the latest one.
I've had the same issue. I read somewhere (don't have the link) that it appears because there are no records in the AppFabric Monitoring DB's table that contains the instances (of the service).
Once you have at least one record there, the error will disappear and the Dashboard will show the WF instances correctly.
This worked in my case.
UPDATE:
To be precise, the table which is relevant for the AppFabric Dashboard to stop showing the aforementioned error is: AppFabric Persistence DB's table [System.Activities.DurableInstancing].[InstancesTable] . This table should contain at least one record that is related to the WF Service(s) that the current AppFabric Dashboard is shown for.