APE Install Missing File - mysql

After installing from the RPM and then trying the Binary versions of APE (AJAX Push Engine) I am getting this error (on both versions) when I try to run the APE server:
[Module] Failed to load ../modules/libmod_spidermonkey.so [Invalid library] (libmysqlclient_r.so.15: cannot open shared object file: No such file or directory)
I am using Fedora Linux, with MySql and apache installed. How can I get this libmysqlclient file? I have found this RPM: http://rpm.pbone.net/index.php3/stat/4/idpl/12471829/dir/fedora_4/com/mysqlclient15-5.0.67-1.fc4.remi.i386.rpm.html
And it says it includes this file, so I downloaded it to the box, attempted to install and tells me that it's already installed.
Any advice would help thanks!

Inside the ape.conf there's a module working directory which must be altered.

Related

Problem upgrading from mysql 5.7 to 8.0 in a rails app - missing mysql.so files

I upgraded a working Rails app from Mysql 5.7 to 8.0 on my dev machine but it fails to work on a staging/test server setup with the exact same directory structure and env vars.
I'm getting an error "file not found" for /apps/bundle/ruby/2.7.0/gems/mysql2-0.5.4/lib/mysql2/mysql2.so
ldd /apps/bundle/ruby/2.7.0/gems/mysql2-0.5.4/lib/mysql2/mysql2.so shows a file not found (mysql.so.20) (? - I'm not at work so the filenames might be off) that definitely existed and was part of Mysql 5.7.
So the overall question is how to force the mysql2 gem install to relink to the correct new .so files?
There are a lot of moving parts to this, making things a mystery:
installing mysql from a source tarball,
installing in non-standard directories (apps/usr/local/stow/mysql-8.0.16),
using GNU stow to link mysql .so files from the install directory apps/usr/local/stow/mysql-8.0.16 into a common /apps/usr/local/lib directory (the env var LD_LIBRARY_PATH=/apps/usr/local/lib),
vendoring the gems in the bundle on my dev machine using the bundle package --all command so they're part of the git repo.
I've blown away the /apps/bundle directory contents and rerun bundle install thinking that would force a proper linkage of the .so files without success.
Any ideas? TIA!

Configure SonarQube (Node.JS) to download binaries from an internal server

What we are trying to do is to get SonarQube to analyze our Typescript (Node.JS) project on a Docker image, but we are running into an error. If it helps, we are trying to use the sonarqube-scanner module from Node.JS.
The error is as encountered below:
[17:57:23] Starting analysis...
[17:57:24] Getting info from "package.json" file
[17:57:24] Checking if executable exists: /root/.sonar/native-sonar-scanner/sonar-scanner-4.5.0.2216-linux/bin/sonar-scanner
[17:57:24] Could not find executable in "/root/.sonar/native-sonar-scanner".
[17:57:24] Proceed with download of the platform binaries for SonarScanner...
[17:57:24] Creating /root/.sonar/native-sonar-scanner
[17:57:24] Downloading from https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-4.5.0.2216-linux.zip
[17:57:24] (executable will be saved in cache folder: /root/.sonar/native-sonar-scanner)
[91m[18:03:53] [0m[91mERROR: impossible to download and extract binary: connect ETIMEDOUT 91.134.125.245:443
[0m[91m[18:03:53] [0m[91m SonarScanner binaries probably don't exist for your OS (linux).
[0m[91m[18:03:53] In such situation, the best solution is to install the standard SonarScanner (requires a JVM).
[0m[91m[18:03:53] Check it out at https://redirect.sonarsource.com/doc/install-configure-scanner.html
Now if you notice from the error, the binaries server encounters an ETIMEDOUT error, and this is because the server that accesses it comes from an internal network that cannot access external sites.
Would it be possible to configure SonarQube to pull from an internal server? And if so how would we go about configurating this?
Many thanks in advance!
I was able to find documentation through the SonarQube Javascript module here (https://www.npmjs.com/package/sonarqube-scanner)
By default, the scanner binaries are downloaded from https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/. To use a custom mirror, set $SONAR_SCANNER_MIRROR. Or download precise version with $SONAR_SCANNER_VERSION
Example:
export SONAR_SCANNER_MIRROR=https://npm.taobao.org/mirrors/sonar-scanner/
export SONAR_SCANNER_VERSION=3.2.0.1227

Can't run PopSQL in Ubuntu 18.04 with node v11.2.0

To learn MySQL I installed PopSQL using .deb package but it's not working, when I launch PopSQL from terminal with sudo popsql I get these error in the terminal and PopSQL ui shows blank screen.
{"name":"PopSQL","hostname":"ivyRose","pid":16621,"level":30,"msg":"Starting app. Look for crash reports in /tmp and error logs in /home/neon/.config/PopSQL/error.log","time":"2018-11-22T12:15:27.927Z","v":0}
(popsql:16621): IBUS-WARNING **: 18:00:28.174: The owner of /home/neon/.config/ibus/bus is not root!
[Oracle] NJS-045: cannot load the oracledb add-on binary for Node.js 8.2.1 (linux, x64)
Node.js require() error was:
DPI-1047: 64-bit Oracle Client library cannot be loaded: "libclntsh.so: cannot open shared object file: No such file or directory". See https://oracle.github.io/odpi/doc/installation.html#linux for help
Node.js require() mapped to /opt/PopSQL/resources/app.asar/node_modules/oracledb/build/Release/oracledb.node
Node-oracledb installation instructions: https://github.com/oracle/node-oracledb/blob/master/INSTALL.md
You must have 64-bit Oracle client libraries in LD_LIBRARY_PATH, or configured with ldconfig.
If you do not have Oracle Database on this computer, then install the Instant Client Basic or Basic Light package from
http://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html
[ODBC] libodbc.so.1: cannot open shared object file: No such file or directory
You don't need PopSQL to learn MySQL.
But, if you want it, to get it going, follow the error message instructions:
download the Instant Client Basic Light package from
http://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html
unzip it
add the directory to your library search path, either via LD_LIBRARY_PATH or using ldconfig (I recommend the latter), as shown at
https://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html#ic_x64_inst
PopSQL should use a try/catch block when it requires oracledb so you don't see the error.
It looks like you are missing the required driver from mysql. You can download and install this from
https://dev.mysql.com/downloads/connector/odbc/
The answer here should help.
https://askubuntu.com/questions/800216/installing-ubuntu-16-04-lts-how-to-install-odbc?answertab=votes#tab-top

unable to install percona mysql on linux centos 7 version

When we try to install percona MySQL using binary installation we are getting error as follows:
./mysql_install_db: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
[mysql#unvacp004 bin]$ ./mysql_install_db --basedir=/fs0/mysql/product/5.7.20/bin --defaults-file=/fs0/mysql/instance/dddd/conf/my.cnf --ledir=/fs0/mysql/product/5.7.20/bin/ --user=mysql
Have you tried the solution here?
https://bugs.launchpad.net/percona-server/+bug/1453395
It seems there are different tarballs which have different SSL library dependencies.
You probably use the wrong one.
Also make sure you have the libssl1.0.0 libssl-dev packages installed. This is for Ubuntu, for RHEL systems the packages might be called differently.

Binary file refuses to run due to a missing shared library

I tried building recutils version 1.7 downloaded from the home page, using the standard configure, make, sudo make install sequence, but when trying to run the resulting binaries. like recinf, I get the error:
recinf: error while loading shared libraries: librec.so.1: cannot open shared object file: No such file or directory
Does this mean I made a mistake during the build or is the package itself in error?
As Etan Reisner said the problem was that the shared object libraries were installed but not loaded into the cache, hence the need to run ldconfig. After running
sudo ldconfig
the binaries ran properly. If I had looked in /usr/local/lib, I would have seen the libs there.