Superset database connection with Teradata error - kubernetes

I am trying to connect TD with superset running in kube. This is code from my Dockerfile:
USER root
RUN pip install sqlalchemy-teradata
RUN pip install teradatasql
RUN pip install "apache-superset[teradata]"
COPY tdodbc1700 /usr/local/lib/python3.8/site-packages/
ENV ODBCINI=/.../teradata/client/ODBC_64/odbc.ini
ENV ODBCINST=/.../teradata/client/ODBC_64/odbcinst.ini
This is the sql alchemy URI I am giving:
teradata://user:pwd#host:port/schema
Error I am getting:
"Unexpected error occurred, please check your logs for details"
I am not sure where to check log for more details? Please suggest how to get TD connected with Superset.
Note:
tdodbc1700 used in Dockerfile is ODBC driver for Linux. This is unzipped folder downloaded from TD site.
The base image I am using is amancevice/superset:latest

Related

Keycloak start failed: org.eclipse.microprofile.context-propagation.microprofile-context-propagation-api-1.2.jar does not exist

I follow this Keycloak guide to start Keycloak on my server. I am receiving the next exception when running the bin/kc.sh start-dev command:
ERROR: Failed to run 'build' command.
ERROR: java.lang.IllegalArgumentException: /srv/keycloak/lib/lib/main/org.eclipse.microprofile.context-propagation.microprofile-context-propagation-api-1.2.jar does not exist
ERROR: /srv/keycloak/lib/lib/main/org.eclipse.microprofile.context-propagation.microprofile-context-propagation-api-1.2.jar does not exist
ERROR: /srv/keycloak/lib/lib/main/org.eclipse.microprofile.context-propagation.microprofile-context-propagation-api-1.2.jar
For more details run the same command passing the '--verbose' option. Also you can use '--help' to see the details about the usage of the particular command.
The Keycloak version is 18.0.1, the installed JDK version is 11.0.15, the OS is Debian 11
Can anyone tell me how to solve it? Thanks
It turned out that some of the jars were missing after extracting the loaded Keycloak 18.0.2 tar.gz file on the server. After replacing the jars under keycloak/lib/lib/main and keycloak/lib/lib/deployment I was able to start the Keycloak. To do that, I extracted Keycloak 18.0.2 tar.gz on my local machine and uploaded corresponding jars to the server machine.

Citus 10.2 not starting an instance of PostgreSQL

I'm using RHEL 8.4 and I followed the installation instruction at Set up a single-node Citus cluster on your own Linux machine from RPM packages..
Step 1 and 2 (Install PostgreSQL 14 and the Citus extension and Initialize the Cluster) went through without any issues.
But When I tried (Step 3: Start the database server)
pg_ctl -D citus -o "-p 9700" -l citus_logfile start
I got the following error in terminal
waiting for server to start.... stopped waiting
pg_ctl: could not start server
Examine the log output.
The log output
FATAL: could not access file "citus": No such file or directory
LOG: database system is shut down
I do have a directory 'citus' in postgres user's home directory with all required files in it along with postgresql.conf
Kindly help.
It appears you ran into one of 2 issues:
Possible issue #1:
You did not successfully install citus package and the citus.so file is missing.
Can you see the file /usr/pgsql-14/lib/citus.so that should be installed via the package citus102_14?
If that is not the case, you should figure out why the package is not installed.
Possible issue #2
You do not run pg_ctl command in the home directory of postgres user.
I was getting the same error. I am using the Postgres compiled from the source file. Thus, instead of
sudo apt-get -y install postgresql-14-citus-10.2
I compiled the source of the Citus from Github and specified the path to location of my Postgres while configuring as:
git clone https://github.com/citusdata/citus.git
cd citus
./configure --prefix=/usr/local/pgsql/
make
sudo make install
I do not get an error during pg_ctl start and I can load extension as CREATE EXTENSION citus;.

How can install sensu-plugins through a proxy or by offline package

I am using Debian 7 amd64, sensu (version 0.28.4-1).
I install sensu-plugins through a proxy with the command:
/opt/sensu/embedded/bin/gem install sensu-plugins-redis --user-install --no-document -p http://myproxy:3128 --verbose -s https://rubygems.org/
But have an error:
ERROR: While executing gem ... (Errno::EPERM)
Operation not permitted - send(2)
When I try to directly install it in a server, which have directly internet connection, everything is successful.
I don't know why.
I also find key work: install sensu-plugins by offline package, but not have recommendation.
Please help me, thanks so much.

How run Odoo 9.0 from source code in Windows 10

i want to run odoo 9.0 directly from source code in windows 10. I done this:
1.- I downloaded source code from [GitHub][1]
2.- I already installed all system requirements (Python 2.7, Node.js, etc)
3.- I already have an postgresql database in AWS (RDS)
My problem is when i run odoo.py and i open this url (http://localhost:8069/web/), it show me an empty screen.
Here is my startup code:
Python odoo.py --db_host VALID-URL.us-east-1.rds.amazonaws.com -r USERNAME -w PASSWORD -d DATABASENAME --addons-path=addons
¿What i am doing wrong?
just add the option --debug to your command to get debug debug infos
or
you will find a file named odoo.conf (v9 -> v11) or openerp-server.conf (v7 or less)
search for debug_mode = false and set them to true.
I think I had this problem and needed to install node js, and npm less

After installing postgres 9.4 on fedora 20, couldn't launch psql

I have installed postgres 9.4 on fedora 20.
i have followed the steps through the link below
https://wiki.postgresql.org/wiki/YUM_Installation
I have started the server using the command
service postgresql-9.4 initdb
Then I set the auto start using the command
chkconfig postgresql-9.4 on
I am able to connect with Data base server via pg admin
but I am not able to connect with postgres DB server or SQL command line via terminal
If I enter psql for postgres/or any user, it says command not found.
can any one please help me on this.
You need to go to the installation bin directory and use './ExecutableFile' to run when logged in with postgres user.
So, use ./psql when you are in bin directory.
Or you can use "export PATH=path/to/bin/" to avoid using './'