Resolved: NS8 Nginx-service from nextcloud failed to start

Linux4All · February 4, 2026, 8:11pm

NethServer Version: Nethserver8
Module: Nextcloud

Hi,

I have some issues with my nextcloud module on Nethserver8. The nginx module from nextcloud is not starting anymore.

Logfile looks like the following:
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Queued start job for default target Main User Target.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Created slice User Application Slice.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Started Mark boot as successful after the user session has run 2 minutes.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Started Daily Cleanup of User’s Temporary Directories.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Reached target Paths.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Reached target Timers.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Starting D-Bus User Message Bus Socket…
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Starting Create User’s Volatile Files and Directories…
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Listening on D-Bus User Message Bus Socket.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Reached target Sockets.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Finished Create User’s Volatile Files and Directories.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Reached target Basic System.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Started Rootless module/nextcloud1 agent.
2026-02-04T20:53:37+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud.service…
2026-02-04T20:53:39+01:00 [1:nextcloud1:systemd] Starting D-Bus User Message Bus…
2026-02-04T20:53:39+01:00 [1:nextcloud1:dbus-broker-launch] Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
2026-02-04T20:53:39+01:00 [1:nextcloud1:systemd] Started D-Bus User Message Bus.
2026-02-04T20:53:39+01:00 [1:nextcloud1:dbus-broker-launch] Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
2026-02-04T20:53:39+01:00 [1:nextcloud1:] Ready
2026-02-04T20:53:39+01:00 [1:nextcloud1:systemd] Created slice Slice /user.
2026-02-04T20:53:39+01:00 [1:nextcloud1:systemd] Created slice cgroup user-libpod_pod_4240b9e4ed7383fe1016f6c2e382fc07096db11a94e2b34d978d8bbaaf1106e7.slice.
2026-02-04T20:53:41+01:00 [1:nextcloud1:podman] 4240b9e4ed7383fe1016f6c2e382fc07096db11a94e2b34d978d8bbaaf1106e7
2026-02-04T20:53:41+01:00 [1:nextcloud1:systemd] podman-pause-107430d7.scope: unit configures an IP firewall, but not running as root.
2026-02-04T20:53:41+01:00 [1:nextcloud1:systemd] (This warning is only shown for the first unit using IP firewalling.)
2026-02-04T20:53:41+01:00 [1:nextcloud1:systemd] Started podman-pause-107430d7.scope.
2026-02-04T20:53:41+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T20:53:43+01:00 [1:nextcloud1:podman] nextcloud
2026-02-04T20:53:43+01:00 [1:nextcloud1:systemd] Started Podman nextcloud.service.
2026-02-04T20:53:43+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-db.service…
2026-02-04T20:53:43+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-redis.service…
2026-02-04T20:53:44+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T20:53:45+01:00 [1:nextcloud1:podman] 7e2465f7c326086fc460beb2c381ef2398e08e401b0553e22065a6ac52889cf1
2026-02-04T20:53:45+01:00 [1:nextcloud1:systemd] Started Podman nextcloud-redis.service.
2026-02-04T20:53:45+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-app.service…
2026-02-04T20:53:45+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T20:53:46+01:00 [1:nextcloud1:podman] 9cac41a356480508cea3df5b0a903842278e5813fe5b93550f4c20d7fca48021
2026-02-04T20:53:46+01:00 [1:nextcloud1:systemd] Started Podman nextcloud-db.service.
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:C 04 Feb 2026 19:53:47.066 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:C 04 Feb 2026 19:53:47.069 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:C 04 Feb 2026 19:53:47.069 * Redis version=7.4.5, bits=64, commit=00000000, modified=0, pid=1, just started
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:C 04 Feb 2026 19:53:47.069 * Configuration loaded
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.070 * monotonic clock: POSIX clock_gettime
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.086 * Running mode=standalone, port=6379.
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.086 * Server initialized
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.228 * Reading RDB base file on AOF loading…
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.235 * Loading RDB produced by version 7.4.5
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.235 * RDB age 1536554 seconds
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.235 * RDB memory usage when created 1.31 Mb
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.235 * RDB is base AOF
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.235 * Done loading RDB, keys loaded: 11, keys expired: 0.
2026-02-04T20:53:47+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:47.242 * DB loaded from base file appendonly.aof.74.base.rdb: 0.120 seconds
2026-02-04T20:53:48+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:47+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.24+maria~ubu2204 started.
2026-02-04T20:53:48+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T20:53:49+01:00 [1:nextcloud1:podman] 5a08be247a0b73fbff0827cc0320e2861b9156219c935615d093f1ed19cdcbba
2026-02-04T20:53:49+01:00 [1:nextcloud1:nextcloud-app] Configuring Redis as session handler
2026-02-04T20:53:51+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:51.676 * DB loaded from incr file appendonly.aof.74.incr.aof: 4.434 seconds
2026-02-04T20:53:51+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:51.676 * DB loaded from append only file: 4.559 seconds
2026-02-04T20:53:51+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:51.676 * Opening AOF incr file appendonly.aof.74.incr.aof on server start
2026-02-04T20:53:51+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:53:51.676 * Ready to accept connections tcp
2026-02-04T20:53:52+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:52+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2026-02-04T20:53:52+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:52+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.24+maria~ubu2204 started.
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] Starting MariaDB 10.6.24-MariaDB-ubu2204 source revision e5994025bec0d34ddef25df2e252b8f1d2e34e51 server_uid 4ygaFQ9U4AVqq4wBiUIP6ADw41I= as process 1
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] InnoDB: Number of pools: 1
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2026-02-04T20:53:53+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:53 0 [Note] InnoDB: Completed initialization of buffer pool
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] InnoDB: 128 rollback segments are active.
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] InnoDB: 10.6.24 started; log sequence number 7211933855; transaction id 18741625
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] Server socket created on IP: ‘0.0.0.0’.
2026-02-04T20:53:54+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:54 0 [Note] Server socket created on IP: ‘::’.
2026-02-04T20:53:57+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:53:57 0 [Note] mariadbd: ready for connections.
2026-02-04T20:53:57+01:00 [1:nextcloud1:nextcloud-db] Version: ‘10.6.24-MariaDB-ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
2026-02-04T20:54:09+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:54:09 0 [Note] InnoDB: Buffer pool(s) load completed at 260204 19:54:09
2026-02-04T20:54:10+01:00 [1:nextcloud1:nextcloud-app] => Searching for hook scripts (*.sh) to run, located in the folder “/docker-entrypoint-hooks.d/before-starting”
2026-02-04T20:54:10+01:00 [1:nextcloud1:nextcloud-app] ==> Skipped: the “before-starting” folder is empty (or does not exist)
2026-02-04T20:54:15+01:00 [1:nextcloud1:nextcloud-app] /usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See Package Discovery and Resource Access using pkg_resources - setuptools 82.0.0 documentation. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
2026-02-04T20:54:15+01:00 [1:nextcloud1:nextcloud-app] import pkg_resources
2026-02-04T20:54:22+01:00 [1:nextcloud1:nextcloud-app] 2026-02-04 19:54:22,928 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2026-02-04T20:54:22+01:00 [1:nextcloud1:nextcloud-app] 2026-02-04 19:54:22,928 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2026-02-04T20:54:29+01:00 [1:nextcloud1:nextcloud-app] crond: crond (busybox 1.37.0) started, log level 8
2026-02-04T20:54:45+01:00 [1:nextcloud1:nextcloud-app] [04-Feb-2026 19:54:45] NOTICE: fpm is running, pid 52
2026-02-04T20:54:45+01:00 [1:nextcloud1:nextcloud-app] [04-Feb-2026 19:54:45] NOTICE: ready to handle connections
2026-02-04T20:54:49+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:54:49.019 * 10000 changes in 60 seconds. Saving…
2026-02-04T20:54:49+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:54:49.485 * Background saving started by pid 16
2026-02-04T20:54:50+01:00 [1:nextcloud1:nextcloud-redis] 16:C 04 Feb 2026 19:54:50.327 * DB saved on disk
2026-02-04T20:54:50+01:00 [1:nextcloud1:nextcloud-redis] 16:C 04 Feb 2026 19:54:50.327 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2026-02-04T20:54:50+01:00 [1:nextcloud1:nextcloud-redis] 1:M 04 Feb 2026 19:54:50.425 * Background saving terminated with success
2026-02-04T20:55:00+01:00 [1:nextcloud1:nextcloud-app] crond: USER www-data pid 58 cmd php -f /var/www/html/cron.php
2026-02-04T20:55:19+01:00 [1:nextcloud1:systemd] nextcloud-app.service: start-post operation timed out. Terminating.
2026-02-04T20:55:19+01:00 [1:nextcloud1:systemd] nextcloud-app.service: Control process exited, code=killed, status=15/TERM
2026-02-04T20:55:19+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:55:19 3 [Warning] Aborted connection 3 to db: ‘nextcloud’ user: ‘nextcloud’ host: ‘127.0.0.1’ (Got an error reading communication packets)
2026-02-04T20:55:19+01:00 [1:nextcloud1:nextcloud-app] [04-Feb-2026 19:55:19] NOTICE: Terminating …
2026-02-04T20:55:19+01:00 [1:nextcloud1:nextcloud-app] [04-Feb-2026 19:55:19] NOTICE: exiting, bye-bye!
2026-02-04T20:55:24+01:00 [1:nextcloud1:nextcloud-db] 2026-02-04 19:55:24 4 [Warning] Aborted connection 4 to db: ‘nextcloud’ user: ‘nextcloud’ host: ‘127.0.0.1’ (Got an error reading communication packets)
2026-02-04T20:55:24+01:00 [1:nextcloud1:systemd] libpod-5a08be247a0b73fbff0827cc0320e2861b9156219c935615d093f1ed19cdcbba.scope: Consumed 2.587s CPU time.
2026-02-04T20:55:28+01:00 [1:nextcloud1:podman] 5a08be247a0b73fbff0827cc0320e2861b9156219c935615d093f1ed19cdcbba
2026-02-04T20:55:28+01:00 [1:nextcloud1:systemd] nextcloud-app.service: Failed with result ‘timeout’.
2026-02-04T20:55:28+01:00 [1:nextcloud1:systemd] Failed to start Podman nextcloud-app.service.
2026-02-04T20:55:28+01:00 [1:nextcloud1:systemd] nextcloud-app.service: Consumed 1.512s CPU time.
2026-02-04T20:55:28+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-nginx.service…
2026-02-04T20:55:28+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-notify_push.service…
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] nextcloud-app.service: Scheduled restart job, restart counter is at 1.
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-app.service.
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] nextcloud-app.service: Consumed 1.512s CPU time.
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-app.service…
2026-02-04T20:55:29+01:00 [1:nextcloud1:podman] Error: looking up container “nextcloud-app” for volumes-from: no container with name or ID “nextcloud-app” found: no such container
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Control process exited, code=exited, status=125/n/a
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Failed with result ‘exit-code’.
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] Failed to start Podman nextcloud-nginx.service.
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Scheduled restart job, restart counter is at 1.
2026-02-04T20:55:29+01:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-nginx.service.
2026-02-04T20:55:33+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T20:55:33+01:00 [1:nextcloud1:podman] d507c3416124dec5730f76c1e93fe3ec6804310289da73a7e4ef1b4d425402bb
2026-02-04T20:55:33+01:00 [1:nextcloud1:systemd] Started Podman nextcloud-notify_push.service.
2026-02-04T20:55:34+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T20:55:34+01:00 [1:nextcloud1:nextcloud-app] Configuring Redis as session handler
2026-02-04T20:55:35+01:00 [1:nextcloud1:podman] 413f5b3825247052dbdbb1a840ab1456a2e8f8c22852b62d916056f091c26371
2026-02-04T20:55:35+01:00 [1:nextcloud1:nextcloud-notify_push] [2026-02-04 19:55:35.153243 +00:00] ERROR [notify_push] src/main.rs:84: Self test failed: Error while communicating with nextcloud instance: error sending request for url (http://127.0.0.1/index.php/apps/notify_push/test/version)
2026-02-04T20:55:35+01:00 [1:nextcloud1:nextcloud-app] => Searching for hook scripts (*.sh) to run, located in the folder “/docker-entrypoint-hooks.d/before-starting”
2026-02-04T20:55:35+01:00 [1:nextcloud1:nextcloud-app] ==> Skipped: the “before-starting” folder is empty (or does not exist)
2026-02-04T20:55:37+01:00 [1:nextcloud1:systemd] Starting Mark boot as successful…
2026-02-04T20:55:37+01:00 [1:nextcloud1:systemd] Finished Mark boot as successful.
2026-02-04T20:55:39+01:00 [1:nextcloud1:nextcloud-app] /usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See Package Discovery and Resource Access using pkg_resources - setuptools 82.0.0 documentation. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
2026-02-04T20:55:39+01:00 [1:nextcloud1:nextcloud-app] import pkg_resources
2026-02-04T20:55:39+01:00 [1:nextcloud1:nextcloud-app] 2026-02-04 19:55:39,690 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2026-02-04T20:55:39+01:00 [1:nextcloud1:nextcloud-app] 2026-02-04 19:55:39,690 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2026-02-04T20:55:40+01:00 [1:nextcloud1:nextcloud-app] crond: crond (busybox 1.37.0) started, log level 8
2026-02-04T20:55:40+01:00 [1:nextcloud1:nextcloud-app] [04-Feb-2026 19:55:40] NOTICE: fpm is running, pid 54
2026-02-04T20:55:40+01:00 [1:nextcloud1:nextcloud-app] [04-Feb-2026 19:55:40] NOTICE: ready to handle connections
2026-02-04T20:56:45+01:00 [1:nextcloud1:runagent] setup-ldap: linux.local configuration completed
2026-02-04T20:56:45+01:00 [1:nextcloud1:systemd] Started Podman nextcloud-app.service.
2026-02-04T20:56:45+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-nginx.service…
2026-02-04T20:56:50+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/a5a8827c-551e-4d5e-a346-da9283276ddf: get-status/20read is starting
2026-02-04T20:56:50+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/c14adea1-c0af-4b24-8b6b-a2e37f9c9b23: get-name/50get_name is starting
2026-02-04T20:56:50+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/159d6f6d-34a9-4811-8c08-16696a75631a: get-configuration/20read is starting
2026-02-04T20:56:51+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/c14adea1-c0af-4b24-8b6b-a2e37f9c9b23: action “get-name” status is “completed” (0) at step 50get_name
2026-02-04T20:56:52+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/a5a8827c-551e-4d5e-a346-da9283276ddf: action “get-status” status is “completed” (0) at step validate-output.json
2026-02-04T20:56:54+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0e748054-7ea7-4285-a180-a09a432db1f5: get-status/20read is starting
2026-02-04T20:56:54+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/45e2a647-2530-42e3-a72c-1f24be75043c: get-configuration/20read is starting
2026-02-04T20:56:56+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/159d6f6d-34a9-4811-8c08-16696a75631a: action “get-configuration” status is “completed” (0) at step 20read
2026-02-04T20:56:57+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0e748054-7ea7-4285-a180-a09a432db1f5: action “get-status” status is “completed” (0) at step validate-output.json
2026-02-04T20:56:58+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/45e2a647-2530-42e3-a72c-1f24be75043c: action “get-configuration” status is “completed” (0) at step 20read
2026-02-04T20:58:16+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: start operation timed out. Terminating.
2026-02-04T20:58:16+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Control process exited, code=exited, status=1/FAILURE
2026-02-04T20:58:19+01:00 [1:nextcloud1:podman] ae0ff9ca2fa62c29dd5143427a84335a22889193fef3dcad060b9f77a9819130
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Failed with result ‘timeout’.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] Failed to start Podman nextcloud-nginx.service.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Consumed 4.741s CPU time.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] Reached target Main User Target.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] Startup finished in 4min 42.539s.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Scheduled restart job, restart counter is at 2.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-nginx.service.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Consumed 4.741s CPU time.
2026-02-04T20:58:19+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-nginx.service…
2026-02-04T20:58:36+01:00 [1:nextcloud1:systemd] Created slice User Background Tasks Slice.
2026-02-04T20:58:36+01:00 [1:nextcloud1:systemd] Starting Cleanup of User’s Temporary Files and Directories…
2026-02-04T20:58:36+01:00 [1:nextcloud1:systemd] Finished Cleanup of User’s Temporary Files and Directories.
2026-02-04T20:59:49+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: start operation timed out. Terminating.
2026-02-04T20:59:49+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Control process exited, code=exited, status=1/FAILURE
2026-02-04T20:59:49+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/5ea9a755-765d-4e5a-9e1f-4b453056405c: get-name/50get_name is starting
2026-02-04T20:59:49+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/b9283032-92a4-41b3-82dc-18fdc7641038: get-status/20read is starting
2026-02-04T20:59:49+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/77adeee6-ff29-4737-81b9-abeae09c445c: get-configuration/20read is starting
2026-02-04T20:59:50+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/5ea9a755-765d-4e5a-9e1f-4b453056405c: action “get-name” status is “completed” (0) at step 50get_name
2026-02-04T20:59:52+01:00 [1:nextcloud1:podman] 6d863115f523626d59d0add0ff61fb473bbcd25c5593478d7105fb11dd0e4278
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Failed with result ‘timeout’.
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] Failed to start Podman nextcloud-nginx.service.
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Consumed 6.103s CPU time.
2026-02-04T20:59:52+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/b9283032-92a4-41b3-82dc-18fdc7641038: action “get-status” status is “completed” (0) at step validate-output.json
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Scheduled restart job, restart counter is at 3.
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-nginx.service.
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Consumed 6.103s CPU time.
2026-02-04T20:59:52+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-nginx.service…
2026-02-04T21:00:01+01:00 [1:nextcloud1:nextcloud-app] crond: USER www-data pid 151 cmd php -f /var/www/html/cron.php
2026-02-04T21:00:25+01:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/77adeee6-ff29-4737-81b9-abeae09c445c: action “get-configuration” status is “completed” (0) at step 20read

