How to change innodb_stats_on_metadata in MySQL

innodb_stats_on_metadata – Lets you collect statistics on metadata operations such as SHOW TABLE STATUS when accessing INFORMATION_SCHEMA.TABLES or INFORMATION_SCHEMA.STATISTICS tables.
In newer versions of MySQL, the innodb_stats_on_metadata parameter is disabled by default, which makes working with these tables faster.

Continue reading “How to change innodb_stats_on_metadata in MySQL”

Configuring OCSP Stapling

OCSP is a protocol for checking the validity of certificates, that is, to make sure that they have not been revoked and whether they were actually issued. Enabling OCSP Stapling on the web server side allows you to increase the speed of site opening, since the request to the certification authority is made not by the browser, but by the web server.

Continue reading “Configuring OCSP Stapling”

How to change default-storage-engine in MySQL

When creating a table, the ENGINE option is used, which specifies the storage engine, if this option is not specified in the SQL query, then the default storage engine is used, which is specified in the MySQL server configuration file or when it starts mysqld –default-storage-engine=InnoDB.

Continue reading “How to change default-storage-engine in MySQL”

Configuring Multicast on Eltex MES2324B

Once I needed to receive Multicast traffic from different TV providers and from different VLANs, so I had to use access-list in order to correctly transmit the igmp-report from the client to the required VLAN. If Multicast is in only one VLAN, then you can do without access-list.

Continue reading “Configuring Multicast on Eltex MES2324B”

Solution for warning Asked to transmit frame type ulaw, while native formats is (g729) read/write = ulaw/ulaw

Once a user made a call and Asterisk began to display a lot of warnings, and there was also no sound:

Continue reading “Solution for warning Asked to transmit frame type ulaw, while native formats is (g729) read/write = ulaw/ulaw”

Changing innodb_flush_log_at_trx_commit in MySQL

Default value is 1, possible values are 0-2.

0 – Logs are written and flushed to disk once per second. Transactions that have not been flushed out can be lost as a result of a crash.
1 – Logs are written and flushed to disk every time a transaction is committed.
2 – Logs are written after each commit of a transaction and flushed to disk once per second. Transactions that have not been flushed out can be lost in the event of a failure.

Continue reading “Changing innodb_flush_log_at_trx_commit in MySQL”