Need dedicated support? Click here
Need dedicated support?
Click here

Install Onlyoffice Workspace on a Virtual Environment?

Hello all,
Question can install Onlyoffice Workspace on a Virtual Environment?
Background: the installation on a ProxMox Server 8.0.4, Debian 12.1 in a VM with
8GB memory, 4 CPU’s and 100GB diskspace always aborts!

wget https://download.onlyoffice.com/install/install-Debian.sh
bash install-Debian.sh -it WORKSPACE
mysql: [Warning] Using a password on the command line interface can be insecure.
Job for elasticsearch.service failed because a timeout was exceeded.
See "systemctl status elasticsearch.service" and "journalctl -xeu elasticsearch.service" for details.
dpkg: error processing package onlyoffice-communityserver (--configure):
 installed onlyoffice-communityserver package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 onlyoffice-communityserver
E: Sub-process /usr/bin/dpkg returned an error code (1)

**systemctl status elasticsearch.service**

× elasticsearch.service - Elasticsearch
     Loaded: loaded (/lib/systemd/system/elasticsearch.service; disabled; preset: enabled)
     Active: failed (Result: timeout) since Fri 2023-09-08 13:26:06 CEST; 56min ago
       Docs: https://www.elastic.co
    Process: 22344 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=143)
   Main PID: 22344 (code=exited, status=143)
        CPU: 2min 38.040s

Sep 08 13:24:50 VM-OO-WS systemd[1]: Starting elasticsearch.service - Elasticsearch...
Sep 08 13:26:05 VM-OO-WS systemd[1]: elasticsearch.service: start operation timed out. Terminating.

Hello @judie07

Community Server relies on Elasticsearch service and it fails to start automatically. You can try starting it manually with either service elasticsearch start or systemctl start elasticsearch and if it starts that way, execute installation script again to finish installation.

In general, the status code 143 may be sent due to lack of RAM according to the Elasticsearch forums:
https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303
You may also try increasing amount of RAM for the test purposes.