Infos:
- Used Zammad version: 3.3.0
- Used Zammad installation source: (source, package, …) helm charts
- Operating system: 18.04
- Browser + version: chrome
Expected behavior:
zammad should create http_logs table table and it should create database on mysql
*
Actual behavior:
CREATE TABLE http_logs
(id
int NOT NULL AUTO_INCREMENT PRIMARY KEY, direction
varchar(20) NOT NULL, facility
varchar(100) NOT NULL, method
varchar(100) NOT NULL, url
varchar(255) NOT NULL, status
varchar(20),
→ ip
varchar(50), request
varchar(10000) NOT NULL, response
varchar(10000) NOT NULL, updated_by_id
int, created_by_id
int, created_at
datetime(3) NOT NULL, updated_at
datetime(3) NOT NULL) ENGINE=InnoDB;
ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
Steps to reproduce the behavior:
- installed mysql external
- create zammad image with installed package for mysql and mysql2 adpator
- change mysql2 adaptor in database.yaml
4.installed zammad with disable internal postgressql
5.mysql init container failed with below error.
CREATE TABLE http_logs
(id
int NOT NULL AUTO_INCREMENT PRIMARY KEY, direction
varchar(20) NOT NULL, facility
varchar(100) NOT NULL, method
varchar(100) NOT NULL, url
varchar(255) NOT NULL, status
varchar(20),
→ ip
varchar(50), request
varchar(10000) NOT NULL, response
varchar(10000) NOT NULL, updated_by_id
int, created_by_id
int, created_at
datetime(3) NOT NULL, updated_at
datetime(3) NOT NULL) ENGINE=InnoDB;
ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs