Howto install Onlyoffice document server as Nextcloud app

dnutan · April 7, 2018, 11:03pm

Update from onlyoffice-documentserver 5.1.0 to 5.1.1 with the new nethserver-onlyoffice package works.
The new nethserver-onlyoffice package has the same version number as the latter (forced installation with yum reinstall).

Details

---> Package onlyoffice-documentserver.x86_64 0:5.1.0-115 will be updated
---> Package onlyoffice-documentserver.x86_64 0:5.1.1-23 will be an update

Failed to start The Apache HTTP Server (port conflict due to documentserver update changing nginx conf files?: fixed later by nethserver-onlyoffice)

Apr  8 00:07:29 server httpd: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Apr  8 00:07:29 server httpd: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Apr  8 00:07:29 server httpd: no listening sockets available, shutting down
Apr  8 00:07:29 server httpd: AH00015: Unable to open logs
Apr  8 00:07:29 server systemd: httpd.service: main process exited, code=exited, status=1/FAILURE
Apr  8 00:07:29 server kill: kill: cannot find process ""
Apr  8 00:07:29 server systemd: httpd.service: control process exited, code=exited status=1
Apr  8 00:07:29 server systemd: Failed to start The Apache HTTP Server.
Apr  8 00:07:29 server systemd: Unit httpd.service entered failed state.
Apr  8 00:07:29 server systemd: httpd.service failed.

yum reinstall https://smart-ict.services/mirror/devtest/nethserver-onlyoffice-0.0.1-3.ns7.noarch.rpm
---> Package nethserver-onlyoffice.noarch 0:0.0.1-3.ns7 will be reinstalled

nethserver-onlyoffice (/var/log/messages)

Apr  8 00:21:38 server esmith::event[2604]: expanding /#
Apr  8 00:21:38 server esmith::event[2604]: ERROR: No templates were found for /#.
Apr  8 00:21:38 server esmith::event[2604]: at /etc/e-smith/events/actions/generic_template_expand line 64.
Apr  8 00:21:38 server esmith::event[2604]: [WARNING] expansion of /# failed
Apr  8 00:21:38 server esmith::event[2604]: expanding /etc/nginx/conf.d/onlyoffice-documentserver.conf
Apr  8 00:21:38 server esmith::event[2604]: expanding /etc/onlyoffice/documentserver/default.json
Apr  8 00:21:38 server esmith::event[2604]: ERROR: No templates were found for /etc/onlyoffice/documentserver/default.json.
Apr  8 00:21:38 server esmith::event[2604]: at /etc/e-smith/events/actions/generic_template_expand line 64.
Apr  8 00:21:38 server esmith::event[2604]: [WARNING] expansion of /etc/onlyoffice/documentserver/default.json failed

Apr  8 00:22:02 server esmith::event[2604]: Event: nethserver-onlyoffice-update FAILED

Clean install went ok.
Update from 5.0.7 to 5.1.1 had the same problems as reported earlier, but worked after reinstall of onlyoffice-documentserver and issuing signal-event nethserver-onlyoffice-update

mrmarkuz · April 8, 2018, 10:51am

Thanks for testing!

I really have to improve my versioning system for testing

Yes but I don’t see a way for solving it except maybe repack the documentserver in some way.

This is strange because these errors were fixed and do not occur on a fresh install. They were because of a wrong comment interpreted as template and /etc/onlyoffice/documentserver/default.json was templated in the old version. Maybe it’s just because of the reinstall.

dnutan · April 8, 2018, 11:38am

You’re right, doesn’t happen on a clean install.

Don’t know which is the best option (the one with lesser hassle for both you, as maintainer, and users). stephdl or dev_team might be able to give some advice.
Hosting the package on your repo you’ll have more control on updates and possible troubles at the cost of extra bandwidth usage. Using nethserver-onlyoffice to download external package (i.e. as some flash player packages did IIRC) you have control on the order of installation and signaling events without affecting your bandwidth, but don’t know if it’s considered a good practice or accepted by the terms of use of external package.

mrmarkuz · April 9, 2018, 12:04am

I found out that an update from nethserver-onlyoffice 0.0.1-2 to 0.0.1-3 only works with documentserver 5.0.7 because of the templated /etc/onlyoffice/documentserver/default.json which only fits to the old version. I try to find a solution but if it’s too much effort I’d release a “hard” update, where one has to manually reinstall the documentserver. Future updates will work smoothly as default.json is not templated anymore.

This is a good option. This way we can test new docserver rpms with direct install and if they work we update the repo.

For the future repackaging or integrating like you described are the way to go but I have to learn first…

mrmarkuz · April 11, 2018, 1:49pm

Released the update to fix future documentserver update problems.

alefattorini · April 26, 2018, 3:25pm

47 posts were split to a new topic: Get onlyoffice to work with nextcloud

hector · April 26, 2018, 7:30pm

Ok mrmarkuz it’s working thank for de port 8082 I put it and is working now.

oneitonitram · July 7, 2018, 2:04pm

is this the better method of installing than

mrmarkuz:

We start with installing packages and preparing postgres:

