Debian Debian-France Debian-Facile Debian-fr.org Forum-Debian.fr Debian ? Communautés

Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

#1 Re : Matériel » Un ecommande ntfsfix qui ne résoud pas toput. » 21-09-2022 11:25:24

Bonjour wink
Bon. J'ai dû me tromper.
En tout cas, le disque Mac n'est pas réparable (je ne m'y risquerais pas : trop de données médicales très importantes).

Je n'ai (et en root) qu'un accès en lecture sur ce disque.
Resterait GParted, mais pas question de me voir reprocher d'avoir flingué quoi que ce soit.


Alors, pour les virgules dans les noms de fichiers, oui ça passe... plus ou moins sur une partition Windows.

J'ai fait comme ça : source : dd Mac, destination  : partition EXT4, puis copie de ce que je pouvais repérer avec ces noms bizarres, vers une partition NTFS. Si j'y allais directement sur une partition Windows, catastrophe. Plantage du gestionnaire de fichiers (pourtant très sûr) et chkdsk /f indispensable aussitôt après.

Quelle idée de créer et/ou renommer des répertoires et fichiers comme ça kernal_panic.gif

#2 Re : Matériel » Un ecommande ntfsfix qui ne résoud pas toput. » 13-09-2022 17:43:28

Merci, Ubub !

Pour Bullseye. Je verrai bien si ça existe pour Buster.

#3 Re : Matériel » Un ecommande ntfsfix qui ne résoud pas toput. » 13-09-2022 17:06:55

Désolé pour l'exhumation de post, mais je commence à avoir des doutes sur le disque source, partitionné et formaté sous Mac.
Ca fait X fois qu'il me contraint à un chkdsk /f sur le disque de destination. Il doit être lu sous Windows : donc : formaté NTFS.

Or, le disque source, très ancien, a été partitionné et formaté sous Mac.
Ce que je prenais pour de la fragmentation (elle existe aussi un petit peu sous Linux), ne serait-il pas des erreurs d'accès disque ?

En clair : sous Linux, et sans trop de risque, existe-t-il une façon de faire pour réparer le système de fichiers d'un Mac ?

Après tout, Mac OS, c'est du Debian...

GParted ? Je ne sais pas s'il est conçu pour ça.

De toute façon, avant toute "artisterie" (je parle pour moi, pas pour vous wink ) sur ce disque, j'en fais une image avec CloneZilla. Le disque en question (le Mac) n'est pas occupé à plus de 700 Go. Peu importe qu'il supporte 3 To...

Qu'en pensez-vous ?

Ca gratte, ça gratte... Mais c'est peut-être à cause, non de sa fragmentation, mais d'erreurs d'écriture ?

#4 Re : Matériel » Un ecommande ntfsfix qui ne résoud pas toput. » 12-09-2022 18:01:25

Désolé... Il a tiré plus vite que moi.
Un chkdsk /f semble avoir résolu le problème.

Mais, pour mon information personnelle : Mac Os (qui descend de Debian) accepte les nom de fichiers de type : blabla:09:2016 ??

#5 Matériel » Un ecommande ntfsfix qui ne résoud pas toput. » 12-09-2022 17:42:16

Lupa
Réponses : 8
Bonjour à tous smile

La commande :


ntfsfix /dev/sdc1
 



Elle me disait que le problème était résolu. Non, pas vraiment.

Contexte

Je récupère de très précieux fichiers depuis un dd externe partitionné, formaté et utilisé sous Mac OS. 3 To. Partitionnement GPT bien sûr.

Or, lorsque j'ai tenté de le monter sous Win10, impossible. La gestion des fichiers voyait bien une partition GPT, avec même une EFI etc. Mais pas Explorer. Je me suis dit que Linux lirait ce disque. C'est exact.

Vu le contenu plus que bizarre (des nom de répertoire et/ou fichiers avec des ':' notamment, que je vais forcément renommer) j'ai commencé la copie des dossiers vers un 2 To NTFS. Partitionné et formaté par GParted.

Ca prend des plombes, mais tant pis. Les fichiers n'étant pas lisibles sous Windows le seront sans doute sous Mac. Dans le bureau du propriétaire, il travaille sous Windows 10.

Nous sommes donc sur mon 2 To, et surtout pas sur le disque à sauvegarder ! AUCUN accès en écriture là-dessus.
Mais...

J'ai dû faire une bêtise en le démontant. Mal ou trop vite. Résultat : impossible de le monter à nouveau.
J'ai donc saisi cette commande ci-dessus.
Mais PAS sur le /dev/sdc : sur le /dev/sdc1 !

La même commande sur le /dev/sdc me retourne un erreur.
Gparted, lancé à la rescousse sur mon 2 To, m'affiche un fichier .htm TRES long. Je vais essayer de le mettre ici :




GParted 0.32.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Vérifier et réparer le système de fichiers (ntfs) sur /dev/sdd1  00:00:04    ( ERREUR )
     
calibrer /dev/sdd1  00:00:00    ( SUCCÈS )
     
chemin : /dev/sdd1 (partition)
début : 2048
fin : 3907028991
taille : 3907026944 (1.82 Tio)
vérifier le système de fichiers sur /dev/sdd1 et corriger les problèmes (si possible)  00:00:04    ( ERREUR )
     
ntfsresize -i -f -v '/dev/sdd1'  00:00:04    ( ERREUR )
     
ntfsresize v2017.3.23AR.3 (libntfs-3g)
Device name : /dev/sdd1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 2000397791744 bytes (2000398 MB)
Current device size: 2000397795328 bytes (2000398 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Cluster 61067039 is referenced multiple times!
Cluster 61095536 is referenced multiple times!
Cluster 61095537 is referenced multiple times!
Cluster 61095538 is referenced multiple times!
Cluster 61095539 is referenced multiple times!
Cluster 61095540 is referenced multiple times!
Cluster 61095541 is referenced multiple times!
Cluster 61095542 is referenced multiple times!
Cluster 61095543 is referenced multiple times!
Cluster 61095544 is referenced multiple times!
Cluster 61095545 is referenced multiple times!
Cluster 61095546 is referenced multiple times!
Cluster 61095547 is referenced multiple times!
Cluster 61095548 is referenced multiple times!
Cluster 61099853 is referenced multiple times!
Cluster 61141594 is referenced multiple times!
Cluster 61151092 is referenced multiple times!
Cluster 61151093 is referenced multiple times!
Cluster 61151094 is referenced multiple times!
Cluster 61151095 is referenced multiple times!
Cluster 61151096 is referenced multiple times!
Cluster 61151097 is referenced multiple times!
Cluster 61151098 is referenced multiple times!
Cluster 61151099 is referenced multiple times!
Cluster 61151100 is referenced multiple times!
Cluster 61151101 is referenced multiple times!
Cluster 61151102 is referenced multiple times!
Cluster 61151103 is referenced multiple times!
Cluster 61151104 is referenced multiple times!
Cluster 61151105 is referenced multiple times!
Cluster 61217950 is referenced multiple times!
Cluster 61217951 is referenced multiple times!
Cluster 61217952 is referenced multiple times!
Cluster 61217953 is referenced multiple times!
Cluster 61217954 is referenced multiple times!
Cluster 61217955 is referenced multiple times!
Cluster 61217956 is referenced multiple times!
Cluster 61217957 is referenced multiple times!
Cluster 61217958 is referenced multiple times!
Cluster 61217959 is referenced multiple times!
Cluster 61217960 is referenced multiple times!
Cluster 61217961 is referenced multiple times!
Cluster 61256910 is referenced multiple times!
Cluster 61256911 is referenced multiple times!
Cluster 61256912 is referenced multiple times!
Cluster 61256913 is referenced multiple times!
Cluster 61256914 is referenced multiple times!
Cluster 61256915 is referenced multiple times!
Cluster 61256916 is referenced multiple times!
Cluster 61256917 is referenced multiple times!
Cluster 61256918 is referenced multiple times!
Cluster 61256919 is referenced multiple times!
Cluster 61256920 is referenced multiple times!
Cluster 61261243 is referenced multiple times!
Cluster 61261244 is referenced multiple times!
Cluster 61261245 is referenced multiple times!
Cluster 61261246 is referenced multiple times!
Cluster 61261247 is referenced multiple times!
Cluster 61261248 is referenced multiple times!
Cluster 61261249 is referenced multiple times!
Cluster 61261250 is referenced multiple times!
Cluster 61261251 is referenced multiple times!
Cluster 61269623 is referenced multiple times!
Cluster 61269624 is referenced multiple times!
Cluster 61269625 is referenced multiple times!
Cluster 61269626 is referenced multiple times!
Cluster 61269627 is referenced multiple times!
Cluster 61269628 is referenced multiple times!
Cluster 61269629 is referenced multiple times!
Cluster 61269630 is referenced multiple times!
Cluster 61269631 is referenced multiple times!
Cluster 61269632 is referenced multiple times!
Cluster 61269633 is referenced multiple times!
Cluster 61269634 is referenced multiple times!
Cluster 61298317 is referenced multiple times!
Cluster 61298318 is referenced multiple times!
Cluster 61298319 is referenced multiple times!
Cluster 61298320 is referenced multiple times!
Cluster 61298321 is referenced multiple times!
Cluster 61298322 is referenced multiple times!
Cluster 61298323 is referenced multiple times!
Cluster 61298324 is referenced multiple times!
Cluster 61298325 is referenced multiple times!
Cluster 61298326 is referenced multiple times!
Cluster 61298327 is referenced multiple times!
Cluster 61298328 is referenced multiple times!
Cluster 62619829 is referenced multiple times!
Cluster 62619830 is referenced multiple times!
Cluster 62619831 is referenced multiple times!
Cluster 62619832 is referenced multiple times!
Cluster 62619833 is referenced multiple times!
Cluster 62619834 is referenced multiple times!
Cluster 66446418 is referenced multiple times!
Cluster 66270358 is referenced multiple times!
Cluster 66270359 is referenced multiple times!
Cluster 66270360 is referenced multiple times!
Cluster 66270361 is referenced multiple times!
Cluster 66270362 is referenced multiple times!
Cluster 66270363 is referenced multiple times!
Cluster 66274482 is referenced multiple times!
Cluster 66274483 is referenced multiple times!
Cluster 66274484 is referenced multiple times!
Cluster 66274485 is referenced multiple times!
Cluster 66274486 is referenced multiple times!
Cluster 66274487 is referenced multiple times!
Cluster 66274488 is referenced multiple times!
Cluster 66274489 is referenced multiple times!
Cluster 66282805 is referenced multiple times!
Cluster 66282806 is referenced multiple times!
Cluster 66282807 is referenced multiple times!
Cluster 66282808 is referenced multiple times!
Cluster 66282809 is referenced multiple times!
Cluster 66282810 is referenced multiple times!
Cluster 61369446 is referenced multiple times!
Cluster 61318922 is referenced multiple times!
Cluster 61318923 is referenced multiple times!
Cluster 61348883 is referenced multiple times!
Cluster 61348884 is referenced multiple times!
Cluster 61348885 is referenced multiple times!
Cluster 61348886 is referenced multiple times!
Cluster 61348887 is referenced multiple times!
Cluster 61348888 is referenced multiple times!
Cluster 61348889 is referenced multiple times!
Cluster 61348890 is referenced multiple times!
Cluster 61361071 is referenced multiple times!
Cluster 61361072 is referenced multiple times!
Cluster 61361073 is referenced multiple times!
Cluster 61361074 is referenced multiple times!
Cluster 61361075 is referenced multiple times!
Cluster 61361076 is referenced multiple times!
Cluster 61361077 is referenced multiple times!
Cluster 61361078 is referenced multiple times!
Cluster 61361079 is referenced multiple times!
Cluster 61361080 is referenced multiple times!
Cluster 61361081 is referenced multiple times!
Cluster 61361082 is referenced multiple times!
Cluster 61373546 is referenced multiple times!
Cluster 61373547 is referenced multiple times!
Cluster 61373548 is referenced multiple times!
Cluster 61373549 is referenced multiple times!
Cluster 61373550 is referenced multiple times!
Cluster 61373551 is referenced multiple times!
Cluster 61373552 is referenced multiple times!
Cluster 61373553 is referenced multiple times!
Cluster 61373554 is referenced multiple times!
Cluster 61373555 is referenced multiple times!
Cluster 61373556 is referenced multiple times!
Cluster 61373557 is referenced multiple times!
Cluster 61373558 is referenced multiple times!
Cluster 61381771 is referenced multiple times!
Cluster 61381772 is referenced multiple times!
Cluster 61381773 is referenced multiple times!
Cluster 61381774 is referenced multiple times!
Cluster 61381775 is referenced multiple times!
Cluster 61381776 is referenced multiple times!
Cluster 61381777 is referenced multiple times!
Cluster 61381778 is referenced multiple times!
Cluster 61394089 is referenced multiple times!
Cluster 61394090 is referenced multiple times!
Cluster 61394091 is referenced multiple times!
Cluster 61394092 is referenced multiple times!
Cluster 61394093 is referenced multiple times!
Cluster 61394094 is referenced multiple times!
Cluster 61394095 is referenced multiple times!
Cluster 61394096 is referenced multiple times!
Cluster 61394097 is referenced multiple times!
Cluster 61394098 is referenced multiple times!
Cluster 61394099 is referenced multiple times!
Cluster 61394100 is referenced multiple times!
Cluster 61402332 is referenced multiple times!
Cluster 61402333 is referenced multiple times!
Cluster 61402334 is referenced multiple times!
Cluster 61402335 is referenced multiple times!
Cluster 61402336 is referenced multiple times!
Cluster 61402337 is referenced multiple times!
Cluster 61402338 is referenced multiple times!
Cluster 61402339 is referenced multiple times!
Cluster 61402340 is referenced multiple times!
Cluster 61402341 is referenced multiple times!
Cluster 61402342 is referenced multiple times!
Cluster 61402343 is referenced multiple times!
Cluster 61402344 is referenced multiple times!
Cluster 61402345 is referenced multiple times!
Cluster 61406442 is referenced multiple times!
Cluster 61406443 is referenced multiple times!
Cluster 61406444 is referenced multiple times!
Cluster 61406445 is referenced multiple times!
Cluster 61406446 is referenced multiple times!
Cluster 61406447 is referenced multiple times!
Cluster 61406448 is referenced multiple times!
Cluster 61406449 is referenced multiple times!
Cluster 61406450 is referenced multiple times!
Cluster 61406451 is referenced multiple times!
Cluster 61406452 is referenced multiple times!
Cluster 61410547 is referenced multiple times!
Cluster 61410548 is referenced multiple times!
Cluster 61410549 is referenced multiple times!
Cluster 61410550 is referenced multiple times!
Cluster 61410551 is referenced multiple times!
Cluster 61410552 is referenced multiple times!
Cluster 61410553 is referenced multiple times!
Cluster 61410554 is referenced multiple times!
Cluster 61426935 is referenced multiple times!
Cluster 61426936 is referenced multiple times!
Cluster 61426937 is referenced multiple times!
Cluster 61426938 is referenced multiple times!
Cluster 61426939 is referenced multiple times!
Cluster 61426940 is referenced multiple times!
Cluster 61426941 is referenced multiple times!
Cluster 61426942 is referenced multiple times!
Cluster 61426943 is referenced multiple times!
Cluster 61426944 is referenced multiple times!
Cluster 61426945 is referenced multiple times!
Cluster 61426946 is referenced multiple times!
Cluster 61439244 is referenced multiple times!
Cluster 61439245 is referenced multiple times!
Cluster 61439246 is referenced multiple times!
Cluster 61439247 is referenced multiple times!
Cluster 61439248 is referenced multiple times!
Cluster 61439249 is referenced multiple times!
Cluster 61439250 is referenced multiple times!
Cluster 61439251 is referenced multiple times!
Cluster 61439252 is referenced multiple times!
Cluster 61439253 is referenced multiple times!
Cluster 61439254 is referenced multiple times!
Cluster 61439255 is referenced multiple times!
Cluster 61439256 is referenced multiple times!
Cluster 61447912 is referenced multiple times!
Cluster 61447913 is referenced multiple times!
Cluster 61447914 is referenced multiple times!
Cluster 61447915 is referenced multiple times!
Cluster 61447916 is referenced multiple times!
Cluster 61447917 is referenced multiple times!
Cluster 61447918 is referenced multiple times!
Cluster 61447919 is referenced multiple times!
Cluster 61447920 is referenced multiple times!
Cluster 61447921 is referenced multiple times!
Cluster 61447922 is referenced multiple times!
Cluster 61452245 is referenced multiple times!
Cluster 61452246 is referenced multiple times!
Cluster 61452247 is referenced multiple times!
Cluster 61452248 is referenced multiple times!
Cluster 61452249 is referenced multiple times!
Cluster 61452250 is referenced multiple times!
Cluster 61452251 is referenced multiple times!
Cluster 61484184 is referenced multiple times!
Cluster 61484185 is referenced multiple times!
Cluster 61484186 is referenced multiple times!
Cluster 61484187 is referenced multiple times!
Cluster 61484188 is referenced multiple times!
Cluster 61484189 is referenced multiple times!
Cluster 61484190 is referenced multiple times!
Cluster 61496881 is referenced multiple times!
Cluster 61496882 is referenced multiple times!
Cluster 61496883 is referenced multiple times!
Cluster 61496884 is referenced multiple times!
Cluster 61496885 is referenced multiple times!
Cluster 61496886 is referenced multiple times!
Cluster 61496887 is referenced multiple times!
Cluster 61719419 is referenced multiple times!
Cluster 61719420 is referenced multiple times!
Cluster 61719421 is referenced multiple times!
Cluster 61719422 is referenced multiple times!
Cluster 61719423 is referenced multiple times!
Cluster 61719424 is referenced multiple times!
Cluster 61719425 is referenced multiple times!
Cluster 61735590 is referenced multiple times!
Cluster 61735591 is referenced multiple times!
Cluster 61735592 is referenced multiple times!
Cluster 61735593 is referenced multiple times!
Cluster 61735594 is referenced multiple times!
Cluster 61735595 is referenced multiple times!
Cluster 61735596 is referenced multiple times!
Cluster 61743808 is referenced multiple times!
Cluster 61743809 is referenced multiple times!
Cluster 61743810 is referenced multiple times!
Cluster 61743811 is referenced multiple times!
Cluster 61743812 is referenced multiple times!
Cluster 61743813 is referenced multiple times!
Cluster 61743814 is referenced multiple times!
Cluster 61752042 is referenced multiple times!
Cluster 61752043 is referenced multiple times!
Cluster 61752044 is referenced multiple times!
Cluster 61752045 is referenced multiple times!
Cluster 61752046 is referenced multiple times!
Cluster 61752047 is referenced multiple times!
Cluster 61764347 is referenced multiple times!
Cluster 61764348 is referenced multiple times!
Cluster 61764349 is referenced multiple times!
Cluster 61764350 is referenced multiple times!
Cluster 61764351 is referenced multiple times!
Cluster 61764352 is referenced multiple times!
Cluster 61764353 is referenced multiple times!
Cluster 61776891 is referenced multiple times!
Cluster 61776892 is referenced multiple times!
Cluster 61776893 is referenced multiple times!
Cluster 61776894 is referenced multiple times!
Cluster 61776895 is referenced multiple times!
Cluster 61776896 is referenced multiple times!
Cluster 61776897 is referenced multiple times!
Cluster 61781144 is referenced multiple times!
Cluster 61781145 is referenced multiple times!
Cluster 61781146 is referenced multiple times!
Cluster 61781147 is referenced multiple times!
Cluster 61781148 is referenced multiple times!
Cluster 61781149 is referenced multiple times!
Cluster 61781150 is referenced multiple times!
Cluster 61786276 is referenced multiple times!
Cluster 61786277 is referenced multiple times!
Cluster 61786278 is referenced multiple times!
Cluster 61786279 is referenced multiple times!
Cluster 61786280 is referenced multiple times!
Cluster 61786281 is referenced multiple times!
Cluster 61786282 is referenced multiple times!
Cluster 61794872 is referenced multiple times!
Cluster 61794873 is referenced multiple times!
Cluster 61794874 is referenced multiple times!
Cluster 61794875 is referenced multiple times!
Cluster 61794876 is referenced multiple times!
Cluster 61794877 is referenced multiple times!
Cluster 62054719 is referenced multiple times!
Cluster 62054720 is referenced multiple times!
Cluster 62054721 is referenced multiple times!
Cluster 62054722 is referenced multiple times!
Cluster 62054723 is referenced multiple times!
Cluster 62054724 is referenced multiple times!
Cluster 62054725 is referenced multiple times!
Cluster 62054726 is referenced multiple times!
Cluster 62054727 is referenced multiple times!
Cluster 62054728 is referenced multiple times!
Cluster 62054729 is referenced multiple times!
Cluster 62054730 is referenced multiple times!
Cluster 62054731 is referenced multiple times!
Cluster 62062299 is referenced multiple times!
Cluster 62062300 is referenced multiple times!
Cluster 62062301 is referenced multiple times!
Cluster 62062302 is referenced multiple times!
Cluster 62062303 is referenced multiple times!
Cluster 62062304 is referenced multiple times!
Cluster 62066406 is referenced multiple times!
Cluster 62066407 is referenced multiple times!
Cluster 62066408 is referenced multiple times!
Cluster 62066409 is referenced multiple times!
Cluster 62066410 is referenced multiple times!
Cluster 62066411 is referenced multiple times!
Cluster 62066412 is referenced multiple times!
Cluster 62066413 is referenced multiple times!
Cluster 62066414 is referenced multiple times!
Cluster 62066415 is referenced multiple times!
Cluster 62066416 is referenced multiple times!
Cluster 62066417 is referenced multiple times!
Cluster 62066418 is referenced multiple times!
Cluster 62066419 is referenced multiple times!
Cluster 62076476 is referenced multiple times!
Cluster 62076477 is referenced multiple times!
Cluster 62076478 is referenced multiple times!
Cluster 62076479 is referenced multiple times!
Cluster 62076480 is referenced multiple times!
Cluster 62092311 is referenced multiple times!
Cluster 62092312 is referenced multiple times!
Cluster 62092313 is referenced multiple times!
Cluster 62092314 is referenced multiple times!
Cluster 62092315 is referenced multiple times!
Cluster 62092316 is referenced multiple times!
Cluster 62092317 is referenced multiple times!
Cluster 62154346 is referenced multiple times!
Cluster 62154347 is referenced multiple times!
Cluster 62154348 is referenced multiple times!
Cluster 62154349 is referenced multiple times!
Cluster 62154350 is referenced multiple times!
Cluster 62154351 is referenced multiple times!
Cluster 62162523 is referenced multiple times!
Cluster 62162524 is referenced multiple times!
Cluster 62162525 is referenced multiple times!
Cluster 62162526 is referenced multiple times!
Cluster 62162527 is referenced multiple times!
Cluster 62162528 is referenced multiple times!
Cluster 62162529 is referenced multiple times!
Cluster 62162530 is referenced multiple times!
Cluster 62162531 is referenced multiple times!
Cluster 62162532 is referenced multiple times!
Cluster 62162533 is referenced multiple times!
Cluster 62162534 is referenced multiple times!
Cluster 62183040 is referenced multiple times!
Cluster 62183041 is referenced multiple times!
Cluster 62183042 is referenced multiple times!
Cluster 62183043 is referenced multiple times!
Cluster 62183044 is referenced multiple times!
Cluster 62183045 is referenced multiple times!
Cluster 62199473 is referenced multiple times!
Cluster 62199474 is referenced multiple times!
Cluster 62199475 is referenced multiple times!
Cluster 62199476 is referenced multiple times!
Cluster 62199477 is referenced multiple times!
Cluster 62203714 is referenced multiple times!
Cluster 62203715 is referenced multiple times!
Cluster 62203716 is referenced multiple times!
Cluster 62203717 is referenced multiple times!
Cluster 62203718 is referenced multiple times!
Cluster 62203719 is referenced multiple times!
Cluster 62203720 is referenced multiple times!
Cluster 62207814 is referenced multiple times!
Cluster 62207815 is referenced multiple times!
Cluster 62207816 is referenced multiple times!
Cluster 62207817 is referenced multiple times!
Cluster 62207818 is referenced multiple times!
Cluster 62207819 is referenced multiple times!
Cluster 62207820 is referenced multiple times!
Cluster 62207821 is referenced multiple times!
Cluster 62207822 is referenced multiple times!
Cluster 62207823 is referenced multiple times!
Cluster 62207824 is referenced multiple times!
Cluster 62207825 is referenced multiple times!
Cluster 62207826 is referenced multiple times!
Cluster 62207827 is referenced multiple times!
Cluster 62207828 is referenced multiple times!
Cluster 62207829 is referenced multiple times!
Cluster 62216008 is referenced multiple times!
Cluster 62216009 is referenced multiple times!
Cluster 62216010 is referenced multiple times!
Cluster 62216011 is referenced multiple times!
Cluster 62216012 is referenced multiple times!
Cluster 62216013 is referenced multiple times!
Cluster 62220131 is referenced multiple times!
Cluster 62220132 is referenced multiple times!
Cluster 62220133 is referenced multiple times!
Cluster 62220134 is referenced multiple times!
Cluster 62220135 is referenced multiple times!
Cluster 62220136 is referenced multiple times!
Cluster 62220137 is referenced multiple times!
Cluster 62220138 is referenced multiple times!
Cluster 62220139 is referenced multiple times!
Cluster 62220140 is referenced multiple times!
Cluster 62220141 is referenced multiple times!
Cluster 62220142 is referenced multiple times!
Cluster 62220143 is referenced multiple times!
Cluster 62220144 is referenced multiple times!
Cluster 62220145 is referenced multiple times!
Cluster 62220146 is referenced multiple times!
Cluster 62228338 is referenced multiple times!
Cluster 62228339 is referenced multiple times!
Cluster 62228340 is referenced multiple times!
Cluster 62228341 is referenced multiple times!
Cluster 62228342 is referenced multiple times!
Cluster 62228343 is referenced multiple times!
Cluster 66295112 is referenced multiple times!
Cluster 66295113 is referenced multiple times!
Cluster 66295114 is referenced multiple times!
Cluster 66295115 is referenced multiple times!
Cluster 66295116 is referenced multiple times!
Cluster 66295117 is referenced multiple times!
Cluster 66295118 is referenced multiple times!
Cluster 66295119 is referenced multiple times!
Cluster 66319576 is referenced multiple times!
Cluster 66319577 is referenced multiple times!
Cluster 66319578 is referenced multiple times!
Cluster 66319579 is referenced multiple times!
Cluster 66319580 is referenced multiple times!
Cluster 66319581 is referenced multiple times!
Cluster 66319582 is referenced multiple times!
Cluster 66319583 is referenced multiple times!
Cluster 66319584 is referenced multiple times!
Cluster 66319585 is referenced multiple times!
Cluster 66339990 is referenced multiple times!
Cluster 66339991 is referenced multiple times!
Cluster 66339992 is referenced multiple times!
Cluster 66339993 is referenced multiple times!
Cluster 66339994 is referenced multiple times!
Cluster 66339995 is referenced multiple times!
Cluster 66339996 is referenced multiple times!
Cluster 66339997 is referenced multiple times!
Cluster 66339998 is referenced multiple times!
Cluster 66339999 is referenced multiple times!
Cluster 66364538 is referenced multiple times!
Cluster 66364539 is referenced multiple times!
Cluster 66364540 is referenced multiple times!
Cluster 66364541 is referenced multiple times!
Cluster 66364542 is referenced multiple times!
Cluster 66364543 is referenced multiple times!
Cluster 66364544 is referenced multiple times!
Cluster 66364545 is referenced multiple times!
Cluster 66364546 is referenced multiple times!
Cluster 66364547 is referenced multiple times!
Cluster 66364548 is referenced multiple times!
Cluster 66364549 is referenced multiple times!
Cluster 66364550 is referenced multiple times!
Cluster 66364551 is referenced multiple times!
Cluster 66389059 is referenced multiple times!
Cluster 66389060 is referenced multiple times!
Cluster 66389061 is referenced multiple times!
Cluster 66389062 is referenced multiple times!
Cluster 66389063 is referenced multiple times!
Cluster 66389064 is referenced multiple times!
Cluster 66389065 is referenced multiple times!
Cluster 66389066 is referenced multiple times!
Cluster 66389067 is referenced multiple times!
Cluster 66389068 is referenced multiple times!
Cluster 66389069 is referenced multiple times!
Cluster 66397252 is referenced multiple times!
Cluster 66397253 is referenced multiple times!
Cluster 66397254 is referenced multiple times!
Cluster 66397255 is referenced multiple times!
Cluster 66397256 is referenced multiple times!
Cluster 66397257 is referenced multiple times!
Cluster 66397258 is referenced multiple times!
Cluster 66397259 is referenced multiple times!
Cluster 66430172 is referenced multiple times!
Cluster 66430173 is referenced multiple times!
Cluster 66430174 is referenced multiple times!
Cluster 66430175 is referenced multiple times!
Cluster 66430176 is referenced multiple times!
Cluster 66430177 is referenced multiple times!
Cluster 66430178 is referenced multiple times!
Cluster 66430179 is referenced multiple times!
Cluster 66430180 is referenced multiple times!
Cluster 66450538 is referenced multiple times!
Cluster 66450539 is referenced multiple times!
Cluster 66450540 is referenced multiple times!
Cluster 66450541 is referenced multiple times!
Cluster 66450542 is referenced multiple times!
Cluster 66450543 is referenced multiple times!
Cluster 66450544 is referenced multiple times!
Cluster 66450545 is referenced multiple times!
Cluster 66450546 is referenced multiple times!
Cluster 66450547 is referenced multiple times!
Cluster 66483304 is referenced multiple times!
Cluster 66491470 is referenced multiple times!
Cluster 66520168 is referenced multiple times!
Cluster 66520169 is referenced multiple times!
Cluster 66520170 is referenced multiple times!
Cluster 66520171 is referenced multiple times!
Cluster 66520172 is referenced multiple times!
Cluster 66520173 is referenced multiple times!
Cluster 66520174 is referenced multiple times!
Cluster 66520175 is referenced multiple times!
Cluster 66589799 is referenced multiple times!
Cluster 66536524 is referenced multiple times!
Cluster 66536525 is referenced multiple times!
Cluster 66552908 is referenced multiple times!
Cluster 66552909 is referenced multiple times!
Cluster 66552910 is referenced multiple times!
Cluster 66552911 is referenced multiple times!
Cluster 66552912 is referenced multiple times!
Cluster 66552913 is referenced multiple times!
Cluster 66552914 is referenced multiple times!
Cluster 66552915 is referenced multiple times!
Cluster 66552916 is referenced multiple times!
Cluster 66552917 is referenced multiple times!
Cluster 66552918 is referenced multiple times!
Cluster 66552919 is referenced multiple times!
Cluster 66557033 is referenced multiple times!
Cluster 66557034 is referenced multiple times!
Cluster 66557035 is referenced multiple times!
Cluster 66557036 is referenced multiple times!
Cluster 66557037 is referenced multiple times!
Cluster 66626753 is referenced multiple times!
Cluster 66606210 is referenced multiple times!
Cluster 66606211 is referenced multiple times!
Cluster 66606212 is referenced multiple times!
Cluster 66606213 is referenced multiple times!
Cluster 66606214 is referenced multiple times!
Cluster 66606215 is referenced multiple times!
Cluster 66606216 is referenced multiple times!
Cluster 66606217 is referenced multiple times!
Cluster 66606218 is referenced multiple times!
Cluster 66622657 is referenced multiple times!
Cluster 66622658 is referenced multiple times!
Cluster 66622659 is referenced multiple times!
Cluster 66622660 is referenced multiple times!
Cluster 66622661 is referenced multiple times!
Cluster 66622662 is referenced multiple times!
Cluster 66622663 is referenced multiple times!
Cluster 66622664 is referenced multiple times!
Cluster 66622665 is referenced multiple times!
Cluster 66659509 is referenced multiple times!
Cluster 66659510 is referenced multiple times!
Cluster 66659511 is referenced multiple times!
Cluster 66659512 is referenced multiple times!
Cluster 66659513 is referenced multiple times!
Cluster 66659514 is referenced multiple times!
Cluster 66659515 is referenced multiple times!
Cluster 66659516 is referenced multiple times!
Cluster 66659517 is referenced multiple times!
Cluster 66659518 is referenced multiple times!
Cluster 66675833 is referenced multiple times!
Cluster 66675834 is referenced multiple times!
Cluster 66675835 is referenced multiple times!
Cluster 66675836 is referenced multiple times!
Cluster 66675837 is referenced multiple times!
Cluster 66675838 is referenced multiple times!
Cluster 66675839 is referenced multiple times!
Cluster 66675840 is referenced multiple times!
Cluster 66675841 is referenced multiple times!
Cluster 66704499 is referenced multiple times!
Cluster 66704500 is referenced multiple times!
Cluster 66704501 is referenced multiple times!
Cluster 66704502 is referenced multiple times!
Cluster 66704503 is referenced multiple times!
Cluster 66704504 is referenced multiple times!
Cluster 66704505 is referenced multiple times!
Cluster 66704506 is referenced multiple times!
Cluster 66704507 is referenced multiple times!
Cluster 66704508 is referenced multiple times!
Cluster 66704509 is referenced multiple times!
Cluster 66704510 is referenced multiple times!
Cluster 66724978 is referenced multiple times!
Cluster 66724979 is referenced multiple times!
Cluster 66724980 is referenced multiple times!
Cluster 66724981 is referenced multiple times!
Cluster 66724982 is referenced multiple times!
Cluster 66724983 is referenced multiple times!
Cluster 66724984 is referenced multiple times!
Cluster 66724985 is referenced multiple times!
Cluster 66724986 is referenced multiple times!
Cluster 66749534 is referenced multiple times!
Cluster 66749535 is referenced multiple times!
Cluster 66749536 is referenced multiple times!
Cluster 66749537 is referenced multiple times!
Cluster 66749538 is referenced multiple times!
Cluster 66749539 is referenced multiple times!
Cluster 66749540 is referenced multiple times!
Cluster 66749541 is referenced multiple times!
Cluster 66749542 is referenced multiple times!
Cluster 66749543 is referenced multiple times!
Cluster 66749544 is referenced multiple times!
Cluster 66761840 is referenced multiple times!
Cluster 66761841 is referenced multiple times!
Cluster 66761842 is referenced multiple times!
Cluster 66761843 is referenced multiple times!
Cluster 66761844 is referenced multiple times!
Cluster 66761845 is referenced multiple times!
Cluster 66761846 is referenced multiple times!
Cluster 66761847 is referenced multiple times!
Cluster 66761848 is referenced multiple times!
Cluster 66765965 is referenced multiple times!
Cluster 66765966 is referenced multiple times!
Cluster 66765967 is referenced multiple times!
Cluster 66765968 is referenced multiple times!
Cluster 66765969 is referenced multiple times!
Cluster 66765970 is referenced multiple times!
Cluster 66765971 is referenced multiple times!
Cluster 66765972 is referenced multiple times!
Cluster 66765973 is referenced multiple times!
Cluster 66765974 is referenced multiple times!
Cluster 66765975 is referenced multiple times!
Cluster 66765976 is referenced multiple times!
Cluster 66765977 is referenced multiple times!
Cluster 66765978 is referenced multiple times!
Cluster 66765979 is referenced multiple times!
Cluster 66765980 is referenced multiple times!
Cluster 66765981 is referenced multiple times!
Cluster 66765982 is referenced multiple times!
Cluster 66765983 is referenced multiple times!
Cluster 66774171 is referenced multiple times!
Cluster 66774172 is referenced multiple times!
Cluster 66774173 is referenced multiple times!
Cluster 66774174 is referenced multiple times!
Cluster 66774175 is referenced multiple times!
Cluster 66774176 is referenced multiple times!
Cluster 66774177 is referenced multiple times!
Cluster 66774178 is referenced multiple times!
Cluster 66774179 is referenced multiple times!
Cluster 66774180 is referenced multiple times!
Cluster 66774181 is referenced multiple times!
Cluster 66806958 is referenced multiple times!
Cluster 66806959 is referenced multiple times!
Cluster 66806960 is referenced multiple times!
Cluster 66806961 is referenced multiple times!
Cluster 66806962 is referenced multiple times!
Cluster 66806963 is referenced multiple times!
Cluster 66806964 is referenced multiple times!
Cluster 66806965 is referenced multiple times!
Cluster 66806966 is referenced multiple times!
Cluster 66827414 is referenced multiple times!
Cluster 66827415 is referenced multiple times!
Cluster 66827416 is referenced multiple times!
Cluster 66827417 is referenced multiple times!
Cluster 66827418 is referenced multiple times!
Cluster 66827419 is referenced multiple times!
Cluster 66827420 is referenced multiple times!
Cluster 66827421 is referenced multiple times!
Cluster 66827422 is referenced multiple times!
Cluster 66827423 is referenced multiple times!
Cluster 66827424 is referenced multiple times!
Cluster 66827425 is referenced multiple times!
Cluster 66827426 is referenced multiple times!
Cluster 66827427 is referenced multiple times!
Cluster 66827428 is referenced multiple times!
Cluster 66827429 is referenced multiple times!
Cluster 66827430 is referenced multiple times!
Cluster 66847877 is referenced multiple times!
Cluster 66847878 is referenced multiple times!
Cluster 66847879 is referenced multiple times!
Cluster 66847880 is referenced multiple times!
Cluster 66847881 is referenced multiple times!
Cluster 66847882 is referenced multiple times!
Cluster 66847883 is referenced multiple times!
Cluster 66847884 is referenced multiple times!
Cluster 66847885 is referenced multiple times!
Cluster 66847886 is referenced multiple times!
Cluster 66847887 is referenced multiple times!
Cluster 66847888 is referenced multiple times!
Cluster 66847889 is referenced multiple times!
Cluster 66847890 is referenced multiple times!
Cluster 66847891 is referenced multiple times!
Cluster 66847892 is referenced multiple times!
Cluster 66876539 is referenced multiple times!
Cluster 66876540 is referenced multiple times!
Cluster 66876541 is referenced multiple times!
Cluster 66876542 is referenced multiple times!
Cluster 66876543 is referenced multiple times!
Cluster 66876544 is referenced multiple times!
Cluster 66880641 is referenced multiple times!
Cluster 66880642 is referenced multiple times!
Cluster 66880643 is referenced multiple times!
Cluster 66880644 is referenced multiple times!
Cluster 66880645 is referenced multiple times!
Cluster 66880646 is referenced multiple times!
Cluster 66905287 is referenced multiple times!
Cluster 66905288 is referenced multiple times!
Cluster 66905289 is referenced multiple times!
Cluster 66905290 is referenced multiple times!
Cluster 66905291 is referenced multiple times!
Cluster 66905292 is referenced multiple times!
Cluster 66925886 is referenced multiple times!
Cluster 66925887 is referenced multiple times!
Cluster 66925888 is referenced multiple times!
Cluster 66925889 is referenced multiple times!
Cluster 66925890 is referenced multiple times!
Cluster 66925891 is referenced multiple times!
Cluster 66925892 is referenced multiple times!
Cluster 66925893 is referenced multiple times!
Cluster 66925894 is referenced multiple times!
Cluster 66925895 is referenced multiple times!
Cluster 61151091 is referenced multiple times!
Cluster 61067040 is referenced multiple times!
Cluster 61067041 is referenced multiple times!
Cluster 61067042 is referenced multiple times!
Cluster 61067043 is referenced multiple times!
Cluster 61067044 is referenced multiple times!
Cluster 61067045 is referenced multiple times!
Cluster 61067046 is referenced multiple times!
Cluster 61067047 is referenced multiple times!
Cluster 61067048 is referenced multiple times!
Cluster 61067049 is referenced multiple times!
Cluster 61067050 is referenced multiple times!
Cluster 61067051 is referenced multiple times!
Cluster 61067052 is referenced multiple times!
Cluster 61067053 is referenced multiple times!
Cluster 61087159 is referenced multiple times!
Cluster 61087160 is referenced multiple times!
Cluster 61087161 is referenced multiple times!
Cluster 61087162 is referenced multiple times!
Cluster 61087163 is referenced multiple times!
Cluster 61087164 is referenced multiple times!
Cluster 61087165 is referenced multiple times!
Cluster 61087166 is referenced multiple times!
Cluster 61087167 is referenced multiple times!
Cluster 61087168 is referenced multiple times!
Cluster 61087169 is referenced multiple times!
Cluster 61087170 is referenced multiple times!
Cluster 61087171 is referenced multiple times!
Cluster 61087172 is referenced multiple times!
Cluster 61087173 is referenced multiple times!
Cluster 61087174 is referenced multiple times!
Cluster 61099845 is referenced multiple times!
Cluster 61099846 is referenced multiple times!
Cluster 61099847 is referenced multiple times!
Cluster 61099848 is referenced multiple times!
Cluster 61099849 is referenced multiple times!
Cluster 61099850 is referenced multiple times!
Cluster 61099851 is referenced multiple times!
Cluster 61099852 is referenced multiple times!
Cluster 61217949 is referenced multiple times!
Cluster 61195492 is referenced multiple times!
Cluster 61195493 is referenced multiple times!
Cluster 61195494 is referenced multiple times!
Cluster 61195495 is referenced multiple times!
Cluster 61195496 is referenced multiple times!
Cluster 61195497 is referenced multiple times!
Cluster 61195498 is referenced multiple times!
Cluster 61195499 is referenced multiple times!
Cluster 61195500 is referenced multiple times!
Cluster 61195501 is referenced multiple times!
Cluster 61195502 is referenced multiple times!
Cluster 61195503 is referenced multiple times!
Cluster 61195504 is referenced multiple times!
Cluster 61195505 is referenced multiple times!
Cluster 61207871 is referenced multiple times!
Cluster 61207872 is referenced multiple times!
Cluster 61207873 is referenced multiple times!
Cluster 61207874 is referenced multiple times!
Cluster 61207875 is referenced multiple times!
Cluster 61207876 is referenced multiple times!
Cluster 61207877 is referenced multiple times!
Cluster 61207878 is referenced multiple times!
Cluster 61207879 is referenced multiple times!
Cluster 61207880 is referenced multiple times!
Cluster 61207881 is referenced multiple times!
Cluster 61207882 is referenced multiple times!
Cluster 61212359 is referenced multiple times!
Cluster 61212360 is referenced multiple times!
Cluster 61212361 is referenced multiple times!
Cluster 61212362 is referenced multiple times!
Cluster 61212363 is referenced multiple times!
Cluster 61212364 is referenced multiple times!
Cluster 61212365 is referenced multiple times!
Cluster 61212366 is referenced multiple times!
Cluster 61256907 is referenced multiple times!
Cluster 61256908 is referenced multiple times!
Cluster 61256909 is referenced multiple times!
Cluster 61261241 is referenced multiple times!
Cluster 61261242 is referenced multiple times!
Cluster 61265383 is referenced multiple times!
Cluster 61265384 is referenced multiple times!
Cluster 61265385 is referenced multiple times!
Cluster 61265386 is referenced multiple times!
Cluster 61265387 is referenced multiple times!
Cluster 61265388 is referenced multiple times!
Cluster 61265389 is referenced multiple times!
Cluster 61265390 is referenced multiple times!
Cluster 61269622 is referenced multiple times!
Cluster 61298316 is referenced multiple times!
Cluster 61318924 is referenced multiple times!
Cluster 61318925 is referenced multiple times!
Cluster 61318926 is referenced multiple times!
Cluster 61318927 is referenced multiple times!
Cluster 61318928 is referenced multiple times!
Cluster 61318929 is referenced multiple times!
Cluster 61318930 is referenced multiple times!
Cluster 61318931 is referenced multiple times!
Cluster 61318932 is referenced multiple times!
Cluster 61369447 is referenced multiple times!
Cluster 61369448 is referenced multiple times!
Cluster 61369449 is referenced multiple times!
Cluster 61369450 is referenced multiple times!
Cluster 61369451 is referenced multiple times!
Cluster 61369452 is referenced multiple times!
Cluster 61369453 is referenced multiple times!
Cluster 61369454 is referenced multiple times!
Cluster 61369455 is referenced multiple times!
Cluster 61369456 is referenced multiple times!
Cluster 62236582 is referenced multiple times!
Cluster 62236583 is referenced multiple times!
Cluster 62236584 is referenced multiple times!
Cluster 62236585 is referenced multiple times!
Cluster 62236586 is referenced multiple times!
Cluster 62236587 is referenced multiple times!
Cluster 62236588 is referenced multiple times!
Cluster 62236589 is referenced multiple times!
Cluster 62236590 is referenced multiple times!
Cluster 62236591 is referenced multiple times!
Cluster 62236592 is referenced multiple times!
Cluster 62236593 is referenced multiple times!
Cluster 62236594 is referenced multiple times!
Cluster 62236595 is referenced multiple times!
Cluster 62236596 is referenced multiple times!
Cluster 62236597 is referenced multiple times!
Cluster 62240888 is referenced multiple times!
Cluster 62240889 is referenced multiple times!
Cluster 62240890 is referenced multiple times!
Cluster 62240891 is referenced multiple times!
Cluster 62240892 is referenced multiple times!
Cluster 62240893 is referenced multiple times!
Cluster 62245012 is referenced multiple times!
Cluster 62245013 is referenced multiple times!
Cluster 62245014 is referenced multiple times!
Cluster 62245015 is referenced multiple times!
Cluster 62245016 is referenced multiple times!
Cluster 62245017 is referenced multiple times!
Cluster 62245018 is referenced multiple times!
Cluster 62245019 is referenced multiple times!
Cluster 62245020 is referenced multiple times!
Cluster 62245021 is referenced multiple times!
Cluster 62245022 is referenced multiple times!
Cluster 62245023 is referenced multiple times!
Cluster 62245024 is referenced multiple times!
Cluster 62245025 is referenced multiple times!
Cluster 62245026 is referenced multiple times!
Cluster 62245027 is referenced multiple times!
Cluster 62249249 is referenced multiple times!
Cluster 62249250 is referenced multiple times!
Cluster 62249251 is referenced multiple times!
Cluster 62249252 is referenced multiple times!
Cluster 62249253 is referenced multiple times!
Cluster 62249254 is referenced multiple times!
Cluster 62249255 is referenced multiple times!
Cluster 62257466 is referenced multiple times!
Cluster 62257467 is referenced multiple times!
Cluster 62257468 is referenced multiple times!
Cluster 62257469 is referenced multiple times!
Cluster 62257470 is referenced multiple times!
Cluster 62257471 is referenced multiple times!
Cluster 62257472 is referenced multiple times!
Cluster 62263493 is referenced multiple times!
Cluster 62263494 is referenced multiple times!
Cluster 62263495 is referenced multiple times!
Cluster 62263496 is referenced multiple times!
Cluster 62263497 is referenced multiple times!
Cluster 62263498 is referenced multiple times!
Cluster 62460911 is referenced multiple times!
Cluster 62460912 is referenced multiple times!
Cluster 62460913 is referenced multiple times!
Cluster 62460914 is referenced multiple times!
Cluster 62460915 is referenced multiple times!
Cluster 62460916 is referenced multiple times!
Cluster 62460917 is referenced multiple times!
Cluster 62460918 is referenced multiple times!
Cluster 62460919 is referenced multiple times!
Cluster 62460920 is referenced multiple times!
Cluster 62460921 is referenced multiple times!
Cluster 62460922 is referenced multiple times!
Cluster 62460923 is referenced multiple times!
Cluster 62460924 is referenced multiple times!
Cluster 62460925 is referenced multiple times!
Cluster 62460926 is referenced multiple times!
Cluster 62524487 is referenced multiple times!
Cluster 62524488 is referenced multiple times!
Cluster 62524489 is referenced multiple times!
Cluster 62524490 is referenced multiple times!
Cluster 62524491 is referenced multiple times!
Cluster 62524492 is referenced multiple times!
Cluster 62535425 is referenced multiple times!
Cluster 62535426 is referenced multiple times!
Cluster 62535427 is referenced multiple times!
Cluster 62535428 is referenced multiple times!
Cluster 62535429 is referenced multiple times!
Cluster 62535430 is referenced multiple times!
Cluster 62535431 is referenced multiple times!
Cluster 62535432 is referenced multiple times!
Cluster 62535433 is referenced multiple times!
Cluster 62535434 is referenced multiple times!
Cluster 62535435 is referenced multiple times!
Cluster 62535436 is referenced multiple times!
Cluster 62535437 is referenced multiple times!
Cluster 62535438 is referenced multiple times!
Cluster 62535439 is referenced multiple times!
Cluster 62535440 is referenced multiple times!
Cluster 62568158 is referenced multiple times!
Cluster 62568159 is referenced multiple times!
Cluster 62568160 is referenced multiple times!
Cluster 62568161 is referenced multiple times!
Cluster 62568162 is referenced multiple times!
Cluster 62568163 is referenced multiple times!
Cluster 62607052 is referenced multiple times!
Cluster 62607053 is referenced multiple times!
Cluster 62607054 is referenced multiple times!
Cluster 62607055 is referenced multiple times!
Cluster 62607056 is referenced multiple times!
Cluster 62607057 is referenced multiple times!
Cluster 62632308 is referenced multiple times!
Cluster 62632309 is referenced multiple times!
Cluster 62632310 is referenced multiple times!
Cluster 62632311 is referenced multiple times!
Cluster 62632312 is referenced multiple times!
Cluster 62632313 is referenced multiple times!
Cluster 62632314 is referenced multiple times!
Cluster 62685187 is referenced multiple times!
Cluster 62685188 is referenced multiple times!
Cluster 62685189 is referenced multiple times!
Cluster 62685190 is referenced multiple times!
Cluster 62685191 is referenced multiple times!
Cluster 62685192 is referenced multiple times!
Cluster 62689374 is referenced multiple times!
Cluster 62689375 is referenced multiple times!
Cluster 62689376 is referenced multiple times!
Cluster 62689377 is referenced multiple times!
Cluster 62689378 is referenced multiple times!
Cluster 62689379 is referenced multiple times!
Cluster 62689380 is referenced multiple times!
Cluster 62701683 is referenced multiple times!
Cluster 62701684 is referenced multiple times!
Cluster 62701685 is referenced multiple times!
Cluster 62701686 is referenced multiple times!
Cluster 62701687 is referenced multiple times!
Cluster 62701688 is referenced multiple times!
Cluster 62701689 is referenced multiple times!
Cluster 62705820 is referenced multiple times!
Cluster 62705821 is referenced multiple times!
Cluster 62705822 is referenced multiple times!
Cluster 62705823 is referenced multiple times!
Cluster 62714027 is referenced multiple times!
Cluster 62718159 is referenced multiple times!
Cluster 62718160 is referenced multiple times!
Cluster 62718161 is referenced multiple times!
Cluster 62718162 is referenced multiple times!
Cluster 62718163 is referenced multiple times!
Cluster 62718164 is referenced multiple times!
Cluster 62718165 is referenced multiple times!
Cluster 62718166 is referenced multiple times!
Cluster 62718167 is referenced multiple times!
Cluster 62718168 is referenced multiple times!
Cluster 62718169 is referenced multiple times!
Cluster 62718170 is referenced multiple times!
Cluster 62718171 is referenced multiple times!
100.00 percent completed
ERROR: Filesystem check failed!
ERROR: 995 clusters are referenced multiple times.
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.

========================================

 



Je voulais bien faire chkdsk /f , comme il le dit,


ERROR: Filesystem check failed!
ERROR: 995 clusters are referenced multiple times.
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.
 



mais lorsque je lance la commande, il ne se passe rien.

Ma question : mieux vaut le reformater, quitte à recommencer une partie des sauvegardes non encore déjà copiées sur le 2 To, ou existe-t-il une commande pour faire ça sous Linux ?

Un utilitaire qui permettait de réparer mon disque ?

Merci.
Rien que l'un seulement des répertoires du précieux disque source a pris.... trois jours sans discontinuer pour effectuer les copies. C'est fragmenté, des répertoires contiennent une quantité pharamineuse de fichiers... Plus les ':' Pfff ! La galère. J'ignorais que les Mac toléraient ce type de nom de fichier...

#6 Re : Réseau » Petit souci avec le https et un certificat auto resenigné. » 21-04-2022 12:27:20

Bonjour.
J'ai fait (mal) ce que tu m'as conseillé. A savoir : faire pointer les DNS de mon nom de domaine vers mon IP publique.

J'ai mal dû m'y prendre.

Voici des captures d'écran :
https://cjoint.com/c/LDvkxb1i5nj

Là, je saisis mon IP publique :

https://cjoint.com/c/LDvkxzumYmj

Rien à faire. Marche pas. Et j'ai du mal à joindre l'hébergeur au téléphone pour me guider. J'ai sans doute renseigné mon IP là où il ne le fallait pas...

A votre avis ?

Pas facile de faire passer des images ici...
Merci sad

20 H 09 : bon. J'ai pu avoir mon hébergeur au téléphone. Je m'y étais mal pris, effectivement. J'ai fait le nécessaire. Encore fallait-il savoir comment hmm La manip sera active d'ici quelques... minutes ou heures. Peu importe.

Je donne le retour. Demain si j'ai le temps de valider le certificat.
Les journées n'ont que 24 heures. C'est si peu... wink

29-04.
Je pense avoir pigé.
La config de mon nom de domaine est désormais OK.
MAIS : lorsque j'ai effectué la passage en HTTPS, j'ai utilisé open-ssl, et ensuite seulement, j'ai voulu obtenir un certificat approuvé. Je suis arrivé à utiliser certbot. Mais Apache ne prend pas en compte les clefs générées par Lets encrypt.

C'est sans doute dès le passage en HTTPS qu'il faut envoyer certbot, pas après !

Je remonte le serveur. De zéro. Et je poste le retour après le passage en HTTPS via certbot et Lets encrypt.

Ca peut peut-être intéresser quelqu'un ?

#7 Re : Réseau » Petit souci avec le https et un certificat auto resenigné. » 18-04-2022 17:36:41

Ah...

Je suis ET en ipv4 ET en ipv6. Mon IP publique est en ipV4. C'est comme ça que je l''ai renseignée dans Debian. Et j'ai éradiqué toute trace d'ipV6 sur le serveur.

Je vais voir ça chez 1&1.  Et je donne le retour. Merci wink

C'est fait.

Je suppose qu'il faut attendre un peu, ce n'est pas instantané ?


Et la box :

- un paramétrage supplémentaire ?

- faut-il la redémarrer ? Je vais le faire, ça leur fait du bien.

#8 Réseau » Petit souci avec le https et un certificat auto resenigné. » 18-04-2022 15:33:10

Lupa
Réponses : 3
Bonjour à tous smile

J'ai monté mon serveur perso chez moi. Donc pas chez un hébergeur.

J'ai généré mon certificat avec openssl.

Le problème : il est "auto renseigné", dixit Owncloud lors d'une connexion ou reconnexion. Et les navigateurs de tousser, bien sûr. Ca ne fait pas très propre hmm

Je pourrais demander à l'hébergeur de mes mails (avec mon nom de domaine) d'approuver mon certificat.

Mais je sais que l'on peut se passer d'une autorité de certification. Une pki ?

Le gros pépin : c'est que, même avec Lets Encrypt, il faut avoir un nom de domaine. Certbot ne laissera pas passer une IP (la mienne en l'occurrence). Je le sais : j'ai testé.

