(Solved) Help installing Collabora CODE and starting loolwsd

🚧 Installation
1

Hello,

Can i get some troubleshooting why loolwsd is not starting. I’ve read through other forum post but i cant seem to fix my own problem.

I’ve installed CODE on CentOS 7 not via Docker but as a separate package (followed the instruction on the official collabora site)

SELinux is disabled and firewalld as well.

I am using NGINX and PHP7.3

This is the message i get

● loolwsd.service - LibreOffice Online WebSocket Daemon
   Loaded: loaded (/usr/lib/systemd/system/loolwsd.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2019-02-12 15:05:12 UTC; 11min ago
  Process: 4858 ExecStart=/usr/bin/loolwsd --version --o:sys_template_path=/opt/lool/systemplate --o:child_root_path=/opt/lool/child-roots --o:file_server_root_path=/usr/share/loolwsd (code=exited, status=70)
 Main PID: 4858 (code=exited, status=70)

Feb 12 15:05:12 shield systemd[1]: loolwsd.service: main process exited, code=exited, status=70/n/a
Feb 12 15:05:12 shield systemd[1]: Unit loolwsd.service entered failed state.
Feb 12 15:05:12 shield systemd[1]: loolwsd.service failed.
Feb 12 15:05:12 shield systemd[1]: loolwsd.service holdoff time over, scheduling restart.
Feb 12 15:05:12 shield systemd[1]: Stopped LibreOffice Online WebSocket Daemon.
Feb 12 15:05:12 shield systemd[1]: start request repeated too quickly for loolwsd.service
Feb 12 15:05:12 shield systemd[1]: Failed to start LibreOffice Online WebSocket Daemon.
Feb 12 15:05:12 shield systemd[1]: Unit loolwsd.service entered failed state.
Feb 12 15:05:12 shield systemd[1]: loolwsd.service failed.
`

when I run journalctl -u loolwsd, this is the last lines before crashing

Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.784325 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/ve.json as '/loleaflet/dist/l10n/locore/ve.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.775504 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/ur.json as '/loleaflet/dist/l10n/locore/ur.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.775583 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/hsb.json as '/loleaflet/dist/l10n/locore/hsb.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.776722 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/ks.json as '/loleaflet/dist/l10n/locore/ks.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.777101 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/hu-Hung.json as '/loleaflet/dist/l10n/locore/hu-Hung.json'| wsd/FileServer.cp
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.777159 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/uz.json as '/loleaflet/dist/l10n/locore/uz.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.782785 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/hu.json as '/loleaflet/dist/l10n/locore/hu.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.784325 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/ve.json as '/loleaflet/dist/l10n/locore/ve.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.785081 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/id.json as '/loleaflet/dist/l10n/locore/id.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield loolwsd[4850]: wsd-04850-04850 2019-02-12 15:05:09.786156 [ loolwsd ] TRC  Reading file: '/usr/share/loolwsd/loleaflet/dist/l10n/locore/vec.json as '/loleaflet/dist/l10n/locore/vec.json'| wsd/FileServer.cpp:476
Feb 12 15:05:09 shield systemd[1]: loolwsd.service: main process exited, code=exited, status=70/n/a
Feb 12 15:05:09 shield systemd[1]: Unit loolwsd.service entered failed state.
Feb 12 15:05:09 shield systemd[1]: loolwsd.service failed.
Feb 12 15:05:10 shield systemd[1]: loolwsd.service holdoff time over, scheduling restart.
Feb 12 15:05:10 shield systemd[1]: Stopped LibreOffice Online WebSocket Daemon.
Feb 12 15:05:10 shield systemd[1]: Started LibreOffice Online WebSocket Daemon.
Feb 12 15:05:10 shield systemd[1]: loolwsd.service: main process exited, code=exited, status=70/n/a
Feb 12 15:05:10 shield systemd[1]: Unit loolwsd.service entered failed state.
Feb 12 15:05:10 shield systemd[1]: loolwsd.service failed.
Feb 12 15:05:10 shield systemd[1]: loolwsd.service holdoff time over, scheduling restart.
Feb 12 15:05:10 shield systemd[1]: Stopped LibreOffice Online WebSocket Daemon.
Feb 12 15:05:10 shield systemd[1]: Started LibreOffice Online WebSocket Daemon.
Feb 12 15:05:11 shield systemd[1]: loolwsd.service: main process exited, code=exited, status=70/n/a
Feb 12 15:05:11 shield systemd[1]: Unit loolwsd.service entered failed state.
Feb 12 15:05:11 shield systemd[1]: loolwsd.service failed.
Feb 12 15:05:11 shield systemd[1]: loolwsd.service holdoff time over, scheduling restart.
Feb 12 15:05:11 shield systemd[1]: Stopped LibreOffice Online WebSocket Daemon.
Feb 12 15:05:11 shield systemd[1]: Started LibreOffice Online WebSocket Daemon.
Feb 12 15:05:12 shield systemd[1]: loolwsd.service: main process exited, code=exited, status=70/n/a
Feb 12 15:05:12 shield systemd[1]: Unit loolwsd.service entered failed state.
2

Hi

Can you paste an output of journalctl -xe if it is not the same as journalctl -u loolwsd above? The -xe one usually tells me if I made a config mistake somewhere, or had some finger trouble.

3

@Starfish I cant believe that i solved the problem in 2 minutes with journalctl -xe after i spend hours yesterday trying to make it work.

The output of journalctl -xe said Access to /var/log/loolwsd.log denied (amongst other lines of messages) so i changed the permissions and gave the user starting loolwsd read and write ability. That was it.

Thank you for helping out!

4

Glad it worked! All the best!

5

@Starfish

Hello, I just have one small question regarding the installation. I’ve installed everything and I can open, edit, and save files so everything works as expected. However, when i visit office.mydomain.com, i get a 404 error. Is this normal behavior or is there still something misconfigured. I think that i am supposed to get some type of admin area.

6

I am not that confident with CODE installation. I did it many years ago, but remember something about the admin interface being on some very funky ports, not port 80. Maybe just check you config again for the admin console ports setting, or something similar.

1 Like