# install packages
yum -y install nethserver-nextcloud nethserver-postgresql nethserver-redis rabbitmq-server nano

# customize postgres pg_hba.conf
mkdir -p /etc/e-smith/templates-custom/var/lib/pgsql/data/pg_hba.conf
echo -e "host all all 127.0.0.1/32 trust\nhost all all ::1/128 trust" > /etc/e-smith/templates-custom/var/lib/pgsql/data/pg_hba.conf/15onlyoffice
signal-event nethserver-postgresql-update

# create postgres db and user
sudo -u postgres psql -c "CREATE DATABASE onlyoffice;"
sudo -u postgres psql -c "CREATE USER onlyoffice WITH password 'onlyoffice';"
sudo -u postgres psql -c "GRANT ALL privileges ON DATABASE onlyoffice TO onlyoffice;"

# start and enable redis and rabbitmq
systemctl enable redis --now
systemctl enable rabbitmq-server --now

# install fonts and documentserver
yum -y install https://downloads.sourceforge.net/project/mscorefonts2/rpms/msttcore-fonts-installer-2.6-1.noarch.rpm
yum -y install https://github.com/ONLYOFFICE/DocumentServer/releases/download/ONLYOFFICE-DocumentServer-5.0.7/onlyoffice-documentserver.x86_64.rpm

# stop httpd and start and enable supervisord and nginx
systemctl stop httpd
systemctl enable supervisord --now
systemctl enable nginx --now

# change documentserver http port from 80 to 8081 to have no conflict
export DS_PORT=8081
documentserver-configure.sh

Now we have to go through the documentserver-configure script. Accept the defaults here. Set the password for Postgres user to “onlyoffice” and the password for RabbitMQ user to “guest”.

than this method.

mrmarkuz · July 7, 2018, 2:14pm

The module is the better method as it eases installation a lot and preconfigures onlyoffice.

oneitonitram · July 7, 2018, 2:16pm

Thank you,

and whats the difference between the quick install, and the installation in the documentation.

do I have to run write both, or only chose one

mrmarkuz · July 7, 2018, 2:17pm

Choose one. First we make a howto and then we make the module out of the howto. So the module integrates the howto.

oneitonitram · July 7, 2018, 2:20pm

when I install the module with the instruction, will it install on sub.doamin.tld/onlyoffice or do I need to point a subdomain like https://onlyoffice.domin.tld

mrmarkuz · July 7, 2018, 2:36pm

The module integrates itself in nextcloud so it depends on nextcloud.

oneitonitram · July 7, 2018, 2:46pm

does that mean I do not have to go and add theh onlyoffcie erver in the nextcloud settings?

oneitonitram · July 7, 2018, 2:48pm

thank you

kizotux · July 15, 2018, 9:45am

Hi everyone,

Yesterday i made a clean install Nethserver + Nextcloud (from Software center) + OnlyOffice + DocumentServer 5.1.4 as per instructions (onlyoffice Wiki).

Despite this, I have always received an error (when I press the Save button in Nextcloud - ONLYOFFICE):
“Command Request on check error: Error while downloading the document file to be converted.”

I spent the whole day trying to solve the problem.

I found a solution this morning. In file default.json (/etc/onlyoffice/documentserver/) I made a simple change (true to false):

“requestDefaults”: {
“headers”: {
“userAgent”: “Node.js/6.13”
},
“rejectUnauthorized”: false
},

I know the problem is in the certificates, but only in this way have I managed to make Onlyoffice to work.

I am a little confused

mrmarkuz · July 15, 2018, 11:02am

Hi Zoran,

Yes, you need a valid trusted cert like letsencrypt and you probably need to port forward 8082 from your router to your Nethserver. You have to set your domain too.

Thanks for sharing, this is great for using onlyoffice without valid cert but I am afraid it’s not the best for security.

kizotux · July 15, 2018, 11:14am

Thanks Markus,

now I will try to implement the certificates.

flatspin · September 17, 2018, 3:58pm

Hi Markus @mrmarkuz ,

I installed a new NS instance with NC-13.0.6 and only-office 5.0.7 (selfsigned certs).
I had to install librabbitmq and librabbitmq-tools from puias-unsupported.

I did:
wget http://springdale.math.ias.edu/data/puias/unsupported/7/x86_64//librabbitmq-0.5.2-1.sdl7.x86_64.rpm
and
wget http://springdale.math.ias.edu/data/puias/unsupported/7/x86_64//librabbitmq-tools-0.5.2-1.sdl7.x86_64.rpm

and then

yum localinstall -y librabbitmq-0.5.2-1.sdl7.x86_64.rpm
yum localinstall -y librabbitmq-tools-0.5.2-1.sdl7.x86_64.rpm

Now onlyoffice in NC 13 on NS 7.5 is running fine:

Maybe you want to update your Howto.

mrmarkuz · September 17, 2018, 5:10pm

IIRC it’s only a problem with old documentserver needed for self-signed certs, newer documentserver version should just work. It’s because epel changed rabbitmq packages.
Thanx, I’ll update the wiki entry asap.

EDIT: updated.