MySQL INNODB Crash etti. Napicaz?

1- nano /etc/my.cnf

innodb_force_recovery = 2

2den basla 6ya kadar yolu var

GUNCELLEME: Agustos 2018

Be sure to check your MySQL logs, and if it loops with something like:

InnoDB: Waiting for the background threads to start

You should also add innodb_purge_threads=0 to your my.cnf.

So all together to bring back database, I had to add these 3 parameters in my.cnf:

port = 8881
innodb_force_recovery=3
innodb_purge_threads=0

2- killall -9 mysqld

calisan bir mysql processi kalmasin

3- innodb recovery ile calistiktan sonra read only olarak.

herseyi dump et tek buyuk bir dosyaya

cat /usr/local/directadmin/conf/mysql.conf

mysqldump -u da_admin -p --opt --all-databases > alldb.sql

4- /var/lib/mysql altindaki

ibdata1
ib_logfile0
ib_logfile1

sil, veya sen en iyisi tum /mysql dizinini yedekle sonra sil

5- herseyi restore et buyuk dosya yedeginden.

mysql -u da_admin -p < alldb.sql

server.err logu tail le duruma bak

gule gule kullan.

NOT: 2021 mart::

Use the --force (-f) flag on your mysql import. Rather than stopping on the offending statement, MySQL will continue and just log the errors to the console.

For example:

mysql -u userName -p -f -D dbName < script.sql

ek:

aynisi oldu 1 serverda db leri dump ederken 1 table hata veriyordu.

inatla hangi table hangi db icinde onuda bulamadim crash diyip duruyodu

ne yaptim

updatedb

locate crashedentable.frm

frm ler cikinca tek tek hepsini (1den cok vardi ) 12 tane toplam

el ile fix ettim. aslinda otomatik auto-repair calismasi gerekirdi.

calismadi pust nedense ..

mysqlcheck -u da_admin -p --auto-repair --optimize --all-databases

bu yukairdaki otomatik olan hepsini fixleyen. neden calismadiki acep. bilinmez..

ben naptim:

mysqlcheck -u da_admin -p --auto-repair --databases esila_shop eticaret2_shop

bu ise yaradi.

bilgim olsun :)

artik kod modundanda cikalim..

evet/./

Hizmetlerimize gosterdiginiz ilgi icin tesekkur ederiz.
3 farkli hizmet seklimiz bulunmaktadir.
IYI – UCUZ – HIZLI
Yukaridaki Herhangi iki adet hizmet seklini secebilirsiniz.
Ancak Unutmayiniz ki:
IYI ve UCUZ hizmet HIZLI olmayacaktir,
IYI ve HIZLI hizmet UCUZ olmayacaktir,
HIZLI ve UCUZ hizmet IYI olmayacaktir.

1- online.net console gir > makinayi sec > proxmox kur
2- online.net console dan 1 tane failover ip siparis et
3- failover ipi proxmox kurdugun makinaya ata
4- failover ip icin virtual mac olustur – virtual maci kopyala
5- proxmoxuna git su sekilde vm olustur
linux 2.6 KVM
256 MB RAM
1 CPU
Sata Disk 8 GB yeterli
Virtio ethernet > mac adresi kopyaladigin virtual mac > yapistir.
numa secebilirsin
makinada kvm default olsun , host secme boot etmez.
6- proxmox html5 novnc konsol ile makinayi boot et
7- mikrotik tum modulleri sec yukle de
8- mikrotik acildiginda su komutlari calistir

ip address add interface=ether1 address=212.129.22.22 netmask=255.255.255.255 broadcast=212.129.22.22 network=195.154.171.1
ip route add dst-address=0.0.0.0/0 gateway=195.154.171.1

not: 212.129.22.22 > sana verilmis olan virtual mac olusturdugun failover ip
195.154.171.1 > proxmox makinandaki ana ipin gateway ipi

9- su an failover ipine pingleyebiliyor ve winbox ile baglanabiliyor olmalisin.

gule gule kullan.

Heval , [06.12.15 00:34]
shukko masaüstüne linux kuracağım linux mint harici önerebileceğin sistem var mı?

METEHAN, [06.12.15 00:50]
fedora

METEHAN, [06.12.15 00:50]
ezelden fedora cıyız.biz

METEHAN, [06.12.15 00:50]
uyumayın genclık cumartesı uyunurmu

sHuKKo Kazandibi, [06.12.15 00:53]
var

sHuKKo Kazandibi, [06.12.15 00:54]
ama senin evet ben biraz ugrasmak istiyorum diyip dememene bagli

sHuKKo Kazandibi, [06.12.15 00:54]
3 senecek yazacagim sana

sHuKKo Kazandibi, [06.12.15 00:55]
1- linux mint cinnamon – en stabili ve en sorunsuzu budur en klasik olan 17.3 cikti cikicak 1 2 gun icinde ubuntu temellidir yani debian tureveidir apt-get paket yoneticisidir nette %99 sorun cozum bulmak kolay olur