Que faire, dans ces cas-là ? Autrement dit : faire passer mon certificat auto renseigné pour un certificat approuvé ?

Il n'y a rien d'illégal à cela...

A votre avis ?

Merci wink

#9 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 06-04-2022 10:46:58

Gagné !
Ca fonctionne.


<VirtualHost *:443>
    DocumentRoot /var/www/owncloud/
    ServerAdmin webmaster@localhost

    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key

# Conseillé par Allan :
# A désactiver éventuellement
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>

# Voir éventuellement fichier owncloud-ssl.txt

 



Merci les amis !! :hello:

#10 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 06-04-2022 10:31:54

Bonjour.
Je vais tenter ça.
Cette nuit, j'ai pu utiliser la commande occ en tant que ww-data.

La prochaine fois, et je n'exclue pas de recommencer aujourd'hui-même, pourquoi ne pas effectuer le montage sur /srv AVANT de lancer le setup de Owncloud ? Ce doit être faisable, si je modifie correctement le owncloud.conf et le apache2.conf .

A ton avis ?

Le manuel de Owncloud y réfère lui-même. Je cite (de mémoire) qu'il est plus aisé de le faire à l'installation plutôt qu'après.

#11 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 05-04-2022 19:45:48

Même topo. Index Of :
https://cjoint.com/c/LDfrLUydGFj

