Hello Claudio,
Thanks for the reply. That indeed did the trick! Which leaves me wondering
what all of those other configuration variables actually do, but I'll read
the docs one more time, hopefully it will come to me!
Thanks!
BR,
George
On Fri, 2 Nov 2018 at 22:52, Claudio Nanni
wrote:
> Geo
George,
On Fri, Nov 2, 2018 at 7:01 PM George Diamantopoulos
wrote:
> Hello all,
>
> I've setup a galera cluster with 3 nodes, and I believe that
> wsrep_node_incoming_address
> is not honoured when set in the configuration. More specifically, the
> setting persists in mariadb:
>
> +-
Hello all,
I've setup a galera cluster with 3 nodes, and I believe that
wsrep_node_incoming_address
is not honoured when set in the configuration. More specifically, the
setting persists in mariadb:
+-+---+
| Variable_name | Value |
+-
Hello,
Does the MariaDB development team intend to add account locking? I
don’t see it in the 10.4 roadmap.
MySQL added this in 5.7.6. Previously we’d accomplished this by
reversing the password hash; for our servers that run MariaDB it would be great
to be able to use the same
Hi,
Since you are using LXC, you have to pass an option to change the limit.
For docker:
docker run --name mariadb --ulimit nofile=65535:65535 mariadb:10.1.35
In LXC:
lxc config set mariadb limits.kernel.nofile 65535
-GL
Le ven. 2 nov. 2018 à 12:07, a écrit :
> Hi,
> I have installed
> Ma
Hi,
I have installed
MariaDB 10.1.35
in a container (LXC) with Debian 9.5.
Starting the database service I get this warning:
Nov 02 03:23:50 ct125-netdot mysqld[25687]: 2018-11-02 3:23:50 140396535071680 [Warning] Could not increase number of max_open_files to more than 4096 (request: 418
6 matches
Mail list logo