Heval , [06.12.15 00:55]
çıktı indirdim onu shukko bekliyor

Heval , [06.12.15 00:55]
yarın kurayım kurmayayım dan önce

Heval , [06.12.15 00:56]
sorayım bir dedim

sHuKKo Kazandibi, [06.12.15 00:56]
2- linux manjaro xfce edition – bu arch linux temellidir ve rolling releasedir . xfce ile fisek gibi calisir . en sorunsuzu degildir ama cevaplar %99 arch wikisindedir . bunu kurup daha kaldirmazsin. paket yoneticisi pacman dir . pacman -Syu full sistem guncellemesi yapar.

sHuKKo Kazandibi, [06.12.15 00:57]
3- bu son secenk eger ben bleeding edge olacagim ancak eye candy seviyesi en yuksek olsun diyosan kurulacak secenektir. Linux Korora – linux fedora versyonlari takip eder . asagi yukari 6 ayda bir yeni versyon cikar. kernel 4.2 lerdedir en bleeding edge dir. ozellikle KDE versyonunu oneririm. ust seviyede eglence vaat eder. Paket yoneticisi Yum’dan DNF ye gecmistir. DNF gelecegin ileri duzey paket yoneticisidir.

sHuKKo Kazandibi, [06.12.15 00:57]
evet en detayli olarak yazacaklarim bunlar

sHuKKo Kazandibi, [06.12.15 00:58]
3 secenek sebep sonuc

sHuKKo Kazandibi, [06.12.15 00:58]
sen sec kur

yandex botu blokluyoruz bu tur olunca.

bknz: https://www.shukko.com/x3/?s=yandex&submit=Search

baskalarinin yaptigi yorumlar:

Yandex botu ile başımız dertte, URL’de Session ID veya Query String içinde sayfanın görüntüsünü etkilemeyen herşeyi saniyede 3-5 sayfa alacak şekilde tarıyor. Saatlerce aynı sayfanın aynı görüntüsünü tarıyor bunu ayırt edemiyor. Sonuç Load Avarage 20.00+ ve CPU usage hep %50-80 Bunun için bir önerisi olan varmı? Siz bu tür bir sorunla baş etmek için müşteri hesabımı kapatırsınız Yandex IP ‘lerinimi bloklarsınız? Çıkamadım işin içinden

Harun – yandex mail ve metrika hariç ne kadar ip varsa blokladım loadlarda düşüş inanılmaz

buda bizim haricimizde webmasterin yapabilecegi:

https://yandex.com.tr/support/webmaster/controlling-robot/robots-txt.xml#crawl-delay


[root@xxxx admin_backups]# w
03:56:10 up 611 days, 11:27, 1 user, load average: 0,66, 0,19, 0,06
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 x.x.x.x 03:50 0.00s 0.04s 0.00s w

model name : Intel(R) Celeron(R) CPU G1610 @ 2.60GHz


Crucial m4 CT128M4SSD2 128GB // 8GB RAM

I use Iodine, it’s super simple to set up! Say your VPS’s IP is 8.8.8.8, you set DNS as follows:

dns2.domain.com A 8.8.8.8
dns.domain.com NS dns2.domain.com

apt-get install iodine, or compile on other systems

On server run: screen iodined -fP ultrasecurepassword 10.0.0.1 dns.domain.com
On client run: iodine -fP ultrasecurepassword 8.8.8.8 dns.domain.com

You can then setup Squid or ziproxy with image compression to listen on tun0, and set the HTTP proxy for your client to 10.0.0.1. SSH tunneling with compression also works, not tried NAT

http://code.kryo.se/iodine/

iodine lets you tunnel IPv4 data through a DNS server. This can be usable in different situations where internet access is firewalled, but DNS queries are allowed.

$ apt-get install weechat 🙂

https://weechat.org/files/doc/devel/weechat_quickstart.en.html

1. Start WeeChat

A recommended terminal emulator for X (but not mandatory) is rxvt-unicode (it has good UTF-8 support, and no problem with default keyboard bindings).

Run from your shell:

$ weechat

2. Online help / options

WeeChat has help for all commands, just issue:

/help

To get help on a specific command, issue:

/help command

To set options, issue:

/set config.section.option value

(where config is configuration name (weechat for core, or a plugin name), section the section of this configuration and option the option name).

WeeChat immediately uses the new value (you never need to restart WeeChat after changes to configuration).

You can use /set option with partial name and wildcard “*” at the beginning or end to display all options containing letters. For example:

display all options (WeeChat and plugins):

/set

display WeeChat options:

/set weechat.*

display IRC plugin options:

/set irc.*

You can display help for an option with /help, for example:

/help weechat.look.highlight