Je ne me décourage jamais. (Heureusement !)

J'ai appliqué la solution 2 référencée par le lien de dejieres. https://help.nextcloud.com/t/howto-chan … tion/17170
J'ai fait ce qui suit :

COMMANDES DECOMPOSEES :
su -u www-data php /var/www/owncloud occ maintenance:mode --on
su -u www-data && php /var/www/owncloud occ maintenance:mode --on
Marche pas !! Je ne peux pas devenir www-data !

Parce que leur commande à eux non plus, ne passe pas :
sudo -u www-data php /path/to/nextcloud/occ maintenance:mode --on

J'ai essayé d'autres trucs :

Réponses de l'OS :


root@1150-SRV:/var/www/owncloud# su -u www-data && php /var/www/owncloud occ maintenance:mode --on
Exécutez « su --help » pour obtenir des renseignements complémentaires.

root@1150-SRV:/var/www/owncloud# su www-data && php /var/www/owncloud occ maintenance:mode --on
This account is currently not available.

 



"not available" !! Faut le faire !

Puis :

cp -ra /var/www/owncloud/data/ /srv/ocdata
cp -ra /var/www/owncloud/data/ /srv/ocdata/data/dataBackup
chown -R www-data:www-data /var/www/owncloud/data/


Depuis le /var/www/owncloud : je vire le dossier data. Parce que j'avais créé un lien 'data' pointant bien vers le dossier /srv/ocdata/data... mais ça ne marchait pas.
rm -rf ./data

