Warning in Logfile

ℹ️ Support
, , ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32.0.3
  • Operating system and version (e.g., Ubuntu 24.04):
    • Opensuse Leap 16.0
  • Web server and version (e.g, Apache 2.4.25):
    • nginx
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • nginx
  • PHP version (e.g, 8.3):
    • 8.4
  • Is this the first time you’ve seen this error? (Yes / No):
    • No
  • When did this problem seem to first start?
    • a long while ago. But it is annoying by now.
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Bare metal
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

I use Onlyoffice in a Docker container, lined into my Nextcloud instance via the Onlyoffice Connector. I CAN open and edit Files, I can see no issue in functionality. I am NOT using Colabora. Every once in a while I see the following entries in the Nextcloud log (GUI)

exec(): Unable to fork \[command -v -- 'openoffice'\] at /srv/www/htdocs/Nextcloud/3rdparty/symfony/process/ExecutableFinder.php#97

and:

exec(): Unable to fork \[command -v -- 'libreoffice'\] at /srv/www/htdocs/Nextcloud/3rdparty/symfony/process/ExecutableFinder.php#97

So once Libreoffice, once Openoffice, neither of which I am using. There is a Docker container running Onlyoffice and it is connected and does work.

How can I get rid of these messages?

Steps to replicate it (hint: details matter!):

  1. In my case: Install NExtcloud

  2. Instal and connect Onlyoffice in a Docker container

  3. Log in, open Office Files

  4. Check the Event log in the Web GUI when logged in as an admin

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.
2

It’s challenging to assist since you didn’t include your config nor app list.

preview_libreoffice_path comes to mind.

That error shouldn’t normally occur though.

The error itself indicates the shell can’t be executed at all (e.g., /bin/sh missing, permissions issue, or fork failure due to resource problems).

3

Hello jtr.

Thank you for the right hint maybe. At some point a while ago I activated AppArmor and yes, I remember declining shell authorization as I didnt see a reason why Nextcloud should be authorized to start shells (for the same reason I don’t use the APP API to not have nextcloud basically administer Docker).

But why would nextcloud anyways want to try and start libreoffice or Openoffice? I don’t understand this.

I will try and check the parameter you mentioned.

Update: I neither have the “enable previews” set, nor the libreoffice path. These parameters don’t exist in my config.php file…

4

Hello all, to whom it may concern: I solved the issue now. Basically the hint regarding the Previews was the right one.

Turns out: Even when the config.php has NO mention of previews at all, the Nextcloud default kicks in and that includes the generation of previews for office files for which it will try to use a locally installed libreoffice/openoffice.

To switch this off, one needs to ADD a preview section to config.php and that section shall NOT have the office formats. This will stop the error message.

Instead, in the Onlyoffice connector settings, one can select Onlyoffice to then generate the previews for the office files. → Problem solved.

Cheers and merry christmas everyone!

1 Like
5

Yeah there’s a default value for enabledPreviewProviders as documented in the Admin Manual here.