Having error to fetch k6 when using nebula-bench in NebulaGraph Database - nebula-graph

With Nebula Graph Bench v1.0.0, I got the git and compiled k6 by scripts/setup.sh, and the version of k6 I installed was v0.0.7;
After I executed this command (python3 run.py stress run), it reported an error directly, suggesting that it seems to be a version problem; then I got the k6 of v0.0.9 again, ending up with the same error.
Please help me to solve it.

You seemed to use a mismatched version of the NebulaGraph bench to the NebulaGraph database as it's complaining graph client version is incompatible.
Refer to https://github.com/nebula-contrib/NebulaGraph-Bench#dependency on the compatibility matrix to get the correct version of NebulaGraph Bench :).

Related

How do I solve this error `/lib64/libm.so.6: version 'GLIBC_2.29' is not found` when I perform a task on workflow in NebulaGraph Explorer?

The complete error message in NebulaGraph Explorer is:
/lib64/libm.so.6: version 'GLIBC_2.29' not found (required by /home/vesoft/jdk-18.0.1/jre/lib/amd64/server/libjvm.so)
I encountered the same problem and found the solution for your reference.
Because the operating system version does not support JDK18, the command YUM cannot download GLIBC_2.29, you can install JDK1.8. Do not forget to change the JDK address in nebula-analytics/scripts/set_env.sh.

Telepresence Connection Error - Traffic Manager version unsupported, must be 2.4.5 or higher while it is 2.6.5

I have started to face this problem. While trying to connect, I am facing an error stating that my traffic-manager version is 2.1.5 and it should be at least 2.4.5.
"telepresence connect" command checks for new versions and modifies it if there is any new version exists. So I am thinking that started to create a problem. Because I was using it as normal.
When I check the connector.log file these two lines create the problem.
connector/session : Existing Traffic Manager 2.6.5 not owned by cli or does not need upgrade, will not modify
connector/session : failed to connect to root daemon: rpc error: code = Unknown desc = unsupported traffic-manager version 2.1.5. Minimum supported version is 2.4.5
So somehow I have two versions now while checking for the update it hits 2.6.5 but while trying to run it tries with 2.1.5. Trying to uninstall telepresence but it also faces the same problem and I couldn't locate and delete traffic-manager 2.1.5. My OS is Windows 11.
Because of that, I am kind of blocked with my tests. Any help will be well appreciated. Thanks!
After asking the question, a new version arrived, if anyone encountered this problem, please update telepresence to 2.6.6. It is fixed now.

Issue running airflow on Mac M1: error in Flask-OpenID setup command: use_2to3 is invalid