Depuis le /srv/ocdata :
ln -s /srv/ocdata/data /var/www/owncloud/data
chown -R www-data:www-data /var/www/owncloud/

Ca crée le "data" lien vers le vrai dossier data. Il n'y a plus de dossier data dans /var/www/owncloud mais un lien à la place.

service apache2 restart
apache2ctl configtest
root@1150-SRV:~# apache2ctl configtest
Syntax OK

root@1150-SRV:~# apache2ctl -S
VirtualHost configuration:
*:443                  localhost (/etc/apache2/sites-enabled/owncloud.conf:1)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name="www-data" id=33
Group: name="www-data" id=33


Dernières lignes du log dd'Apache :



[Tue Apr 05 19:00:14.476143 2022] [mpm_prefork:notice] [pid 859] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Tue Apr 05 19:00:14.476163 2022] [core:notice] [pid 859] AH00094: Command line: '/usr/sbin/apache2'
[Tue Apr 05 19:01:00.292635 2022] [authz_core:error] [pid 863] [client 192.168.0.51:35502] AH01630: client denied by server configuration: /srv/ocdata/data/
[Tue Apr 05 19:02:20.440753 2022] [mpm_prefork:notice] [pid 859] AH00169: caught SIGTERM, shutting down
[Tue Apr 05 19:02:32.600424 2022] [ssl:warn] [pid 1638] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 19:02:32.624795 2022] [ssl:warn] [pid 1639] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 19:02:32.628771 2022] [mpm_prefork:notice] [pid 1639] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Tue Apr 05 19:02:32.628792 2022] [core:notice] [pid 1639] AH00094: Command line: '/usr/sbin/apache2'
[Tue Apr 05 19:03:23.889014 2022] [authz_core:error] [pid 1641] [client 192.168.0.51:35522] AH01630: client denied by server configuration: /srv/ocdata/data/
[Tue Apr 05 19:03:23.950759 2022] [authz_core:error] [pid 1641] [client 192.168.0.51:35522] AH01630: client denied by server configuration: /srv/ocdata/data/favicon.ico, referer: https://192.168.0.51/
[Tue Apr 05 19:05:48.665841 2022] [authz_core:error] [pid 1643] [client 192.168.0.51:35540] AH01630: client denied by server configuration: /srv/ocdata/data/
[Tue Apr 05 19:05:48.730830 2022] [authz_core:error] [pid 1643] [client 192.168.0.51:35540] AH01630: client denied by server configuration: /srv/ocdata/data/favicon.ico, referer: https://192.168.0.51/
[Tue Apr 05 19:06:37.481421 2022] [mpm_prefork:notice] [pid 1639] AH00169: caught SIGTERM, shutting down
[Tue Apr 05 19:06:59.368305 2022] [ssl:warn] [pid 2369] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 19:06:59.391197 2022] [ssl:warn] [pid 2370] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 19:06:59.395190 2022] [mpm_prefork:notice] [pid 2370] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Tue Apr 05 19:06:59.395211 2022] [core:notice] [pid 2370] AH00094: Command line: '/usr/sbin/apache2'
[Tue Apr 05 19:07:36.840143 2022] [authz_core:error] [pid 2373] [client 192.168.0.51:35560] AH01630: client denied by server configuration: /srv/ocdata/data/
[Tue Apr 05 19:09:02.040964 2022] [mpm_prefork:notice] [pid 2370] AH00169: caught SIGTERM, shutting down
[Tue Apr 05 19:19:03.153873 2022] [ssl:warn] [pid 4239] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 19:19:03.175851 2022] [ssl:warn] [pid 4240] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 19:19:03.179494 2022] [mpm_prefork:notice] [pid 4240] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Tue Apr 05 19:19:03.179513 2022] [core:notice] [pid 4240] AH00094: Command line: '/usr/sbin/apache2'
[Tue Apr 05 19:19:43.770335 2022] [authz_core:error] [pid 4242] [client 192.168.0.51:35610] AH01630: client denied by server configuration: /srv/ocdata/data/

 





