Nextcloud(Helm) dont come up after Update(Nextcloud + MicroK8s)

[X9n4]

Nextcloud-Helm: https://nextcloud.github.io/helm/
Nextcloud version (eg, 20.0.5): 28.0.4-apache
Operating system and version (eg, Ubuntu 20.04): MicroK8s v1.28.7 on Debian 12.5
Apache or nginx version (eg, Apache 2.4.25): from Helm Repo
PHP version (eg, 7.4): from Helm Repo
MariaDB: 10.11.7

The issue you are facing:

Is this the first time you’ve seen this error? (Y/N):

Steps to replicate it:

1. Nextcloud-Helm was running on my MicroK8s-Cluster
2. Upgrade Debian, MicroK8s and Nextcloud-Helm
3. Nextcloud upgrade and then CrashLoopBackOff

The output of your Nextcloud log in Admin > Logging:

can´t open WebUI

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'htaccess.RewriteBase' => '/',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'apps_paths' => 
  array (
    0 => 
    array (
      'path' => '/var/www/html/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 => 
    array (
      'path' => '/var/www/html/custom_apps',
      'url' => '/custom_apps',
      'writable' => true,
    ),
  ),
  'passwordsalt' => 'axxxxxxxxxxxxxxxxxxxxxxxxxxxxxa',
  'secret' => 'UxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN',
  'trusted_domains' => 
  array (
    0 => 'localhost',
    1 => 'cloud.mydomain.com',
    2 => 'cloud1.mydomain.com',
    3 => 'cloud.home.domain',
  ),
  'datadirectory' => '/var/www/html/data',
  'dbtype' => 'mysql',
  'version' => '28.0.4.1',
  'overwrite.cli.url' => 'http://localhost',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextcloud-helm-mariadb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => 'Lxxxxxxxxxxxxxxxz',
  'installed' => true,
  'instanceid' => 'oxqrcdtmemv9',
  'default_language' => 'de',
  'default_locale' => 'de_DE',
  'logfile' => '/var/www/html/log/nextcloud.log',
  'loglevel' => 2,
  'maintenance' => false,
  'overwritehost' => 'cloud.mydomain.com',
  'overwriteprotocol' => 'https',
);

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

can´t exec in container

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.
Click me to view at pastebin

The output from kubectl:

kubectl get all,ingress,pvc,pv --all-namespaces -o wide | grep next                                                                                                                                           
nextcloud-helm        pod/nextcloud-helm-mariadb-0                      1/1     Running             0                35m    10.1.133.182      cluster-node01     <none>           <none>
nextcloud-helm        pod/nextcloud-helm-f6fcfcf66-smlrz                1/1     Running             0                35m    10.1.133.139      cluster-node01     <none>           <none>
nextcloud-helm        service/nextcloud-helm              ClusterIP      10.152.183.132   <none>            8080/TCP                                                                                    35m    app.kubernetes.io/component=app,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=nextcloud
nextcloud-helm        service/nextcloud-helm-mariadb      ClusterIP      10.152.183.128   <none>            3306/TCP                                                                                    35m    app.kubernetes.io/component=primary,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=mariadb
nextcloud-helm        deployment.apps/nextcloud-helm               1/1     1            1           35m    nextcloud                                     nextcloud:28.0.4-apache                                                                                                                                         app.kubernetes.io/component=app,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=nextcloud
nextcloud-helm        replicaset.apps/nextcloud-helm-f6fcfcf66                1         1         1       35m    nextcloud                                     nextcloud:28.0.4-apache                                                                                                                                         app.kubernetes.io/component=app,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=nextcloud,pod-template-hash=f6fcfcf66
nextcloud-helm   statefulset.apps/nextcloud-helm-mariadb   1/1     35m    mariadb      docker.io/bitnami/mariadb:10.11.7
nextcloud-helm   ingress.networking.k8s.io/nextcloud-helm      public   cloud.mydomain.com                                              127.0.0.1   80, 443   35m
nextcloud-helm        persistentvolumeclaim/nextcloud-helm-data-pv     Bound    nextcloud-helm-data-pv                     10Gi       RWO            microk8s-hostpath   35m    Filesystem
nextcloud-helm        persistentvolumeclaim/nextcloud-helm-html-pv     Bound    nextcloud-helm-html-pv                     10Gi       RWO            microk8s-hostpath   35m    Filesystem
nextcloud-helm        persistentvolumeclaim/nextcloud-helm-mysql-pv    Bound    nextcloud-helm-mysql-pv                    10Gi       RWO            microk8s-hostpath   35m    Filesystem
            persistentvolume/nextcloud-helm-data-pv                     10Gi       RWO            Retain           Bound      nextcloud-helm/nextcloud-helm-data-pv                                 35m    Filesystem
            persistentvolume/nextcloud-helm-html-pv                     10Gi       RWO            Retain           Bound      nextcloud-helm/nextcloud-helm-html-pv                                 35m    Filesystem
            persistentvolume/nextcloud-helm-mysql-pv                    10Gi       RWO            Retain           Bound      nextcloud-helm/nextcloud-helm-mysql-pv                                35m    Filesystem
            