Having an issue running airflow on my M1 Mac. Keeps erroring out with error in Flask-OpenID setup command: use_2to3 is invalid. I have setuptools < 58 and still having issues.
ERROR: Could not find a version that satisfies the requirement flask-openid==1.2.5 (from versions: 0.9, 0.9.1, 1.0, 1.0.1, 1.1, 1.1.1, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.0)
ERROR: No matching distribution found for flask-openid==1.2.5
Yes. It's been fixed in flask_openid 1.2.6 (It's not a problem with Airflow but with FlaskOpenID).
Looks like for some reason your setuptools is not what you think it is. See:
https://github.com/pallets-eco/flask-openid/issues/59
You have not explained a crucial things - how you are installing airflow, neither which version of Airflow you try to install - which does not help in trying to help you unfortunately, so I have to make some guesses. Here is what you can do if you cannot - for any reason - downgrade to setuptools < 0.58.
If you are using Airlfow 2 and using constraints (as you should - this is the only supported way https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html) for some older version of Airflow, then possibly flask-openid is 1.2.5 in those old constraint versions. Please check it and if you REALLY want to stay with an older version, then you can download the constraint file locally, modify flask-openid version to 1.2.6 and point to the file instead of the github URL as you should do normally (If you don't use constraints - start using them immediately).
However, better option than installing an old version of Airflow, will be to update to the latest version of Airflow (currently 2.2.2 but we are about to start voting on 2.2.3), where this problem is for sure fixed (also in few other versions). Airflow folows SemVer so you should be generally safe to migrate to 2.2.2 if you've used an earlier version of Airflow 2.
If you are trying to install Airflow 1.10.* - then don't do it. Move Airflow 2 immediately. Airflow 1.10 has reached end of life in June 2021 and it's almost half a year as it did not receive any fixes - it won't receive any fixes for the Flask OpenID problem, so you are pretty much on your own here.
Also you make yourself vulnerable to unpatched security issues (Airlfow 1.10 stopped receiving also critical security fixes as of June 2021).

ROracle Error in .oci.Driver

I'm trying to use ROracle. My Oracle database version is Oracle Database 12c Release 12.1.0.1.0 - 64bit Production, and I have installed Instant Client and SDK for the version 12.1.0.2.0 (12.1.0.1.0 isn't available on Oracle's site).
I can access the Oracle database through Oracle SQL Developer without any issues. The error message I get in RStudio is:
Error in .oci.Driver(.oci.drv(), interruptible = interruptible, unicode_as_utf8 = unicode_as_utf8, :
In case it's useful, I have installed Instant Client and SDK here:
C:\oreclient_install_dir\instantclient_12_1
I'm running a Windows machine and I followed the instructions on CRAN:
http://cran.us.r-project.org/web/packages/ROracle/INSTALL
Including adding the environment variables.
After some searching (e.g. here) it looks like I need to set LD_LIBRARY_PATH and ORACLE_HOME and "OCI_LIB", which I did:
Sys.setenv(LD_LIBRARY_PATH="C:/oreclient_install_dir/instantclient_12_1")
Sys.setenv("ORACLE_HOME" = "C:/oreclient_install_dir/instantclient_12_1")
Sys.setenv("OCI_LIB" = "C:/oreclient_install_dir/instantclient_12_1")
Same error comes up. I'm likely not doing this right, however; I'm not a DBA and don't know all the details.
Any help with this would be appreciated.
LD_LIBRARY_PATH is for Linux. Assuming that you already have Rtools installed in C:\Rtools, you can use the following code to install ROracle
Sys.setenv(OCI_LIB64="C:\\oreclient_install_dir\\instantclient_12_1")
Sys.setenv(PATH=paste0(Sys.getenv("PATH"),";C:\\oreclient_install_dir\\instantclient_12_1"))
install.packages("ROracle", type="source", INSTALL_opts="--no-multiarch")
For using the ROracle package, you can use the following:
Sys.setenv(OCI_LIB64="C:\\oreclient_install_dir\\instantclient_12_1")
Sys.setenv(PATH=paste0(Sys.getenv("PATH"),";C:\\oreclient_install_dir\\instantclient_12_1"))
library(ROracle)

Error in installing Virtuoso Conductor on CentOS

I installed the latest version of Virtuoso using yum on CentOs. I was able to successfully do that first time. However,when I restarted the virtuoso server after uploading a dataset/CSV file, I am not seeing the 'conductor tab' in the webUI.
I thought something went wrong - and tried to do a clean install. But I have somehow managed to loose conductor completely this time. Below is the log snippet of virtuoso-t.
10:41:00 INFO: PL LOG: Installing Virtuoso Conductor version 1.00.8727 (DAV)
10:41:00 INFO: Checkpoint started
10:41:00 INFO: Checkpoint finished, log reused
10:41:00 INFO: PL LOG: VAD_INSTALL: Please update server version (FATAL)
10:41:00 INFO: PL LOG: Errors where detected during installation of "Virtuoso Conductor".
You report you "installed the latest version of Virtuoso using yum" -- but what version did you actually get? We provide a CentOS-specific guide which may now be outdated if someone has produced a yum package -- but that package may also be outdated.
Please check the version you have actually installed (output of virtuoso-t -? gives the best version string), and be sure it is at least 6.1.8 (if Virtuoso v6) or 7.2.2 (if Virtuoso v7). If not, I would suggest a clean rebuild/reinstall, following our instructions, based on the latest source from GitHub.
For future, questions specifically regarding Virtuoso are often best raised on the public Virtuoso Users mailing list, the public OpenLink Support Forums, or through a confidential Support Case. ObDisclaimer: I work for OpenLink Software, producer of Virtuoso.

Resources