Le fstab :



# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4b0c937b-eb1c-46b9-bed9-23932e9c6943 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=4abdeb87-995c-4045-82d5-9a04536a52d6 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
LABEL=DATA  /mnt  ext4  defaults  0 0
LABEL=DONNEES /srv/ocdata ext4  resuid=33,resgid=33 0 0

 



df :


root@1150-SRV:~# df
Sys. de fichiers blocs de 1K  Utilisé Disponible Uti% Monté sur
udev                 8009732        0    8009732   0% /dev
tmpfs                1607200     9840    1597360   1% /run
/dev/sda1           98664624  6821404   86788296   8% /
tmpfs                8035996    14608    8021388   1% /dev/shm
tmpfs                   5120        4       5116   1% /run/lock
tmpfs                8035996        0    8035996   0% /sys/fs/cgroup
/dev/sdb1          256614804 27993136  215516672  12% /mnt
/dev/sdb3          295941968   455804  280383548   1% /srv/ocdata
tmpfs                1607196       12    1607184   1% /run/user/0
 




apache2.conf :



# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `--  ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
#   `-- sites-enabled
#   `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.

# TRADUCTION :
# ServerRoot : le sommet de l'arborescence de répertoires sous lequel le serveur
# les fichiers de configuration, d'erreur et de journal sont conservés.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
# ServerRoot : le sommet de l'arborescence de répertoires sous lequel le serveur
# les fichiers de configuration, d'erreur et de journal sont conservés.

# TRADUCTION :

# REMARQUE! Si vous avez l'intention de le placer sur un NFS (ou autre réseau)
# système de fichiers monté, veuillez lire la documentation Mutex (disponible
# à <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# vous vous épargnerez bien des ennuis.
#
# N'ajoutez PAS de barre oblique à la fin du chemin du répertoire.#

# TEST du 28 mars : décommenté la ligne suivante :
# TEST du 29 mars : re-commenté la ligne suivante :
ServerRoot "/etc/apache2"
ServerName localhost

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
#TRADUCTION
# HostnameLookups : enregistrez les noms des clients ou uniquement leurs adresses IP
# par exemple, www.apache.org (activé) ou 204.62.129.132 (désactivé).
# La valeur par défaut est off car ce serait globalement mieux pour le net si les gens
# devait sciemment activer cette fonctionnalité, car l'activer signifie que
# chaque requête client entraînera AU MOINS une requête de recherche vers le
# nom du serveur.

#HostnameLookups Off
#HostnameLookups On
# Rajouté ceci :
#HostnameLookups 82.66.155.194
HostnameLookups On

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.

<Directory />
  Options FollowSymLinks
  AllowOverride None
  Require all denied
</Directory>

<Directory /usr/share>
  AllowOverride None
  Require all granted
</Directory>

<Directory /var/www/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
 
  # ==>> pour éviter le warning de apache2ctl -S
        #Options Indexes FollowSymLinks MultiViews
# AllowOverride all
  # Require all granted
        #Satisfy Any
</Directory>

<Directory /srv/>
  Options Indexes FollowSymLinks
  AllowOverride all
# AllowOverride None
  Require all granted
#   Satisfy Any
</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
  Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet


 





Le config.php :




