Unable to start acces to nextcloud about nextcloud-snap HOT 2 CLOSED

● snap.nextcloud.apache.service - Service for snap application nextcloud.apache
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.apache.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-12-20 10:51:11 CET; 3min 54s ago
   Main PID: 11040 (run-httpd)
      Tasks: 3 (limit: 9477)
     Memory: 712.0K
        CPU: 647ms
     CGroup: /system.slice/snap.nextcloud.apache.service
             ├─11040 /bin/sh /snap/nextcloud/39212/bin/run-httpd -k start -DFOREGROUND
             ├─11103 /bin/sh /snap/nextcloud/39212/bin/setup-nextcloud
             └─14182 sleep 1

Dec 20 10:51:11 nextcloud systemd[1]: Started snap.nextcloud.apache.service - Service for snap application nextcloud.apache.
Dec 20 10:51:12 nextcloud nextcloud.apache[11040]: Making sure nextcloud is setup...
Dec 20 10:51:12 nextcloud nextcloud.apache[11103]: Waiting for PHP...

[Mon Dec 18 00:00:10.278675 2023] [ssl:warn] [pid 2772:tid 140074134885568] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 18 00:00:10.280799 2023] [lbmethod_heartbeat:notice] [pid 2772:tid 140074134885568] AH02282: No slotmem from mod_heartmonitor
[Mon Dec 18 00:00:10.281508 2023] [mpm_event:notice] [pid 2772:tid 140074134885568] AH00489: Apache/2.4.58 (Unix) OpenSSL/1.1.1 configured -- resuming normal operations
[Mon Dec 18 00:00:10.281566 2023] [core:notice] [pid 2772:tid 140074134885568] AH00094: Command line: 'httpd -d /snap/nextcloud/38457 -D EnableHTTPS -D EnableHSTS -D FOREGROUND'
[Mon Dec 18 00:00:10.310875 2023] [unixd:alert] [pid 2672767:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Mon Dec 18 00:00:10.310920 2023] [unixd:alert] [pid 2672769:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Mon Dec 18 00:00:10.310894 2023] [unixd:alert] [pid 2672768:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Mon Dec 18 00:00:16.609038 2023] [mpm_event:notice] [pid 2772:tid 140074134885568] AH00493: SIGUSR1 received.  Doing graceful restart
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Mon Dec 18 00:00:16.621535 2023] [ssl:warn] [pid 2772:tid 140074134885568] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 18 00:00:16.622153 2023] [lbmethod_heartbeat:notice] [pid 2772:tid 140074134885568] AH02282: No slotmem from mod_heartmonitor
[Mon Dec 18 00:00:16.622650 2023] [mpm_event:notice] [pid 2772:tid 140074134885568] AH00489: Apache/2.4.58 (Unix) OpenSSL/1.1.1 configured -- resuming normal operations
[Mon Dec 18 00:00:16.622683 2023] [core:notice] [pid 2772:tid 140074134885568] AH00094: Command line: 'httpd -d /snap/nextcloud/38457 -D EnableHTTPS -D EnableHSTS -D FOREGROUND'
[Mon Dec 18 00:00:16.626479 2023] [unixd:alert] [pid 2672947:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Mon Dec 18 00:00:16.627524 2023] [unixd:alert] [pid 2672949:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Mon Dec 18 00:00:16.632090 2023] [unixd:alert] [pid 2672948:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Mon Dec 18 00:03:25.835453 2023] [unixd:alert] [pid 2673436:tid 140074134885568] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Tue Dec 19 03:25:37.741552 2023] [mpm_event:notice] [pid 2772:tid 140074134885568] AH00491: caught SIGTERM, shutting down
[Tue Dec 19 03:28:09.786651 2023] [ssl:warn] [pid 2825661:tid 140298457576640] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Tue Dec 19 03:28:09.790170 2023] [ssl:warn] [pid 2825661:tid 140298457576640] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
[Tue Dec 19 03:28:09.790456 2023] [lbmethod_heartbeat:notice] [pid 2825661:tid 140298457576640] AH02282: No slotmem from mod_heartmonitor
[Tue Dec 19 03:28:09.791644 2023] [mpm_event:notice] [pid 2825661:tid 140298457576640] AH00489: Apache/2.4.58 (Unix) OpenSSL/1.1.1 configured -- resuming normal operations
[Tue Dec 19 03:28:09.791683 2023] [core:notice] [pid 2825661:tid 140298457576640] AH00094: Command line: 'httpd -d /snap/nextcloud/39212 -D EnableHTTPS -D EnableHSTS -D FOREGROUND'
[Tue Dec 19 03:28:09.807437 2023] [unixd:alert] [pid 2825664:tid 140298457576640] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Tue Dec 19 03:28:09.807474 2023] [unixd:alert] [pid 2825663:tid 140298457576640] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Tue Dec 19 03:28:09.807476 2023] [unixd:alert] [pid 2825662:tid 140298457576640] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Tue Dec 19 03:28:25.811812 2023] [unixd:alert] [pid 2826263:tid 140298457576640] AH02155: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
[Tue Dec 19 18:48:56.259793 2023] [proxy_fcgi:error] [pid 2825662:tid 140298185336576] [client 192.168.21.48:34562] AH01071: Got error 'Primary script unknown', referer: http://home.mrqt.fr/wp-login.php

● snap.nextcloud.php-fpm.service - Service for snap application nextcloud.php-fpm
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.php-fpm.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-12-20 10:51:12 CET; 3min 54s ago
   Main PID: 11258 (start-php-fpm)
      Tasks: 2 (limit: 9477)
     Memory: 448.0K
        CPU: 556ms
     CGroup: /system.slice/snap.nextcloud.php-fpm.service
             ├─11258 /bin/sh /snap/nextcloud/39212/bin/start-php-fpm
             └─14196 sleep 1

Dec 20 10:51:12 nextcloud systemd[1]: Started snap.nextcloud.php-fpm.service - Service for snap application nextcloud.php-fpm.
Dec 20 10:51:12 nextcloud nextcloud.php-fpm[11258]: Waiting for MySQL...

[18-Dec-2023 00:00:17] NOTICE: error log file re-opened
[18-Dec-2023 00:00:17] NOTICE: error log file re-opened
[19-Dec-2023 03:25:35] NOTICE: Terminating ...
[19-Dec-2023 03:25:35] NOTICE: exiting, bye-bye!
[19-Dec-2023 03:26:56] NOTICE: fpm is running, pid 2824874
[19-Dec-2023 03:26:56] NOTICE: ready to handle connections

