Zabbix 5.2 and 5.4 tables #30
Conversation
The previous code enumerates lists both listening and connected sockets. The output of listening (-l) is enough for the intended purpose. Optimizing this. Further on, it matches on the first socket which in my case was mysqlx.sock which leads later to a protocol error. More specific search string resolves this. As on this situation: # netstat -axn | grep mysql unix 2 [ ACC ] STREAM LISTENING 1934165 /var/run/mysqld/mysqlx.sock unix 2 [ ACC ] STREAM LISTENING 1934169 /var/run/mysqld/mysqld.sock unix 3 [ ] STREAM CONNECTED 1934197 /var/run/mysqld/mysqld.sock [...] we had # netstat -axn | grep -m1 mysq unix 2 [ ACC ] STREAM LISTENING 1934165 /var/run/mysqld/mysqlx.sock and error ERROR 2007 (HY000): Protocol mismatch; server version = 11, client version = 10 After the fix it finds the right socket: # netstat -lxn | grep -m1 mysqld.sock unix 2 [ ACC ] STREAM LISTENING 1934169 /var/run/mysqld/mysqld.sock
release 0.9.4
as described in maxhq#23 (comment)
5.2 tables
|
@ironbishop @stephankn item_rtdata with schemaonly flag will give you broken installation. This table is only populated with database upgrade or from scratch. Server is not able to recover it after backup restore. Does anyone tested this tool before using on production environments, i'v already met several times users with installation broken and all of them pointed to this repo. Owner of this repo ignores emails, pull requests. |
This is absolutely correct. Owner of this repo is very sorry for letting people down, esp. if there are users with broken installations after backup file recovery. I thought I would find some time again to look after It seems that @ironbishop is the most active contributor. IMHO the best solution to recover from this unfortunate situation is:
@ironbishop would you be fine with taking over? |
|
Thank you for reply. Would be good to off this repo and move project to the active contributor. |
|
yes i'm ok with that |
actually this includes #23 too