<?php
$CONFIG = array (
  'instanceid' => 'oc3204klngo7',
  'passwordsalt' => 'lS1yqxqIhEwp7wIIJxrPmpDhJXYMAm',
  'secret' => 'vshQa4xHcoibxnA8i1u0I4UwOWJLsK+TWEaK/Dpu4hAQ/huR',
  'trusted_domains' =>
  array (
    0 => 'localhost',
    1 => '192.168.0.51',
    2 => '82.66.155.194',
  ),
#  'datadirectory' => '/var/www/owncloud/data',
  'datadirectory' => '/srv/ocdata/data',
  'overwrite.cli.url' => 'http://192.168.0.51',
  'dbtype' => 'mysql',
  'version' => '10.9.1.2',
  'dbname' => 'owncloud',
  'dbhost' => 'localhost:3306',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_root',
  'dbpassword' => 'SY4eaUPESfo5lCM0dEt/WUzm22Q1qF',
  'allow_user_to_change_mail_address' => '',
  'logtimezone' => 'UTC',
  'apps_paths' =>
  array (
    0 =>
    array (
      'path' => '/var/www/owncloud/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 =>
    array (
      'path' => '/var/www/owncloud/apps-external',
      'url' => '/apps-external',
      'writable' => true,
    ),
  ),
  'installed' => true,
  'forcessl' => true,
 
);

 




Le virtual host de owncloud :


<VirtualHost *:443>
#    DocumentRoot /var/www/owncloud/
#    DocumentRoot /srv/ocdata/data
     DocumentRoot /srv/ocdata/
    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key

# Conseillé par Allan :
# A désactiver éventuellement
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>

# Voir éventuellement fichier owncloud-ssl.txt

 

#12 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 04-04-2022 21:25:56

Bonsoir à tous smile
@dejieres : je vois. Il y a plusieurs solutions.

Dont l'une m'est interdite : c'est la commande /var/www/owncloud/occ
Elle exige d'être exécutée par www-data. Or, je ne peux pas. J'ai bien tenté le coup !
Ca marchait sous Jesssie, plus sous Buster. Mystère...


root@1150-SRV:~# su www-data
This account is currently not available.
 



Même en user et du groupe sudo,


1150-SRV:~# su - install
install@1150-SRV:~$ su www-data
Mot de passe :
 



Mais lequel ?
Dois-je lui en attribuer un ? Pour un user système ?

Il y a aussi mention du lien symbolique vers le /srv... Ouais ! Je vais tenter ça aussi. Apparemment, je ne suis pas le seul à rencontrer ce pépin. Confer les forums dans toutes les langues imaginables.

"Passer par la réindexation" : c'est-à-dire ? Quant au temps, il n'y a presque rien dedans, lorsque j'effectue le déplacement, alors... Mais "réindexer", ça, je ne comprends pas bien.

@raleur : Si j'effectue le montage sur le /war.www/owncloud/data  -> les données de mes users arrivaient sur le  sur le SSD système de 120 Go, au lieu d'être sur le /srv/ocdata/data de la partition DONNEES : elle, elle restait vierge hmm Mais je peux bien réessayer.

@Croutons : oui. le /srv/ocdata/data était inexistant. La commande mv a peut-être bien déplacé le dossier data, sur une partition vierge, mais... il fallait peutêtre déjà créer ce /srv/ocdata/data : j'ai peut-re fait une c*** , là...

root@@raleur : j'ai tenté ça, bien sûr, puis que dejieres me l'avait dit. Le serveur fonctionnait... mais il remettait tout dans ce fichu dossier /var/www/owncloud/data. Et rien dans le montage.

Je recommence demain.
Et je donne le retour.

Merci pour votre soutien ! Je ne m'attendais pas du tout à une telle difficulté sur le déplacement du dossier data...

#13 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 04-04-2022 12:55:47


root@1150-SRV:~# df
Sys. de fichiers blocs de 1K  Utilisé Disponible Uti% Monté sur
udev                 8009728        0    8009728   0% /dev
tmpfs                1607200     9828    1597372   1% /run
/dev/sda1           98664624  7396720   86212980   8% /
tmpfs                8035996     7284    8028712   1% /dev/shm
tmpfs                   5120        4       5116   1% /run/lock
tmpfs                8035996        0    8035996   0% /sys/fs/cgroup
/dev/sdb1          256614804 26555972  216953836  11% /mnt
tmpfs                1607196       40    1607156   1% /run/user/0
/dev/sdb3          295941968    64872  280774480   1% /srv/ocdata

 



Oui. J'ai arrêté Apache, puis l'ai redémarré.

J'oubliais : le apache2.conf : (modifié)


# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `--  ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
#   `-- sites-enabled
#   `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.

# TRADUCTION :
# ServerRoot : le sommet de l'arborescence de répertoires sous lequel le serveur
# les fichiers de configuration, d'erreur et de journal sont conservés.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
# ServerRoot : le sommet de l'arborescence de répertoires sous lequel le serveur
# les fichiers de configuration, d'erreur et de journal sont conservés.

# TRADUCTION :

# REMARQUE! Si vous avez l'intention de le placer sur un NFS (ou autre réseau)
# système de fichiers monté, veuillez lire la documentation Mutex (disponible
# à <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# vous vous épargnerez bien des ennuis.
#
# N'ajoutez PAS de barre oblique à la fin du chemin du répertoire.#

# TEST du 28 mars : décommenté la ligne suivante :
# TEST du 29 mars : re-commenté la ligne suivante :
ServerRoot "/etc/apache2"
ServerName localhost

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
#TRADUCTION
# HostnameLookups : enregistrez les noms des clients ou uniquement leurs adresses IP
# par exemple, www.apache.org (activé) ou 204.62.129.132 (désactivé).
# La valeur par défaut est off car ce serait globalement mieux pour le net si les gens
# devait sciemment activer cette fonctionnalité, car l'activer signifie que
# chaque requête client entraînera AU MOINS une requête de recherche vers le
# nom du serveur.

#HostnameLookups Off
#HostnameLookups On
# Rajouté ceci :
#HostnameLookups 82.66.155.194
HostnameLookups On

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.

<Directory />
  Options FollowSymLinks
  AllowOverride None
  Require all denied
</Directory>

<Directory /usr/share>
  AllowOverride None
  Require all granted
</Directory>

<Directory /var/www/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
 
  # ==>> pour éviter le warning de apache2ctl -S
        #Options Indexes FollowSymLinks MultiViews
# AllowOverride all
  # Require all granted
        #Satisfy Any
</Directory>

<Directory /srv/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
  Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

 

#14 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 04-04-2022 12:47:11

Attends ! Je corrige !
Si et seulement si le vhost est le suivant ça marche. Mais les données arrivent dans /var/www/owncloud/data


<VirtualHost *:443>
    DocumentRoot /var/www/owncloud/
#    DocumentRoot /srv/ocdata/
    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key

# Conseillé par Allan :
# A désactiver éventuellement
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>

# Voir éventuellement fichier owncloud-ssl.txt


 



MAIS si je le fais pointer sur /srv/ocdata/data, le serveur ne fonctionne plus et j'ai ça, côté serveur :

https://cjoint.com/c/LDekYC04Lrj

#15 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 04-04-2022 10:36:56

Bonjour à tous.

@dejieres : j'ai modifié le owncloud.conf selon test conseils :


<VirtualHost *:443>
    DocumentRoot /var/www/owncloud/
#    DocumentRoot /srv/ocdata/
    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key

# Conseillé par Allan :
# A désactiver éventuellement
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>


 



Si je mets : DocumentRoot /srv/ocdata/  ==>> j'arrive sur un indexoff, côté serveur, et pas d'accès du tout côté client.


Plus de forbidden mais... les données envoyées sur le serveur par le client arrivent... sur l'ancien /var/www/owncloud/data sad
Et pas sur le /srv/ocdata/data ! Comme si je n'avais pas déplacé de dossier data...

Mon apache2.conf :


# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `--  ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
#   `-- sites-enabled
#   `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.

# TRADUCTION :
# ServerRoot : le sommet de l'arborescence de répertoires sous lequel le serveur
# les fichiers de configuration, d'erreur et de journal sont conservés.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
# ServerRoot : le sommet de l'arborescence de répertoires sous lequel le serveur
# les fichiers de configuration, d'erreur et de journal sont conservés.

# TRADUCTION :

# REMARQUE! Si vous avez l'intention de le placer sur un NFS (ou autre réseau)
# système de fichiers monté, veuillez lire la documentation Mutex (disponible
# à <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# vous vous épargnerez bien des ennuis.
#
# N'ajoutez PAS de barre oblique à la fin du chemin du répertoire.#

# TEST du 28 mars : décommenté la ligne suivante :
# TEST du 29 mars : re-commenté la ligne suivante :
ServerRoot "/etc/apache2"
ServerName localhost

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
#TRADUCTION
# HostnameLookups : enregistrez les noms des clients ou uniquement leurs adresses IP
# par exemple, www.apache.org (activé) ou 204.62.129.132 (désactivé).
# La valeur par défaut est off car ce serait globalement mieux pour le net si les gens
# devait sciemment activer cette fonctionnalité, car l'activer signifie que
# chaque requête client entraînera AU MOINS une requête de recherche vers le
# nom du serveur.

#HostnameLookups Off
#HostnameLookups On
# Rajouté ceci :
#HostnameLookups 82.66.155.194
HostnameLookups On

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.

<Directory />
  Options FollowSymLinks
  AllowOverride None
  Require all denied
</Directory>

<Directory /usr/share>
  AllowOverride None
  Require all granted
</Directory>

<Directory /var/www/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
 
  # ==>> pour éviter le warning de apache2ctl -S
        #Options Indexes FollowSymLinks MultiViews
# AllowOverride all
  # Require all granted
        #Satisfy Any
</Directory>

<Directory /srv/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
  Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

 



Comprends pas...

#16 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 03-04-2022 20:14:01

Je prends note wink

Et puis j'ai saisi ceci:


root@1150-SRV:~# apache2 --help
[Sun Apr 03 19:31:30.111388 2022] [core:warn] [pid 2435] AH00111: Config variable ${APACHE_RUN_DIR} is not defined
apache2: Syntax error on line 97 of /etc/apache2/apache2.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot
 



Pour connaître ma version d'Apache. Je questionne apache. Et il m'a retourné ça ! Malgré un


root@1150-SRV:~# apache2ctl configtest
Syntax OK
 



En fait, c'est ET le owncloud.conf ET apache2.conf que je dois modifier.

Ici : https://httpd.apache.org/docs/2.4/upgrading.html

Beaucoup d'explications !!

Ce qui marchait avec une version plus ancienne d'Apache ne fonctionne plus maintenant !

La voici, ma version d'Apache :


root@1150-SRV:~# apache2ctl -v
Server version: Apache/2.4.38 (Debian)
Server built:   2021-12-21T16:50:43
 



Je vais potasser ça.

Je suis un peu fatigué, là, mais je sens que je ne suis pas loin du but...

#17 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 03-04-2022 19:25:31

Mais Oh ! là ! là!!
Regardez-moi ces logs d'apache :


[Sun Apr 03 19:07:54.124679 2022] [mpm_prefork:notice] [pid 1575] AH00169: caught SIGTERM, shutting down
[Sun Apr 03 19:20:46.318172 2022] [ssl:warn] [pid 2823] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Sun Apr 03 19:20:46.340807 2022] [ssl:warn] [pid 2824] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Sun Apr 03 19:20:46.344919 2022] [mpm_prefork:notice] [pid 2824] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Sun Apr 03 19:20:46.344953 2022] [core:notice] [pid 2824] AH00094: Command line: '/usr/sbin/apache2'
[Sun Apr 03 19:21:01.823369 2022] [mpm_prefork:notice] [pid 2824] AH00169: caught SIGTERM, shutting down
[Sun Apr 03 19:21:28.275177 2022] [ssl:warn] [pid 791] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Sun Apr 03 19:21:28.400872 2022] [ssl:warn] [pid 807] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Sun Apr 03 19:21:28.404708 2022] [mpm_prefork:notice] [pid 807] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Sun Apr 03 19:21:28.404736 2022] [core:notice] [pid 807] AH00094: Command line: '/usr/sbin/apache2'
[Sun Apr 03 19:22:05.773421 2022] [authz_core:error] [pid 811] [client 192.168.0.51:47652] AH01630: client denied by server configuration: /srv/ocdata/data/
[Sun Apr 03 19:22:05.847851 2022] [authz_core:error] [pid 811] [client 192.168.0.51:47652] AH01630: client denied by server configuration: /srv/ocdata/data/favicon.ico, referer: https://192.168.0.51/

 



