Meet ONLYOFFICE Docs Cloud, complete office software as a service
Meet ONLYOFFICE Docs Cloud

Debian Groups Install fails on CLEAN install of Ubuntu20.04

I have a clean install of Ubuntu 20.04, SELINUX not running.
I follow the instructions here using steps 1 and 2.

https://helpcenter.onlyoffice.com/installation/groups-install-ubuntu.aspx

The install fails while MYSQL is being accessed to configure the communityserver

mysql error log attached and screen shot of failure point during the install.

Its connected to this issue with how Onlyoffice is using MYSQL

Help appreciated.

----------------- MYSQL e2022-04-28T18:19:59.253089Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.29) initializing of server in progress as process 15469
2022-04-28T18:19:59.335117Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-28T18:20:14.286200Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-28T18:20:44.312610Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2022-04-28T18:21:58.243675Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 15519
2022-04-28T18:21:58.326972Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-28T18:21:59.510962Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-28T18:22:01.244116Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-04-28T18:22:01.244178Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-04-28T18:22:01.463923Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location ‘/tmp’ in the path is accessible to all OS users. Consider choosing a different directory.
2022-04-28T18:22:01.714101Z 7 [System] [MY-013172] [Server] Received SHUTDOWN from user boot. Shutting down mysqld (Version: 8.0.29).
2022-04-28T18:22:01.715566Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: ‘::’ port: 33060, socket: /var/run/mysqld/mysqlx.sock
2022-04-28T18:22:06.478775Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.29) MySQL Community Server - GPL.
2022-04-28T18:22:08.565311Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 15715
2022-04-28T18:22:08.702048Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-28T18:22:09.890993Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-28T18:22:10.878308Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-04-28T18:22:10.878367Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-04-28T18:22:10.912868Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: ‘::’ port: 33060, socket: /var/run/mysqld/mysqlx.sock
2022-04-28T18:22:10.912930Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: ‘8.0.29’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server - GPL.
2022-04-28T18:41:57.387998Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutting down mysqld (Version: 8.0.29).
2022-04-28T18:41:58.600561Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.29) MySQL Community Server - GPL.
2022-04-28T18:41:59.132404Z 0 [Warning] [MY-010918] [Server] ‘default_authentication_plugin’ is deprecated and will be removed in a future release. Please use authentication_policy instead.
2022-04-28T18:41:59.132437Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 30318
2022-04-28T18:41:59.134243Z 0 [Warning] [MY-013242] [Server] --character-set-server: ‘utf8’ is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2022-04-28T18:41:59.134256Z 0 [Warning] [MY-013244] [Server] --collation-server: ‘utf8_general_ci’ is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2022-04-28T18:41:59.144999Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-28T18:42:00.705767Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-28T18:42:01.685448Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-04-28T18:42:01.685508Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-04-28T18:42:01.721191Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: ‘::’ port: 33060, socket: /var/run/mysqld/mysqlx.sock
2022-04-28T18:42:01.721233Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: ‘8.0.29’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server - GPL.
2022-04-28T18:45:34.085614Z 10 [ERROR] [MY-011825] [InnoDB] Cannot add field introduction in table onlyoffice.mail_mail because after adding it, the row size is 8607 which is greater than maximum allowed size (8126) for a record on index leaf page

Hello Ivan,
Please run these commands on this server and send me the output:

apt list --installed | grep mariadb
apt list --installed | grep mysql

isb@onlyoffice:~$ apt list --installed | grep -i maria

isb@onlyoffice:~$ apt list --installed | grep -i mysql

mysql-apt-config/unknown,now 0.8.22-1 all [installed]
mysql-client/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed]
mysql-common/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed,automatic]
mysql-community-client-core/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed,automatic]
mysql-community-client-plugins/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed,automatic]
mysql-community-client/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed,automatic]
mysql-community-server-core/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed,automatic]
mysql-community-server/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed,automatic]
mysql-server/unknown,now 8.0.29-1ubuntu20.04 amd64 [installed]

Thanks Carl.

Heres the output

I found this reference too.

Some MySQL queries create internal temporary tables to hold partial results.

As of MySQL 5.7.6, the default storage engine for internal temporary tables is InnoDB, which has a pretty small limit on row size, as you can see (though BLOB/TEXT columns can go beyond that limit).

You can go back to the old pre-5.7 default storage engine for internal temporary tables:

 internal_tmp_disk_storage_engine=MyISAM

This is the workaround mentioned in this bug: “Bug #77398 row size too large in mysql 5.7 query

Hello Ivan,

Sorry for the delayed reply.