Last thing I did was assigning an TLS certificate. But it was starting afterwards.
I did some final datasync and now it is not working anymore.

I didn’t find any hint in this logs. Is there any more detailed log somewhere?
Any other idea?

Many thanks for your help!

mrmarkuz · February 4, 2026, 8:44pm

Timeouts can occur due to slower disks. At least SSDs are required, see System requirements — NS8 documentation

Does it help to restart Nextcloud manually in Software Center or on CLI?

runagent -m nextcloud1 systemctl --user restart nextcloud

Linux4All · February 4, 2026, 8:59pm

Sadly also a manually start is resulting in a timeout.
It is running on an USB3 external disk, but it was running some time ago.
But as you pointed to the disk, I noticed it is all the time working.

I need to do this step to replace my nethserver7.9 therefore it is running on a VM. Later it will be back on my server, but there is no option for an in-place upgrade thats why I choose this way.

Is there anything I can do to get it back running. Increasing the timeout value for example?

mrmarkuz · February 4, 2026, 9:11pm

It could work to increase the service timeouts, see Continuing NS8 Nextcloud + other problems - #19 by stephdl for more details.

Edit the service file, for example nextcloud-nginx:

runagent -m nextcloud1 systemctl --user edit --full nextcloud-nginx

Change the timeout:

TimeoutStopSec=70

Linux4All · February 4, 2026, 10:19pm

Tried that. but seems not to be respected. I set it to 600s but terminated already after about a minute
026-02-04T23:16:57+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-nginx.service…
2026-02-04T23:16:57+01:00 [1:nextcloud1:systemd] Starting Podman nextcloud-notify_push.service…
2026-02-04T23:16:59+01:00 [1:nextcloud1:systemd] Started libcrun container.
2026-02-04T23:16:59+01:00 [1:nextcloud1:podman] 69b24209c5f294e3cccefc6962de530be567d21f66521719c018df0c3cad9eaf
2026-02-04T23:16:59+01:00 [1:nextcloud1:systemd] Started Podman nextcloud-notify_push.service.
2026-02-04T23:17:00+01:00 [1:nextcloud1:nextcloud-notify_push] [2026-02-04 22:17:00.083080 +00:00] ERROR [notify_push] src/main.rs:84: Self test failed: Error while communicating with nextcloud instance: error sending request for url (http://127.0.0.1/index.php/apps/notify_push/test/version)
2026-02-04T23:17:21+01:00 [1:nextcloud1:systemd] Starting Mark boot as successful…
2026-02-04T23:17:21+01:00 [1:nextcloud1:systemd] Finished Mark boot as successful.
2026-02-04T23:18:27+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: start operation timed out. Terminating.
2026-02-04T23:18:27+01:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Control process exited, code=exited, status=1/FAILURE

LayLow · February 4, 2026, 10:23pm

FWIIW

Unreliable systems and ‘stange things happening’ had some serious issues with RAM memory modules in te past. Just a wild guess…

Linux4All · February 4, 2026, 11:34pm

Found the issue why timeout was not working.
You need to set it for TimeoutStartSec. But it didn’t start also with 600s timeout.
Seems I need to reinstall the module

Linux4All · February 5, 2026, 7:41am

Reinstalling the module has helped. But I need to bring in the data again.
Is there a local way on the server itself?
Just to do a move of the files will probably not work, won’t it?

Update:
Found that command, that needs to be applied after moving files in the files data directory.

How do I need to adopt this command that it will work with nethserver8?

sudo -u www-data php /var/www/nextcloud occ files:scan --all

mrmarkuz · February 5, 2026, 7:49am

Great that a fresh instance seems working.

You can use following command, see GitHub - NethServer/ns8-nextcloud: Nextcloud module for NS8

runagent -m nextcloud2 occ files:scan --all

Linux4All · February 9, 2026, 10:10pm

Many thanks for your help!