All settings are saved when WeeChat ends (or with /save command to force a write of the options).

You can edit configuration files (*.conf) by hand and reload them by /reload command if you don’t want to use /set command.
3. Core vs plugins

WeeChat “core” is only used to display data on screen and interact with the user, that means weechat core without plugins is useless (faithful users: IRC was part of core for versions ≤ 0.2.6).

All network protocols like IRC are provided in separate plugins.

Use the /plugin command to list loaded plugins, you should see “irc” and other plugins in the list.
4. Add an IRC server

You can add an IRC server with /server command, for example:

/server add freenode chat.freenode.net

As usual, help is available if you’re lost:

/help server

5. Set custom IRC server options

WeeChat uses default values for all servers (“fall backs”), if you don’t specify a specific value for a server option. These default options are “irc.server_default.*”.

For each server option, WeeChat uses its value if it is defined (not “null”). Otherwise WeeChat uses default value (“irc.server_default.xxx”).

For example there’s default nicks (based on your un*x login), and you can override them for freenode server with following command:

/set irc.server.freenode.nicks “mynick,mynick2,mynick3,mynick4,mynick5”

To set username and realname:

/set irc.server.freenode.username “My user name”
/set irc.server.freenode.realname “My real name”

To enable auto-connect to server at startup:

/set irc.server.freenode.autoconnect on

To connect with SSL:

/set irc.server.freenode.addresses “chat.freenode.net/7000”
/set irc.server.freenode.ssl on

If SASL is available on server, you can use it for authentication (you will be identified before you join channels):

/set irc.server.freenode.sasl_username “mynick”
/set irc.server.freenode.sasl_password “xxxxxxx”

To run a command after connection to server, for example to authenticate with nickserv (only if you don’t use SASL for authentication):

/set irc.server.freenode.command “/msg nickserv identify xxxxxxx”

Note
Many commands in option command can be separated by ; (semi-colon).

To auto-join some channels when connecting to server:

/set irc.server.freenode.autojoin “#channel1,#channel2”

To remove a value of a server option, and use the default value instead, for example to use default nicks (irc.server_default.nicks):

/set irc.server.freenode.nicks null

Other options: you can setup other options with following command (“xxx” is option name):

/set irc.server.freenode.xxx value

6. Connect to IRC server and auto-join channels

/connect freenode

Note
This command can be used to create and connect to a new server without using /server command (should I repeat you can see help for this command with /help connect ?).

By default, server buffers are merged with WeeChat core buffer. To switch between core buffer and server buffers, you can use ctrl+x.

It is possible to disable auto merge of server buffers to have independent server buffers:

/set irc.look.server_buffer independent

7. Join/part IRC channels

Join a channel:

/join #channel

Part a channel (keeping buffer open):

/part [quit message]

Close server or channel buffer (/close is an alias for /buffer close):

/close

8. IRC private messages

Open a buffer and send a message to another user (nick foo):

/query foo this is a message

Close the private buffer:

/close

9. Buffer/window management

A buffer is a component linked to a plugin with a number, a category, and a name. A buffer contains the data displayed on the screen.

A window is a view on a buffer. By default there’s only one window displaying one buffer. If you split screen, you will see many windows with many buffers at same time.

Commands to manage buffers and windows:

/buffer
/window

(I’ll not repeat here that you can get help with /help on these commands)

For example, to vertically split your screen into a small window (1/3 width), and a large window (2/3), use command:

/window splitv 33

10. Key bindings

WeeChat uses many keys by default. All these keys are in the documentation, but you should know at least some vital keys:

alt+←/→ or F5/F6: switch to previous/next buffer

F7/F8: switch to previous/next window (when screen is split)

F9/F10: scroll title bar

F11/F12: scroll nicklist

Tab: complete text in input bar, like in your shell

PgUp/PgDn: scroll text in current buffer

alt+a: jump to buffer with activity (in hotlist)

According to your keyboard and/or your needs, you can rebind any key to a command with /key command. A useful key is alt+k to find key codes.

For example, to bind alt+y to command /buffer close:

/key bind (press alt-k) (press alt-y) /buffer close

You’ll have a command line like:

/key bind meta-y /buffer close

To remove key:

/key unbind meta-y

11. Plugins/scripts

On some distros like Debian, plugins are available via a separate package (like weechat-plugins). Plugins are automatically loaded when found (please look at the WeeChat documentation to load/unload plugins or scripts).

Many external scripts (from contributors) are available for WeeChat, you can download and install scripts from the repository with the /script command, for example:

/script install iset.pl

See /help script for more info.

A list of scripts is available in WeeChat with /script or at this URL: https://weechat.org/scripts
12. More documentation

You can now use WeeChat and read FAQ/documentation for any other questions: https://weechat.org/doc

Enjoy using WeeChat!
Version 1.4-dev
Last updated 2015-06-10 23:21:25 CEST