Ad Widget

Collapse

Начал отваливаться zabbix сервер

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ZhKSteaL
    Junior Member
    • Aug 2015
    • 3

    #1

    Начал отваливаться zabbix сервер

    Добрый день!
    С какого то момента стал отваливаться заббикс.

    Выражается в виде (почему то ссылка на картинку с тегами html не отображается):


    Что удалось увидеть в systemctl status zabbix-server через 3-4 минуты после запуска:
    Code:
    [xxx@yyy]# systemctl status zabbix-server
    ● zabbix-server.service - Zabbix Server
       Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
       Active: active (running) since Чт 2016-02-04 11:17:59 OMST; 3min 46s ago
     Main PID: 1861 (zabbix_server)
       CGroup: /system.slice/zabbix-server.service
               ├─1861 /usr/bin/zabbix_server
               ├─1869 /usr/bin/zabbix_server: configuration syncer [synced configuration in 0.156337 sec, idle 60 sec]
               ├─1870 /usr/bin/zabbix_server: db watchdog [synced alerts config in 0.000931 sec, idle 60 sec]
               ├─1871 /usr/bin/zabbix_server: poller #1 [got 84 values in 2.096773 sec, getting values]
               ├─1872 /usr/bin/zabbix_server: poller #2 [got 84 values in 2.074714 sec, getting values]
               ├─1873 /usr/bin/zabbix_server: poller #3 [got 75 values in 2.011884 sec, getting values]
               ├─1874 /usr/bin/zabbix_server: poller #4 [got 79 values in 2.144245 sec, getting values]
               ├─1875 /usr/bin/zabbix_server: poller #5 [got 88 values in 2.084857 sec, getting values]
               ├─1876 /usr/bin/zabbix_server: unreachable poller #1 [got 0 values in 0.000005 sec, idle 5 sec]
               ├─1877 /usr/bin/zabbix_server: trapper #1 [processed data in 0.000520 sec, waiting for connection]
               ├─1878 /usr/bin/zabbix_server: trapper #2 [processed data in 0.000678 sec, waiting for connection]
               ├─1879 /usr/bin/zabbix_server: trapper #3 [processed data in 0.000471 sec, waiting for connection]
               ├─1880 /usr/bin/zabbix_server: trapper #4 [processed data in 0.068578 sec, waiting for connection]
               ├─1881 /usr/bin/zabbix_server: trapper #5 [processed data in 0.000498 sec, waiting for connection]
               ├─1882 /usr/bin/zabbix_server: icmp pinger #1 [got 0 values in 0.000005 sec, idle 5 sec]
               ├─1883 /usr/bin/zabbix_server: alerter [sent alerts: 0 success, 0 fail in 0.000412 sec, idle 30 sec]
               ├─1884 /usr/bin/zabbix_server: housekeeper [startup idle for 30 minutes]
               ├─1888 /usr/bin/zabbix_server: timer #1 [processed 0 triggers, 0 events in 0.000009 sec, 0 maintenances in 0.000000 sec, idle 30 sec]
               ├─1889 /usr/bin/zabbix_server: http poller #1 [got 0 values in 0.000694 sec, idle 5 sec]
               ├─1890 /usr/bin/zabbix_server: discoverer #1 [processed 0 rules in 0.000531 sec, idle 60 sec]
               ├─1893 /usr/bin/zabbix_server: history syncer #1 [synced 6 items in 0.000188 sec, idle 5 sec]
               ├─1894 /usr/bin/zabbix_server: history syncer #2 [synced 574 items in 0.042572 sec, idle 5 sec]
               ├─1895 /usr/bin/zabbix_server: history syncer #3 [synced 0 items in 0.000001 sec, syncing history]
               ├─1896 /usr/bin/zabbix_server: history syncer #4 [synced 18 items in 0.000216 sec, idle 5 sec]
               ├─1897 /usr/bin/zabbix_server: escalator [processed 0 escalations in 0.000350 sec, idle 3 sec]
               ├─1898 /usr/bin/zabbix_server: proxy poller #1 [exchanged data with 0 proxies in 0.000003 sec, idle 5 sec]
               └─1899 /usr/bin/zabbix_server: self-monitoring [processed data in 0.000006 sec, idle 1 sec]
    
    фев 04 11:17:59 bssonline systemd[1]: Stopped Zabbix Server.
    фев 04 11:17:59 bssonline systemd[1]: Stopping Zabbix Server...
    фев 04 11:17:59 bssonline systemd[1]: Started Zabbix Server.
    [xxx@yyy]# systemctl status zabbix-server
    ● zabbix-server.service - Zabbix Server
       Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
       Active: active (running) since Чт 2016-02-04 11:17:59 OMST; 3min 46s ago
     Main PID: 1861 (zabbix_server)
       CGroup: /system.slice/zabbix-server.service
               └─1861 /usr/bin/zabbix_server
    
    фев 04 11:17:59 bssonline systemd[1]: Stopped Zabbix Server.
    фев 04 11:17:59 bssonline systemd[1]: Stopping Zabbix Server...
    фев 04 11:17:59 bssonline systemd[1]: Started Zabbix Server.
    Т.е. как получены первые данные заббикс отваливается.

    Что есть в логах journalctl:
    Code:
    фев 04 11:17:59 xxx systemd[1]: Stopped Zabbix Server.
    фев 04 11:17:59 xxx systemd[1]: Stopping Zabbix Server...
    фев 04 11:17:59 xxx polkitd[577]: Unregistered Authentication Agent for unix-process:1852:84422741 (system bus name :1.70, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_RU.UTF-8
    фев 04 11:17:59 xxx systemd[1]: Started Zabbix Server.
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f378711a700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f3785cda700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f379b9e9700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f3785cda700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:00 xxx mysqld[242]: 2016-02-04 11:18:00 7f3785c91700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:01 xxx mysqld[242]: 2016-02-04 11:18:01 7f3785dfe700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:25 xxx mysqld[242]: 2016-02-04 11:18:25 7f37830d6700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:18:25 xxx mysqld[242]: 2016-02-04 11:18:25 7f37830d6700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:19:00 xxx mysqld[242]: 2016-02-04 11:19:00 7f3787163700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:19:00 xxx mysqld[242]: 2016-02-04 11:19:00 7f3787163700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:19:00 xxx mysqld[242]: 2016-02-04 11:19:00 7f3787163700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:21:47 xxx mysqld[242]: 2016-02-04 11:21:47 7f3797f23700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type
    фев 04 11:23:59 xxx smbd[308]: [2016/02/04 11:23:59.669782,  0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
    фев 04 11:23:59 xxx smbd[308]:   Unable to open printcap file /etc/printcap for read!
    фев 04 11:37:00 xxx smbd[308]: [2016/02/04 11:37:00.286780,  0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
    фев 04 11:37:00 xxx smbd[308]:   Unable to open printcap file /etc/printcap for read!
    фев 04 11:38:50 xxx sshd[22656]: pam_unix(sshd:session): session closed for user bsscp
    фев 04 11:38:50 xxx systemd-logind[248]: Removed session c19.
    фев 04 11:50:00 xxx smbd[308]: [2016/02/04 11:50:00.960018,  0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
    фев 04 11:50:00 xxx smbd[308]:   Unable to open printcap file /etc/printcap for read!
    фев 04 12:03:01 xxx smbd[308]: [2016/02/04 12:03:01.366644,  0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
    фев 04 12:03:01 xxx smbd[308]:   Unable to open printcap file /etc/printcap for read!
    фев 04 12:16:02 xxx smbd[308]: [2016/02/04 12:16:02.043206,  0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
    фев 04 12:16:02 xxx smbd[308]:   Unable to open printcap file /etc/printcap for read!
    фев 04 12:16:46 xxx sshd[10789]: Accepted password for bsscp from 10.78.42.109 port 60874 ssh2
    фев 04 12:16:46 xxx sshd[10789]: pam_unix(sshd:session): session opened for user bsscp by (uid=0)
    фев 04 12:16:46 xxx systemd-logind[248]: New session c26 of user bsscp.
    Подскажите, куда копать? (
    Last edited by ZhKSteaL; 04-02-2016, 08:19.
  • zmdpc
    Senior Member
    • Oct 2014
    • 484

    #2
    В сторону решения проблем с mysql. Обновляли недавно mysql?

    Comment

    Working...