Document editor error after migrating db to another server

Issues during installation and related to database
Post Reply
phobos79
Posts: 2
Joined: Thu Oct 03, 2019 1:46 pm

Document editor error after migrating db to another server

Post by phobos79 » Thu Oct 03, 2019 1:57 pm

Hello,

i'm testing the suite in the company, i've succesfully installed (on VM) both docker than standard linux version (that i prefere), and all is ok

now, due to design, i've decided to move db from onlyoffice machine to a more powerful phisical machine that run mariadb on wich reside all other databases.

as found on support, i've edited the web.connections.config files, and changed the line to this:

<add name="default" connectionString="Server=10.15.4.7;Database=onlyoffice;User ID=onlyoffice;Password=xxxxxxx

dumped the db via mysqldump and reimported via phpmyadmin on the destination server
disable mysql on onlyoffice and after restart all work 100% fine, but only DOCUMENT EDITOR had problem

the CREATE button is grayed out and for each "click" popup an error message, that i cannot find everywhere in the system logs (no errors)
screen.jpg
screen.jpg (43.89 KiB) Viewed 90 times
having the db on another server is mission critical, i hope to get some lucky suggestion here ^__^

Carl
Posts: 200
Joined: Thu Apr 12, 2018 10:00 am

Re: Document editor error after migrating db to another server

Post by Carl » Thu Oct 10, 2019 1:38 pm

Hello,

MySQL version 5.7.26 is a strict requirement, MariaDB is not supported.

phobos79
Posts: 2
Joined: Thu Oct 03, 2019 1:46 pm

Re: Document editor error after migrating db to another server

Post by phobos79 » Fri Oct 11, 2019 1:08 pm

Hello,

i've solved, if someone want to test in a "modular" VM environment this is how

VM1 Database backend = MariaDB 10.1.41 , Postgresql 11

VM2 Document Server = (installed with linux instruction, no docker)

VM3 Community Server = (installed with linux instruction, no docker)

To migrate the databases to the separate server

Document Server VM2: dump db with pg_dump, create a DB on VM1 (use official instruction) and restore on it.
Alter configuration files: /etc/onlyoffice/documentserver/local.json, where you find services CoAuthoring change parameters to your separate db server "services": {
"CoAuthoring": {
"sql": {
"dbHost": "your ip address of VM1",
"dbName": "onlyoffice",
"dbUser": "onlyoffice",
"dbPass": "onlyoffice"

Alter configuration file: /etc/onlyoffice/documentserver/default.json, where you fine sql change parameters to your separate db server

"sql": { "type": "postgres",
"tableChanges": "doc_changes",
"tableResult": "task_result",
"dbHost": "your ip address of VM1",
"dbPort": 5432,
"dbName": "onlyoffice",
"dbUser": "onlyoffice",
"dbPass": "onlyoffice",
"charset": "utf8",
"connectionlimit": 10,
"max_allowed_packet": 1048575
},


Community Server VM3 dump db with mysql_dump, create a DB on VM1 (use official instruction) and restore on it.
Alter configuration file /var/www/onlyoffice/WebStudio/web.connections.config, find and replace server address
<connectionStrings>
<clear />
<add name="default" connectionString="Server=you DB VM1 ip address ;



Now reboot all and you have a modular installation of onlyoffice suite.

Post Reply