× snap.nextcloud.mysql.service - Service for snap application nextcloud.mysql
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.mysql.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-12-20 10:51:18 CET; 3min 48s ago
   Duration: 1.134s
    Process: 12863 ExecStart=/usr/bin/snap run nextcloud.mysql (code=exited, status=1/FAILURE)
   Main PID: 12863 (code=exited, status=1/FAILURE)
        CPU: 684ms

Dec 20 10:51:18 nextcloud systemd[1]: snap.nextcloud.mysql.service: Scheduled restart job, restart counter is at 5.
Dec 20 10:51:18 nextcloud systemd[1]: Stopped snap.nextcloud.mysql.service - Service for snap application nextcloud.mysql.
Dec 20 10:51:18 nextcloud systemd[1]: snap.nextcloud.mysql.service: Start request repeated too quickly.
Dec 20 10:51:18 nextcloud systemd[1]: snap.nextcloud.mysql.service: Failed with result 'exit-code'.
Dec 20 10:51:18 nextcloud systemd[1]: Failed to start snap.nextcloud.mysql.service - Service for snap application nextcloud.mysql.

InnoDB: about forcing recovery.
2023-12-20T09:51:12Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=71e496f654356cd4a1c671ede7265fbca6cb7a6f
Thread pointer: 0x564137b7c710
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f3910809a00 thread_stack 0x100000
/snap/nextcloud/39212/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x56413367ad6d]
/snap/nextcloud/39212/bin/mysqld(print_fatal_signal(int)+0x3c3) [0x5641325b5e83]
/snap/nextcloud/39212/bin/mysqld(my_server_abort()+0x6e) [0x5641325b5f9e]
/snap/nextcloud/39212/bin/mysqld(my_abort()+0xa) [0x5641336744da]
/snap/nextcloud/39212/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2e9) [0x564133904949]
/snap/nextcloud/39212/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2cbc) [0x5641337b68dc]
/snap/nextcloud/39212/bin/mysqld(srv_start(bool)+0x1538) [0x5641338a2438]
/snap/nextcloud/39212/bin/mysqld(+0x22c7495) [0x5641336c7495]
/snap/nextcloud/39212/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xd9) [0x5641333afff9]
/snap/nextcloud/39212/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x19a) [0x56413364a01a]
/snap/nextcloud/39212/bin/mysqld(+0x1274b46) [0x564132674b46]
/snap/nextcloud/39212/bin/mysqld(+0x27da9f6) [0x564133bda9f6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f3912e926db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f391207861f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2023-12-20T09:51:13.817659Z 0 [System] [MY-010116] [Server] /snap/nextcloud/39212/bin/mysqld (mysqld 8.0.35) starting as process 12210
2023-12-20T09:51:13.823998Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-20T09:51:13.971868Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
2023-12-20T09:51:13.971939Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3623:err == DB_SUCCESS thread 140436003227392
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-12-20T09:51:13Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=71e496f654356cd4a1c671ede7265fbca6cb7a6f
Thread pointer: 0x55c6b0de5710
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fb9ce15fa00 thread_stack 0x100000
/snap/nextcloud/39212/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x55c6adc7ad6d]
/snap/nextcloud/39212/bin/mysqld(print_fatal_signal(int)+0x3c3) [0x55c6acbb5e83]
/snap/nextcloud/39212/bin/mysqld(my_server_abort()+0x6e) [0x55c6acbb5f9e]
/snap/nextcloud/39212/bin/mysqld(my_abort()+0xa) [0x55c6adc744da]
/snap/nextcloud/39212/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2e9) [0x55c6adf04949]
/snap/nextcloud/39212/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2cbc) [0x55c6addb68dc]
/snap/nextcloud/39212/bin/mysqld(srv_start(bool)+0x1538) [0x55c6adea2438]
/snap/nextcloud/39212/bin/mysqld(+0x22c7495) [0x55c6adcc7495]
/snap/nextcloud/39212/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xd9) [0x55c6ad9afff9]
/snap/nextcloud/39212/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x19a) [0x55c6adc4a01a]
/snap/nextcloud/39212/bin/mysqld(+0x1274b46) [0x55c6acc74b46]
/snap/nextcloud/39212/bin/mysqld(+0x27da9f6) [0x55c6ae1da9f6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7fb9d07e86db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fb9cf9ce61f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2023-12-20T09:51:15.049610Z 0 [System] [MY-010116] [Server] /snap/nextcloud/39212/bin/mysqld (mysqld 8.0.35) starting as process 12524
2023-12-20T09:51:15.055849Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-20T09:51:15.198216Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
2023-12-20T09:51:15.198280Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3623:err == DB_SUCCESS thread 140206202058496
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-12-20T09:51:15Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=71e496f654356cd4a1c671ede7265fbca6cb7a6f
Thread pointer: 0x55a1971e8710
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f844cde6a00 thread_stack 0x100000
/snap/nextcloud/39212/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x55a19387ad6d]
/snap/nextcloud/39212/bin/mysqld(print_fatal_signal(int)+0x3c3) [0x55a1927b5e83]
/snap/nextcloud/39212/bin/mysqld(my_server_abort()+0x6e) [0x55a1927b5f9e]
/snap/nextcloud/39212/bin/mysqld(my_abort()+0xa) [0x55a1938744da]
/snap/nextcloud/39212/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2e9) [0x55a193b04949]
/snap/nextcloud/39212/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2cbc) [0x55a1939b68dc]
/snap/nextcloud/39212/bin/mysqld(srv_start(bool)+0x1538) [0x55a193aa2438]
/snap/nextcloud/39212/bin/mysqld(+0x22c7495) [0x55a1938c7495]
/snap/nextcloud/39212/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xd9) [0x55a1935afff9]
/snap/nextcloud/39212/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x19a) [0x55a19384a01a]
/snap/nextcloud/39212/bin/mysqld(+0x1274b46) [0x55a192874b46]
/snap/nextcloud/39212/bin/mysqld(+0x27da9f6) [0x55a193dda9f6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f844f46f6db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f844e65561f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2023-12-20T09:51:16.317438Z 0 [System] [MY-010116] [Server] /snap/nextcloud/39212/bin/mysqld (mysqld 8.0.35) starting as process 12840
2023-12-20T09:51:16.323751Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-20T09:51:16.473444Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
2023-12-20T09:51:16.473513Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3623:err == DB_SUCCESS thread 140174419961600
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-12-20T09:51:16Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=71e496f654356cd4a1c671ede7265fbca6cb7a6f
Thread pointer: 0x560bbdd39710
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f7ce6821a00 thread_stack 0x100000
/snap/nextcloud/39212/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x560bbac7ad6d]
/snap/nextcloud/39212/bin/mysqld(print_fatal_signal(int)+0x3c3) [0x560bb9bb5e83]
/snap/nextcloud/39212/bin/mysqld(my_server_abort()+0x6e) [0x560bb9bb5f9e]
/snap/nextcloud/39212/bin/mysqld(my_abort()+0xa) [0x560bbac744da]
/snap/nextcloud/39212/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2e9) [0x560bbaf04949]
/snap/nextcloud/39212/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2cbc) [0x560bbadb68dc]
/snap/nextcloud/39212/bin/mysqld(srv_start(bool)+0x1538) [0x560bbaea2438]
/snap/nextcloud/39212/bin/mysqld(+0x22c7495) [0x560bbacc7495]
/snap/nextcloud/39212/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xd9) [0x560bba9afff9]
/snap/nextcloud/39212/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x19a) [0x560bbac4a01a]
/snap/nextcloud/39212/bin/mysqld(+0x1274b46) [0x560bb9c74b46]
/snap/nextcloud/39212/bin/mysqld(+0x27da9f6) [0x560bbb1da9f6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f7ce8eaa6db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f7ce809061f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2023-12-20T09:51:17.597600Z 0 [System] [MY-010116] [Server] /snap/nextcloud/39212/bin/mysqld (mysqld 8.0.35) starting as process 13156
2023-12-20T09:51:17.604124Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-20T09:51:17.753696Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
2023-12-20T09:51:17.753779Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3623:err == DB_SUCCESS thread 140699162085120
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-12-20T09:51:17Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=71e496f654356cd4a1c671ede7265fbca6cb7a6f
Thread pointer: 0x56054146e710
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7ff713937a00 thread_stack 0x100000
/snap/nextcloud/39212/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x56053d07ad6d]
/snap/nextcloud/39212/bin/mysqld(print_fatal_signal(int)+0x3c3) [0x56053bfb5e83]
/snap/nextcloud/39212/bin/mysqld(my_server_abort()+0x6e) [0x56053bfb5f9e]
/snap/nextcloud/39212/bin/mysqld(my_abort()+0xa) [0x56053d0744da]
/snap/nextcloud/39212/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2e9) [0x56053d304949]
/snap/nextcloud/39212/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2cbc) [0x56053d1b68dc]
/snap/nextcloud/39212/bin/mysqld(srv_start(bool)+0x1538) [0x56053d2a2438]
/snap/nextcloud/39212/bin/mysqld(+0x22c7495) [0x56053d0c7495]
/snap/nextcloud/39212/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xd9) [0x56053cdafff9]
/snap/nextcloud/39212/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x19a) [0x56053d04a01a]
/snap/nextcloud/39212/bin/mysqld(+0x1274b46) [0x56053c074b46]
/snap/nextcloud/39212/bin/mysqld(+0x27da9f6) [0x56053d5da9f6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7ff715fc06db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7ff7151a661f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

× snap.nextcloud.redis-server.service - Service for snap application nextcloud.redis-server
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.redis-server.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-12-20 10:51:13 CET; 3min 53s ago
   Duration: 77ms
    Process: 11872 ExecStart=/usr/bin/snap run nextcloud.redis-server (code=exited, status=1/FAILURE)
   Main PID: 11872 (code=exited, status=1/FAILURE)
        CPU: 79ms

Dec 20 10:51:13 nextcloud systemd[1]: snap.nextcloud.redis-server.service: Scheduled restart job, restart counter is at 5.
Dec 20 10:51:13 nextcloud systemd[1]: Stopped snap.nextcloud.redis-server.service - Service for snap application nextcloud.redis-server.
Dec 20 10:51:13 nextcloud systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Dec 20 10:51:13 nextcloud systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Dec 20 10:51:13 nextcloud systemd[1]: Failed to start snap.nextcloud.redis-server.service - Service for snap application nextcloud.redis-server.

1214:M 20 Dec 2023 10:35:30.814 # Wrong signature trying to load DB from file
1214:M 20 Dec 2023 10:35:30.814 # Fatal error loading the DB: Invalid argument. Exiting.
1261:C 20 Dec 2023 10:35:31.061 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1261:C 20 Dec 2023 10:35:31.061 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=1261, just started
1261:C 20 Dec 2023 10:35:31.061 # Configuration loaded
1261:M 20 Dec 2023 10:35:31.062 * monotonic clock: POSIX clock_gettime
1261:M 20 Dec 2023 10:35:31.062 * Running mode=standalone, port=0.
1261:M 20 Dec 2023 10:35:31.062 # Server initialized
1261:M 20 Dec 2023 10:35:31.062 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1261:M 20 Dec 2023 10:35:31.063 # Wrong signature trying to load DB from file
1261:M 20 Dec 2023 10:35:31.063 # Fatal error loading the DB: Invalid argument. Exiting.
1310:C 20 Dec 2023 10:35:31.304 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1310:C 20 Dec 2023 10:35:31.304 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=1310, just started
1310:C 20 Dec 2023 10:35:31.304 # Configuration loaded
1310:M 20 Dec 2023 10:35:31.304 * monotonic clock: POSIX clock_gettime
1310:M 20 Dec 2023 10:35:31.305 * Running mode=standalone, port=0.
1310:M 20 Dec 2023 10:35:31.305 # Server initialized
1310:M 20 Dec 2023 10:35:31.305 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1310:M 20 Dec 2023 10:35:31.305 # Wrong signature trying to load DB from file
1310:M 20 Dec 2023 10:35:31.305 # Fatal error loading the DB: Invalid argument. Exiting.
984:C 20 Dec 2023 10:36:31.604 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
984:C 20 Dec 2023 10:36:31.606 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=984, just started
984:C 20 Dec 2023 10:36:31.606 # Configuration loaded
984:M 20 Dec 2023 10:36:31.607 * monotonic clock: POSIX clock_gettime
984:M 20 Dec 2023 10:36:31.607 * Running mode=standalone, port=0.
984:M 20 Dec 2023 10:36:31.607 # Server initialized
984:M 20 Dec 2023 10:36:31.607 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
984:M 20 Dec 2023 10:36:31.610 # Wrong signature trying to load DB from file
984:M 20 Dec 2023 10:36:31.610 # Fatal error loading the DB: Invalid argument. Exiting.
1149:C 20 Dec 2023 10:36:31.887 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1149:C 20 Dec 2023 10:36:31.887 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=1149, just started
1149:C 20 Dec 2023 10:36:31.887 # Configuration loaded
1149:M 20 Dec 2023 10:36:31.887 * monotonic clock: POSIX clock_gettime
1149:M 20 Dec 2023 10:36:31.888 * Running mode=standalone, port=0.
1149:M 20 Dec 2023 10:36:31.888 # Server initialized
1149:M 20 Dec 2023 10:36:31.888 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1149:M 20 Dec 2023 10:36:31.888 # Wrong signature trying to load DB from file
1149:M 20 Dec 2023 10:36:31.888 # Fatal error loading the DB: Invalid argument. Exiting.
1200:C 20 Dec 2023 10:36:32.355 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1200:C 20 Dec 2023 10:36:32.355 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=1200, just started
1200:C 20 Dec 2023 10:36:32.355 # Configuration loaded
1200:M 20 Dec 2023 10:36:32.356 * monotonic clock: POSIX clock_gettime
1200:M 20 Dec 2023 10:36:32.356 * Running mode=standalone, port=0.
1200:M 20 Dec 2023 10:36:32.356 # Server initialized
1200:M 20 Dec 2023 10:36:32.356 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1200:M 20 Dec 2023 10:36:32.357 # Wrong signature trying to load DB from file
1200:M 20 Dec 2023 10:36:32.357 # Fatal error loading the DB: Invalid argument. Exiting.
1251:C 20 Dec 2023 10:36:32.833 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1251:C 20 Dec 2023 10:36:32.833 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=1251, just started
1251:C 20 Dec 2023 10:36:32.833 # Configuration loaded
1251:M 20 Dec 2023 10:36:32.834 * monotonic clock: POSIX clock_gettime
1251:M 20 Dec 2023 10:36:32.835 * Running mode=standalone, port=0.
1251:M 20 Dec 2023 10:36:32.835 # Server initialized
1251:M 20 Dec 2023 10:36:32.835 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1251:M 20 Dec 2023 10:36:32.836 # Wrong signature trying to load DB from file
1251:M 20 Dec 2023 10:36:32.836 # Fatal error loading the DB: Invalid argument. Exiting.
1548:C 20 Dec 2023 10:36:33.292 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1548:C 20 Dec 2023 10:36:33.292 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=1548, just started
1548:C 20 Dec 2023 10:36:33.292 # Configuration loaded
1548:M 20 Dec 2023 10:36:33.293 * monotonic clock: POSIX clock_gettime
1548:M 20 Dec 2023 10:36:33.293 * Running mode=standalone, port=0.
1548:M 20 Dec 2023 10:36:33.293 # Server initialized
1548:M 20 Dec 2023 10:36:33.293 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1548:M 20 Dec 2023 10:36:33.294 # Wrong signature trying to load DB from file
1548:M 20 Dec 2023 10:36:33.294 # Fatal error loading the DB: Invalid argument. Exiting.
6226:C 20 Dec 2023 10:47:51.869 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6226:C 20 Dec 2023 10:47:51.869 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=6226, just started
6226:C 20 Dec 2023 10:47:51.869 # Configuration loaded
6226:M 20 Dec 2023 10:47:51.870 * monotonic clock: POSIX clock_gettime
6226:M 20 Dec 2023 10:47:51.871 * Running mode=standalone, port=0.
6226:M 20 Dec 2023 10:47:51.871 # Server initialized
6226:M 20 Dec 2023 10:47:51.871 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
6226:M 20 Dec 2023 10:47:51.871 # Wrong signature trying to load DB from file
6226:M 20 Dec 2023 10:47:51.871 # Fatal error loading the DB: Invalid argument. Exiting.
6497:C 20 Dec 2023 10:47:52.177 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6497:C 20 Dec 2023 10:47:52.177 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=6497, just started
6497:C 20 Dec 2023 10:47:52.177 # Configuration loaded
6497:M 20 Dec 2023 10:47:52.177 * monotonic clock: POSIX clock_gettime
6497:M 20 Dec 2023 10:47:52.178 * Running mode=standalone, port=0.
6497:M 20 Dec 2023 10:47:52.178 # Server initialized
6497:M 20 Dec 2023 10:47:52.178 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
6497:M 20 Dec 2023 10:47:52.179 # Wrong signature trying to load DB from file
6497:M 20 Dec 2023 10:47:52.179 # Fatal error loading the DB: Invalid argument. Exiting.
6564:C 20 Dec 2023 10:47:52.425 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6564:C 20 Dec 2023 10:47:52.425 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=6564, just started
6564:C 20 Dec 2023 10:47:52.425 # Configuration loaded
6564:M 20 Dec 2023 10:47:52.425 * monotonic clock: POSIX clock_gettime
6564:M 20 Dec 2023 10:47:52.426 * Running mode=standalone, port=0.
6564:M 20 Dec 2023 10:47:52.426 # Server initialized
6564:M 20 Dec 2023 10:47:52.426 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
6564:M 20 Dec 2023 10:47:52.427 # Wrong signature trying to load DB from file
6564:M 20 Dec 2023 10:47:52.427 # Fatal error loading the DB: Invalid argument. Exiting.
6609:C 20 Dec 2023 10:47:52.673 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6609:C 20 Dec 2023 10:47:52.673 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=6609, just started
6609:C 20 Dec 2023 10:47:52.673 # Configuration loaded
6609:M 20 Dec 2023 10:47:52.674 * monotonic clock: POSIX clock_gettime
6609:M 20 Dec 2023 10:47:52.674 * Running mode=standalone, port=0.
6609:M 20 Dec 2023 10:47:52.675 # Server initialized
6609:M 20 Dec 2023 10:47:52.675 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
6609:M 20 Dec 2023 10:47:52.675 # Wrong signature trying to load DB from file
6609:M 20 Dec 2023 10:47:52.675 # Fatal error loading the DB: Invalid argument. Exiting.
6657:C 20 Dec 2023 10:47:52.915 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6657:C 20 Dec 2023 10:47:52.915 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=6657, just started
6657:C 20 Dec 2023 10:47:52.915 # Configuration loaded
6657:M 20 Dec 2023 10:47:52.916 * monotonic clock: POSIX clock_gettime
6657:M 20 Dec 2023 10:47:52.917 * Running mode=standalone, port=0.
6657:M 20 Dec 2023 10:47:52.917 # Server initialized
6657:M 20 Dec 2023 10:47:52.917 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
6657:M 20 Dec 2023 10:47:52.917 # Wrong signature trying to load DB from file
6657:M 20 Dec 2023 10:47:52.917 # Fatal error loading the DB: Invalid argument. Exiting.
9035:C 20 Dec 2023 10:50:04.073 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9035:C 20 Dec 2023 10:50:04.073 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=9035, just started
9035:C 20 Dec 2023 10:50:04.073 # Configuration loaded
9035:M 20 Dec 2023 10:50:04.074 * monotonic clock: POSIX clock_gettime
9035:M 20 Dec 2023 10:50:04.075 * Running mode=standalone, port=0.
9035:M 20 Dec 2023 10:50:04.075 # Server initialized
9035:M 20 Dec 2023 10:50:04.075 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
9035:M 20 Dec 2023 10:50:04.075 # Wrong signature trying to load DB from file
9035:M 20 Dec 2023 10:50:04.075 # Fatal error loading the DB: Invalid argument. Exiting.
9273:C 20 Dec 2023 10:50:04.459 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9273:C 20 Dec 2023 10:50:04.459 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=9273, just started
9273:C 20 Dec 2023 10:50:04.459 # Configuration loaded
9273:M 20 Dec 2023 10:50:04.460 * monotonic clock: POSIX clock_gettime
9273:M 20 Dec 2023 10:50:04.460 * Running mode=standalone, port=0.
9273:M 20 Dec 2023 10:50:04.460 # Server initialized
9273:M 20 Dec 2023 10:50:04.460 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
9273:M 20 Dec 2023 10:50:04.461 # Wrong signature trying to load DB from file
9273:M 20 Dec 2023 10:50:04.461 # Fatal error loading the DB: Invalid argument. Exiting.
9324:C 20 Dec 2023 10:50:04.664 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9324:C 20 Dec 2023 10:50:04.664 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=9324, just started
9324:C 20 Dec 2023 10:50:04.664 # Configuration loaded
9324:M 20 Dec 2023 10:50:04.664 * monotonic clock: POSIX clock_gettime
9324:M 20 Dec 2023 10:50:04.665 * Running mode=standalone, port=0.
9324:M 20 Dec 2023 10:50:04.665 # Server initialized
9324:M 20 Dec 2023 10:50:04.665 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
9324:M 20 Dec 2023 10:50:04.666 # Wrong signature trying to load DB from file
9324:M 20 Dec 2023 10:50:04.666 # Fatal error loading the DB: Invalid argument. Exiting.
9368:C 20 Dec 2023 10:50:04.909 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9368:C 20 Dec 2023 10:50:04.910 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=9368, just started
9368:C 20 Dec 2023 10:50:04.910 # Configuration loaded
9368:M 20 Dec 2023 10:50:04.910 * monotonic clock: POSIX clock_gettime
9368:M 20 Dec 2023 10:50:04.911 * Running mode=standalone, port=0.
9368:M 20 Dec 2023 10:50:04.911 # Server initialized
9368:M 20 Dec 2023 10:50:04.911 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
9368:M 20 Dec 2023 10:50:04.911 # Wrong signature trying to load DB from file
9368:M 20 Dec 2023 10:50:04.911 # Fatal error loading the DB: Invalid argument. Exiting.
9461:C 20 Dec 2023 10:50:05.168 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9461:C 20 Dec 2023 10:50:05.168 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=9461, just started
9461:C 20 Dec 2023 10:50:05.168 # Configuration loaded
9461:M 20 Dec 2023 10:50:05.168 * monotonic clock: POSIX clock_gettime
9461:M 20 Dec 2023 10:50:05.169 * Running mode=standalone, port=0.
9461:M 20 Dec 2023 10:50:05.169 # Server initialized
9461:M 20 Dec 2023 10:50:05.169 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
9461:M 20 Dec 2023 10:50:05.169 # Wrong signature trying to load DB from file
9461:M 20 Dec 2023 10:50:05.169 # Fatal error loading the DB: Invalid argument. Exiting.
11557:C 20 Dec 2023 10:51:12.324 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11557:C 20 Dec 2023 10:51:12.324 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=11557, just started
11557:C 20 Dec 2023 10:51:12.324 # Configuration loaded
11557:M 20 Dec 2023 10:51:12.325 * monotonic clock: POSIX clock_gettime
11557:M 20 Dec 2023 10:51:12.326 * Running mode=standalone, port=0.
11557:M 20 Dec 2023 10:51:12.326 # Server initialized
11557:M 20 Dec 2023 10:51:12.326 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
11557:M 20 Dec 2023 10:51:12.326 # Wrong signature trying to load DB from file
11557:M 20 Dec 2023 10:51:12.326 # Fatal error loading the DB: Invalid argument. Exiting.
11767:C 20 Dec 2023 10:51:12.705 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11767:C 20 Dec 2023 10:51:12.705 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=11767, just started
11767:C 20 Dec 2023 10:51:12.705 # Configuration loaded
11767:M 20 Dec 2023 10:51:12.706 * monotonic clock: POSIX clock_gettime
11767:M 20 Dec 2023 10:51:12.706 * Running mode=standalone, port=0.
11767:M 20 Dec 2023 10:51:12.706 # Server initialized
11767:M 20 Dec 2023 10:51:12.706 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
11767:M 20 Dec 2023 10:51:12.707 # Wrong signature trying to load DB from file
11767:M 20 Dec 2023 10:51:12.707 # Fatal error loading the DB: Invalid argument. Exiting.
11818:C 20 Dec 2023 10:51:12.916 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11818:C 20 Dec 2023 10:51:12.916 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=11818, just started
11818:C 20 Dec 2023 10:51:12.916 # Configuration loaded
11818:M 20 Dec 2023 10:51:12.917 * monotonic clock: POSIX clock_gettime
11818:M 20 Dec 2023 10:51:12.918 * Running mode=standalone, port=0.
11818:M 20 Dec 2023 10:51:12.918 # Server initialized
11818:M 20 Dec 2023 10:51:12.918 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
11818:M 20 Dec 2023 10:51:12.918 # Wrong signature trying to load DB from file
11818:M 20 Dec 2023 10:51:12.918 # Fatal error loading the DB: Invalid argument. Exiting.
11862:C 20 Dec 2023 10:51:13.163 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11862:C 20 Dec 2023 10:51:13.163 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=11862, just started
11862:C 20 Dec 2023 10:51:13.163 # Configuration loaded
11862:M 20 Dec 2023 10:51:13.164 * monotonic clock: POSIX clock_gettime
11862:M 20 Dec 2023 10:51:13.164 * Running mode=standalone, port=0.
11862:M 20 Dec 2023 10:51:13.164 # Server initialized
11862:M 20 Dec 2023 10:51:13.164 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
11862:M 20 Dec 2023 10:51:13.165 # Wrong signature trying to load DB from file
11862:M 20 Dec 2023 10:51:13.165 # Fatal error loading the DB: Invalid argument. Exiting.
11954:C 20 Dec 2023 10:51:13.415 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11954:C 20 Dec 2023 10:51:13.415 # Redis version=6.2.14, bits=64, commit=fa756862, modified=0, pid=11954, just started
11954:C 20 Dec 2023 10:51:13.415 # Configuration loaded
11954:M 20 Dec 2023 10:51:13.416 * monotonic clock: POSIX clock_gettime
11954:M 20 Dec 2023 10:51:13.417 * Running mode=standalone, port=0.
11954:M 20 Dec 2023 10:51:13.417 # Server initialized
11954:M 20 Dec 2023 10:51:13.417 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
11954:M 20 Dec 2023 10:51:13.417 # Wrong signature trying to load DB from file
11954:M 20 Dec 2023 10:51:13.417 # Fatal error loading the DB: Invalid argument. Exiting.

● snap.nextcloud.renew-certs.service - Service for snap application nextcloud.renew-certs
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.renew-certs.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-12-20 10:51:12 CET; 3min 54s ago
   Main PID: 11444 (renew-certs)
      Tasks: 2 (limit: 9477)
     Memory: 452.0K
        CPU: 1.535s
     CGroup: /system.slice/snap.nextcloud.renew-certs.service
             ├─11444 /bin/sh /snap/nextcloud/39212/bin/renew-certs
             └─12211 sleep 1d

Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: Processing
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: /var/snap/nextcloud/current/certs/certbot/config/renewal/home.mrqt.fr.conf
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: Cert not yet due for renewal
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: The following certs are not due for renewal yet:
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]:   /var/snap/nextcloud/current/certs/certbot/config/live/home.mrqt.fr/fullchain.pem expires on 2024-02-01 (skipped)
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: No renewals were attempted.
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: No hooks were run.
Dec 20 10:51:13 nextcloud nextcloud.renew-certs[11593]: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

○ snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.logrotate.service; static)
     Active: inactive (dead) since Wed 2023-12-20 10:51:12 CET; 3min 55s ago
   Duration: 44ms
TriggeredBy: ● snap.nextcloud.logrotate.timer
    Process: 11060 ExecStart=/usr/bin/snap run --timer=00:00 nextcloud.logrotate (code=exited, status=0/SUCCESS)
   Main PID: 11060 (code=exited, status=0/SUCCESS)
        CPU: 41ms

Dec 20 10:51:12 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 20 10:51:12 nextcloud nextcloud.logrotate[11060]: 2023-12-20T10:51:12+01:00: attempted to run "nextcloud.logrotate" timer outside of scheduled time "00:00"
Dec 20 10:51:12 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.

Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: old log /var/snap/nextcloud/current/logs/php_errors.log.0.gz does not exist
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: log /var/snap/nextcloud/current/logs/php_errors.log.5.gz doesn't exist -- won't try to dispose of it
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: renaming /var/snap/nextcloud/current/logs/php_errors.log to /var/snap/nextcloud/current/logs/php_errors.log.1
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: creating new /var/snap/nextcloud/current/logs/php_errors.log mode = 0640 uid = 0 gid = 0
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: running postrotate script
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: rotating pattern: /var/snap/nextcloud/current/logs/redis.log  weekly (4 rotations)
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: empty log files are not rotated, old logs are removed
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: considering log /var/snap/nextcloud/current/logs/redis.log
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]:   Now: 2023-12-17 00:00
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]:   Last rotated at 2023-12-10 00:00
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]:   log does not need rotating (log has been rotated at 2023-12-10 0:0, that is not week ago yet)
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: rotating pattern: /var/snap/nextcloud/current/logs/mysql_errors.log  weekly (4 rotations)
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: empty log files are not rotated, old logs are removed
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]: considering log /var/snap/nextcloud/current/logs/mysql_errors.log
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]:   Now: 2023-12-17 00:00
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]:   Last rotated at 2023-11-29 00:00
Dec 17 00:00:11 nextcloud nextcloud.logrotate[2536907]:   log does not need rotating (log is empty)
Dec 17 00:00:11 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.
Dec 17 00:00:11 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Consumed 2.190s CPU time.
Dec 18 00:00:06 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: reading config file /tmp/tmp.VT5QP2aaNC
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Reading state from file: /var/snap/nextcloud/38457/logrotate/status
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Allocating hash table for state file, size 64 entries
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Creating new state
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: Handling 4 logs
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: rotating pattern: /var/snap/nextcloud/current/logs/apache_errors.log /var/snap/nextcloud/current/logs/apache_access.log  weekly (4 rotations)
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: empty log files are not rotated, old logs are removed
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/apache_errors.log
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-12-10 00:00
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]:   log needs rotating
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/apache_access.log
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-12-10 00:00
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]:   log needs rotating
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: rotating log /var/snap/nextcloud/current/logs/apache_errors.log, log->rotateCount is 4
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: dateext suffix '-20231218'
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: compressing log with: /bin/gzip
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_errors.log.4.gz to /var/snap/nextcloud/current/logs/apache_errors.log.5.gz (rotatecount 4, logstart 1, i 4),
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_errors.log.3.gz to /var/snap/nextcloud/current/logs/apache_errors.log.4.gz (rotatecount 4, logstart 1, i 3),
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_errors.log.2.gz to /var/snap/nextcloud/current/logs/apache_errors.log.3.gz (rotatecount 4, logstart 1, i 2),
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_errors.log.1.gz to /var/snap/nextcloud/current/logs/apache_errors.log.2.gz (rotatecount 4, logstart 1, i 1),
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_errors.log.0.gz to /var/snap/nextcloud/current/logs/apache_errors.log.1.gz (rotatecount 4, logstart 1, i 0),
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: old log /var/snap/nextcloud/current/logs/apache_errors.log.0.gz does not exist
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_errors.log to /var/snap/nextcloud/current/logs/apache_errors.log.1
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: creating new /var/snap/nextcloud/current/logs/apache_errors.log mode = 0640 uid = 0 gid = 0
Dec 18 00:00:09 nextcloud nextcloud.logrotate[2672675]: running postrotate script
Dec 18 00:00:10 nextcloud nextcloud.logrotate[2672675]: removing old log /var/snap/nextcloud/current/logs/apache_errors.log.5.gz
Dec 18 00:00:10 nextcloud nextcloud.logrotate[2672675]: rotating log /var/snap/nextcloud/current/logs/apache_access.log, log->rotateCount is 4
Dec 18 00:00:10 nextcloud nextcloud.logrotate[2672675]: dateext suffix '-20231218'
Dec 18 00:00:10 nextcloud nextcloud.logrotate[2672675]: glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
Dec 18 00:00:10 nextcloud nextcloud.logrotate[2672675]: compressing log with: /bin/gzip
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_access.log.4.gz to /var/snap/nextcloud/current/logs/apache_access.log.5.gz (rotatecount 4, logstart 1, i 4),
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_access.log.3.gz to /var/snap/nextcloud/current/logs/apache_access.log.4.gz (rotatecount 4, logstart 1, i 3),
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_access.log.2.gz to /var/snap/nextcloud/current/logs/apache_access.log.3.gz (rotatecount 4, logstart 1, i 2),
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_access.log.1.gz to /var/snap/nextcloud/current/logs/apache_access.log.2.gz (rotatecount 4, logstart 1, i 1),
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_access.log.0.gz to /var/snap/nextcloud/current/logs/apache_access.log.1.gz (rotatecount 4, logstart 1, i 0),
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: old log /var/snap/nextcloud/current/logs/apache_access.log.0.gz does not exist
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/apache_access.log to /var/snap/nextcloud/current/logs/apache_access.log.1
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: creating new /var/snap/nextcloud/current/logs/apache_access.log mode = 0640 uid = 0 gid = 0
Dec 18 00:00:13 nextcloud nextcloud.logrotate[2672675]: running postrotate script
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: removing old log /var/snap/nextcloud/current/logs/apache_access.log.5.gz
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: rotating pattern: /var/snap/nextcloud/current/logs/php_errors.log /var/snap/nextcloud/current/logs/php-fpm_errors.log /var/snap/nextcloud/current/logs/nextcloud.log  weekly (4 rotations)
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: empty log files are not rotated, old logs are removed
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/php_errors.log
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-12-17 00:00
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   log does not need rotating (log has been rotated at 2023-12-17 0:0, that is not week ago yet)
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/php-fpm_errors.log
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-12-10 00:00
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   log needs rotating
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/nextcloud.log
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-12-10 00:00
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]:   log needs rotating
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: rotating log /var/snap/nextcloud/current/logs/php-fpm_errors.log, log->rotateCount is 4
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: dateext suffix '-20231218'
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: compressing log with: /bin/gzip
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/php-fpm_errors.log.4.gz to /var/snap/nextcloud/current/logs/php-fpm_errors.log.5.gz (rotatecount 4, logstart 1, i 4),
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/php-fpm_errors.log.3.gz to /var/snap/nextcloud/current/logs/php-fpm_errors.log.4.gz (rotatecount 4, logstart 1, i 3),
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/php-fpm_errors.log.2.gz to /var/snap/nextcloud/current/logs/php-fpm_errors.log.3.gz (rotatecount 4, logstart 1, i 2),
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/php-fpm_errors.log.1.gz to /var/snap/nextcloud/current/logs/php-fpm_errors.log.2.gz (rotatecount 4, logstart 1, i 1),
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/php-fpm_errors.log.0.gz to /var/snap/nextcloud/current/logs/php-fpm_errors.log.1.gz (rotatecount 4, logstart 1, i 0),
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: old log /var/snap/nextcloud/current/logs/php-fpm_errors.log.0.gz does not exist
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/php-fpm_errors.log to /var/snap/nextcloud/current/logs/php-fpm_errors.log.1
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: creating new /var/snap/nextcloud/current/logs/php-fpm_errors.log mode = 0640 uid = 0 gid = 0
Dec 18 00:00:16 nextcloud nextcloud.logrotate[2672675]: running postrotate script
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: removing old log /var/snap/nextcloud/current/logs/php-fpm_errors.log.5.gz
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: rotating log /var/snap/nextcloud/current/logs/nextcloud.log, log->rotateCount is 4
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: dateext suffix '-20231218'
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: compressing log with: /bin/gzip
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/nextcloud.log.4.gz to /var/snap/nextcloud/current/logs/nextcloud.log.5.gz (rotatecount 4, logstart 1, i 4),
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/nextcloud.log.3.gz to /var/snap/nextcloud/current/logs/nextcloud.log.4.gz (rotatecount 4, logstart 1, i 3),
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/nextcloud.log.2.gz to /var/snap/nextcloud/current/logs/nextcloud.log.3.gz (rotatecount 4, logstart 1, i 2),
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/nextcloud.log.1.gz to /var/snap/nextcloud/current/logs/nextcloud.log.2.gz (rotatecount 4, logstart 1, i 1),
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/nextcloud.log.0.gz to /var/snap/nextcloud/current/logs/nextcloud.log.1.gz (rotatecount 4, logstart 1, i 0),
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: old log /var/snap/nextcloud/current/logs/nextcloud.log.0.gz does not exist
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/nextcloud.log to /var/snap/nextcloud/current/logs/nextcloud.log.1
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: creating new /var/snap/nextcloud/current/logs/nextcloud.log mode = 0640 uid = 0 gid = 0
Dec 18 00:00:17 nextcloud nextcloud.logrotate[2672675]: running postrotate script
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: removing old log /var/snap/nextcloud/current/logs/nextcloud.log.5.gz
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: rotating pattern: /var/snap/nextcloud/current/logs/redis.log  weekly (4 rotations)
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: empty log files are not rotated, old logs are removed
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/redis.log
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-12-10 00:00
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]:   log needs rotating
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: rotating log /var/snap/nextcloud/current/logs/redis.log, log->rotateCount is 4
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: dateext suffix '-20231218'
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: compressing log with: /bin/gzip
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/redis.log.4.gz to /var/snap/nextcloud/current/logs/redis.log.5.gz (rotatecount 4, logstart 1, i 4),
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/redis.log.3.gz to /var/snap/nextcloud/current/logs/redis.log.4.gz (rotatecount 4, logstart 1, i 3),
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/redis.log.2.gz to /var/snap/nextcloud/current/logs/redis.log.3.gz (rotatecount 4, logstart 1, i 2),
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/redis.log.1.gz to /var/snap/nextcloud/current/logs/redis.log.2.gz (rotatecount 4, logstart 1, i 1),
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/redis.log.0.gz to /var/snap/nextcloud/current/logs/redis.log.1.gz (rotatecount 4, logstart 1, i 0),
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: old log /var/snap/nextcloud/current/logs/redis.log.0.gz does not exist
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: renaming /var/snap/nextcloud/current/logs/redis.log to /var/snap/nextcloud/current/logs/redis.log.1
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: creating new /var/snap/nextcloud/current/logs/redis.log mode = 0640 uid = 0 gid = 0
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: removing old log /var/snap/nextcloud/current/logs/redis.log.5.gz
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: rotating pattern: /var/snap/nextcloud/current/logs/mysql_errors.log  weekly (4 rotations)
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: empty log files are not rotated, old logs are removed
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]: considering log /var/snap/nextcloud/current/logs/mysql_errors.log
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]:   Now: 2023-12-18 00:00
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]:   Last rotated at 2023-11-29 00:00
Dec 18 00:00:18 nextcloud nextcloud.logrotate[2672675]:   log does not need rotating (log is empty)
Dec 18 00:00:18 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.
Dec 18 00:00:18 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Consumed 2.642s CPU time.
Dec 19 00:00:06 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: reading config file /tmp/tmp.ljqSKqYuKv
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Reading state from file: /var/snap/nextcloud/38457/logrotate/status
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Allocating hash table for state file, size 64 entries
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Creating new state
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: Handling 4 logs
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: rotating pattern: /var/snap/nextcloud/current/logs/apache_errors.log /var/snap/nextcloud/current/logs/apache_access.log  weekly (4 rotations)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: empty log files are not rotated, old logs are removed
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/apache_errors.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-12-18 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log has been rotated at 2023-12-18 0:0, that is not week ago yet)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/apache_access.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-12-18 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log has been rotated at 2023-12-18 0:0, that is not week ago yet)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: rotating pattern: /var/snap/nextcloud/current/logs/php_errors.log /var/snap/nextcloud/current/logs/php-fpm_errors.log /var/snap/nextcloud/current/logs/nextcloud.log  weekly (4 rotations)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: empty log files are not rotated, old logs are removed
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/php_errors.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-12-17 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log has been rotated at 2023-12-17 0:0, that is not week ago yet)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/php-fpm_errors.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-12-18 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log has been rotated at 2023-12-18 0:0, that is not week ago yet)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/nextcloud.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-12-18 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log has been rotated at 2023-12-18 0:0, that is not week ago yet)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: rotating pattern: /var/snap/nextcloud/current/logs/redis.log  weekly (4 rotations)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: empty log files are not rotated, old logs are removed
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/redis.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-12-18 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log has been rotated at 2023-12-18 0:0, that is not week ago yet)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: rotating pattern: /var/snap/nextcloud/current/logs/mysql_errors.log  weekly (4 rotations)
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: empty log files are not rotated, old logs are removed
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]: considering log /var/snap/nextcloud/current/logs/mysql_errors.log
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Now: 2023-12-19 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   Last rotated at 2023-11-29 00:00
Dec 19 00:00:09 nextcloud nextcloud.logrotate[2805857]:   log does not need rotating (log is empty)
Dec 19 00:00:09 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.
Dec 19 00:00:09 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Consumed 1.767s CPU time.
-- Boot 037554dcb80e4b8b81d28cd9f901cde9 --
Dec 20 10:16:48 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 20 10:16:48 nextcloud nextcloud.logrotate[13118]: 2023-12-20T10:16:48+01:00: attempted to run "nextcloud.logrotate" timer outside of scheduled time "00:00"
Dec 20 10:16:48 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.
-- Boot 8096e6cccd304b7f905e7ce4f1126be6 --
Dec 20 10:47:51 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 20 10:47:51 nextcloud nextcloud.logrotate[5797]: 2023-12-20T10:47:51+01:00: attempted to run "nextcloud.logrotate" timer outside of scheduled time "00:00"
Dec 20 10:47:51 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.
Dec 20 10:50:03 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 20 10:50:03 nextcloud nextcloud.logrotate[8565]: 2023-12-20T10:50:03+01:00: attempted to run "nextcloud.logrotate" timer outside of scheduled time "00:00"
Dec 20 10:50:03 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.
Dec 20 10:51:12 nextcloud systemd[1]: Started snap.nextcloud.logrotate.service - Service for snap application nextcloud.logrotate.
Dec 20 10:51:12 nextcloud nextcloud.logrotate[11060]: 2023-12-20T10:51:12+01:00: attempted to run "nextcloud.logrotate" timer outside of scheduled time "00:00"
Dec 20 10:51:12 nextcloud systemd[1]: snap.nextcloud.logrotate.service: Deactivated successfully.

