Systemctl start coolwsd doesn't give error, but no ports are listening

Installation & Configuration
1

I have installed the code on Ubuntu 22.04 following the instructions here. However, when I start the coolwsd service, there are no ports listening. I believe port 9980 should be listening.

# systemctl status coolwsd
x coolwsd.service - Collabora Online WebSocket Daemon
     Loaded: loaded (/lib/systemd/system/coolwsd.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Thu 2022-06-02 20:52:09 SAST; 36min ago
    Process: 6931 ExecStart=/usr/bin/coolwsd --version --o:sys_template_path=/opt/cool/systemplate --o:child_root_path=/opt/cool/child-roots --o:file_server_root_path=/usr/share/coolwsd (code=killed, signal=ABR>
   Main PID: 6931 (code=killed, signal=ABRT)
        CPU: 1.392s

Jun 02 20:52:09 Collabora1 systemd[1]: coolwsd.service: Scheduled restart job, restart counter is at 10.
Jun 02 20:52:09 Collabora1 systemd[1]: Stopped Collabora Online WebSocket Daemon.
Jun 02 20:52:09 Collabora1 systemd[1]: coolwsd.service: Consumed 1.392s CPU time.
Jun 02 20:52:09 Collabora1 systemd[1]: coolwsd.service: Start request repeated too quickly.
Jun 02 20:52:09 Collabora1 systemd[1]: coolwsd.service: Failed with result 'signal'.
Jun 02 20:52:09 Collabora1 systemd[1]: Failed to start Collabora Online WebSocket Daemon.

From the above it’s clear the service is not running, but why?

# journalctl -xeu coolwsd.service
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Main process exited, code=killed, status=6/ABRT
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- An ExecStart= process belonging to unit coolwsd.service has exited.
-- 
-- The process' exit code is 'killed' and its exit status is 6.
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit coolwsd.service has entered the 'failed' state with result 'signal'.
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Consumed 1.134s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit coolwsd.service completed and consumed the indicated resources.
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Scheduled restart job, restart counter is at 10.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Automatic restarting of the unit coolwsd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Jun 02 21:30:37 Collabora1 systemd[1]: Stopped Collabora Online WebSocket Daemon.
-- Subject: A stop job for unit coolwsd.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A stop job for unit coolwsd.service has finished.
-- 
-- The job identifier is 4068 and the job result is done.
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Consumed 1.134s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit coolwsd.service completed and consumed the indicated resources.
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Start request repeated too quickly.
Jun 02 21:30:37 Collabora1 systemd[1]: coolwsd.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit coolwsd.service has entered the 'failed' state with result 'signal'.
Jun 02 21:30:37 Collabora1 systemd[1]: Failed to start Collabora Online WebSocket Daemon.
-- Subject: A start job for unit coolwsd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit coolwsd.service has finished with a failure.
-- 
-- The job identifier is 4068 and the job result is failed.

There is a note in the installation page to disable ssl in the coolwsd.xml file, but the file is quite large, so where does on do that? Or is this not what causes the problem?

2

Ah!

I found this in coolwsd.xml and disabled ssl and enabled termination:

    <ssl desc="SSL settings">
        <!-- switches from https:// + wss:// to http:// + ws:// -->
        <enable type="bool" desc="Controls whether SSL encryption between coolwsd and the network is enabled (do not disable for production deployment). If default is false, must first be compiled with SSL support to enable." default="true">false</enable>
        <!-- SSL off-load can be done in a proxy, if so disable SSL, and enable termination below in production -->
        <termination desc="Connection via proxy where coolwsd acts as working via https, but actually uses http." type="bool" default="true">true</termination>

Now it’s running!

1 Like