Ad Widget

Collapse

Обновление с 2.4.8 до 3.2.1

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • zverek06
    Member
    • Oct 2016
    • 51
    #1

    Обновление с 2.4.8 до 3.2.1

    Добрый день!
    При обновлении происходит ошибка, не пойму что с ней делать
    База MySQL
    ОС: FreeBSD 10.3

    Code:
     1306:20170128:104909.515 completed 70% of database upgrade
  1306:20170128:104909.963 completed 71% of database upgrade
  1306:20170128:104910.233 completed 72% of database upgrade
  1306:20170128:104910.234 Action "Report problems to Zabbix administrators" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.235 Action "Отправка в OTRS" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.236 Action "(Белгород) Мало места на SRV-Belgorod-%" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.236 Action "(КУРСК) Высокая температура в серверной" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.237 Action "(КУРСК) Идет ВКС" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.237 Action "(КУРСК) Дверь в серверную была открыта" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.237 Action "(КУРСК) Мало места на srv-term01 (%)" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.238 Action "(КУРСК) Низкий процент записи на видео сервере!!!" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.238 Action "(КУРСК) Пропало входящие напряжение на UPS в серверной" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.238 Action "(КУРСК) Мало места на srv-sql01 (%)" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.239 Action "(КУРСК) Недоступен GW PTF" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.239 Action "(КУРСК) Упала UC на видео серверах" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.239 Action "(КУРСК) Недоступен polycom" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.239 Action "(КУРСК) Нет доступа к сайту sysadminu.hol.es" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.240 Action "(КУРСК) Пропало входящие напряжение на UPS (площадки)" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104910.240 Action "(КУРСК) Видео сервер был перезагружен" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
  1306:20170128:104912.918 completed 73% of database upgrade
  1306:20170128:104916.682 completed 74% of database upgrade
  1306:20170128:104919.780 completed 75% of database upgrade
  1306:20170128:104922.730 completed 76% of database upgrade
  1306:20170128:104927.661 slow query: 4.120255 sec, "alter table problem add constraint c_problem_2 foreign key (r_eventid) references events (eventid) on delete cascade"
  1306:20170128:104927.662 completed 77% of database upgrade
  1306:20170128:104927.908 completed 78% of database upgrade
  1306:20170128:104928.250 completed 79% of database upgrade
  1306:20170128:104928.264 completed 80% of database upgrade
  1306:20170128:104930.367 completed 81% of database upgrade
  1306:20170128:111150.763 slow query: 1340.393758 sec, "alter table event_recovery add c_eventid bigint unsigned"
  1306:20170128:111357.831 [Z3005] query failed: [1034] Incorrect key file for table 'event_recovery'; try to repair it [alter table event_recovery add correlationid bigint unsigned]
  1306:20170128:111357.831 slow query: 127.044083 sec, "alter table event_recovery add correlationid bigint unsigned"
  1306:20170128:111357.832 database upgrade failed
    MySQL:
    Code:
    2017-01-28 11:13:57 9393bc8002017-01-28 11:13:57 1074 [ERROR] InnoDB: Failure of system call pwrite(). Operating system error number is 28.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
    Code:
    # df -h
Filesystem    Size    Used   Avail Capacity  Mounted on
/dev/da0p2    480G    313G    129G    71%    /
devfs         1.0K    1.0K      0B   100%    /dev
tmpfs         6.0G    4.0K    6.0G     0%    /var/db/mysql/tmptable


    Места где не хватило? У него есть на HDD место еще... и много
    81% и все....
    Или нельзя обновляться на 3.2 сразу? Только через 3.0? Или я чего то не догоняю??? Помогите пожалуйста... Ооочень надо...
    Last edited by zverek06; 28-01-2017, 11:00.
    Tags: None
    • zverek06
      Member
      • Oct 2016
      • 51
      #2
      cat my.cnf
      [mysqld]
      character-set-server = utf8
      collation-server = utf8_unicode_ci
      skip-character-set-client-handshake
      init_connect='SET collation_connection = utf8_unicode_ci'
      init_connect='SET NAMES utf8'

      log_error = /var/db/mysql/mysql-error.log

      innodb_buffer_pool_size = 6G
      innodb_flush_log_at_trx_commit = 2
      innodb_log_buffer_size = 8M
      innodb_log_file_size = 128M
      tmpdir=/var/db/mysql/tmptable
      max_connections = 300

        Comment

        • zverek06
          Member
          • Oct 2016
          • 51
          #3
          Отвечу сам себе
          Раздел tmpfs увеличил и добавил ОЗУ и все поехало отлично!

            Comment

            • SolarW
              Member
              • Feb 2011
              • 41
              #4
              Originally posted by zverek06
              Отвечу сам себе
              Раздел tmpfs увеличил и добавил ОЗУ и все поехало отлично!
              Т.е. он у вас во временном каталоге пытался создать копию базы при конвертации и ему там для этого места не хватало?

                Comment

                • zverek06
                  Member
                  • Oct 2016
                  • 51
                  #5
                  Originally posted by SolarW
                  Т.е. он у вас во временном каталоге пытался создать копию базы при конвертации и ему там для этого места не хватало?
                  Да не, копию наврятли.
                  Он упирался в те 6 ГБ, поднял до 10, он больше 7 не брал себе от туда, хотя база весит 320ГБ
                  Потом он начал упираться в оперативку + swap (12/4)
                  Пришлось добавить памяти. В итоге дали 64ГБ памяти ему, он при обновлении съел ее до "потолка", но обновился

                    Comment

                    Previous template Next
                    Working...