nextcloud/all-in-one

AIO: Nextcloud becomes unresponsive while Mail app logs repeated `kitinerary-extractor: not found`

Closed this issue · 1 comments

vawaver commented

Environment

  • Nextcloud AIO: 11.9.0
  • Nextcloud version: 31.0.9
  • Nextcloud Mail app: 5.5.6
  • Deployment type: Official Nextcloud AIO Docker stack

Description

Nextcloud suddenly became completely unresponsive — the web UI stopped loading and PHP stopped responding.
The nextcloud-aio-nextcloud container logs were filled with repeated errors like:

sh: /var/www/html/custom_apps/mail/vendor/nextcloud/kitinerary-bin/src/../bin/kitinerary-extractor: not found
sh: flatpak: not found
sh: kitinerary-extractor: not found

Restarting only the nextcloud-aio-nextcloud container immediately restored full functionality.
The Mail app remained enabled during the entire incident — there were no manual changes or configuration edits.

occ status output before/after restart:

- installed: true
- version: 31.0.9.1
- maintenance: false
- needsDbUpgrade: false

Steps to Reproduce (as observed)

  1. Run Nextcloud AIO 11.9.0 with Nextcloud 31.0.9 and Mail app 5.5.6.
  2. After some time (normal operation, not during update), the container nextcloud-aio-nextcloud begins logging kitinerary-extractor: not found and flatpak: not found errors repeatedly.
  3. The Nextcloud UI becomes unreachable (no response from PHP backend).
  4. Restarting the container nextcloud-aio-nextcloud resolves the issue temporarily.

Expected Behavior

If the kitinerary-extractor binary (KDE Itinerary parser) is missing inside AIO, the Mail app should gracefully skip itinerary extraction without affecting overall system stability.

Actual Behavior

Missing kitinerary-extractor causes repeated execution attempts in Mail, filling logs and eventually freezing PHP inside the nextcloud-aio-nextcloud container, making the entire instance unresponsive until manually restarted.

Workaround

Manually restarting the container nextcloud-aio-nextcloud restores functionality.
No configuration or app changes were made to recover the instance.

Notes

This appears to be an interaction between the Mail app and the AIO environment.
The AIO containers do not include kitinerary-extractor or flatpak, and the Mail app does not degrade gracefully when these binaries are missing.

szaimen commented

Hi, please report this to https://github.com/nextcloud/mail/issues if not already done. Thanks!