Error uploading excel file to CKAN datastore - datastore

I have a CKAN 2.8 installed on an Ubuntu 16.04 server and I have successfully configured filestore, datastore and datapusher. Whenever I try to upload a to datastore, I get the message "Error: Process completed but unable to post to result_url" and the status says pending. I have set SSL_VERIFY to FALSE in datapusher_settings.py but the error kept coming. Anyone who can help with this?
Thanks.

Related

Update google cloud composer withterragrunt

I am trying to update cloud composer from composer-1.17.3-airflow-1.10.14 to composer-1.17.10-airflow-1.10.15 using terragrunt. 
After one hour it fails with the message:
Upgrade database failed.
Error: Error waiting to update Environment: Error waiting for Updating newly created Environment: Error code 9, message: Failed to update image version.
I already checked the logs and the recommendations on the docs (database is less than 16 GB, that the PyPI packages are compatible and that I can use the correct version for the upgrade)
Any help is appreciated!

expo wont start after switching wsl1 to wsl2

I tried to run expo start or yarn start and the console threw an error. On wsl1 it is working fine, it shows the QR code. However, I have to switch to wsl2 to set up mysql for my local server and now expo is not starting.
Also sometimes the QR code shows up but when I try to open the app in my device, the same error shows up.
Developer tools running on http://localhost:19002
Could not get status from Metro bundler. connect ECONNREFUSED 127.0.0.1:19001
Connecting to Metro bundler failed.
Error: Connecting to Metro bundler failed.
at _waitForRunningAsync (/home/kevsmercs/.nvm/versions/node/v12.13.0/lib/node_modules/expo-cli/node_modules/xdl/src/start/startLegacyReactNativeServerAsync.ts:344:11)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
I think the problem here is expo itself. I tried to I check the developer tools url, the site cant be reached. I also tried to check my account using expo login and this error shows up
Fetching the user profile failed
connect ECONNREFUSED 127.0.0.1:8888
connect ECONNREFUSED 127.0.0.1:8888
Error: connect ECONNREFUSED 127.0.0.1:8888
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14)
jest-haste-map: Watchman crawl failed. Retrying once with node crawler. Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project. Error: Watchman error: query failed: synchronization failed: Connection timed out. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html.
I tried multiple fixes but no luck.
1. set `REACT_NATIVE_PACKAGER_HOSTNAME` to my ip using `export`
2. delete `.expo` from root of project and run `expo start -c`
3. turn off windows defender and firewall
4. update `expo-cli` to latest (4.4.1)
5. restart laptop
Maybe this GitHub issue describes your problem and the workaround?
This can usually happen when publishing without ever having run expo start, also it's a good idea to run rm -rf .expo to clear your local state
it's listed in our common development errors
Your latest edit shows this error message and suggested fix: Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project. Did you try that?

Cannot install ibm-wdt V8.5

When I want to install IBM WDT V8.5 via MarketPlace, I get this error:
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Failed to transfer artifact canonical: osgi.bundle,com.ibm.websphere.v85.core,1.0.200.v20170613_0418.
Connection to http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/oxygen_comp/repository/plugins/com.ibm.websphere.v85.core_1.0.200.v20170613_0418.jar failed on Read timed out.
.
.
.
Retry attempt 15 started
Read timed out
Unable to read repository at http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/oxygen_comp/repository/plugins/com.ibm.websphere.v85.core_1.0.200.v20170613_0418.jar.
Read timed out
The download of the file always freezes after about 2.9 MB. The same problem occurs when trying to download the file in a browser. The resource is however downloadable via secured https.
I tried Oxygen and Oxygen1 versions of Eclipse.
How to fix it? Or at least, is there any workaround?
The jar file that you mentioned is not available any longer. It has been replaced by:
http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/oxygen_comp/repository/plugins/com.ibm.websphere.v85.core_1.0.200.v20171214_0201.jar
I was able to successfully install WDT via Eclipse marketplace using Oxygen.

Failed to execute 'send' on 'XMLHttpRequest' error while installing Sitecore Azure

I want to deploy my website (built in sitecore 8.0) in Azure using Sitcore Azure module. I have downloaded the Sitecore azure 8.0 module from https://dev.sitecore.net/Downloads/Sitecore_Azure/80/Sitecore_Azure_80.aspx . And started installation using Installation wizard, I got an error after around 2 hours are spent on installation process. The error saying "Failed to execute 'send' on 'XMLHttpRequest' : Failed to load 'sitecoredemo/.../InstallationWizard'.
How to proceed further, please suggest.

Unable to start ws02 application server on Windows - error "The system cannot find the batch label specified - commandLifecycle"

I downloaded wso2 application server 5.0.0. I placed it on my windows server and attempted to execute wso2server.bat --run. When I do that, I receive this error:
The system cannot find the batch label specified - commandLifecycle
If I look in the wso2server.bat file, I see that the commandLifecycle label doesn't exist.
Has anyone else run into this same issue?
Edit: I just tried running 4.1.2 and I did not have the same problem.
I just run the shell: wso2server.bat without the parameter [--run] and it start ok.