bionic | * * Bionic - An Ionic CLI clone | Binary Executable Format library

The upstream repo is

Your script has a number of oddities which should probably be straightened out regardless of the immediate problem.

• kill -0 "$$" || exit 0 is weird and probably does nothing useful. I guess you probably simply should do nothing in this case, as the purpose of the script seems to be to install the component if it's missing, and then proceed into the mongodb_status= ... part.
• As basically all the commands here are privileged, it would make more sense to just abort up front if the entire script is not running with privileges.

Stylistically, everything which looks like sudo bash -c 'singlecommand' should be just sudo singlecommand; but with the proposed refactoring, you don't need these at all.

The immediate problem with your script seems to be that it takes a while for the server to start listening on the port you configured it for. I don't know enough about Mongo to tell you how to properly wait for it to tell you when it's up "for real" but adding a sleep is a common (albeit crude) workaround. Another is to examine the log file, looking for the listening event.

Just had a similar issue and for me, this fixed it. Basically, I had add the new repository key and delete the old one. Listing the commands here for convenience:

The SinkBinding object has a subject configured using a label selector:

Finally, I found the problem!

Fast answer

Reading trace log on SQL Server, on "Application Name" field, we can observe that some origins calls DataBase (Apache, PHP-FPM and PHP Freetds)

The issue occurs using PHP SQLSRV (pdo), with only with FreeTDS (php ext DBLIB) does not have problem.

Then is a good idea use only PHP DBLIB with FreeTDS on unix systems.

Complete answer

TL;DR;

Of course, the problem is not with only with PHP SQLSRV extension. On our investigation, we look at diver version, and client Linux uses newest version of driver MSODBCSQL17.

But on our server, running SQL SERVER 2016, the driver version is 13.

But the Microsoft have a upgrade to version 17 (same used on Linux client)

Reading the change log, an issue about high cpu usage is fixed.

"Can you prove?"

Yes!

We didi a simple test, on our linux "server 1", we remove support from freetds (disable DBLIB), and immediately we can observe a decrease performance on our dashboard, and after some minutes, when freetds is enabled again (DBLIB) the performance returns to normal, see above.

Our new linux does not have freetds installed, we only taken drivers from Microsoft to PHP 7+ and PECL extension.

The problem is because our SQL SERVER uses ODBC Driver 13 and our cliente have ODBC Driver 17.

We can not upgrade the driver on SQL SERVER, because we need this version, and ODBC 17 is supported only on SQL SERVER 2019.

Then, for now our solution is to use freetds and not PHP SQLSRV extension.

Another point to observe is, all query from PHP SQLSRV is parametrized like this:

This is a known issue. Read this for more info.

You can first add the correct repository GPG key using the following command.

I followed the steps described in the below link to upgrade, hope it helps:

https://phoenixnap.com/kb/update-node-js-version

I chose the first option to Update Node.js with NVM (Node Version Manager)

This code:

I dont know why but separating the install scripts into separate layers makes an image that works.