Fulltextsearch cannot be enabled in AIO 12.6.1 (checkbox resets after Save)

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
,
1

Hi,

I’m experiencing an issue with Fulltextsearch in Nextcloud AIO 12.6.1 (confirmed on both latest and beta).

Problem

When I enable (checkbox):

Fulltextsearch (needs ~1GB additional RAM, does not work on Kernels without Seccomp)

and click Save Changes, the checkbox immediately unchecks itself.

No elasticsearch container is created.

There is no visible error message in the UI.

Environment

Nextcloud AIO: 12.6.1
Nextcloud: 32.0.5
Host OS: Ubuntu 24.04.3 LTS
Kernel: 6.8.0-100-generic
Docker: seccomp enabled (builtin profile)
CPU: 12 threads
RAM: 16 GB
Storage: NVMe

Seccomp verification

Kernel:

CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y

Docker:

Security Options:
 seccomp
  Profile: builtin

Inside container:

Seccomp:        2
Seccomp_filters:        1

Elasticsearch prerequisite

vm.max_map_count = 1048576

Additional information

Fulltextsearch was working previously on this same server configuration.
There were no hardware changes and no kernel changes.

I cannot say exactly which AIO version it last worked on, but the environment itself has not changed.

Any suggestions?

2

Hi, can you post your compose file here?

3

Of course! :wink:

# version: "3.4"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer  # musĂ­ sa volaĹĄ presne takto!
    external: true

networks:
  default:
    name: nextcloud-aio                   # oficiálna AIO sieť, vytvára ju aj mastercontainer

services:
  nextcloud:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    restart: unless-stopped
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /etc/cups/client.conf:/etc/cups/client.conf:ro
      - /mnt/media_large/nextcloud_borg2:/mnt/media_large/nextcloud_borg2

    ports:
      - "6789:8080"  # Web UI mastercontainer (port pre AIO inštalátor)
    environment:
      - APACHE_PORT=11000
      - NEXTCLOUD_MEMORY_LIMIT=4096M
      - BORG_RETENTION_POLICY=--keep-daily=7
4

Hm… Can you add - COLLABORA_SECCOMP_DISABLED=false in the environment section and check if that helps?

5

I tested your suggestion.

I added this to the AIO environment section:

COLLABORA_SECCOMP_DISABLED=false

(no other changes)

Result is the same:

  • I enable Fulltextsearch

  • click Save Changes

  • the checkbox immediately resets (becomes unchecked again)

  • Fulltextsearch stays disabled and the checkbox is empty again after reload

So this variable doesn’t affect the behavior in my case.

6

Hey, thanks for the report! This is a bug that was caused by a huge refactoring that we did recently. It will be fixed in the next version. See https://github.com/nextcloud/all-in-one/pull/7578

1 Like
7

I’m glad I could help with reporting the issue.

Feel free to reach out if you need further testing or additional information from my side.

Keep up the great work! :clap:

2 Likes
8

This is now released with v12.7.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel

9

@szaimen

I can confirm that AIO 12.7.0 Beta fixed the issue with nextcloud-aio-fulltextsearch

:clap:

1 Like
10

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.