It seems the issue is caused by the version 8.0.29 of MySQL. With the version 8.0.28 installation goes correctly. Please try this to avoid the issue:

  1. Remove all installed ONLYOFFICE components and MySQL.
  2. Download the scripts
    wget https://download.onlyoffice.com/install/install-Debian.sh
    wget https://download.onlyoffice.com/install/install-Debian/install-preq.sh
  3. Open the install-preq.sh script => find this section
# install
apt-get install -o DPkg::options::="--force-confnew" -yq wget \
        cron \
        rsyslog \
        ruby-dev \
        ruby-god \
        mono-complete=$mono_complete_version \
        ca-certificates-mono \
        mono-webserver-hyperfastcgi=$hyperfastcgi_version \
        nodejs=$node_version \
        mysql-server \
        mysql-client \

and add the version number to mysql-server and mysql-client:

mysql-server=8.0.28 \
mysql-client=8.0.28 \
  1. Save the script.
  2. Run the installation script bash install-Debian.sh

Let me know the results.

Hello Carl, the .28 version is NOT the latest at Oracle (mysql) so when you use the repo’s you configure it can only find 8.0.29
This means you get a “not found version” error when you simply try and define 8.0.28 as suggested

Can you either

[1] fix the code so its in step with the MYSQL release 8.0.29 and later
or

[2] freeze the mysqlDB to 8.0.28 for now and install and configure it manually in insatll-preq
using a build pulled from MySQL :: Download MySQL Community Server (Archived Versions)

The fix will be released with Community Server v12.0 (1-2 weeks).

Thanks Carl I tried really hard to modify the repo to swallow “28” but didnt succeed :frowning:

REALLY appreciate your help

mysql-server=8.0.28
It doesn’t help. Should I wait for mysql version?
Or can you create a new SQL for me?
no matter what to do.

As I was working on the DB,
The mail_mail table is strange.
ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPACT;
It is expected that an error is probably caught in this part, is there any part that can be fixed and run?

Hello @freeit
Please provide us with details (screenshots, step-by-step scenario). Do I understand you right that you are trying to install Workspace\Groups on clean OS and you are facing the same issue as topic starter?

Hello @freeit and @ivan,

Community Server 12.0 is released. Please run the installation script with update parameter and check if the issue persists:

bash workspace-install.sh -u true

Hi Carl, the install was PERFECT. No issues at all.

Congrats to the entire OO dev team. Nice job getting to .NET6 too.

ONE question :wink: How do I install the documenyt server :slight_smile: now?

Connecting ONLYOFFICE Docs to ONLYOFFICE Groups - ONLYOFFICE ?

Hi Ivan,
Glad to know the installation went smoothly this time. Could you specify how you executed the installation script? Workspace script should install both Groups and Docs on one server.

wget https://download.onlyoffice.com/install/workspace-install.sh

bash workspace-install.sh
use Debian not DOCKER.

IT all works PERFECTLY BUT…

THERE is A REPO ISSUE.

It wll be impossoble for people to run

apt-get update followed by apt-get upgrade because of the MONO sources entry

https://www.mono-project.com/docs/getting-started/install/linux/

Are OO locking the versions of Elasticsearch and Mono in the repo files you distribute to stop those packages creeping away from validated / supported versions?

Hi, any guidance on the ubuntu.debian repo question?
apt-get update
Hit:1 https://artifacts.elastic.co/packages/7.x/apt stable InRelease
Hit:2 http://download.onlyoffice.com/repo/debian squeeze InRelease
Hit:3 Index of /ubuntu/20.04/prod/ focal InRelease
Hit:4 Index of /232905/apt/ubuntu focal InRelease
Hit:5 Index of /node_12.x/ focal InRelease
Hit:6 Index of /repo/ubuntu stable-focal/snapshots/6.8.0.123 InRelease
Hit:7 Index of /chris-lea/redis-server/ubuntu focal InRelease
Hit:8 https://d2nlctn12v279m.cloudfront.net/repo/mono/ubuntu focal InRelease
Hit:9 Index of /packages/ubuntu/ focal InRelease
Hit:10 Index of /ubuntu focal InRelease
Get:11 Index of /ubuntu focal-updates InRelease [114 kB]
Get:12 Index of /ubuntu focal-backports InRelease [108 kB]
Get:13 Index of /ubuntu focal-security InRelease [114 kB]
Fetched 336 kB in 3s (130 kB/s)
Reading package lists… Done
W: Conflicting distribution: Index of /repo/ubuntu stable-focal/snapshots/6.8.0.123 InRelease (expected stable-focal/snapshots/6.8.0.123 but got focal)
root@onlyoffice:~# apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages have been kept back:
elasticsearch fwupd
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Hi @ivan,
Please accept my apologies for the delayed reply.
You can ignore this warning, it won’t affect updating other packages in the system.