@mrmarkuz thank you for everything, right now I would like to solve another issue within regards on this OPACHE , trying to figure-out the location but /php folder on this can’t find.
I don’t get this message on my NS8 Nextclouds.
To adapt the opcache.memory_consumption value in NS8 Nextcloud:
Enter nextcloud1:
runagent -m nextcloud1
Add the following to the file ./config.env for 256 MB:
PHP_OPCACHE_MEMORY_CONSUMPTION=256
Restart Nextcloud app:
systemctl --user restart nextcloud-app
Exit environment:
exit
4 Likes
Hi, I have the same problem ‘Bad Gateway’
I use a VPS Contabo 6 Core 12GB RAM 300GB SSD Rocky 9
I removed the app and installed a new instance but
“nextcloud-app.service” and “nextcloud-nginx.service” do not start
Job for nextcloud-app.service failed because a timeout was exceeded.
See "systemctl --user status nextcloud-app.service" and "journalctl --user -xeu nextcloud-app.service" for details.
Job for nextcloud-nginx.service failed because the control process exited with error code.
See "systemctl --user status nextcloud-nginx.service" and "journalctl --user -xeu nextcloud-nginx.service" for details.
Since I still had no data stored, I decided to do a complete reset of the VPS and reinstall Rocky 9.
so i use this script to set hostname and swap
#!/bin/bash
# === CONFIGURAZIONE HOSTNAME ===
NEW_HOSTNAME="myhost"
echo ">>> Configurazione hostname su $NEW_HOSTNAME..."
hostnamectl set-hostname $NEW_HOSTNAME
# === CONFIGURAZIONE SWAP ===
SWAP_SIZE=8G
SWAP_FILE=/swapfile
echo ">>> Creazione file di swap da $SWAP_SIZE in $SWAP_FILE..."
# 1. Crea il file di swap (prova fallocate, altrimenti usa dd)
fallocate -l $SWAP_SIZE $SWAP_FILE || dd if=/dev/zero of=$SWAP_FILE bs=1M count=8192
# 2. Imposta i permessi corretti
chmod 600 $SWAP_FILE
# 3. Inizializza il file come area di swap
mkswap $SWAP_FILE
# 4. Attiva lo swap
swapon $SWAP_FILE
# 5. Verifica che lo swap sia attivo
echo ">>> Swap attivo:"
swapon --show
# 6. Aggiungi allo /etc/fstab per renderlo permanente
if ! grep -q "$SWAP_FILE" /etc/fstab; then
echo "$SWAP_FILE none swap sw 0 0" >> /etc/fstab
echo ">>> Aggiunto a /etc/fstab per persistenza al riavvio."
fi
# 7. Ottimizzazione: Imposta swappiness a 10
sysctl -w vm.swappiness=10
if ! grep -q "vm.swappiness" /etc/sysctl.conf; then
echo "vm.swappiness=10" >> /etc/sysctl.conf
echo ">>> Impostato vm.swappiness=10 in /etc/sysctl.conf"
fi
# 8. Ottimizzazione: Imposta vfs_cache_pressure a 50
sysctl -w vm.vfs_cache_pressure=50
if ! grep -q "vm.vfs_cache_pressure" /etc/sysctl.conf; then
echo "vm.vfs_cache_pressure=50" >> /etc/sysctl.conf
echo ">>> Impostato vm.vfs_cache_pressure=50 in /etc/sysctl.conf"
fi
echo "✅ Configurazione completata con successo (swap + ottimizzazioni)."
then i install nethserver and change port to sshd
curl https://raw.githubusercontent.com/NethServer/ns8-core/ns8-stable/core/install.sh | bash
firewall-cmd --permanent --add-forward-port=port=22222:proto=tcp:toport=22
firewall-cmd --permanent --service=ssh --add-port=22222/tcp
firewall-cmd --permanent --service=ssh --remove-port=22/tcp
firewall-cmd --reload
I proceed with installation and setup:
LDAP server - OK
Mail server - OK
Crowdsec - OK
Collabora app - OK
I proceed with the installation of Nextcloud, access the administration panel and add the official NC apps that interest me.
This is the app list:
runagent -m nextcloud1 occ app:list
Enabled:
- bruteforcesettings: 3.0.0
- calendar: 5.2.2
- circles: 30.0.0
- cloud_federation_api: 1.13.0
- comments: 1.20.1
- contacts: 7.0.6
- contactsinteraction: 1.11.0
- dav: 1.31.1
- encryption: 2.18.0
- federatedfilesharing: 1.20.0
- federation: 1.20.0
- files: 2.2.0
- files_downloadlimit: 3.0.0
- files_reminders: 1.3.0
- files_sharing: 1.22.0
- files_trashbin: 1.20.1
- files_versions: 1.23.0
- groupfolders: 18.1.2
- lookup_server_connector: 1.18.0
- mail: 5.0.3
- nextcloud_announcements: 2.0.0
- notifications: 3.0.0
- notify_push: 1.0.0
- oauth2: 1.18.1
- password_policy: 2.0.0
- privacy: 2.0.0
- provisioning_api: 1.20.0
- recommendations: 3.0.0
- related_resources: 1.5.0
- richdocuments: 8.5.6
- serverinfo: 2.0.0
- settings: 1.13.0
- sharebymail: 1.20.0
- spreed: 20.1.6
- support: 2.0.0
- survey_client: 2.0.0
- systemtags: 1.20.0
- text: 4.1.0
- theming: 2.6.0
- twofactor_backupcodes: 1.19.0
- twofactor_nextcloud_notification: 4.0.0
- twofactor_totp: 12.0.0-dev
- twofactor_webauthn: 2.1.0
- updatenotification: 1.20.0
- user_ldap: 1.21.0
- user_status: 1.10.0
- viewer: 3.0.0
- weather_status: 1.10.0
- webhook_listeners: 1.1.0-dev
- workflowengine: 2.12.0
Disabled:
- activity: 3.0.0 (installed 3.0.0)
- admin_audit: 1.20.0
- app_api: 4.0.6 (installed 4.0.6)
- dashboard: 7.10.0 (installed 7.10.0)
- files_external: 1.22.0
- files_pdfviewer: 3.0.0 (installed 3.0.0)
- firstrunwizard: 3.0.0 (installed 3.0.0)
- logreader: 3.0.0 (installed 3.0.0)
- photos: 3.0.2 (installed 3.0.2)
- suspicious_login: 8.0.0
I add the Hostname of the CODE server in Cluster-admin and I get the error
Job for nextcloud-app.service failed because a timeout was exceeded.
See "systemctl --user status nextcloud-app.service" and "journalctl --user -xeu nextcloud-app.service" for details.
Job for nextcloud-nginx.service failed because the control process exited with error code.
See "systemctl --user status nextcloud-nginx.service" and "journalctl --user -xeu nextcloud-nginx.service" for details.
I try to execute from shell but from now on NC always responds “Bad gateway”
runagent -m nextcloud1 systemctl --user try-reload-or-restart nextcloud nextcloud-{redis,db,app,nginx}
I have reset the server several times and minimized the changes to the various services but I always get the same error
I ask if you can kindly help me understand what I’m doing wrong.
Thanks
P.S.
I ran the commands:
runagent -m nextcloud1 occ maintenance:repair
runagent -m nextcloud1 systemctl --user restart nextcloud-app
Nc is now online but I received this:
Job for nextcloud-app.service failed because a timeout was exceeded.
See "systemctl --user status nextcloud-app.service" and "journalctl --user -xeu nextcloud-app.service" for details.
Hi Giuseppe,
welcome to NethServer community.
So Nextcloud does work until you set the collabora server in the NS8 Nextcloud app settings?
Maybe one of the apps you installed causes the issue? Did you already try without app install?
Please also check the system logs for errors.
Maybe it helps to increase the timeout, see also Continuing NS8 Nextcloud + other problems - #19 by stephdl
2 Likes
Thanks for the advice, unfortunately even increasing the timeout to 120 for
- nextcloud.service
- nextcloud-nginx.service
- nextcloud-app.service
and then running
runagent -m nextcloud1 systemctl --user try-reload-or-restart nextcloud nextcloud-{redis,db,app,nginx}
always responds “Bad Gateway”
and this is the log after the command
Log
2025-05-05T12:33:24+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:24 10 [Warning] Aborted connection 10 to db: ‘nextcloud’ user: ‘nextcloud’ host: ‘127.0.0.1’ (Got an error reading communication packets)
2025-05-05T12:33:24+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:24 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
2025-05-05T12:33:24+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:24 0 [Note] InnoDB: FTS optimize thread exiting.
2025-05-05T12:33:24+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:24 0 [Note] InnoDB: Starting shutdown…
2025-05-05T12:33:25+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:25 0 [Note] InnoDB: Removed temporary tablespace data file: “./ibtmp1”
2025-05-05T12:33:25+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:33:25] NOTICE: Terminating …
2025-05-05T12:33:26+02:00 [1:nextcloud1:podman] 1f9a8335ca335a00173069ba1b3dbb6887c7cd770a4297bcfb1de7ca099ccd06
2025-05-05T12:33:26+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-db.service.
2025-05-05T12:33:26+02:00 [1:nextcloud1:systemd] nextcloud-db.service: Consumed 2.735s CPU time.
2025-05-05T12:33:27+02:00 [1:nextcloud1:podman] 1a414e50430eb7a5e5c8de2da44d49b2ed9a108c1f9f5a67284e88531ea10ab3
2025-05-05T12:33:27+02:00 [1:nextcloud1:systemd] nextcloud-app.service: Consumed 18.556s CPU time.
2025-05-05T12:33:27+02:00 [1:nextcloud1:systemd] Stopping Podman nextcloud-redis.service…
2025-05-05T12:33:27+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:27.793 * User requested shutdown…
2025-05-05T12:33:27+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:27.798 * Saving the final RDB snapshot before exiting.
2025-05-05T12:33:27+02:00 [1:nextcloud1:systemd] libpod-0b648fa0366a92d3c8489194feb12a19d4c55736ecbe3ec3def5766339b51baf.scope: Consumed 3.492s CPU time.
2025-05-05T12:33:27+02:00 [1:nextcloud1:conmon] conmon 0b648fa0366a92d3c848 : Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1008.slice/user@1008.service/user.slice/user-libpod_pod_4dae17276a1f4fe52c5e579bbfa0c1338fbbd30bed900ba411ecb9adc56d44f0.slice/libpod-0b648fa0366a92d3c8489194feb12a19d4c55736ecbe3ec3def5766339b51baf.scope/container/memory.events
2025-05-05T12:33:28+02:00 [1:nextcloud1:podman] 0b648fa0366a92d3c8489194feb12a19d4c55736ecbe3ec3def5766339b51baf
2025-05-05T12:33:28+02:00 [1:nextcloud1:podman] 0b648fa0366a92d3c8489194feb12a19d4c55736ecbe3ec3def5766339b51baf
2025-05-05T12:33:28+02:00 [1:nextcloud1:systemd] Stopping Podman nextcloud.service…
2025-05-05T12:33:29+02:00 [1:nextcloud1:systemd] Removed slice cgroup user-libpod_pod_4dae17276a1f4fe52c5e579bbfa0c1338fbbd30bed900ba411ecb9adc56d44f0.slice.
2025-05-05T12:33:29+02:00 [1:nextcloud1:systemd] user-libpod_pod_4dae17276a1f4fe52c5e579bbfa0c1338fbbd30bed900ba411ecb9adc56d44f0.slice: Consumed 41.079s CPU time.
2025-05-05T12:33:29+02:00 [1:nextcloud1:podman] nextcloud
2025-05-05T12:33:30+02:00 [1:nextcloud1:podman] 4dae17276a1f4fe52c5e579bbfa0c1338fbbd30bed900ba411ecb9adc56d44f0
2025-05-05T12:33:30+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud.service.
2025-05-05T12:33:30+02:00 [1:nextcloud1:systemd] nextcloud.service: Consumed 3.363s CPU time.
2025-05-05T12:33:30+02:00 [1:nextcloud1:systemd] Starting Podman nextcloud.service…
2025-05-05T12:33:31+02:00 [1:nextcloud1:systemd] Created slice cgroup user-libpod_pod_1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd.slice.
2025-05-05T12:33:31+02:00 [1:nextcloud1:podman] 1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd
2025-05-05T12:33:32+02:00 [1:nextcloud1:systemd] Starting Podman nextcloud-redis.service…
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:C 05 May 2025 10:33:33.025 * Redis version=7.4.3, bits=64, commit=00000000, modified=0, pid=1, just started
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.031 * Server initialized
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.031 * Reading RDB base file on AOF loading…
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.032 * RDB memory usage when created 0.90 Mb
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.033 * DB loaded from base file appendonly.aof.1.base.rdb: 0.001 seconds
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.372 * DB loaded from incr file appendonly.aof.1.incr.aof: 0.339 seconds
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.372 * DB loaded from append only file: 0.341 seconds
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.372 * Opening AOF incr file appendonly.aof.1.incr.aof on server start
2025-05-05T12:33:33+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:33:33.372 * Ready to accept connections tcp
2025-05-05T12:33:34+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:34+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2025-05-05T12:33:34+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:34+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.21+maria~ubu2004 started.
2025-05-05T12:33:34+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:34+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2025-05-05T12:33:34+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:34 0 [Note] InnoDB: Completed initialization of buffer pool
2025-05-05T12:33:35+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:35 0 [Note] InnoDB: 128 rollback segments are active.
2025-05-05T12:33:35+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:35 0 [Note] InnoDB: 10.6.21 started; log sequence number 84666969; transaction id 309392
2025-05-05T12:33:35+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:35 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2025-05-05T12:33:35+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:35 0 [Note] Server socket created on IP: ‘::’.
2025-05-05T12:33:35+02:00 [1:nextcloud1:systemd] Started libcrun container.
2025-05-05T12:33:36+02:00 [1:nextcloud1:nextcloud-app] Configuring Redis as session handler
2025-05-05T12:33:36+02:00 [1:nextcloud1:podman] 06091d6689b7e1a77dff10c520c14e0d8939e8d64ce1f7b8ef79442ba8bbbd27
2025-05-05T12:33:36+02:00 [1:nextcloud1:nextcloud-app] => Searching for hook scripts (*.sh) to run, located in the folder “/docker-entrypoint-hooks.d/before-starting”
2025-05-05T12:33:36+02:00 [1:nextcloud1:nextcloud-app] ==> Skipped: the “before-starting” folder is empty (or does not exist)
2025-05-05T12:33:36+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:33:36 0 [Note] InnoDB: Buffer pool(s) load completed at 250505 10:33:36
2025-05-05T12:33:37+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:33:37,682 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.
2025-05-05T12:33:37+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:33:37,682 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.
2025-05-05T12:33:38+02:00 [1:nextcloud1:nextcloud-app] crond: crond (busybox 1.37.0) started, log level 8
2025-05-05T12:33:39+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:33:39] NOTICE: fpm is running, pid 52
2025-05-05T12:33:39+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:33:39] NOTICE: ready to handle connections
Log after saving in setup panel in clauster-admin
Log
2025-05-05T12:35:33+02:00 [1:nextcloud1:nextcloud-app] => Searching for hook scripts (.sh) to run, located in the folder “/docker-entrypoint-hooks.d/before-starting”
2025-05-05T12:35:33+02:00 [1:nextcloud1:nextcloud-app] ==> Skipped: the “before-starting” folder is empty (or does not exist)
2025-05-05T12:35:34+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:35:34,264 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.
2025-05-05T12:35:34+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:35:34,264 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.
2025-05-05T12:35:35+02:00 [1:nextcloud1:nextcloud-app] crond: crond (busybox 1.37.0) started, log level 8
2025-05-05T12:35:35+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:35:35] NOTICE: fpm is running, pid 52
2025-05-05T12:35:35+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:35:35] NOTICE: ready to handle connections
2025-05-05T12:35:50+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/79ab9bf8-f82c-4dc6-b83d-3bdb61e7c239: get-configuration/20read is starting
2025-05-05T12:35:56+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/79ab9bf8-f82c-4dc6-b83d-3bdb61e7c239: action “get-configuration” status is “completed” (0) at step 20read
2025-05-05T12:35:59+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0dc8b3ef-8251-4b06-95d1-ce7ea57b3bda: configure-module/20configure is starting
2025-05-05T12:35:59+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0dc8b3ef-8251-4b06-95d1-ce7ea57b3bda: configure-module/30traefik is starting
2025-05-05T12:36:09+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0dc8b3ef-8251-4b06-95d1-ce7ea57b3bda: configure-module/40migrate is starting
2025-05-05T12:36:09+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0dc8b3ef-8251-4b06-95d1-ce7ea57b3bda: configure-module/50systemd is starting
2025-05-05T12:36:09+02:00 [1:nextcloud1:systemd] Reloading.
2025-05-05T12:36:10+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:10 32 [Warning] Aborted connection 32 to db: ‘nextcloud’ user: ‘nextcloud’ host: ‘127.0.0.1’ (Got an error reading communication packets)
2025-05-05T12:36:10+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:36:10] NOTICE: exiting, bye-bye!
2025-05-05T12:36:10+02:00 [1:nextcloud1:systemd] Stopping Podman nextcloud-db.service…
2025-05-05T12:36:11+02:00 [1:nextcloud1:systemd] libpod-dc60d1ee9a9a1a8eafad6526fee6971cff98ced55b21b6e156fda12242a3e854.scope: Consumed 31.866s CPU time.
2025-05-05T12:36:11+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:11 0 [Note] InnoDB: Starting shutdown…
2025-05-05T12:36:11+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:11 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2025-05-05T12:36:12+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:12 0 [Note] mariadbd: Shutdown complete
2025-05-05T12:36:12+02:00 [1:nextcloud1:systemd] libpod-70ac3d7cd00e3cc7bd043a854e25012a987a0b21a911495910fd8f1a883a5b03.scope: Consumed 4.097s CPU time.
2025-05-05T12:36:13+02:00 [1:nextcloud1:podman] 791fe5631f777a1a953f3045d58648935cbdaa43a03f6e415c376e624b8b1021
2025-05-05T12:36:13+02:00 [1:nextcloud1:podman] 70ac3d7cd00e3cc7bd043a854e25012a987a0b21a911495910fd8f1a883a5b03
2025-05-05T12:36:14+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-app.service.
2025-05-05T12:36:15+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-notify_push.service.
2025-05-05T12:36:15+02:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Consumed 3.576s CPU time.
2025-05-05T12:36:15+02:00 [1:nextcloud1:podman] 70ac3d7cd00e3cc7bd043a854e25012a987a0b21a911495910fd8f1a883a5b03
2025-05-05T12:36:15+02:00 [1:nextcloud1:systemd] nextcloud-db.service: Consumed 3.585s CPU time.
2025-05-05T12:36:15+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:36:15.964 * User requested shutdown…
2025-05-05T12:36:16+02:00 [1:nextcloud1:systemd] libpod-62e13bc3d79cec8e87efdd3b84e2c27911039c6ede55672d7f75673bf6d911b4.scope: Consumed 5.216s CPU time.
2025-05-05T12:36:16+02:00 [1:nextcloud1:conmon] conmon 62e13bc3d79cec8e87ef : Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1008.slice/user@1008.service/user.slice/user-libpod_pod_1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd.slice/libpod-62e13bc3d79cec8e87efdd3b84e2c27911039c6ede55672d7f75673bf6d911b4.scope/container/memory.events
2025-05-05T12:36:16+02:00 [1:nextcloud1:podman] 62e13bc3d79cec8e87efdd3b84e2c27911039c6ede55672d7f75673bf6d911b4
2025-05-05T12:36:17+02:00 [1:nextcloud1:podman] 62e13bc3d79cec8e87efdd3b84e2c27911039c6ede55672d7f75673bf6d911b4
2025-05-05T12:36:17+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-redis.service.
2025-05-05T12:36:17+02:00 [1:nextcloud1:systemd] nextcloud-redis.service: Consumed 3.778s CPU time.
2025-05-05T12:36:17+02:00 [1:nextcloud1:systemd] Stopping Podman nextcloud.service…
2025-05-05T12:36:19+02:00 [1:nextcloud1:systemd] Removed slice cgroup user-libpod_pod_1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd.slice.
2025-05-05T12:36:19+02:00 [1:nextcloud1:systemd] user-libpod_pod_1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd.slice: Consumed 2min 13.529s CPU time.
2025-05-05T12:36:19+02:00 [1:nextcloud1:podman] nextcloud
2025-05-05T12:36:19+02:00 [1:nextcloud1:systemd] user-libpod_pod_1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd.slice: Failed to open /run/user/1008/systemd/transient/user-libpod_pod_1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd.slice: No such file or directory
2025-05-05T12:36:19+02:00 [1:nextcloud1:podman] 1dd02508045ca87830a195b4dbc1684a40ae3e62b400f406f594f6fb388b28bd
2025-05-05T12:36:19+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud.service.
2025-05-05T12:36:20+02:00 [1:nextcloud1:systemd] Created slice cgroup user-libpod_pod_7ef27ba315eccea448bf1173917ae6d873da46308a7536a3be6b654878a6bccb.slice.
2025-05-05T12:36:21+02:00 [1:nextcloud1:podman] 7ef27ba315eccea448bf1173917ae6d873da46308a7536a3be6b654878a6bccb
2025-05-05T12:36:22+02:00 [1:nextcloud1:systemd] Started libcrun container.
2025-05-05T12:36:22+02:00 [1:nextcloud1:podman] nextcloud
2025-05-05T12:36:22+02:00 [1:nextcloud1:systemd] Started Podman nextcloud.service.
2025-05-05T12:36:22+02:00 [1:nextcloud1:systemd] Starting Podman nextcloud-db.service…
2025-05-05T12:36:22+02:00 [1:nextcloud1:systemd] Starting Podman nextcloud-redis.service…
2025-05-05T12:36:24+02:00 [1:nextcloud1:nextcloud-redis] 1:C 05 May 2025 10:36:24.879 * Redis version=7.4.3, bits=64, commit=00000000, modified=0, pid=1, just started
2025-05-05T12:36:24+02:00 [1:nextcloud1:nextcloud-redis] 1:C 05 May 2025 10:36:24.879 * Configuration loaded
2025-05-05T12:36:24+02:00 [1:nextcloud1:podman] 2bc087f3a151d2de9428b50cc65aa9832285a36b6c8860f107520d909b4e1dc5
2025-05-05T12:36:24+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:36:24.882 * Running mode=standalone, port=6379.
2025-05-05T12:36:24+02:00 [1:nextcloud1:podman] 314f0f8b7346495eccb6178847f35f6316f8c6d495b20d9e7dd3985eedfb239b
2025-05-05T12:36:24+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:36:24.883 * Reading RDB base file on AOF loading…
2025-05-05T12:36:25+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:36:25.840 * DB loaded from append only file: 0.958 seconds
2025-05-05T12:36:26+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:26 0 [Note] Starting MariaDB 10.6.21-MariaDB-ubu2004 source revision 066e8d6aeabc13242193780341e0f845528105de server_uid Qyukua9fvcgXJncqD784b+yOZfI= as process 1
2025-05-05T12:36:26+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:26 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2025-05-05T12:36:26+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:26 0 [Note] InnoDB: Completed initialization of buffer pool
2025-05-05T12:36:26+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:26 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2025-05-05T12:36:26+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:26 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2025-05-05T12:36:26+02:00 [1:nextcloud1:systemd] Started libcrun container.
2025-05-05T12:36:27+02:00 [1:nextcloud1:nextcloud-app] Configuring Redis as session handler
2025-05-05T12:36:27+02:00 [1:nextcloud1:podman] 00d5741ef961e5023a507ee4c60400f98f8d3cbe11e3552c3a04856fd92b6820
2025-05-05T12:36:27+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:36:27 0 [Note] InnoDB: Buffer pool(s) load completed at 250505 10:36:27
2025-05-05T12:36:27+02:00 [1:nextcloud1:nextcloud-app] => Searching for hook scripts (.sh) to run, located in the folder “/docker-entrypoint-hooks.d/before-starting”
2025-05-05T12:36:27+02:00 [1:nextcloud1:nextcloud-app] ==> Skipped: the “before-starting” folder is empty (or does not exist)
2025-05-05T12:36:28+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:36:28,438 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.
2025-05-05T12:36:28+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:36:28,438 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.
2025-05-05T12:36:29+02:00 [1:nextcloud1:nextcloud-app] crond: crond (busybox 1.37.0) started, log level 8
2025-05-05T12:36:29+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:36:29] NOTICE: fpm is running, pid 52
2025-05-05T12:36:29+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:36:29] NOTICE: ready to handle connections
2025-05-05T12:37:25+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:37:25.026 * 10000 changes in 60 seconds. Saving…
2025-05-05T12:37:25+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:37:25.027 * Background saving started by pid 17
2025-05-05T12:37:25+02:00 [1:nextcloud1:nextcloud-redis] 17:C 05 May 2025 10:37:25.079 * DB saved on disk
2025-05-05T12:37:25+02:00 [1:nextcloud1:nextcloud-redis] 17:C 05 May 2025 10:37:25.080 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2025-05-05T12:37:25+02:00 [1:nextcloud1:nextcloud-redis] 1:M 05 May 2025 10:37:25.129 * Background saving terminated with success
2025-05-05T12:38:19+02:00 [1:nextcloud1:systemd] nextcloud-app.service: start-post operation timed out. Terminating.
2025-05-05T12:38:20+02:00 [1:nextcloud1:nextcloud-db] 2025-05-05 10:38:19 19 [Warning] Aborted connection 19 to db: ‘nextcloud’ user: ‘nextcloud’ host: ‘127.0.0.1’ (Got an error reading communication packets)
2025-05-05T12:38:20+02:00 [1:nextcloud1:systemd] nextcloud-app.service: Control process exited, code=killed, status=15/TERM
2025-05-05T12:38:20+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:38:20] NOTICE: Terminating …
2025-05-05T12:38:20+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:38:20] NOTICE: exiting, bye-bye!
2025-05-05T12:38:21+02:00 [1:nextcloud1:systemd] libpod-00d5741ef961e5023a507ee4c60400f98f8d3cbe11e3552c3a04856fd92b6820.scope: Consumed 1min 25.737s CPU time.
2025-05-05T12:38:23+02:00 [1:nextcloud1:agent@nextcloud1] Job for nextcloud-app.service failed because a timeout was exceeded.
2025-05-05T12:38:23+02:00 [1:nextcloud1:podman] 00d5741ef961e5023a507ee4c60400f98f8d3cbe11e3552c3a04856fd92b6820
2025-05-05T12:38:23+02:00 [1:nextcloud1:agent@nextcloud1] See “systemctl --user status nextcloud-app.service” and “journalctl --user -xeu nextcloud-app.service” for details.
2025-05-05T12:38:23+02:00 [1:nextcloud1:systemd] Starting Podman nextcloud-notify_push.service…
2025-05-05T12:38:23+02:00 [1:nextcloud1:systemd] nextcloud-app.service: Scheduled restart job, restart counter is at 1.
2025-05-05T12:38:23+02:00 [1:nextcloud1:systemd] Starting Podman nextcloud-app.service…
2025-05-05T12:38:25+02: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
2025-05-05T12:38:25+02:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Control process exited, code=exited, status=125/n/a
2025-05-05T12:38:26+02:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Failed with result ‘exit-code’.
2025-05-05T12:38:26+02:00 [1:nextcloud1:systemd] Failed to start Podman nextcloud-nginx.service.
2025-05-05T12:38:26+02:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Consumed 3.505s CPU time.
2025-05-05T12:38:26+02:00 [1:nextcloud1:agent@nextcloud1] Job for nextcloud-nginx.service failed because the control process exited with error code.
2025-05-05T12:38:26+02:00 [1:nextcloud1:agent@nextcloud1] See “systemctl --user status nextcloud-nginx.service” and “journalctl --user -xeu nextcloud-nginx.service” for details.
2025-05-05T12:38:27+02:00 [1:nextcloud1:systemd] Stopped Podman nextcloud-nginx.service.
2025-05-05T12:38:27+02:00 [1:nextcloud1:systemd] nextcloud-nginx.service: Consumed 3.505s CPU time.
2025-05-05T12:38:27+02:00 [1:nextcloud1:podman] ccc8e1d2523d81dc92599969a84a476c7a9c2ad1bf9138b31b5b01c1e116a9cc
2025-05-05T12:38:27+02:00 [1:nextcloud1:systemd] Started Podman nextcloud-notify_push.service.
2025-05-05T12:38:28+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0dc8b3ef-8251-4b06-95d1-ce7ea57b3bda: action “configure-module” status is “aborted” (1) at step 50systemd
2025-05-05T12:38:28+02:00 [1:nextcloud1:nextcloud-notify_push] [2025-05-05 10:38:28.202699 +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)
2025-05-05T12:38:29+02:00 [1:nextcloud1:systemd] Started libcrun container.
2025-05-05T12:38:29+02:00 [1:nextcloud1:podman] d8250638e3dc2511fc5c959bd1e17800a99488ffad05aa55c4e1b320e351bc02
2025-05-05T12:38:29+02:00 [1:nextcloud1:nextcloud-app] Configuring Redis as session handler
2025-05-05T12:38:30+02:00 [1:nextcloud1:nextcloud-app] => Searching for hook scripts (*.sh) to run, located in the folder “/docker-entrypoint-hooks.d/before-starting”
2025-05-05T12:38:30+02:00 [1:nextcloud1:nextcloud-app] ==> Skipped: the “before-starting” folder is empty (or does not exist)
2025-05-05T12:38:31+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:38:31,521 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.
2025-05-05T12:38:31+02:00 [1:nextcloud1:nextcloud-app] 2025-05-05 10:38:31,521 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.
2025-05-05T12:38:32+02:00 [1:nextcloud1:nextcloud-app] crond: crond (busybox 1.37.0) started, log level 8
2025-05-05T12:38:33+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:38:33] NOTICE: fpm is running, pid 52
2025-05-05T12:38:33+02:00 [1:nextcloud1:nextcloud-app] [05-May-2025 10:38:33] NOTICE: ready to handle connections
Did you try the following restart command?
systemctl --user restart nextcloud.service nextcloud-redis.service nextcloud-db.service nextcloud-app.service nextcloud-nginx.service nextcloud-notify_push.service
Let’s check if the containers are running:
[root@ns8rockytest ~]# runagent -m nextcloud1 podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cb697f967f8d localhost/podman-pause:5.2.2-1743105461 26 hours ago Up 26 hours 127.0.0.1:20011->80/tcp d3f958f4bd82-infra
f7411475dbdf docker.io/library/mariadb:10.6.21 mariadbd 26 hours ago Up 26 hours 127.0.0.1:20011->80/tcp, 3306/tcp nextcloud-db
1f869e18a804 docker.io/library/redis:7.4.3-alpine --appendonly yes 26 hours ago Up 26 hours 127.0.0.1:20011->80/tcp, 6379/tcp nextcloud-redis
b2bc81117e92 ghcr.io/nethserver/nextcloud-app:1.4.2 /usr/bin/supervis... 26 hours ago Up 26 hours 127.0.0.1:20011->80/tcp, 9000/tcp nextcloud-app
827dca355f08 docker.io/library/nginx:1.28.0-alpine nginx -g daemon o... 26 hours ago Up 26 hours 127.0.0.1:20011->80/tcp, 80/tcp nextcloud-nginx
34e72e2fadb3 ghcr.io/nethserver/nextcloud-notify_push:1.4.2 /notify_push 26 hours ago Up 26 hours 127.0.0.1:20011->80/tcp, 7867/tcp nextcloud-notify_push
runagent -m nextcloud1 podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7f29912e9b9d localhost/podman-pause:5.2.2-1743105461 25 minutes ago Up 25 minutes 127.0.0.1:20007->80/tcp 7ef27ba315ec-infra
2bc087f3a151 docker.io/library/redis:7.4.3-alpine --appendonly yes 25 minutes ago Up 25 minutes 127.0.0.1:20007->80/tcp, 6379/tcp nextcloud-redis
314f0f8b7346 docker.io/library/mariadb:10.6.21 mariadbd 25 minutes ago Up 25 minutes 127.0.0.1:20007->80/tcp, 3306/tcp nextcloud-db
ccc8e1d2523d ghcr.io/nethserver/nextcloud-notify_push:1.4.2 /notify_push 23 minutes ago Up 23 minutes 127.0.0.1:20007->80/tcp, 7867/tcp nextcloud-notify_push
21c59399a4d8 ghcr.io/nethserver/nextcloud-app:1.4.2 /usr/bin/supervis... About a minute ago Up About a minute 127.0.0.1:20007->80/tcp, 9000/tcp nextcloud-app
[root@neth ~]# runagent -m nextcloud1 systemctl --user try-reload-or-restart nextcloud-nginx
[root@neth ~]# runagent -m nextcloud1 podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7f29912e9b9d localhost/podman-pause:5.2.2-1743105461 31 minutes ago Up 31 minutes 127.0.0.1:20007->80/tcp 7ef27ba315ec-infra
2bc087f3a151 docker.io/library/redis:7.4.3-alpine --appendonly yes 31 minutes ago Up 31 minutes 127.0.0.1:20007->80/tcp, 6379/tcp nextcloud-redis
314f0f8b7346 docker.io/library/mariadb:10.6.21 mariadbd 31 minutes ago Up 31 minutes 127.0.0.1:20007->80/tcp, 3306/tcp nextcloud-db
ccc8e1d2523d ghcr.io/nethserver/nextcloud-notify_push:1.4.2 /notify_push 29 minutes ago Up 29 minutes 127.0.0.1:20007->80/tcp, 7867/tcp nextcloud-notify_push
91bea93c1e8e ghcr.io/nethserver/nextcloud-app:1.4.2 /usr/bin/supervis... About a minute ago Up About a minute 127.0.0.1:20007->80/tcp, 9000/tcp nextcloud-app
Let’s check the status of service nextcloud-nginx:
runagent -m nextcloud1 systemctl --user status nextcloud-nginx
Let’s check the permissions of the service file:
ls -l /home/nextcloud1/.config/systemd/user/nextcloud-nginx.service
[root@neth ~]# runagent -m nextcloud1 podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7f29912e9b9d localhost/podman-pause:5.2.2-1743105461 31 minutes ago Up 31 minutes 127.0.0.1:20007->80/tcp 7ef27ba315ec-infra
2bc087f3a151 docker.io/library/redis:7.4.3-alpine --appendonly yes 31 minutes ago Up 31 minutes 127.0.0.1:20007->80/tcp, 6379/tcp nextcloud-redis
314f0f8b7346 docker.io/library/mariadb:10.6.21 mariadbd 31 minutes ago Up 31 minutes 127.0.0.1:20007->80/tcp, 3306/tcp nextcloud-db
ccc8e1d2523d ghcr.io/nethserver/nextcloud-notify_push:1.4.2 /notify_push 29 minutes ago Up 29 minutes 127.0.0.1:20007->80/tcp, 7867/tcp nextcloud-notify_push
91bea93c1e8e ghcr.io/nethserver/nextcloud-app:1.4.2 /usr/bin/supervis... About a minute ago Up About a minute 127.0.0.1:20007->80/tcp, 9000/tcp nextcloud-app
[root@neth ~]# runagent -m nextcloud1 systemctl --user status nextcloud-nginx
○ nextcloud-nginx.service - Podman nextcloud-nginx.service
Loaded: loaded (/home/nextcloud1/.config/systemd/user/nextcloud-nginx.service; enabled; preset: disabled)
Active: inactive (dead) (Result: exit-code) since Mon 2025-05-05 13:13:54 CEST; 17s ago
Process: 37618 ExecStartPre=/bin/rm -f /run/user/1008/nextcloud-.pid /run/user/1008/nextcloud-nginx.ctr-id (code=exited, status=0/SUCCESS)
Process: 37619 ExecStart=/usr/bin/podman run --conmon-pidfile /run/user/1008/nextcloud-nginx.pid --cidfile /run/user/1008/nextcloud-nginx.ctr-id --cgroups=no-conmon --pod-id-file /run/user/1008/nextcloud.pod-id --replace -d >
Process: 37633 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/user/1008/nextcloud-nginx.ctr-id (code=exited, status=0/SUCCESS)
CPU: 454ms
[root@neth ~]# ls -l /home/nextcloud1/.config/systemd/user/nextcloud-nginx.service
-rw-r--r-- 1 nextcloud1 nextcloud1 830 May 5 11:48 /home/nextcloud1/.config/systemd/user/nextcloud-nginx.service
[root@neth ~]# cat /home/nextcloud1/.config/systemd/user/nextcloud-nginx.service
[Unit]
Description=Podman nextcloud-nginx.service
After=nextcloud-app.service
[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
EnvironmentFile=%S/state/environment
Restart=always
TimeoutStopSec=120
ExecStartPre=/bin/rm -f %t/nextcloud-.pid %t/nextcloud-nginx.ctr-id
ExecStart=/usr/bin/podman run --conmon-pidfile %t/nextcloud-nginx.pid --cidfile %t/nextcloud-nginx.ctr-id --cgroups=no-conmon --pod-id-file %t/nextcloud.pod-id --replace -d --name nextcloud-nginx --env-file=%S/state/config.env -v %S/state/nginx.conf:/etc/nginx/nginx.conf:ro,Z --volumes-from nextcloud-app:rw,z ${NGINX_IMAGE}
ExecStop=/usr/bin/podman stop --ignore --cidfile %t/nextcloud-nginx.ctr-id -t 10
ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile %t/nextcloud-nginx.ctr-id
PIDFile=%t/nextcloud-nginx.pid
Type=forking
[Install]
WantedBy=default.target
nextcloud-app.service is loaded bat non enabled?
[root@neth ~]# runagent -m nextcloud1 systemctl --user status nextcloud-app
● nextcloud-app.service - Podman nextcloud-app.service
Loaded: loaded (/home/nextcloud1/.config/systemd/user/nextcloud-app.service; enabled; preset: disabled)
Active: activating (start-post) since Mon 2025-05-05 13:17:36 CEST; 27s ago
Process: 39460 ExecStartPre=/bin/rm -f /run/user/1008/nextcloud-app.pid /run/user/1008/nextcloud-app.ctr-id (code=exited, status=0/SUCCESS)
Process: 39466 ExecStartPre=runagent discover-smarthost (code=exited, status=0/SUCCESS)
Process: 39503 ExecStart=/usr/bin/podman run --conmon-pidfile /run/user/1008/nextcloud-app.pid --cidfile /run/user/1008/nextcloud-app.ctr-id --cgroups=no-conmon --pod-id-file /run/user/1008/nextcloud.pod-id --replace -d --na>
Process: 39554 ExecStartPost=runagent wait-startup (code=exited, status=0/SUCCESS)
Process: 39629 ExecStartPost=runagent setup-smtp (code=exited, status=0/SUCCESS)
Main PID: 39531 (conmon); Control PID: 39718 (python3)
Tasks: 13 (limit: 74652)
Memory: 46.7M
CPU: 7.104s
CGroup: /user.slice/user-1008.slice/user@1008.service/app.slice/nextcloud-app.service
├─39531 /usr/bin/conmon --api-version 1 -c 9322a4b3920ca3367743f9ad618fcf75922798fa93cbc282da70b0e4380e617b -u 9322a4b3920ca3367743f9ad618fcf75922798fa93cbc282da70b0e4380e617b -r /usr/bin/crun -b /home/nextcloud1/.l>
├─39718 python3 /home/nextcloud1/.config/bin/setup-ldap
├─39756 podman exec --user www-data nextcloud-app php ./occ ldap:show-config s01
└─39767 /usr/bin/conmon --api-version 1 -c 9322a4b3920ca3367743f9ad618fcf75922798fa93cbc282da70b0e4380e617b -u 27c1005e3fee8555fa1221bff3830071a7cc9bf40bfcd94acac2de83de339c5f -r /usr/bin/crun -b /home/nextcloud1/.l>
[root@neth ~]#
It should be enabled, just the preset is disabled, to check it:
[root@ns8rockytest ~]# runagent -m nextcloud1 systemctl --user is-enabled nextcloud-app
enabled
It seems nextcloud-nginx is not coming up, so please also check the service status of nextcloud-nginx:
runagent -m nextcloud1 systemctl --user status nextcloud-nginx
[root@neth ~]# runagent -m nextcloud1 systemctl --user is-enabled nextcloud-app enabled
enabled
Failed to get unit file state for enabled.service: No such file or directory
[root@neth ~]# runagent -m nextcloud1 systemctl --user status nextcloud-nginx
○ nextcloud-nginx.service - Podman nextcloud-nginx.service
Loaded: loaded (/home/nextcloud1/.config/systemd/user/nextcloud-nginx.service; enabled; preset: disabled)
Active: inactive (dead) (Result: exit-code) since Mon 2025-05-05 15:04:07 CEST; 15s ago
Process: 90900 ExecStartPre=/bin/rm -f /run/user/1008/nextcloud-.pid /run/user/1008/nextcloud-nginx.ctr-id (code=exited, status=0/SUCCESS)
Process: 90902 ExecStart=/usr/bin/podman run --conmon-pidfile /run/user/1008/nextcloud-nginx.pid --cidfile /run/user/1008/nextcloud-nginx.ctr-id --cgroups=no>
Process: 90914 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/user/1008/nextcloud-nginx.ctr-id (code=exited, status=0/SUCCESS)
CPU: 1.307s
The “enabled” at the end of the command is wrong, it’s just
runagent -m nextcloud1 systemctl --user is-enabled nextcloud-app
Thanks for the support
-
I have disabled all the installed apps.
-
I tried to enable one at a time trying to restart the services with
runagent -m nextcloud1 systemctl --user restart nextcloud nextcloud-{redis,db,app,nginx}
The problem is the basic app encryption
Also by disabling all other apps and activating only Encryption Nextcloud-app and Nextcloud-nginx don’t restart.
On the contrary, by disabling only Encryption, I can enable all the apps I want without the services being interrupted and even by restarting the server all services are active smoothly.
The problem is quite worrying, not being able to activate file encryption is not a good privacy oriented service.
What can it depend on? How could I solve it?
Thanks again for the support
1 Like
You’re welcome.
Great, that you found the issue but I tested the “Default encryption module” now and here a restart of Nextcloud is possible without errors. I enabled it as explained in the Nextcloud docs: Encryption configuration — Nextcloud latest Administration Manual latest documentation
Hi, thank you for your support and for the test you performed,
Unfortunately I followed the procedure in the Nextcloud docs to the letter, but the problem persists.
I decided to start again from a new NC instance:
-
I deleted the old instance of NC
-
I added a new instance of NC.
-
in Cluster-admin I set Namehost, Password and Ldap.
-
in Cluster-admin I set CollaborateAPP.
-
I logged in to NC and added only “Default encryption module” as per guide Encryption configuration — Nextcloud latest Administration Manual latest documentation
-
performed logout
-
I login in NC → OK
-
I restart the Server and wait for all the APPs to be active again.
NC from anyway “Bad Gateway”
Have you tried restarting the server?
1 Like
Did you setup the Collabora App, it also needs a FQDN.
In the Nextcloud settings Collabora needs to be set.
Encryption needs to be enabled on the admin page first and then the app needs to be enabled.
I created a file to check if the encryption worked.
Yes, here it works after a VM restart.
1 Like
Thank you for the tests you performed.
I decided to try using the “Pre-built image” to eliminate any doubts about my configuration.
I just performed exactly the steps indicated in the documentation: Installation — NS8 documentation
I proceed with installation and setup :
LDAP server - OK
Mail server - OK
Crowdsec - OK
Collabora app - OK
I proceed with the installation of Nextcloud OK
proceed with the setup of Nextcloud the task module/nextcloud2/configure-module fails
In the Log I read:
action “configure-module” status is “aborted” (1) at step 90apps_management
2025-05-09T10:40:52+02:00 [1:nextcloud2:agent@nextcloud2] task/module/nextcloud2/da8ab122-fa15-4658-b8a9-c25a9164122b: configure-module/90apps_management is starting
...
2025-05-09T10:40:58+02:00 [1:nextcloud2:agent@nextcloud2] task/module/nextcloud2/da8ab122-fa15-4658-b8a9-c25a9164122b: action "configure-module" status is "aborted" (1) at step 90apps_management
Then I proceed with the identification of the problem by observing what “90apps_management” does:
[root@neth ~]# cat /home/nextcloud2/.config/actions/configure-module/90apps_management
#!/bin/bash
#
# Copyright (C) 2024 Nethesis S.r.l.
# SPDX-License-Identifier: GPL-3.0-or-later
#
# with nextcloud 28 the logreader app is compatible only with `file` log type
# see https://github.com/nextcloud/server/issues/45517
# Failed to get an iterator for log entries: Logreader application only supports "file" log_type
occ app:disable logreader
# install and configure files high performance backend
occ app:install notify_push
occ app:enable notify_push
occ -n notify_push:setup http://127.0.0.1/push
So I execute the individual commands to understand where the error occurs:
[root@neth ~]# runagent -m nextcloud2 occ app:install notify_push
notify_push already installed
[root@neth ~]# runagent -m nextcloud2 occ app:enable notify_push
notify_push already enabled
[root@neth ~]# runagent -m nextcloud2 occ -n notify_push:setup http://127.0.0.1/push
✓ redis is configured
🗴 using unencrypted http for push server is strongly discouraged
✓ push server is receiving redis messages
✓ push server can load mount info from database
✓ push server can connect to the Nextcloud server
✓ push server is a trusted proxy
🗴 push server (version 1.0.0) is not the same version as the app (version 1.1.0).
So currently push server (version 1.0.0) is not the same version as the app (version 1.1.0).
How can I solve it? Thanks for the help
1 Like