● snap.nextcloud.nextcloud-cron.service - Service for snap application nextcloud.nextcloud-cron
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.nextcloud-cron.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-12-20 10:51:12 CET; 3min 55s ago
   Main PID: 11140 (nextcloud-cron)
      Tasks: 5 (limit: 9477)
     Memory: 1.1M
        CPU: 563ms
     CGroup: /system.slice/snap.nextcloud.nextcloud-cron.service
             ├─11140 /bin/sh /snap/nextcloud/39212/bin/nextcloud-cron
             ├─11268 /bin/sh /snap/nextcloud/39212/bin/nextcloud-cron
             ├─11269 /bin/sh -e /snap/nextcloud/39212/bin/occ -n status --output=json
             ├─11270 jq -R "fromjson? | .installed"
             └─14193 sleep 1

Dec 20 10:51:12 nextcloud systemd[1]: Started snap.nextcloud.nextcloud-cron.service - Service for snap application nextcloud.nextcloud-cron.
Dec 20 10:51:12 nextcloud nextcloud.nextcloud-cron[11140]: Waiting for Nextcloud config dir... done

● snap.nextcloud.nextcloud-fixer.service - Service for snap application nextcloud.nextcloud-fixer
     Loaded: loaded (/etc/systemd/system/snap.nextcloud.nextcloud-fixer.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-12-20 10:51:12 CET; 3min 55s ago
   Main PID: 11208 (nextcloud-fixer)
      Tasks: 2 (limit: 9477)
     Memory: 452.0K
        CPU: 489ms
     CGroup: /system.slice/snap.nextcloud.nextcloud-fixer.service
             ├─11208 /bin/sh -e /snap/nextcloud/39212/bin/nextcloud-fixer
             └─14191 sleep 1

Dec 20 10:51:12 nextcloud systemd[1]: Started snap.nextcloud.nextcloud-fixer.service - Service for snap application nextcloud.nextcloud-fixer.
Dec 20 10:51:12 nextcloud nextcloud.nextcloud-fixer[11208]: Waiting for Apache...

Waiting for PHP...