Je vais chercher ce qu'est cette erreur AH01630.

#18 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 03-04-2022 19:19:39

Forbidden sad

J'ai activé a2enmod rewrite, ainsi que conseillé dans le tuto que j'ai suivi.
Je n'ai plus mentionné le répertoire data de owncloud dans apache2.conf . C'est pourtant ce que j'avais fait sur l'ancien serveur, et ça marchait. Enfin : sur lke /media.

Ca devient dur, là wink

Le fstab :




# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4b0c937b-eb1c-46b9-bed9-23932e9c6943 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=4abdeb87-995c-4045-82d5-9a04536a52d6 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
LABEL=DATA  /mnt  ext4  defaults  0 0
#LABEL=DONNEES  /mnt/DONNEES  ext4  defaults  0 0
LABEL=DONNEES /srv/ocdata ext4  resuid=33 0 0

 



df :


Sys. de fichiers blocs de 1K  Utilisé Disponible Uti% Monté sur
udev                 8009728        0    8009728   0% /dev
tmpfs                1607200     9380    1597820   1% /run
/dev/sda1           98664624  6854828   86754872   8% /
tmpfs                8035996    21852    8014144   1% /dev/shm
tmpfs                   5120        4       5116   1% /run/lock
tmpfs                8035996        0    8035996   0% /sys/fs/cgroup
/dev/sdb1          256614804 25119128  218390680  11% /mnt
/dev/sdb3          295941968   278456  280560896   1% /srv/ocdata
tmpfs                1607196       16    1607180   1% /run/user/0
 




apache2.conf :



<Directory />
  Options FollowSymLinks
  AllowOverride None
  Require all denied
</Directory>

<Directory /usr/share>
  AllowOverride None
  Require all granted
</Directory>

<Directory /var/www/>
  # ==>> pour éviter le warning de apache2ctl -S
    #Options Indexes FollowSymLinks MultiViews
 
  AllowOverride all
 
  # Require all granted
    Satisfy Any
   
</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess   <<== [b]Pas de path absolu ?[/b]

 





Le config.php :



<?php
$CONFIG = array (
  'instanceid' => 'oc3204klngo7',
  'passwordsalt' => 'lS1yqxqIhEwp7wIIJxrPmpDhJXYMAm',
  'secret' => 'vshQa4xHcoibxnA8i1u0I4UwOWJLsK+TWEaK/Dpu4hAQ/huR',
  'trusted_domains' =>
  array (
    0 => 'localhost',
    1 => '192.168.0.51',
    2 => 'IP publique',
  ),
  'datadirectory' => '/srv/ocdata/data',
  'overwrite.cli.url' => 'http://192.168.0.51',
  'dbtype' => 'mysql',
  'version' => '10.9.1.2',
  'dbname' => 'owncloud',
  'dbhost' => 'localhost:3306',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_root',
  'dbpassword' => 'SY4eaUPESfo5lCM0dEt/WUzm22Q1qF',
  'allow_user_to_change_mail_address' => '',
  'logtimezone' => 'UTC',
  'apps_paths' =>
  array (
    0 =>
    array (
      'path' => '/var/www/owncloud/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 =>
    array (
      'path' => '/var/www/owncloud/apps-external',
      'url' => '/apps-external',
      'writable' => true,
    ),
  ),
  'installed' => true,
  'forcessl' => true,
 
);

 




Le virtual host de owncloud :


<VirtualHost *:443>
#    DocumentRoot /var/www/owncloud/
    DocumentRoot /srv/ocdata/data/
    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key

# A désactiver éventuellement
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>

# Voir éventuellement fichier owncloud-ssl.txt

 

#19 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 03-04-2022 18:51:23

Salut !

Non, non : il est bien dans /var/www/owncloud

Mais tu m'éclaires... Je vais tester ça. Là, je rentre.
Je donne le retour, après le nouveau déplacement, ET avec tes conseils.

#20 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 03-04-2022 14:18:15

Il y avait le fameux dossier data de owncloud.
Je suis revenu en arrière, et refait le déplacement.

Mais, tests effectués, ça ne change rien : pas d'accès à owncloud côté serveur. Page blanche.
Ca ressemble à un problème de droits, ça...
Quelque chose dans un fichier de configuration : un path incorrect. Ou des droits mal définis dans le vhost ou apache2.conf.

On m'avait conseillé ceci :


<VirtualHost *:443>
#    DocumentRoot /var/www/owncloud/
    DocumentRoot /srv/ocdata/data
    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key


# [b]A désactiver éventuellement[/b]
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>


 




Là, je vais refaire le montage sitôt revenu chez moi.
C'est très bizarre...

#22 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 03-04-2022 11:09:10

Bonjour à tous smile

Ben... je ne suis pas doué, hein ? C'est pas franchement un forbiden, mais le client owncloud ne peut pas se connecter, et, sur le serveur, j'arrive à une page blanche en tapant l'IP locale dans Firefox.

Le fstab :


# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4b0c937b-eb1c-46b9-bed9-23932e9c6943 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=4abdeb87-995c-4045-82d5-9a04536a52d6 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
LABEL=DATA  /mnt  ext4  defaults  0 0
#LABEL=DONNEES  /mnt/DONNEES  ext4  defaults  0 0
LABEL=DONNEES /srv  ext4  defaults  0 0  <<== Pas /srv/data : j'ai tenté le coup, mais ça ne change rien.
 




df :


Sys. de fichiers blocs de 1K  Utilisé Disponible Uti% Monté sur
udev                 8009728        0    8009728   0% /dev
tmpfs                1607200     9384    1597816   1% /run
/dev/sda1           98664624  8015392   85594308   9% /
tmpfs                8035996     7864    8028132   1% /dev/shm
tmpfs                   5120        4       5116   1% /run/lock
tmpfs                8035996        0    8035996   0% /sys/fs/cgroup
/dev/sdb3          295941968   278464  280560888   1% /srv
/dev/sdb1          256614804 24506384  219003424  11% /mnt
tmpfs                1607196       16    1607180   1% /run/user/0
 




apache2.conf :



<Directory />
  Options FollowSymLinks
  AllowOverride None
  Require all denied
</Directory>

<Directory /usr/share>
  AllowOverride None
  Require all granted
</Directory>

<Directory /var/www/>
  # ==>> pour éviter le warning de apache2ctl -S
    #Options Indexes FollowSymLinks MultiViews
 
  AllowOverride all
 
  # Require all granted
    Satisfy Any
   
</Directory>

<Directory /srv/data/>
  # ==>> pour éviter le warning de apache2ctl -S
  # Options Indexes FollowSymLinks

  AllowOverride all
  # Require all granted
   
    Satisfy Any
  #AllowOverride None

  # A décommenter peut-être ?
  #Require all granted
   
</Directory>
 






Le config.php :

<?php
$CONFIG = array (
  'instanceid' => 'oc3204klngo7',
  'passwordsalt' => 'lS1yqxqIhEwp7wIIJxrPmpDhJXYMAm',
  'secret' => 'vshQa4xHcoibxnA8i1u0I4UwOWJLsK+TWEaK/Dpu4hAQ/huR',
  'trusted_domains' =>
  array (
    0 => 'localhost',
    1 => '192.168.0.51',
    2 => 'IP publique',
  ),
  #'datadirectory' => '/var/www/owncloud/data',
  'datadirectory' => '/srv/data/',
  'overwrite.cli.url' => 'http://192.168.0.51',
  'dbtype' => 'mysql',
  'version' => '10.9.1.2',
  'dbname' => 'owncloud',
  'dbhost' => 'localhost:3306',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_root',
  'dbpassword' => 'SY4eaUPESfo5lCM0dEt/WUzm22Q1qF',
  'allow_user_to_change_mail_address' => '',
  'logtimezone' => 'UTC',
  'apps_paths' =>
  array (
    0 =>
    array (
      'path' => '/var/www/owncloud/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 =>
    array (
      'path' => '/var/www/owncloud/apps-external',
      'url' => '/apps-external',
      'writable' => true,
    ),
  ),
  'installed' => true,
  'forcessl' => true,
 
);

 




Le virtual host de owncloud :


<VirtualHost *:443>
#    DocumentRoot /var/www/owncloud/
    DocumentRoot /srv/data
    # Activation du mode SSL
    SSLEngine On
    SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

    # On indique ou est le certificat
    SSLCertificateFile /etc/ssl/certs/owncloud.pem
    SSLCertificateKeyFile /etc/ssl/private/owncloud.key

# A désactiver éventuellement
      RewriteEngine on
      RewriteCond %{HTTPS} !on
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

</VirtualHost>

# Voir éventuellement fichier owncloud-ssl.txt

 



J'ai vérifié les droits de www-dat : il possède tout le /srv/data

sad

#23 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 02-04-2022 20:41:29

Eh : Ouais...


root@1150-SRV:~# df /mnt/DONNEES
Sys. de fichiers blocs de 1K  Utilisé Disponible Uti% Monté sur
/dev/sdb1          256614804 23484324  220025484  10% /mnt
root@1150-SRV:~# df /mnt/DATA
Sys. de fichiers blocs de 1K  Utilisé Disponible Uti% Monté sur
/dev/sdb1          256614804 23484324  220025484  10% /mnt
 



Deux partitions ont le même point de montage.

Alors qu'il me faut monter la partition nommée DONNEES sur /srv/

Je l'avais fait, il y a quelques minutes, mais c'était comme un miroir. Le /srv affichait tout le répertoire de owncloud, exactement comme un


ls /var/www/owncloud
 



Je vais revoir ça en profondeur.
Vive quand-même CloneZilla, hein ! wink

#24 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 02-04-2022 19:32:10

Pardon : je me suis mal exprimé.
La partition DATA  n'a rien à voir avec celle que j'ai appelée DONNEES.
/mnt/DATA est réservé à root.
MAIS la partition nommée "DONNEES", non, évidemment. Surtout pas !

#25 Re : Réseau » [RESOLU]Owncloud : déplacement du dossier data » 02-04-2022 19:09:26

Ah ! Je commence à voir plus clair smile

voici mon fstab :


# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4b0c937b-eb1c-46b9-bed9-23932e9c6943 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=4abdeb87-995c-4045-82d5-9a04536a52d6 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
LABEL=DATA  /mnt  ext4  defaults  0 0
LABEL=DONNEES /mnt/DONNEES  ext4  defaults  0 0

 



Donc, je démonte cette partition /mnt/DONNEES, pour la remonter ensuite sur /svr/DONNEES ...
Le second disque a trois partitions :
DATA : réservée à root pour mes sauvegardes de root. Montée au démarrage sur le /mnt . Réservée à root. Un simple chmod o= -rw
IMAGES : pour les images CloneZilla. Non montée au démarrage mais réservée à root. Là aussi, un chmod -rw
DONNEES : pour les données du serveur. Montée également au démarrage.

Pied de page des forums

Propulsé par FluxBB