I have a Superset, while deployed on PROD, I get Auth error whenever I try to Add any database.
As I test I tried Test Connection with Example database that also give the same error.
Surprisingly there is no error in any backend logs
Check if you have the right driver installed in the running superset environment
Related
Good day,
i have currently my django project running on an aws server. I have used Nginx and configured it all. The application is running, but when i try to login via the login page i have created or try to login via the admin panel it gives me a Server Error (500). I have my DEBUG=False and added my server dns to ALLOWED_HOSTS. As for the Database. I have got my SQL Database running on an Azure server and used environment variables (that i have permanently set in my ubuntu terminal) to get my password and username.
I have also tried to set DEBUG to False and trying to figure out the issue when running python manage.py runserver so i could experiment with it on my localhost, but no luck. I cant access 127.0.0.1 eventhough i have added it to my Allowed hosts.
How could i see what the error is? Thank you in advance
Ok, so fixed it!
After each change, you simply run the command sudo supervisorctl reload in your powershell after you ssh'ed into your aws ec2 server.
As for seeing what the error is, simply set DEBUG=True
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?
I followed the tutorial (https://aws.amazon.com/getting-started/hands-on/deploy-python-application/) on deploying Django website in AWS Lightsail. When I use the
python3 manage.py runserver 0.0.0.0:8000
to deploy the website then it works perfectly and I can access the website at http://AWS.INSTANCE.PUBLIC.IP.ADDRESS:8000
However, if I follow the Host the application using Apache part of the same tutorial, I am getting the following error when I try to access http://AWS.INSTANCE.PUBLIC.IP.ADDRESS:
Internal Server Error
The server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server administrator at you#example.com to inform
them of the time this error occurred, and the actions you performed
just before this error.
More information about this error may be available in the server error
log.
How to successfully deploy the Django website/app using Apache on AWS Lightsail instance?
I was able to run Django on lightsail by following the tutorial.
Make sure all paths in bitnami.conf file is correctly configured. Also, you need to retain the below part.
# Let Apache know we're behind a SSL reverse proxy
SetEnvIf X-Forwarded-Proto https HTTPS=on
This is the part where the tutorial asks to delete but don't delete this part. Below this part, should start.
If you were able to put up the correct paths, you should be able to run Django application on LightSail.
However, there is a bigger problem later on when you try to get HTTPS on lightsail instance;;;
My current set up has a Django project running on Windows 2016 IIS.
The project is hosted on GitHub for collaboration and I would like to set up a GitHub webhook so whenever there's a push to master branch from any of the collaborators, the IIS Server will run a "git pull" to update the project on the server.
What is normally the setup for this?
What I have tried so far is to create an endpoint in the Django project, this endpoint whenever called will run Python subprocess to run "git pull" command in the project itself. However, whenever I run it, it get a 500 response from IIS.
Thanks #VonC for helping.
I have looked to the log (which was the one in XML) but it wasn't much help.
What I'm posting here was my workaround, not exactly to the answer for the question above.
I used django-background-tasks to add the command subprocess.run(['git', 'pull']) as a task to run later (after a few seconds after that by the #background decorator).
Error 500 means the IIS server throws an error.
You need to check said IIS server logs in order to check at what point in the execution of the webhook endpoint script the error occurs.
i have airbnb superset setup on centos 6.6 and python 3.4 virtual env. the web server is booted up without error logged and also OK to browse the web ui. but neither the tables which are already there due to"superset load_examples" in setupup, nor the mysql tables i managed to add in web ui by myself, are accessable from web ui. all tables are reported "The endpoint requires the datasource tablenamexxx, database or 'all datasource_access' permission", "You do not have permission to access the datasource(s):multiformat_time_series."
Anyone familiar with superset can help check this?
Error prompt is like this pic:
I have encountered this issue myself by neglecting to run the superset init command during the installation and initialization process before starting the webserver. Shutting down the webserver, running superset init, then restarting the webserver with superset runserver solved the issue for me.