kubectl logs -n nextcloud-helm pods/nextcloud-helm-f6fcfcf66-smlrz                                                                                                                                            
Defaulted container "nextcloud" out of: nextcloud, mariadb-isalive (init)
Initializing nextcloud 28.0.4.1 ...
Upgrading nextcloud from 28.0.3.2 ...

kubectl logs -n nextcloud-helm pods/nextcloud-helm-f6fcfcf66-smlrz                                                                                                                                            
Defaulted container "nextcloud" out of: nextcloud, mariadb-isalive (init)
Initializing nextcloud 28.0.4.1 ...
Upgrading nextcloud from 28.0.3.2 ...

kubectl logs -n nextcloud-helm pods/nextcloud-helm-f6fcfcf66-smlrz                                                                                                                                            
Defaulted container "nextcloud" out of: nextcloud, mariadb-isalive (init)
=> Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/before-starting
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.1.133.139. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.1.133.139. Set the 'ServerName' directive globally to suppress this message

kubectl get all,ingress,pvc,pv --all-namespaces -o wide | grep next                                                                                                                                           
nextcloud-helm        pod/nextcloud-helm-mariadb-0                      1/1     Running             0                50m    10.1.133.182      cluster-node01     <none>           <none>
nextcloud-helm        pod/nextcloud-helm-f6fcfcf66-smlrz                0/1     CrashLoopBackOff    6 (2m4s ago)     50m    10.1.133.139      cluster-node01     <none>           <none>
nextcloud-helm        service/nextcloud-helm              ClusterIP      10.152.183.132   <none>            8080/TCP                                                                                    50m    app.kubernetes.io/component=app,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=nextcloud
nextcloud-helm        service/nextcloud-helm-mariadb      ClusterIP      10.152.183.128   <none>            3306/TCP                                                                                    50m    app.kubernetes.io/component=primary,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=mariadb
nextcloud-helm        deployment.apps/nextcloud-helm               0/1     1            0           50m    nextcloud                                     nextcloud:28.0.4-apache                                                                                                                                         app.kubernetes.io/component=app,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=nextcloud
nextcloud-helm        replicaset.apps/nextcloud-helm-f6fcfcf66                1         1         0       50m    nextcloud                                     nextcloud:28.0.4-apache                                                                                                                                         app.kubernetes.io/component=app,app.kubernetes.io/instance=nextcloud-helm,app.kubernetes.io/name=nextcloud,pod-template-hash=f6fcfcf66
nextcloud-helm   statefulset.apps/nextcloud-helm-mariadb   1/1     50m    mariadb      docker.io/bitnami/mariadb:10.11.7
nextcloud-helm   ingress.networking.k8s.io/nextcloud-helm      public   cloud.mydomain.com                                              127.0.0.1   80, 443   50m
nextcloud-helm        persistentvolumeclaim/nextcloud-helm-data-pv     Bound    nextcloud-helm-data-pv                     10Gi       RWO            microk8s-hostpath   50m    Filesystem
nextcloud-helm        persistentvolumeclaim/nextcloud-helm-html-pv     Bound    nextcloud-helm-html-pv                     10Gi       RWO            microk8s-hostpath   50m    Filesystem
nextcloud-helm        persistentvolumeclaim/nextcloud-helm-mysql-pv    Bound    nextcloud-helm-mysql-pv                    10Gi       RWO            microk8s-hostpath   50m    Filesystem
            persistentvolume/nextcloud-helm-data-pv                     10Gi       RWO            Retain           Bound      nextcloud-helm/nextcloud-helm-data-pv                                 50m    Filesystem
            persistentvolume/nextcloud-helm-html-pv                     10Gi       RWO            Retain           Bound      nextcloud-helm/nextcloud-helm-html-pv                                 50m    Filesystem
            persistentvolume/nextcloud-helm-mysql-pv                    10Gi       RWO            Retain           Bound      nextcloud-helm/nextcloud-helm-mysql-pv                                50m    Filesystem

[X9n4]

After trying to solve the problem for days and then deciding to open a thread here, I continued my search here in the forum.

and came across the following thread:

Kubernetes Nextcloud POd doesn't start with HugePages enabled

I’m running microk8s single node and had nextcloud working great, then rebooted the machine and it won’t come back. I’m at a loss as there is not real logs. When I describe the pod I see an exit code 135 and that’s it. Name: nextcloud-app-668848b97b-xq4cv Namespace: nextcloud Priority: 0 Node: hv03/192.168.200.222 Start Time: Tue, 07 Jun 2022 12:14:50 -0400 Labels: app=nextcloud-app pod-template-hash=668848b97b service=nextcloud-service Annotations: cni.projectcalico.org/containerID: f5e9b9605…

This is exactly what solves my problem:

sudo sysctl vm.nr_hugepages=0

However, Mayastor -which I recently activated and forgot that this could be the problem- needs these hugepages. Does anyone have a solution for this?