#1 Le 11/11/2023, à 16:01
- waca
Utilisation "redis" Nextcloud [RESOLU]
Bonjour à tous,
U22.04.1/Apache2 (PAS Nginx)
Il me restait une dernière chose à 'affiner' dans ma config c'est l'utilisation du cache.
Donc, je suis ce tuto:
https://docs.nextcloud.com/server/27/ad … ional.html
J'install redis
sudo apt-get install redis-serverPuis je modifie le /etc/redis/redis.conf
pour le faire fonctionner avec systemd
ainsi que l'ajout d'un mot de passe
Enfin, j'ouvre
/var/www/nextcloud/config/config.php
et j'ajoute ces lignes au début (celles qui commence par
'memcache.local' jusqu"à
'redis' =>
<?php
$CONFIG = array (
'memcache.local' => '\\OC\\Memcache\\Redis',
'filelocking.enabled' => 'true',
'memcache.distributed' => '\\OC\\Memcache\\Redis',
'memcache.locking' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => 'localhost',
'port' => 6379,
'timeout' => 0,
'dbindex' => 0,
),
'host' => 'localhost',
'port' => 6379,
'timeout' => 0,
'dbindex' => 0,
),
'instanceid' => 'ocx410z1x49l',
'passwordsalt' => 'NaFHHhv9KkGSTv/kaumun/zC971VWu',
'secret' => 'G24SOoqKg9IOZ5ATKLimDwnz79wF9AnZvb865Cbxt+fi8jZh',
'trusted_domains' =>
array (
0 => 'cloud.maxitag.net',
), etc.suivi d'un
sudo systemctl restart redis.serviceHé bien maintenant quand j'ouvre mon navigateur pour accèder à mon nextcloud, j'ai cette erreur:
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the webserver log.Du coup, je supprime les lignes (en gras) , mais le message reste le même = nextcoud "planté" ...
Arf, dans mon cas, le 'mieux' est l'ennemi du bien, car le serveur fonctionnait bien (depuis 1 an jour pour jour), mais ce 'défaut' de config me titillait depuis un moment....
A l'aide svp, et merci d'avance.
Dernière modification par waca (Le 12/11/2023, à 10:44)
Hors ligne
#2 Le 11/11/2023, à 17:30
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Bonjour,
Si le serveur redis est sur la m^me machine que Nextcloud il est recommandé d'utiliser une connexion par socket. C'est écrit dans la doc que tu cites.
Il faut aussi lire la doc complète sur les différents systèmes de cache. As-tu réellement besoin de Redis ? Pourquoi APCu n'est pas suffisant ? Es-tu sûr que cette ligne est utile (serveur web multiples avec cache distribué) :
'memcache.distributed' => '\\OC\\Memcache\\Redis'?
Visiblement tu as une erreur 500. Il faut examiner les logs.
Dernière modification par bruno (Le 11/11/2023, à 17:34)
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#3 Le 12/11/2023, à 10:44
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Merci Bruno, toujours aussi efficace.
C'est pas tant que j'ai "besoin" de redis, en fait je lis les instructions qui me sont données.
Le 'contrôle' de NC m'indique qu'il faut utiliser un cache, et il fournit le chemin pour le faire,
ce que j'ai suivi (j'en conviens en zappant la partie socket).
C'est OK maintenant.
bon dimanche.
Hors ligne
#4 Le 12/11/2023, à 11:09
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
C'est pourtant bien ce qu'indiquent les « instructions » :
Doc Nextcloud a écrit :
Small/Private home server
Only use APCu:
'memcache.local' => '\OC\Memcache\APCu',Organizations with single-server
Use Redis for everything except local memcache:
'memcache.local' => '\OC\Memcache\APCu', 'memcache.distributed' => '\OC\Memcache\Redis', 'memcache.locking' => '\OC\Memcache\Redis', 'redis' => [ 'host' => 'localhost', 'port' => 6379, ],
En outre il y a une note qui indique bien que l'utilisation d'un cache mémoire n'est pas obligatoire et un avertissement qui dit que APCu est plus performant pour le cache mémoire local.
Il faut juste adapter un peu le second cas :
'memcache.local' => '\\OC\\Memcache\\APCu',
'filelocking.enabled' => true,
'memcache.locking' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => '/run/redis/redis-server.sock',
'port' => 0,
'timeout' => 0.0,
),Car memcache.distributed est inutile dans ce cas et il est préférable d'utiliser une connexion sur socket et ne pas exposer le service Redis publiquement sur un port TCP (port 0 dans /etc/redis/redis.conf)
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#5 Le 12/11/2023, à 15:23
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Arf,
Est-ce que je dois ouvrir une nouvelle discussion? car en fait, je me rend compte que je ne
peux plus ni ajouter, ni supprimer de fichier 
même par l'interface web.
Hors ligne
#6 Le 12/11/2023, à 15:57
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Est-ce que tu as appliqué la configuration que je conseilla au #4 ? Est-ce que tu as fait d'autres modifications ?
Que disent les logs quand tu essaies d'envoyer un fichier ?
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#7 Le 12/11/2023, à 16:59
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
J'ai bien exactement la même chose que ton #4
Le log m'indique une erreur à la ligne 7 array (
<?php
$CONFIG = array (
'memcache.local' => '\\OC\\Memcache\\APCu',
'filelocking.enabled' => true,
'memcache.locking' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => '/run/redis/redis-server.sock',
'port' => 0,
'timeout' => 0,0,
'dbindex' => 0,
),
'instanceid' => '*******',
'passwordsalt' => '********',
'secret' => '*******',
'trusted_domains' =>
array (
0 => 'cloud.chezmoi.net',
),
'datadirectory' => '/var/www/nextcloud-data',
'dbtype' => 'mysql',
'version' => '27.1.3.2',
'overwrite.cli.url' => 'https://cloud.chezmoi.net',
'dbname' => 'nextcloud',
'dbhost' => 'localhost',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => 'casoni',
'dbpassword' => '******',
'installed' => true,
'mail_smtpmode' => 'smtp',
'mail_smtpsecure' => 'tls',
'mail_sendmailmode' => 'smtp',
'mail_from_address' => 'cloud',
'mail_domain' => 'chezmoi.net',
'mail_smtpauthtype' => 'PLAIN',
'mail_smtpauth' => 1,
'mail_smtphost' => 'ssl0.ovh.net',
'mail_smtpport' => '587',
'mail_smtpname' => 'cloud@chezmoi.net',
'mail_smtppassword' => '******',
'default_phone_region' => 'FR',
'filelocking.enabled' => 'false',
'trashbin_retention_obligation' => 'auto',Comme tu l'indiques à la fin du #4 j'ai modifié le redis.conf en passant le port à 0
(au lieu de 6379)
TCP (port 0 dans /etc/redis/redis.conf)
Sauf qu'en relançant le service redis j'ai une erreur:
ubuntu@141:~$ ubuntu@141:~$ sudo systemctl restart redis.service
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.
ubuntu@141:~$J'ai l'impression de m'enfoncer un peu plus
Quand je veux déposer un fichier, l'interface m'indique:
'no such file or directory'
--
Modération: masquage des mots de passe !
Dernière modification par bruno (Le 13/11/2023, à 09:01)
Hors ligne
#8 Le 12/11/2023, à 17:18
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Je ne vois pas l'erreur dans le fichier config.php 
Juste un petit problème d'indentation (deux espaces avant array)?
<?php
$CONFIG = array (
'memcache.local' => '\\OC\\Memcache\\APCu',
'filelocking.enabled' => true,
'memcache.locking' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => '/run/redis/redis-server.sock',
'port' => 0,
'timeout' => 0,0,
'dbindex' => 0,
),Montre nous la ligne du fichier de log.
Pour redis, montre-nous la modification que tu as fait et le retour de :
journalctl --no-pager -xeu redis-server.serviceNormalment il s'agissait de modifier la ligne port 6379 en port 0
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#9 Le 13/11/2023, à 07:30
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Bonjour et bonne semaine,
Voici la modif dans redis.conf
# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
protected-mode yes
# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
port 0
# TCP listen() backlog.
#
# In high requests-per-second environments you need a high backlog in order
# to avoid slow clients connection issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
tcp-backlog 511Partie de fichier log en essayant de 'déposer' un fichier appelé Onduleur.gsheet
202.166.176.77 - - [13/Nov/2023:16:22:59 +1100] "GET /index.php/apps/files/api/v1/stats HTTP/1.1" 200 1332 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/1>
202.166.176.77 - - [13/Nov/2023:16:23:16 +1100] "PUT /ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json HTTP/1.1" 204 1108 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTM>
202.166.176.77 - - [13/Nov/2023:16:23:20 +1100] "PUT /ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json HTTP/1.1" 204 784 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML>
202.166.176.77 - - [13/Nov/2023:16:23:20 +1100] "PUT /remote.php/webdav/Onduleur.gsheet HTTP/1.1" 500 818 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/11>
202.166.176.77 - - [13/Nov/2023:16:23:20 +1100] "GET /index.php/apps/files/api/v1/stats?dir=%2F HTTP/1.1" 200 1332 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)Le retour sur journalctl pèse en gros 300lignes !
Euh, tu veux que je les dépose ici ?
Hors ligne
#10 Le 13/11/2023, à 09:06
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Je ne vois pas d'erreur dans l'extrait du fichier redis.conf.
Il faut relancer le service :
sudo systemctl restart redis-serveret en cas d'échec donner les dernières lignes de :
journalctl -xeu redis-server.serviceLes logs d'Apache montrent une erreur 500 sans plus d'informations Il faut regarder les logs d'erreurs (error.log)
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#11 Le 13/11/2023, à 09:39
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
ubuntu@141:~$ sudo systemctl restart redis-server
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.
ubuntu@141:~$ sudo systemctl status redis-server.service
× redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-11-13 18:27:54 +11; 17s ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 3561217 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf --supervised systemd --daemonize no (code=ex> Main PID: 3561217 (code=exited, status=1/FAILURE)
Status: "Redis is loading..."
CPU: 64ms
nov. 13 18:27:54 141.145.209.128cpanel.maxitag.netcpanel systemd[1]: redis-server.service: Scheduled restart job, resta>nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Stopped Advanced key-value store.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Start request repeated too q>nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Failed with result 'exit-cod>nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Failed to start Advanced key-value store.
lines 1-15/15 (END)
× redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-11-13 18:27:54 +11; 17s ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 3561217 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf --supervised systemd --daemonize no (code=exi>
Main PID: 3561217 (code=exited, status=1/FAILURE)
Status: "Redis is loading..."
CPU: 64ms
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Scheduled restart job, restar>
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Stopped Advanced key-value store.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Start request repeated too qu>
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Failed with result 'exit-code>
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Failed to start Advanced key-value store.
~
~Ci-après les 'blocs noirs' en début de ligne sont en réalité des 'espaces'.
ubuntu@141:~$ sudo journalctl -xeu redis-server.service
The process' exit code is 'exited' and its exit status is 1.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: http://www.ubuntu.com/support
The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Failed to start Advanced key-value store.
Subject: L'unité (unit) redis-server.service a échoué
Defined-By: systemd
Support: http://www.ubuntu.com/support
L'unité (unit) redis-server.service a échoué, avec le résultat failed.
nov. 13 18:27:54 141.145.209.128cpanel.maxitag.netcpanel systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
Subject: Le redémarrage automatique d'une unité (unit) a été planifié
Defined-By: systemd
Support: http://www.ubuntu.com/support
Le redémarrage automatique de l'unité (unit) redis-server.service a été planifié, en
raison de sa configuration avec le paramètre Restart=.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Stopped Advanced key-value store.
░░ Subject: L'unité (unit) redis-server.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) redis-server.service a terminé son arrêt.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Start request repeated too quickly.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Failed to start Advanced key-value store.
░░ Subject: L'unité (unit) redis-server.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) redis-server.service a échoué, avec le résultat failed.
...skipping...
░░
░░ The process' exit code is 'exited' and its exit status is 1.
nov. 13 18:27:54 141.145.209.128cpanel.maxitag.netcpanel systemd[1]: redis-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Failed to start Advanced key-value store.
░░ Subject: L'unité (unit) redis-server.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) redis-server.service a échoué, avec le résultat failed.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) redis-server.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Stopped Advanced key-value store.
░░ Subject: L'unité (unit) redis-server.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) redis-server.service a terminé son arrêt.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Start request repeated too quickly.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: redis-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
nov. 13 18:27:54 141.145.209.128cpanel.moncloud.netcpanel systemd[1]: Failed to start Advanced key-value store.
░░ Subject: L'unité (unit) redis-server.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) redis-server.service a échoué, avec le résultat failed.Je vais regarder dans les log d'Apache
Hors ligne
#12 Le 13/11/2023, à 09:54
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
On ne voit pas l'erreur dans la sortie de journalctl… Peux-tu regarder dans /var/log/redis/redis-server.log
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#13 Le 13/11/2023, à 10:09
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
3516530:C 11 Nov 2023 16:08:24.397 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3516530:C 11 Nov 2023 16:08:24.397 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3516530:C 11 Nov 2023 16:08:24.397 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3516530, just started
3516530:C 11 Nov 2023 16:08:24.397 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3516530
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3516530:M 11 Nov 2023 16:08:24.399 # Server initialized
3516530:M 11 Nov 2023 16:08:24.399 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3516530:M 11 Nov 2023 16:08:24.403 * Ready to accept connections
3516530:signal-handler (1699679693) Received SIGTERM scheduling shutdown...
3516530:M 11 Nov 2023 16:14:53.250 # User requested shutdown...
3516530:M 11 Nov 2023 16:14:53.250 * Saving the final RDB snapshot before exiting.
3516530:M 11 Nov 2023 16:14:53.254 * DB saved on disk
3516530:M 11 Nov 2023 16:14:53.254 * Removing the pid file.
3516530:M 11 Nov 2023 16:14:53.254 # Redis is now ready to exit, bye bye...
3518232:C 11 Nov 2023 16:14:53.340 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3518232:C 11 Nov 2023 16:14:53.340 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3518232:C 11 Nov 2023 16:14:53.340 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3518232, just started
3518232:C 11 Nov 2023 16:14:53.340 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3518232
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3518232:M 11 Nov 2023 16:14:53.341 # Server initialized
3518232:M 11 Nov 2023 16:14:53.341 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3518232:M 11 Nov 2023 16:14:53.343 * Loading RDB produced by version 6.0.16
3518232:M 11 Nov 2023 16:14:53.343 * RDB age 0 seconds
3518232:M 11 Nov 2023 16:14:53.343 * RDB memory usage when created 0.80 Mb
3518232:M 11 Nov 2023 16:14:53.343 * DB loaded from disk: 0.000 seconds
3518232:M 11 Nov 2023 16:14:53.343 * Ready to accept connections
3518232:signal-handler (1699679947) Received SIGTERM scheduling shutdown...
3518232:M 11 Nov 2023 16:19:07.876 # User requested shutdown...
3518232:M 11 Nov 2023 16:19:07.876 * Saving the final RDB snapshot before exiting.
3518232:M 11 Nov 2023 16:19:07.879 * DB saved on disk
3518232:M 11 Nov 2023 16:19:07.879 * Removing the pid file.
3518232:M 11 Nov 2023 16:19:07.879 # Redis is now ready to exit, bye bye...
3518280:C 11 Nov 2023 16:19:07.958 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3518280:C 11 Nov 2023 16:19:07.959 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3518280:C 11 Nov 2023 16:19:07.959 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3518280, just started
3518280:C 11 Nov 2023 16:19:07.959 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3518280
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3518280:M 11 Nov 2023 16:19:07.960 # Server initialized
3518280:M 11 Nov 2023 16:19:07.960 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3518280:M 11 Nov 2023 16:19:07.963 * Loading RDB produced by version 6.0.16
3518280:M 11 Nov 2023 16:19:07.963 * RDB age 0 seconds
3518280:M 11 Nov 2023 16:19:07.963 * RDB memory usage when created 0.80 Mb
3518280:M 11 Nov 2023 16:19:07.963 * DB loaded from disk: 0.000 seconds
3518280:M 11 Nov 2023 16:19:07.963 * Ready to accept connections
3518280:M 11 Nov 2023 16:34:08.018 * 1 changes in 900 seconds. Saving...
3518280:M 11 Nov 2023 16:34:08.018 * Background saving started by pid 3518419
3518419:C 11 Nov 2023 16:34:08.021 * DB saved on disk
3518419:C 11 Nov 2023 16:34:08.022 * RDB: 0 MB of memory used by copy-on-write
3518280:M 11 Nov 2023 16:34:08.119 * Background saving terminated with success
3518280:signal-handler (1699710767) Received SIGTERM scheduling shutdown...
3518280:M 12 Nov 2023 00:52:48.045 # User requested shutdown...
3518280:M 12 Nov 2023 00:52:48.045 * Saving the final RDB snapshot before exiting.
3518280:M 12 Nov 2023 00:52:48.048 * DB saved on disk
3518280:M 12 Nov 2023 00:52:48.048 * Removing the pid file.
3518280:M 12 Nov 2023 00:52:48.048 # Redis is now ready to exit, bye bye...
3522508:C 12 Nov 2023 00:52:48.139 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3522508:C 12 Nov 2023 00:52:48.139 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3522508:C 12 Nov 2023 00:52:48.139 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3522508, just started
3522508:C 12 Nov 2023 00:52:48.139 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3522508
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3522508:M 12 Nov 2023 00:52:48.140 # Server initialized
3522508:M 12 Nov 2023 00:52:48.140 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3522508:M 12 Nov 2023 00:52:48.143 * Loading RDB produced by version 6.0.16
3522508:M 12 Nov 2023 00:52:48.143 * RDB age 0 seconds
3522508:M 12 Nov 2023 00:52:48.143 * RDB memory usage when created 0.80 Mb
3522508:M 12 Nov 2023 00:52:48.143 * DB loaded from disk: 0.000 seconds
3522508:M 12 Nov 2023 00:52:48.143 * Ready to accept connections
3522508:signal-handler (1699780421) Received SIGTERM scheduling shutdown...
3522508:M 12 Nov 2023 20:13:41.940 # User requested shutdown...
3522508:M 12 Nov 2023 20:13:41.940 * Saving the final RDB snapshot before exiting.
3522508:M 12 Nov 2023 20:13:41.943 * DB saved on disk
3522508:M 12 Nov 2023 20:13:41.943 * Removing the pid file.
3522508:M 12 Nov 2023 20:13:41.944 # Redis is now ready to exit, bye bye...
3542066:C 12 Nov 2023 20:13:42.023 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3542066:C 12 Nov 2023 20:13:42.023 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3542066:C 12 Nov 2023 20:13:42.023 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3542066, just started
3542066:C 12 Nov 2023 20:13:42.023 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3542066
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3542066:M 12 Nov 2023 20:13:42.024 # Server initialized
3542066:M 12 Nov 2023 20:13:42.024 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3542066:M 12 Nov 2023 20:13:42.027 * Loading RDB produced by version 6.0.16
3542066:M 12 Nov 2023 20:13:42.027 * RDB age 1 seconds
3542066:M 12 Nov 2023 20:13:42.027 * RDB memory usage when created 0.80 Mb
3542066:M 12 Nov 2023 20:13:42.027 * DB loaded from disk: 0.000 seconds
3542066:M 12 Nov 2023 20:13:42.027 * Ready to accept connections
3542066:signal-handler (1699797932) Received SIGTERM scheduling shutdown...
3542066:M 13 Nov 2023 01:05:32.647 # User requested shutdown...
3542066:M 13 Nov 2023 01:05:32.647 * Saving the final RDB snapshot before exiting.
3542066:M 13 Nov 2023 01:05:32.649 * DB saved on disk
3542066:M 13 Nov 2023 01:05:32.649 * Removing the pid file.
3542066:M 13 Nov 2023 01:05:32.649 # Redis is now ready to exit, bye bye...
3545408:C 13 Nov 2023 01:05:32.734 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3545408:C 13 Nov 2023 01:05:32.734 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3545408:C 13 Nov 2023 01:05:32.734 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3545408, just started
3545408:C 13 Nov 2023 01:05:32.734 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3545408
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3545408:M 13 Nov 2023 01:05:32.736 # Server initialized
3545408:M 13 Nov 2023 01:05:32.736 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3545408:M 13 Nov 2023 01:05:32.738 * Loading RDB produced by version 6.0.16
3545408:M 13 Nov 2023 01:05:32.738 * RDB age 0 seconds
3545408:M 13 Nov 2023 01:05:32.738 * RDB memory usage when created 0.80 Mb
3545408:M 13 Nov 2023 01:05:32.738 * DB loaded from disk: 0.000 seconds
3545408:M 13 Nov 2023 01:05:32.738 * Ready to accept connections
3545408:signal-handler (1699799355) Received SIGTERM scheduling shutdown...
3545408:M 13 Nov 2023 01:29:15.268 # User requested shutdown...
3545408:M 13 Nov 2023 01:29:15.269 * Saving the final RDB snapshot before exiting.
3545408:M 13 Nov 2023 01:29:15.271 * DB saved on disk
3545408:M 13 Nov 2023 01:29:15.271 * Removing the pid file.
3545408:M 13 Nov 2023 01:29:15.271 # Redis is now ready to exit, bye bye...
3545911:C 13 Nov 2023 01:29:15.371 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3545911:C 13 Nov 2023 01:29:15.371 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3545911:C 13 Nov 2023 01:29:15.371 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3545911, just started
3545911:C 13 Nov 2023 01:29:15.371 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3545911
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3545911:M 13 Nov 2023 01:29:15.372 # Server initialized
3545911:M 13 Nov 2023 01:29:15.372 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3545911:M 13 Nov 2023 01:29:15.375 * Loading RDB produced by version 6.0.16
3545911:M 13 Nov 2023 01:29:15.375 * RDB age 0 seconds
3545911:M 13 Nov 2023 01:29:15.375 * RDB memory usage when created 0.80 Mb
3545911:M 13 Nov 2023 01:29:15.375 * DB loaded from disk: 0.000 seconds
3545911:M 13 Nov 2023 01:29:15.375 * Ready to accept connections
3545911:signal-handler (1699799637) Received SIGTERM scheduling shutdown...
3545911:M 13 Nov 2023 01:33:57.756 # User requested shutdown...
3545911:M 13 Nov 2023 01:33:57.756 * Saving the final RDB snapshot before exiting.
3545911:M 13 Nov 2023 01:33:57.759 * DB saved on disk
3545911:M 13 Nov 2023 01:33:57.759 * Removing the pid file.
3545911:M 13 Nov 2023 01:33:57.759 # Redis is now ready to exit, bye bye...
3546030:C 13 Nov 2023 01:33:57.852 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546030:C 13 Nov 2023 01:33:57.852 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546030:C 13 Nov 2023 01:33:57.852 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546030, just started
3546030:C 13 Nov 2023 01:33:57.852 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3546030
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3546030:M 13 Nov 2023 01:33:57.854 # Server initialized
3546030:M 13 Nov 2023 01:33:57.854 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3546030:M 13 Nov 2023 01:33:57.856 * Loading RDB produced by version 6.0.16
3546030:M 13 Nov 2023 01:33:57.856 * RDB age 0 seconds
3546030:M 13 Nov 2023 01:33:57.856 * RDB memory usage when created 0.80 Mb
3546030:M 13 Nov 2023 01:33:57.856 * DB loaded from disk: 0.000 seconds
3546030:M 13 Nov 2023 01:33:57.856 * Ready to accept connections
3546030:signal-handler (1699799840) Received SIGTERM scheduling shutdown...
3546030:M 13 Nov 2023 01:37:20.181 # User requested shutdown...
3546030:M 13 Nov 2023 01:37:20.181 * Saving the final RDB snapshot before exiting.
3546030:M 13 Nov 2023 01:37:20.184 * DB saved on disk
3546030:M 13 Nov 2023 01:37:20.184 * Removing the pid file.
3546030:M 13 Nov 2023 01:37:20.185 # Redis is now ready to exit, bye bye...
3546131:C 13 Nov 2023 01:37:20.276 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546131:C 13 Nov 2023 01:37:20.276 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546131:C 13 Nov 2023 01:37:20.276 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546131, just started
3546131:C 13 Nov 2023 01:37:20.276 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 3546131
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
3546131:M 13 Nov 2023 01:37:20.277 # Server initialized
3546131:M 13 Nov 2023 01:37:20.277 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
3546131:M 13 Nov 2023 01:37:20.280 * Loading RDB produced by version 6.0.16
3546131:M 13 Nov 2023 01:37:20.280 * RDB age 0 seconds
3546131:M 13 Nov 2023 01:37:20.280 * RDB memory usage when created 0.80 Mb
3546131:M 13 Nov 2023 01:37:20.280 * DB loaded from disk: 0.000 seconds
3546131:M 13 Nov 2023 01:37:20.280 * Ready to accept connections
3546131:signal-handler (1699800730) Received SIGTERM scheduling shutdown...
3546131:M 13 Nov 2023 01:52:10.934 # User requested shutdown...
3546131:M 13 Nov 2023 01:52:10.934 * Saving the final RDB snapshot before exiting.
3546131:M 13 Nov 2023 01:52:10.937 * DB saved on disk
3546131:M 13 Nov 2023 01:52:10.937 * Removing the pid file.
3546131:M 13 Nov 2023 01:52:10.937 # Redis is now ready to exit, bye bye...
3546363:C 13 Nov 2023 01:52:11.022 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546363:C 13 Nov 2023 01:52:11.022 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546363:C 13 Nov 2023 01:52:11.022 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546363, just started
3546363:C 13 Nov 2023 01:52:11.022 # Configuration loaded
3546363:M 13 Nov 2023 01:52:11.023 # Configured to not listen anywhere, exiting.
3546368:C 13 Nov 2023 01:52:11.285 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546368:C 13 Nov 2023 01:52:11.285 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546368:C 13 Nov 2023 01:52:11.285 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546368, just started
3546368:C 13 Nov 2023 01:52:11.285 # Configuration loaded
3546368:M 13 Nov 2023 01:52:11.286 # Configured to not listen anywhere, exiting.
3546371:C 13 Nov 2023 01:52:11.528 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546371:C 13 Nov 2023 01:52:11.528 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546371:C 13 Nov 2023 01:52:11.528 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546371, just started
3546371:C 13 Nov 2023 01:52:11.528 # Configuration loaded
3546371:M 13 Nov 2023 01:52:11.529 # Configured to not listen anywhere, exiting.
3546375:C 13 Nov 2023 01:52:11.781 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546375:C 13 Nov 2023 01:52:11.781 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546375:C 13 Nov 2023 01:52:11.781 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546375, just started
3546375:C 13 Nov 2023 01:52:11.781 # Configuration loaded
3546375:M 13 Nov 2023 01:52:11.781 # Configured to not listen anywhere, exiting.
3546379:C 13 Nov 2023 01:52:12.040 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546379:C 13 Nov 2023 01:52:12.040 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546379:C 13 Nov 2023 01:52:12.040 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546379, just started
3546379:C 13 Nov 2023 01:52:12.040 # Configuration loaded
3546379:M 13 Nov 2023 01:52:12.041 # Configured to not listen anywhere, exiting.
3546411:C 13 Nov 2023 01:52:31.760 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546411:C 13 Nov 2023 01:52:31.760 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546411:C 13 Nov 2023 01:52:31.760 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546411, just started
3546411:C 13 Nov 2023 01:52:31.760 # Configuration loaded
3546411:M 13 Nov 2023 01:52:31.760 # Configured to not listen anywhere, exiting.
3546416:C 13 Nov 2023 01:52:32.024 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546416:C 13 Nov 2023 01:52:32.024 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546416:C 13 Nov 2023 01:52:32.024 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546416, just started
3546416:C 13 Nov 2023 01:52:32.024 # Configuration loaded
3546416:M 13 Nov 2023 01:52:32.025 # Configured to not listen anywhere, exiting.
3546420:C 13 Nov 2023 01:52:32.288 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546420:C 13 Nov 2023 01:52:32.288 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546420:C 13 Nov 2023 01:52:32.288 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546420, just started
3546420:C 13 Nov 2023 01:52:32.288 # Configuration loaded
3546420:M 13 Nov 2023 01:52:32.289 # Configured to not listen anywhere, exiting.
3546423:C 13 Nov 2023 01:52:32.540 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546423:C 13 Nov 2023 01:52:32.541 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546423:C 13 Nov 2023 01:52:32.541 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546423, just started
3546423:C 13 Nov 2023 01:52:32.541 # Configuration loaded
3546423:M 13 Nov 2023 01:52:32.541 # Configured to not listen anywhere, exiting.
3546427:C 13 Nov 2023 01:52:32.791 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546427:C 13 Nov 2023 01:52:32.792 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546427:C 13 Nov 2023 01:52:32.792 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546427, just started
3546427:C 13 Nov 2023 01:52:32.792 # Configuration loaded
3546427:M 13 Nov 2023 01:52:32.793 # Configured to not listen anywhere, exiting.
3546495:C 13 Nov 2023 01:55:44.636 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546495:C 13 Nov 2023 01:55:44.636 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546495:C 13 Nov 2023 01:55:44.636 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546495, just started
3546495:C 13 Nov 2023 01:55:44.636 # Configuration loaded
3546495:M 13 Nov 2023 01:55:44.637 # Configured to not listen anywhere, exiting.
3546498:C 13 Nov 2023 01:55:45.024 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546498:C 13 Nov 2023 01:55:45.024 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546498:C 13 Nov 2023 01:55:45.024 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546498, just started
3546498:C 13 Nov 2023 01:55:45.024 # Configuration loaded
3546498:M 13 Nov 2023 01:55:45.025 # Configured to not listen anywhere, exiting.
3546501:C 13 Nov 2023 01:55:45.282 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546501:C 13 Nov 2023 01:55:45.282 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546501:C 13 Nov 2023 01:55:45.282 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546501, just started
3546501:C 13 Nov 2023 01:55:45.282 # Configuration loaded
3546501:M 13 Nov 2023 01:55:45.283 # Configured to not listen anywhere, exiting.
3546504:C 13 Nov 2023 01:55:45.524 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546504:C 13 Nov 2023 01:55:45.525 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546504:C 13 Nov 2023 01:55:45.525 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546504, just started
3546504:C 13 Nov 2023 01:55:45.525 # Configuration loaded
3546504:M 13 Nov 2023 01:55:45.525 # Configured to not listen anywhere, exiting.
3546507:C 13 Nov 2023 01:55:45.781 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3546507:C 13 Nov 2023 01:55:45.782 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3546507:C 13 Nov 2023 01:55:45.782 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3546507, just started
3546507:C 13 Nov 2023 01:55:45.782 # Configuration loaded
3546507:M 13 Nov 2023 01:55:45.782 # Configured to not listen anywhere, exiting.
3561130:C 13 Nov 2023 18:26:18.754 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561130:C 13 Nov 2023 18:26:18.754 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561130:C 13 Nov 2023 18:26:18.754 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561130, just started
3561130:C 13 Nov 2023 18:26:18.754 # Configuration loaded
3561130:M 13 Nov 2023 18:26:18.755 # Configured to not listen anywhere, exiting.
3561135:C 13 Nov 2023 18:26:19.023 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561135:C 13 Nov 2023 18:26:19.023 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561135:C 13 Nov 2023 18:26:19.023 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561135, just started
3561135:C 13 Nov 2023 18:26:19.023 # Configuration loaded
3561135:M 13 Nov 2023 18:26:19.024 # Configured to not listen anywhere, exiting.
3561139:C 13 Nov 2023 18:26:19.279 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561139:C 13 Nov 2023 18:26:19.279 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561139:C 13 Nov 2023 18:26:19.279 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561139, just started
3561139:C 13 Nov 2023 18:26:19.279 # Configuration loaded
3561139:M 13 Nov 2023 18:26:19.280 # Configured to not listen anywhere, exiting.
3561144:C 13 Nov 2023 18:26:19.531 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561144:C 13 Nov 2023 18:26:19.531 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561144:C 13 Nov 2023 18:26:19.531 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561144, just started
3561144:C 13 Nov 2023 18:26:19.531 # Configuration loaded
3561144:M 13 Nov 2023 18:26:19.531 # Configured to not listen anywhere, exiting.
3561149:C 13 Nov 2023 18:26:19.779 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561149:C 13 Nov 2023 18:26:19.779 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561149:C 13 Nov 2023 18:26:19.779 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561149, just started
3561149:C 13 Nov 2023 18:26:19.779 # Configuration loaded
3561149:M 13 Nov 2023 18:26:19.779 # Configured to not listen anywhere, exiting.
3561204:C 13 Nov 2023 18:27:53.835 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561204:C 13 Nov 2023 18:27:53.835 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561204:C 13 Nov 2023 18:27:53.835 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561204, just started
3561204:C 13 Nov 2023 18:27:53.835 # Configuration loaded
3561204:M 13 Nov 2023 18:27:53.836 # Configured to not listen anywhere, exiting.
3561207:C 13 Nov 2023 18:27:54.023 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561207:C 13 Nov 2023 18:27:54.023 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561207:C 13 Nov 2023 18:27:54.023 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561207, just started
3561207:C 13 Nov 2023 18:27:54.023 # Configuration loaded
3561207:M 13 Nov 2023 18:27:54.024 # Configured to not listen anywhere, exiting.
3561210:C 13 Nov 2023 18:27:54.283 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561210:C 13 Nov 2023 18:27:54.283 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561210:C 13 Nov 2023 18:27:54.283 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561210, just started
3561210:C 13 Nov 2023 18:27:54.283 # Configuration loaded
3561210:M 13 Nov 2023 18:27:54.284 # Configured to not listen anywhere, exiting.
3561214:C 13 Nov 2023 18:27:54.523 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561214:C 13 Nov 2023 18:27:54.523 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561214:C 13 Nov 2023 18:27:54.523 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561214, just started
3561214:C 13 Nov 2023 18:27:54.523 # Configuration loaded
3561214:M 13 Nov 2023 18:27:54.524 # Configured to not listen anywhere, exiting.
3561217:C 13 Nov 2023 18:27:54.784 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3561217:C 13 Nov 2023 18:27:54.784 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3561217:C 13 Nov 2023 18:27:54.784 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=3561217, just started
3561217:C 13 Nov 2023 18:27:54.784 # Configuration loaded
3561217:M 13 Nov 2023 18:27:54.785 # Configured to not listen anywhere, exiting.Hors ligne
#14 Le 13/11/2023, à 10:15
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Ok , je vois cette ligne :
3561214:M 13 Nov 2023 18:27:54.524 # Configured to not listen anywhere, exiting.Est-ce que l'écoute sur socket UNIX est bien spécifiée (et non commentée) dans le fichier redis.conf, exemple :
unixsocket /run/redis/redis-server.sock
unixsocketperm 770Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#15 Le 13/11/2023, à 10:25
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Ces 2 lignes étaient bien commentées, je viens de les décommenter,
J'ai relancé Apache et redis
Toujours le même problème.
La valeur initiale (quand commenté) était à 700, je l'ai passée à 770 (comme sur ton #14)
J'ai relancé Apache et redis
Toujours le même problème.
Pour limiter le temps que je te 'prends' (désolé), peut-être plus simple de revenir simple à APCu et donc, "tant pis" pour le compte rendu de NC !
Hors ligne
#16 Le 13/11/2023, à 10:32
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Toujours le même problème
C'est à dire ? Redis-server ne veut pas se lancer ? Les logs de redis disent toujours la même chose ?
L'utilisateur www-data est-il bien dans le groupe redis pour pouvoir accéder au socket ? Le cas échéant :
sudo adduser www-data redisAttention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#17 Le 13/11/2023, à 10:45
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Oui, www-data est déjà
L'utilisateur « www-data » appartient déjà au groupe « redis ».
Je veux dire que je ne peux pas/plus glisser/déposer de fichier de mon win vers mon interface NC
En relachant un glisser/Déposer j'ai
"Connexion au serveur perdu"
"Une erreur inconnue est survenue"
Hors ligne
#18 Le 13/11/2023, à 10:48
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Ce n'est pas ce que je demande…
Est-ce que maintenant redis-server se lance sans erreur ?
systemctl status redis-serverAttention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#19 Le 13/11/2023, à 10:51
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Oui,
Status: "Ready to accept connections"Hors ligne
#20 Le 13/11/2023, à 10:59
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Ok, c'est un problème de réglé.
Maintenant quand tu essaies d'envoyer un fichier, regarde les logs d'Apache, access.log et error.log. On a vu une erreur 500 au #9, c'est le signe d'un problème de configuration Apache ou une erreur fatale dans un script PHP. En #4 tu indiquais une erreur PHP…
Dernière modification par bruno (Le 13/11/2023, à 11:02)
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#21 Le 13/11/2023, à 11:45
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Fichier error.log
[Mon Nov 13 00:00:02.483342 2023] [mpm_prefork:notice] [pid 3542095] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 00:00:02.483550 2023] [core:notice] [pid 3542095] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 01:05:39.687011 2023] [mpm_prefork:notice] [pid 3542095] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 01:05:39.876256 2023] [mpm_prefork:notice] [pid 3545433] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 01:05:39.876428 2023] [core:notice] [pid 3545433] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 01:29:21.086946 2023] [mpm_prefork:notice] [pid 3545433] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 01:29:21.274162 2023] [mpm_prefork:notice] [pid 3545933] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 01:29:21.274215 2023] [core:notice] [pid 3545933] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 01:33:53.526945 2023] [mpm_prefork:notice] [pid 3545933] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 01:33:53.682160 2023] [mpm_prefork:notice] [pid 3546011] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 01:33:53.682214 2023] [core:notice] [pid 3546011] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 01:37:16.603108 2023] [mpm_prefork:notice] [pid 3546011] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 01:37:16.793982 2023] [mpm_prefork:notice] [pid 3546113] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 01:37:16.794132 2023] [core:notice] [pid 3546113] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 01:52:26.603937 2023] [mpm_prefork:notice] [pid 3546113] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 01:52:26.802952 2023] [mpm_prefork:notice] [pid 3546396] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 01:52:26.803125 2023] [core:notice] [pid 3546396] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 19:18:03.687799 2023] [mpm_prefork:notice] [pid 3546396] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 19:18:03.853412 2023] [mpm_prefork:notice] [pid 3562364] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 19:18:03.853596 2023] [core:notice] [pid 3562364] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 19:19:45.913234 2023] [mpm_prefork:notice] [pid 3562364] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 19:19:46.097389 2023] [mpm_prefork:notice] [pid 3562448] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 19:19:46.097446 2023] [core:notice] [pid 3562448] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 13 20:39:04.830480 2023] [mpm_prefork:notice] [pid 3562448] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Nov 13 20:39:05.025355 2023] [mpm_prefork:notice] [pid 3563600] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Mon Nov 13 20:39:05.025521 2023] [core:notice] [pid 3563600] AH00094: Command line: '/usr/sbin/apache2'Fichier access.log (pas très bavard)
il est complètement vierge !
Hors ligne
#22 Le 13/11/2023, à 11:55
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Et l'erreur que tu indiquais en # 4 elle sortait d'où ?
Est-ce que tu examines bien les logs correspondant à ton instance nextcloud ? D'après ton message dans l'autre fil il sont ici :
/var/log/apache2/error.cloud.moncloud.net.log
/var/log/apache2/access.cloud.moncloud.net.log
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#23 Le 13/11/2023, à 12:23
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
Arf, je regardais ceux de apache2;
voici pour NC
[Mon Nov 13 01:36:43.954933 2023] [php:error] [pid 3546017] [client 45.63.29.11:55255] PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /var/www/nextcloud/remote.php:54\nStack trace:\n#0 /var/www/nextcloud/remote.php(176): handleException()\n#1 {main}\n thrown in /var/www/nextcloud/remote.php on line 54
[Mon Nov 13 01:36:44.416434 2023] [php:error] [pid 3546021] [client 45.63.29.11:55256] PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /var/www/nextcloud/remote.php:54\nStack trace:\n#0 /var/www/nextcloud/remote.php(176): handleException()\n#1 {main}\n thrown in /var/www/nextcloud/remote.php on line 54
[Mon Nov 13 01:36:44.531097 2023] [php:error] [pid 3546018] [client 45.63.29.11:55257] PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /var/www/nextcloud/remote.php:54\nStack trace:\n#0 /var/www/nextcloud/remote.php(176): handleException()\n#1 {main}\n thrown in /var/www/nextcloud/remote.php on line 54
[Mon Nov 13 01:36:45.113624 2023] [php:error] [pid 3546014] [client 45.63.29.11:55258] PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /var/www/nextcloud/remote.php:54\nStack trace:\n#0 /var/www/nextcloud/remote.php(176): handleException()\n#1 {main}\n thrown in /var/www/nextcloud/remote.php on line 54
[Mon Nov 13 01:36:45.334427 2023] [php:error] [pid 3546020] [client 45.63.29.11:55259] PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /var/www/nextcloud/remote.php:54\nStack trace:\n#0 /var/www/nextcloud/remote.php(176): handleException()\n#1 {main}\n thrown in /var/www/nextcloud/remote.php on line 54
[Mon Nov 13 01:36:45.372757 2023] [php:error] [pid 3546012] [client 45.63.29.11:55260] PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /var/www/nextcloud/remote.php:54\nStack trace:\n#0 /var/www/nextcloud/remote.php(176): handleException()\n#1 {main}\n thrown in /var/www/nextcloud/remote.php on line 54Et maintenant le remote.php (je laisse le 'copyright de début) pour que la ligne 54 reste bien la ligne 54
<?php
/**
* @copyright Copyright (c) 2016, ownCloud, Inc.
*
* @author Brice Maron <brice@bmaron.net>
* @author Christopher Schäpers <kondou@ts.unde.re>
* @author Christoph Wurst <christoph@winzerhof-wurst.at>
* @author Georg Ehrke <oc.list@georgehrke.com>
* @author Joas Schilling <coding@schilljs.com>
* @author Jörn Friedrich Dreyer <jfd@butonic.de>
* @author Lukas Reschke <lukas@statuscode.ch>
* @author Morris Jobke <hey@morrisjobke.de>
* @author Robin Appelman <robin@icewind.nl>
* @author Robin McCorkell <robin@mccorkell.me.uk>
* @author Roeland Jago Douma <roeland@famdouma.nl>
* @author Thomas Müller <thomas.mueller@tmit.eu>
* @author Vincent Petry <vincent@nextcloud.com>
*
* @license AGPL-3.0
*
* This code is free software: you can redistribute it and/or modify
* it under the terms of the GNU Affero General Public License, version 3,
* as published by the Free Software Foundation.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Affero General Public License for more details.
*
* You should have received a copy of the GNU Affero General Public License, version 3,
* along with this program. If not, see <http://www.gnu.org/licenses/>
*
*/
require_once __DIR__ . '/lib/versioncheck.php';
use OCA\DAV\Connector\Sabre\ExceptionLoggerPlugin;
use Sabre\DAV\Exception\ServiceUnavailable;
use Sabre\DAV\Server;
use Psr\Log\LoggerInterface;
/**
* Class RemoteException
* Dummy exception class to be use locally to identify certain conditions
* Will not be logged to avoid DoS
*/
class RemoteException extends Exception {
}
/**
* @param Exception|Error $e
*/
function handleException($e) {
try {
$request = \OC::$server->getRequest();
// in case the request content type is text/xml - we assume it's a WebDAV request
$isXmlContentType = strpos($request->getHeader('Content-Type'), 'text/xml');
if ($isXmlContentType === 0) {
// fire up a simple server to properly process the exception
$server = new Server();
if (!($e instanceof RemoteException)) {
// we shall not log on RemoteException
$server->addPlugin(new ExceptionLoggerPlugin('webdav', \OC::$server->get(LoggerInterface::class)));
}
$server->on('beforeMethod:*', function () use ($e) {
if ($e instanceof RemoteException) {
switch ($e->getCode()) {
case 503:
throw new ServiceUnavailable($e->getMessage());
case 404:
throw new \Sabre\DAV\Exception\NotFound($e->getMessage());
}
}
$class = get_class($e);
$msg = $e->getMessage();
throw new ServiceUnavailable("$class: $msg");
});
$server->exec();
} else {
$statusCode = 500;
if ($e instanceof \OC\ServiceUnavailableException) {
$statusCode = 503;
}
if ($e instanceof RemoteException) {
// we shall not log on RemoteException
OC_Template::printErrorPage($e->getMessage(), '', $e->getCode());
} else {
\OC::$server->get(LoggerInterface::class)->error($e->getMessage(), ['app' => 'remote','exception' => $e]);
OC_Template::printExceptionErrorPage($e, $statusCode);
}
}
} catch (\Exception $e) {
OC_Template::printExceptionErrorPage($e, 500);
}
}
/**
* @param $service
* @return string
*/
function resolveService($service) {
$services = [
'webdav' => 'dav/appinfo/v1/webdav.php',
'dav' => 'dav/appinfo/v2/remote.php',
'caldav' => 'dav/appinfo/v1/caldav.php',
'calendar' => 'dav/appinfo/v1/caldav.php',
'carddav' => 'dav/appinfo/v1/carddav.php',
'contacts' => 'dav/appinfo/v1/carddav.php',
'files' => 'dav/appinfo/v1/webdav.php',
'direct' => 'dav/appinfo/v2/direct.php',
];
if (isset($services[$service])) {
return $services[$service];
}
return \OC::$server->getConfig()->getAppValue('core', 'remote_' . $service);
}
try {
require_once __DIR__ . '/lib/base.php';
// All resources served via the DAV endpoint should have the strictest possible
// policy. Exempted from this is the SabreDAV browser plugin which overwrites
// this policy with a softer one if debug mode is enabled.
header("Content-Security-Policy: default-src 'none';");
if (\OCP\Util::needUpgrade()) {
// since the behavior of apps or remotes are unpredictable during
// an upgrade, return a 503 directly
throw new RemoteException('Service unavailable', 503);
}
$request = \OC::$server->getRequest();
$pathInfo = $request->getPathInfo();
if ($pathInfo === false || $pathInfo === '') {
throw new RemoteException('Path not found', 404);
}
if (!$pos = strpos($pathInfo, '/', 1)) {
$pos = strlen($pathInfo);
}
$service = substr($pathInfo, 1, $pos - 1);
$file = resolveService($service);
if (is_null($file)) {
throw new RemoteException('Path not found', 404);
}
$file = ltrim($file, '/');
$parts = explode('/', $file, 2);
$app = $parts[0];
// Load all required applications
\OC::$REQUESTEDAPP = $app;
OC_App::loadApps(['authentication']);
OC_App::loadApps(['extended_authentication']);
OC_App::loadApps(['filesystem', 'logging']);
switch ($app) {
case 'core':
$file = OC::$SERVERROOT .'/'. $file;
break;
default:
if (!\OC::$server->getAppManager()->isInstalled($app)) {
throw new RemoteException('App not installed: ' . $app);
}
OC_App::loadApp($app);
$file = OC_App::getAppPath($app) .'/'. $parts[1];
break;
}
$baseuri = OC::$WEBROOT . '/remote.php/'.$service.'/';
require_once $file;
} catch (Exception $ex) {
handleException($ex);
} catch (Error $e) {
handleException($e);
}Et mon access.log j'ai des erreurs 500 en essayant de déposer un fichier.
202.176.156.87 - - [13/Nov/2023:21:15:37 +1100] "PUT /remote.php/webdav/Documents/test_Igor.log HTTP/1.1" 500 1133 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"Hors ligne
#24 Le 13/11/2023, à 12:55
- bruno
Re : Utilisation "redis" Nextcloud [RESOLU]
Étrange…
Il y a peut-être une erreur dans le fichier config.php. Peux-tu le redonner intégralement (en masquant les mots de passe !)
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#25 Le 13/11/2023, à 13:14
- waca
Re : Utilisation "redis" Nextcloud [RESOLU]
<?php
$CONFIG = array (
'memcache.local' => '\\OC\\Memcache\\APCu',
'filelocking.enabled' => true,
'memcache.locking' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => '/run/redis/redis-server.sock',
'port' => 0,
'timeout' => 0,0,
'dbindex' => 0,
),
'instanceid' => 'ocx410z1x49l',
'passwordsalt' => 'NaFHleo93kGSTv/kaumun/zC971VWu',
'secret' => 'G24SOoqKg9IOZ5ATKLiOPZ_!79wF9AnZvb865Cbxt+fi8jZh',
'trusted_domains' =>
array (
0 => 'cloud.moncloud.net',
),
'datadirectory' => '/var/www/nextcloud-data',
'dbtype' => 'mysql',
'version' => '27.1.3.2',
'overwrite.cli.url' => 'https://cloud.moncloud.net',
'dbname' => 'nextcloud',
'dbhost' => 'localhost',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => 'cmoid',
'dbpassword' => 'lepasswd',
'installed' => true,
'mail_smtpmode' => 'smtp',
'mail_smtpsecure' => 'tls',
'mail_sendmailmode' => 'smtp',
'mail_from_address' => 'cloud',
'mail_domain' => 'moncloud.net',
'mail_smtpauthtype' => 'PLAIN',
'mail_smtpauth' => 1,
'mail_smtphost' => 'ssl0.ovh.net',
'mail_smtpport' => '587',
'mail_smtpname' => 'cloud@moncloud.net',
'mail_smtppassword' => 'Alpha00',
'default_phone_region' => 'FR',
'filelocking.enabled' => 'false',
'trashbin_retention_obligation' => 'auto',
'versions_retention_obligation' => 'auto',
'memcache.local' => '\\OC\\Memcache\\APCu',
'app_install_overwrite' =>
array (
0 => 'printer',
1 => 'quicknotes',
2 => 'richdocumentscode',
3 => 'socialsharing_telegram',
4 => 'caniupdate',
5 => 'ocsms',
6 => 'talk_simple_poll',
7 => 'talk_matterbridge',
8 => 'talked',
9 => 'ocjobs',
10 => 'wopi',
),
'maintenance' => false,
'theme' => '',
'loglevel' => 2,
'has_rebuilt_cache' => true,
'twofactor_enforced' => 'false',
'twofactor_enforced_groups' =>
array (
),
'twofactor_enforced_excluded_groups' =>
array (
0 => 'Famille',
1 => 'NW',
),
);Hors ligne