а самая первая версия была на чём написана?

короче база падает вот логи. 170430 16:13:42 [ERROR] mysqld: Out of memory (Needed 6045600 bytes) 170430 16:13:42 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spac 170430 16:13:42 [ERROR] mysqld got signal 11 ; ну тут все понятно. памяти мало. но, есть 2 сервак. с полностью аналогичными версиями марии и концигами. и там тоже вот такая ошибка [ERROR] mysqld got signal 11 ; 170615 10:29:00 InnoDB: Completed initialization of buffer pool 170615 10:29:00 InnoDB: highest supported file format is Barracuda. 170615 10:29:01 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 170615 10:29:01 InnoDB: Error: trying to open a table, but could not InnoDB: open the tablespace file './host_474283_azyk/wz0yt_content.ibd'! InnoDB: Have you moved InnoDB .ibd files around without using the InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? InnoDB: It is also possible that this is a temporary table #sql..., InnoDB: and MySQL removed the .ibd file for this. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html InnoDB: for how to resolve the issue. 170615 10:29:01 InnoDB: Waiting for the background threads to start 170615 10:29:02 Percona XtraDB (http://www.percona.com) 5.5.52-MariaDB-38.3 started; log sequence number 395626559838 170615 10:29:02 [Note] Plugin 'FEEDBACK' is disabled. 170615 10:29:02 [Note] Server socket created on IP: '127.0.0.1'. 170615 10:29:02 [Note] Event Scheduler: Loaded 0 events 170615 10:29:02 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.53-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 170615 10:29:02 [Note] Event Scheduler: scheduler thread started with id 1 170615 10:31:09 [ERROR] mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see http://kb.askmonty.org/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 5.5.53-MariaDB key_buffer_size=67108864 read_buffer_size=2097152 max_used_connections=7 max_threads=258 thread_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1126889 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7f645f211000 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x7f650b56fd60 thread_stack 0x48000 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xa7833b] /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6d2b58] /lib64/libpthread.so.0(+0xf7e0)[0x7f650b2377e0] /usr/sbin/mysqld[0x945288] /usr/sbin/mysqld[0x88bf3e] /usr/sbin/mysqld[0x8c44f2] /usr/sbin/mysqld[0x8c6242] /usr/sbin/mysqld[0x8176b8] /usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x3e)[0x6d687e] /usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x6d8)[0x633998] /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x7ac)[0x56170c] /usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x5a5)[0x5623d5] /usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x44)[0x563044] /usr/sbin/mysqld[0x598418] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x34ac)[0x5a1b9c] /usr/sbin/mysqld[0x5a4474] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1bf8)[0x5a6948

Чо это за херня?

@ignatenkobrain мне iptables оставить или вернуть на firewalld?

давай сначала

iptables-save

firewall-cmd --permanent --direct --add-rule ipv4 nat PREROUTING 0 -p tcp -m tcp --dport 8080 -j REDIRECT --to-ports 80

А каким софтом можно более-менее в графике зашифровать отдельный диск LUKS? Хочу угробить все данные и зашифровать его.

firewall-cmd --permanent --direct --add-rule ipv4 nat PREROUTING 0 -p tcp -m tcp --dport 8080 -j REDIRECT --to-ports 80

firewall-cmd —permanent —direct —add-rule ipv4 nat PREROUTING 0 -p tcp -m tcp —dport 80 -j REDIRECT —to-ports 8080 ?

Сноси KDE. Есть сосноль.

а маскарад включить?

Я так и сделал. i3 называется

Только вот это одно правило (точнее 4)

Я так и сделал. i3 называется

4?

Используй голый tty. И без всяких tmux. Иначе это не сосноль.

80/443/ipv4/ipv6

#sarcasm

wireshark пустой по портам 8080 и 8443

iptables-save

Ну ты не доверишь. А вот какой-нибудь среднестатистической домохозяйке/хозяину хватит и гуя от GNOME Disks.

Раз-два и работает.

Вполне возможно, что нужен ещё firewall-cmd --reload

не помогло

Давай ещё раз список правил