Фёдор Дороднов (Все сообщения пользователя)

Столкнулся сегодня, проблема актуальна.
Делаю следующее Магазин-Настройки-Экспорт данный-Export CSV (new)
Выбираю инфоблок, далее в параметрах отмечаю :

Большое спасибо!
Всё стало устанавливаться.

Если быть более точным при попытке установить любой модуль получаю вот такую ошибку :
Error:Can't cre ate table 'sitemanager0.b_sec_iprule' (errno: -1)!

Система:
Virtual CPU 1600Mhz, 3072Mb memory, 32000Mb disk
centos-6-i386-minimal
Установил «1С-Битрикс: Веб-окружение» - Linux
Установка прошла без ошибок.

А дальше началось:
Пытаюсь установить модуль интернет магазина - получаю ошибку Can't cre ate table ......

Конфиг mysql:

#
# The MySQL database server configuration file.
#
[client]
port = 3306
socket = /var/lib/mysqld/mysqld.sock
default-character-set = utf8
[mysqld_safe]
socket = /var/lib/mysqld/mysqld.sock
nice = 0

[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/lib/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
skip-external-locking
query_cache_size = 32M
table_cache = 4096
thread_cache_size = 32
max_heap_table_size = 32M
tmp_table_size = 32M
innodb_buffer_pool_size = 32M
innodb_flush_log_at_trx_commit = 2
innodb_log_file_size = 64M
innodb_flush_method = O_DIRECT
transaction-isolation = READ-COMMITTED
default-storage-engine = innodb
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 128K
myisam-recover = BACKUP
expire_logs_days = 10
max_binlog_size = 100M
join_buffer_size = 2M
sort_buffer_size = 2M
character-set-server = utf8
collation-server = utf8_unicode_ci
init-connect = "SET NAMES utf8 COLLATE utf8_unicode_ci"
skip-character-set-client-handshake
innodb_file_per_table
[mysqldump]
quick
quote-names
max_allowed_packet = 128M
default-character-set = utf8
[mysql]
[isamchk]
key_buffer = 16M
!includedir /etc/mysql/conf.d/


А вот что показывает в лог ошибок(это самый конец):

130123 12:28:23  InnoDB: Error creating file './sitemanager0/b_sale_person_type_site.ibd'.
130123 12:28:23  InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CRE ATE TABLE? You can
InnoDB: resolve the problem by removing the file './sitemanager0/b_sale_person_type_site.ibd'
InnoDB: under the 'datadir' of MySQL.
130123 12:28:23  InnoDB: Error creating file './sitemanager0/b_sale_discount_group.ibd'.
130123 12:28:23  InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CRE ATE TABLE? You can
InnoDB: resolve the problem by removing the file './sitemanager0/b_sale_discount_group.ibd'
InnoDB: under the 'datadir' of MySQL.
130123 12:28:23  InnoDB: Error creating file './sitemanager0/b_sale_viewed_product.ibd'.
130123 12:28:23  InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CRE ATE TABLE? You can
InnoDB: resolve the problem by removing the file './sitemanager0/b_sale_viewed_product.ibd'
InnoDB: under the 'datadir' of MySQL.

Подскажите в чем проблема? Где, что надо исправлять?
Заранее спасибо!