Échecs répétés à l'installation
pierrechtux opened this issue · comments
Bonjour,
Cela fait quelques temps que je bataille pour remettre en route un Geopoppy, après le décès de mon précédent Pi (dû à une alimentation pas assez puissante, de toute évidence).
Je viens de flasher pour la nième fois une SD que j'ai choisie de bonne qualité et spacieuse (64 Go), et voilà que j'essuie encore un échec...
Le flashage s'est a priori bien passé; il y a juste Etcher qui m'a mis un message "Drive (/dev/mmcblk0) is unusually large for an SD card or USB stick. Are you sure you want to flash this drive? Are you sure you want to continue?", et j'ai bien sûr continué.
Une fois le Pi redémarré, tout semble bien se passer.
Le réseau wifi GeoPoppy_Pi3 apparaît correctement, je peux m'y connecter, mais
https://172.24.1.1
n'arrive nulle part (message de firefox: "La connexion a échoué - Firefox ne peut établir de connexion avec le serveur à l’adresse 172.24.1.1.").
L'IP ne pongue pas, non plus:
ping 172.24.1.1
PING 172.24.1.1 (172.24.1.1) 56(84) bytes of data.
From 80.10.125.80 icmp_seq=1 Packet filtered
From 80.10.125.80 icmp_seq=2 Packet filtered
^C
--- 172.24.1.1 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2ms
Via mon réseau filaire, je peux pinguer le Pi, et y accéder en ssh.
En farfouinant dans les logs, j'ai trouvé ceci dans syslog:
...
Jan 24 09:44:32 geopoppy ntpd[448]: Soliciting pool server 95.81.173.74
Jan 24 09:44:32 geopoppy ntpd[448]: Soliciting pool server 5.135.3.88
Jan 24 09:44:33 geopoppy ntpd[448]: Soliciting pool server 2001:bc8:2a01:100::42
Feb 12 19:43:40 geopoppy systemd[1]: Time has been changed
Feb 12 19:43:40 geopoppy systemd[1]: apt-daily.timer: Adding 4h 56min 7.344629s random time.
Feb 12 19:43:40 geopoppy systemd[1]: apt-daily-upgrade.timer: Adding 58min 50.644175s random time.
Feb 12 19:43:43 geopoppy cloud-init[666]: Loaded image: portainer/portainer:linux-arm
Feb 12 19:43:43 geopoppy cloud-init[666]: docker load --input postgres10-2.4-arm32_1.tar.gz
Feb 12 19:43:43 geopoppy cloud-init[666]: + docker load --input postgres10-2.4-arm32_1.tar.gz
Feb 12 19:49:33 geopoppy ntpd[448]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Feb 12 19:53:25 geopoppy systemd[1]: Starting Cleanup of Temporary Directories...
Feb 12 19:53:25 geopoppy kernel: [ 900.569324] EXT4-fs warning (device mmcblk0p2): ext4_dirent_csum_verify:353: inode #525277: comm systemd-tmpfile: No space for directory leaf checksum. Please run e2fsck -D.
Feb 12 19:53:25 geopoppy kernel: [ 900.569335] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:977: inode #525277: comm systemd-tmpfile: Directory block failed checksum
Feb 12 19:53:25 geopoppy kernel: [ 900.671584] EXT4-fs warning (device mmcblk0p2): ext4_dirent_csum_verify:353: inode #525278: comm systemd-tmpfile: No space for directory leaf checksum. Please run e2fsck -D.
Feb 12 19:53:25 geopoppy kernel: [ 900.671597] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:977: inode #525278: comm systemd-tmpfile: Directory block failed checksum
Feb 12 19:53:25 geopoppy systemd[1]: Started Cleanup of Temporary Directories.
Feb 12 19:53:40 geopoppy cloud-init[666]: Loaded image: jancelin/geopoppy:postgres10-2.4-arm32_1
Feb 12 19:53:40 geopoppy cloud-init[666]: docker load --input qgis3server.tar.gz
Feb 12 19:53:41 geopoppy cloud-init[666]: + docker load --input qgis3server.tar.gz
Feb 12 20:06:53 geopoppy kernel: [ 1708.414961] EXT4-fs error (device mmcblk0p2): ext4_validate_block_bitmap:385: comm exe: bg 64: bad block bitmap checksum
...
Les 3 premières lignes sont les dernières qui étaient déjà là sur l'image de la SD telle que téléchargée.
Un peu plus loin, dans le log, je trouve d'autres messages inquiétants du système de fichiers:
Feb 12 20:47:00 geopoppy kernel: [ 4115.438757] EXT4-fs (mmcblk0p2): Delayed block allocation failed for inode 525622 at logical offset 75776 with max blocks 983 with error 117
Feb 12 20:47:00 geopoppy kernel: [ 4115.438882] EXT4-fs (mmcblk0p2): This should not happen!! Data will be lost
Feb 12 20:47:00 geopoppy kernel: [ 4115.438882]
Feb 12 20:47:00 geopoppy kernel: [ 4115.675327] EXT4-fs (mmcblk0p2): Delayed block allocation failed for inode 525622 at logical offset 76759 with max blocks 1024 with error 117
Feb 12 20:47:00 geopoppy kernel: [ 4115.675454] EXT4-fs (mmcblk0p2): This should not happen!! Data will be lost
Il y a d'autres messages d'erreur, les voici tous:
root@geopoppy:/var/log# cat syslog | grep -v "Jan 24 " | grep -i error
Feb 12 19:49:33 geopoppy ntpd[448]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Feb 12 19:53:25 geopoppy kernel: [ 900.569335] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:977: inode #525277: comm systemd-tmpfile: Directory block failed checksum
Feb 12 19:53:25 geopoppy kernel: [ 900.671597] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:977: inode #525278: comm systemd-tmpfile: Directory block failed checksum
Feb 12 20:06:53 geopoppy kernel: [ 1708.414961] EXT4-fs error (device mmcblk0p2): ext4_validate_block_bitmap:385: comm exe: bg 64: bad block bitmap checksum
Feb 12 20:47:00 geopoppy kernel: [ 4115.438757] EXT4-fs (mmcblk0p2): Delayed block allocation failed for inode 525622 at logical offset 75776 with max blocks 983 with error 117
Feb 12 20:47:00 geopoppy kernel: [ 4115.675327] EXT4-fs (mmcblk0p2): Delayed block allocation failed for inode 525622 at logical offset 76759 with max blocks 1024 with error 117
Feb 12 20:47:03 geopoppy kernel: [ 4118.709216] EXT4-fs (mmcblk0p2): Delayed block allocation failed for inode 525622 at logical offset 77783 with max blocks 1024 with error 117
Feb 12 20:57:48 geopoppy dockerd[390]: time="2019-02-12T20:57:48.064979049Z" level=error msg="Download failed, retrying: read tcp 192.168.1.10:35916->104.18.123.25:443: read: connection reset by peer"
Feb 12 21:28:58 geopoppy kernel: [ 6633.617549] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:28:58 geopoppy kernel: [ 6633.634309] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:28:58 geopoppy kernel: [ 6633.653863] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:28:58 geopoppy kernel: [ 6633.667956] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:28:58 geopoppy kernel: [ 6633.684626] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:28:58 geopoppy dockerd[390]: time="2019-02-12T21:28:58.912640980Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:28:58 geopoppy dockerd[390]: time="2019-02-12T21:28:58.914627887Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:00 geopoppy kernel: [ 6634.968702] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:00 geopoppy kernel: [ 6634.990617] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:00 geopoppy kernel: [ 6635.003661] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:00 geopoppy kernel: [ 6635.039462] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:00 geopoppy kernel: [ 6635.061169] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:00 geopoppy dockerd[390]: time="2019-02-12T21:29:00.248991616Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:00 geopoppy dockerd[390]: time="2019-02-12T21:29:00.249041042Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:00 geopoppy dockerd[390]: time="2019-02-12T21:29:00.356408449Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:00 geopoppy dockerd[390]: time="2019-02-12T21:29:00.356532250Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:00 geopoppy dockerd[390]: time="2019-02-12T21:29:00.383448853Z" level=error msg="affacf302fed9c6e5045c465b4ec7b0586de2965a69df2ac12183afc9641a07d cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:00 geopoppy dockerd[390]: time="2019-02-12T21:29:00.383679007Z" level=error msg="Handler for POST /v1.25/containers/affacf302fed9c6e5045c465b4ec7b0586de2965a69df2ac12183afc9641a07d/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:00 geopoppy cloud-init[666]: #033[7A#033[2K#015Creating pirate_redis_1 ... #033[31merror#033[0m#015#033[7B
Feb 12 21:29:00 geopoppy cloud-init[666]: ERROR: for pirate_redis_1 Cannot start service redis: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:04 geopoppy kernel: [ 6639.160965] EXT4-fs error: 5 callbacks suppressed
Feb 12 21:29:04 geopoppy kernel: [ 6639.160974] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:05 geopoppy kernel: [ 6639.910576] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:05 geopoppy kernel: [ 6639.958046] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:05 geopoppy kernel: [ 6640.312156] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:05 geopoppy kernel: [ 6640.412215] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:05 geopoppy dockerd[390]: time="2019-02-12T21:29:05.588179149Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:05 geopoppy dockerd[390]: time="2019-02-12T21:29:05.593255921Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:05 geopoppy kernel: [ 6640.538818] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:06 geopoppy kernel: [ 6641.139863] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:06 geopoppy kernel: [ 6641.184540] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:06 geopoppy kernel: [ 6641.204285] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:06 geopoppy kernel: [ 6641.224846] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.399362628Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.401326618Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.782946152Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.783798279Z" level=error msg="bf9fc7634a1c20bc2cca4607bc42dde00b8337533d9f61977bab50b53de3b400 cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.784079578Z" level=error msg="Handler for POST /v1.25/containers/bf9fc7634a1c20bc2cca4607bc42dde00b8337533d9f61977bab50b53de3b400/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.791307630Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:06 geopoppy cloud-init[666]: #033[5A#033[2K#015Creating pirate_postgis_1 ... #033[31merror#033[0m#015#033[5B
Feb 12 21:29:06 geopoppy cloud-init[666]: ERROR: for pirate_postgis_1 Cannot start service postgis: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.873421176Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.873235449Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.973395740Z" level=error msg="1ec36006ae994080e973fdb8fbe5634ecdddef194c8451fc687f42719085792c cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:06 geopoppy dockerd[390]: time="2019-02-12T21:29:06.973575998Z" level=error msg="Handler for POST /v1.25/containers/1ec36006ae994080e973fdb8fbe5634ecdddef194c8451fc687f42719085792c/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:06 geopoppy cloud-init[666]: #033[4A#033[2K#015Creating pirate_tracking_1 ... #033[31merror#033[0m#015#033[4B
Feb 12 21:29:06 geopoppy cloud-init[666]: ERROR: for pirate_tracking_1 Cannot start service tracking: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.393500405Z" level=error msg="5be28d4443311f1c3d4058a1470dba3af3b5ada596c29382e1de43128c7aac49 cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.393687486Z" level=error msg="Handler for POST /v1.25/containers/5be28d4443311f1c3d4058a1470dba3af3b5ada596c29382e1de43128c7aac49/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:07 geopoppy cloud-init[666]: #033[6A#033[2K#015Creating pirate_lizmap_1 ... #033[31merror#033[0m#015#033[6B
Feb 12 21:29:07 geopoppy cloud-init[666]: ERROR: for pirate_lizmap_1 Cannot start service lizmap: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.763455733Z" level=error msg="9a8cb608b9952d9ae05bea8927ee6d61c27a82b8552de104694a2a238b84fee8 cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.763652085Z" level=error msg="Handler for POST /v1.25/containers/9a8cb608b9952d9ae05bea8927ee6d61c27a82b8552de104694a2a238b84fee8/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:07 geopoppy cloud-init[666]: #033[3A#033[2K#015Creating pirate_cloud_1 ... #033[31merror#033[0m#015#033[3B
Feb 12 21:29:07 geopoppy cloud-init[666]: ERROR: for pirate_cloud_1 Cannot start service cloud: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.873674412Z" level=error msg="59d0cd8aa5a2a31343da65d0971e3cb3fa88e37fc29464f3639bc696a81d7c4e cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.873967690Z" level=error msg="Handler for POST /v1.25/containers/59d0cd8aa5a2a31343da65d0971e3cb3fa88e37fc29464f3639bc696a81d7c4e/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:07 geopoppy cloud-init[666]: #033[1A#033[2K#015Creating pirate_map_1 ... #033[31merror#033[0m#015#033[1B
Feb 12 21:29:07 geopoppy cloud-init[666]: ERROR: for pirate_map_1 Cannot start service map: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.983538146Z" level=error msg="0a53c893ff403e995e4e9dd0eb1257143f280b56881f33e68eee2387002be5cb cleanup: failed to delete container from containerd: no such container"
Feb 12 21:29:07 geopoppy dockerd[390]: time="2019-02-12T21:29:07.983847154Z" level=error msg="Handler for POST /v1.25/containers/0a53c893ff403e995e4e9dd0eb1257143f280b56881f33e68eee2387002be5cb/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
Feb 12 21:29:07 geopoppy cloud-init[666]: #033[2A#033[2K#015Creating pirate_portainer_1 ... #033[31merror#033[0m#015#033[2B
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for pirate_portainer_1 Cannot start service portainer: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for map Cannot start service map: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for tracking Cannot start service tracking: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for redis Cannot start service redis: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for postgis Cannot start service postgis: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for portainer Cannot start service portainer: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for lizmap Cannot start service lizmap: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: ERROR: for cloud Cannot start service cloud: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux: bad message: unknown
Feb 12 21:29:08 geopoppy cloud-init[666]: Encountered errors while bringing up the project.
Feb 12 21:31:39 geopoppy check_docker.sh[4096]: ERROR: for pirate_portainer_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for pirate_tracking_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for pirate_cloud_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for pirate_map_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for pirate_redis_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for pirate_lizmap_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for pirate_postgis_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for map UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for tracking UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for redis UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for postgis UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for portainer UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for lizmap UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy check_docker.sh[4096]: ERROR: for cloud UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Feb 12 21:31:40 geopoppy cloud-init[666]: Job for Cdocker.service failed because the control process exited with error code.
Feb 12 21:32:00 geopoppy kernel: [ 6815.688193] EXT4-fs error: 10 callbacks suppressed
Feb 12 21:32:00 geopoppy kernel: [ 6815.688203] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:32:00 geopoppy kernel: [ 6815.703246] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:32:00 geopoppy dockerd[390]: time="2019-02-12T21:32:00.892003049Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:32:00 geopoppy dockerd[390]: time="2019-02-12T21:32:00.903441369Z" level=error msg="stream copy error: reading from a closed fifo"
Feb 12 21:32:00 geopoppy kernel: [ 6815.718477] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:32:00 geopoppy kernel: [ 6815.723327] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:32:00 geopoppy kernel: [ 6815.728069] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1447: inode #525343: comm docker-containe: checksumming directory block 0
Feb 12 21:32:01 geopoppy dockerd[390]: time="2019-02-12T21:32:01.463480194Z" level=error msg="8e574c82fac7cdd63040ff86ce0c01032206781e11fc50ebb7d4b6f4b351bf15 cleanup: failed to delete container from containerd: no such container"
Feb 12 21:32:01 geopoppy dockerd[390]: time="2019-02-12T21:32:01.463672015Z" level=error msg="Handler for POST /v1.25/containers/8e574c82fac7cdd63040ff86ce0c01032206781e11fc50ebb7d4b6f4b351bf15/start returned error: mkdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux:
root@geopoppy:/var/log#
C'est grave, docteur? Que puis-je faire, à ce stade?
J'ai continué l'aventure, en suivant le conseil trouvé dans le log de faire un "e2fsck -D".
J'ai bien sûr éteint le pi, puis mis la SD dans mon autre ordi:
# root@latitude: ~ < 2019_02_13__16_28_05 >
fsck /dev/mmcblk0p2
...
/var/lib/docker/overlay2/12bb288c56c53e9015f4abcc9dcdfc4f25dec02f404673a6e8d5595a50cad94f/diff/usr/include/qgis/qgsprocessingregistry.h (i-noeud n°2594811, date de modification Sat Oct 13 12:00:24 2018)
/var/lib/docker/overlay2/12bb288c56c53e9015f4abcc9dcdfc4f25dec02f404673a6e8d5595a50cad94f/diff/usr/include/qgis/qgsprocessingparametertypeimpl.h (i-noeud n°2594809, date de modification Sat Oct 13 12:00:24 2018)
Cloner les blocs réclamés plusieurs fois<o>? oui
Le fichier /var/lib/docker/overlay2/12bb288c56c53e9015f4abcc9dcdfc4f25dec02f404673a6e8d5595a50cad94f/diff/usr/include/qgis/qgslayoutitemhtml.h (i-noeud n°2594562, date de modification Tue Jul 1 07:38:57 2014)
a 230 bloc(s) réclamé(s) plusieurs fois, partagés avec 110 fichier(s) :
/var/lib/docker/overlay2/12bb288c56c53e9015f4abcc9dcdfc4f25dec02f404673a6e8d5595a50cad94f/diff/usr/include/qgis/qgsscalewidget.h (i-noeud n°2594921, date de modification Sat Oct 13 12:00:24 2018)
...
Boudiou...
...
le compteur de référence de l'i-noeud 2596237 est 1, devrait être 2. Corriger ? oui
le compteur de référence de l'i-noeud 2596238 est 1, devrait être 2. Corriger ? oui
le compteur de référence de l'i-noeud 2596239 est 1, devrait être 2. Corriger ? oui
le compteur de référence de l'i-noeud 2596240 est 1, devrait être 2. Corriger ? oui
...
# root@latitude: ~ < 2019_02_13__16_28_05 >
fsck /dev/mmcblk0p2 -y
...
root: ***** LE SYSTÈME DE FICHIERS A ÉTÉ MODIFIÉ *****
root : 226885/16200000 fichiers (0.1% non contigus), 2670701/16367360 blocs
# root@latitude: ~ < 2019_02_13__16_28_05 >
fsck /dev/mmcblk0p2 -y
fsck de util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
root : propre, 226885/16200000 fichiers, 2670701/16367360 blocs
# root@latitude: ~ < 2019_02_13__16_28_05 >
fsck /dev/mmcblk0p1
fsck de util-linux 2.33.1
fsck.fat 4.1 (2017-01-24)
/dev/mmcblk0p1: 160 files, 18031/32695 clusters
Il y avait du grabuge!
J'ai aussi fait le e2fsck -D. Selon la page de man:
-D Optimize directories in filesystem. This option causes e2fsck
to try to optimize all directories, either by reindexing them if
the filesystem supports directory indexing, or by sorting and
compressing directories for smaller directories, or for filesys‐
tems using traditional linear directories.
Voilà ce que ça a donné, il a fallu forcer:
# root@latitude: ~ < 2019_02_13__16_28_05 >
e2fsck -D /dev/mmcblk0p2
e2fsck 1.44.5 (15-Dec-2018)
root : propre, 226885/16200000 fichiers, 2670701/16367360 blocs
# root@latitude: ~ < 2019_02_13__16_28_05 >
e2fsck -D -f /dev/mmcblk0p2
e2fsck 1.44.5 (15-Dec-2018)
Passe 1 : vérification des i-noeuds, des blocs et des tailles
Passe 2 : vérification de la structure des répertoires
Passe 3 : vérification de la connectivité des répertoires
Passe 3A : optimisation des répertoires
Passe 4 : vérification des compteurs de référence
Passe 5 : vérification de l'information du sommaire de groupe
différences de bitmap de blocs : +7864320 +7864336 +(7864352--7866376) +8388608 +8388624 +(8388640--8390664) +8912896 +8912912 +(8912928--8914952) +9437184 +9437200 +(9437216--9439240) +9961472 +9961488 +(9961504--9963528) +10485760 +10485776 +(10485792--10487816) +11010048 +11010064 +(11010080--11012104) +11534336 +11534352 +(11534368--11536392) +12058624 +12058640 +(12058656--12060680) +12582912 +12582928 +(12582944--12584968) +13107200 +13107216 +(13107232--13109256) +13631488 +13631504 +(13631520--13633544) +14155776 +14155792 +(14155808--14157832) +14680064 +14680080 +(14680096--14682120) +15204352 +15204368 +(15204384--15206408) +15728640 +15728656 +(15728672--15730696) +16252928 +(16252931--16252932) +(16252935--16254960) +(16259011--16261035)
Corriger<o>? oui
root: ***** LE SYSTÈME DE FICHIERS A ÉTÉ MODIFIÉ *****
root : 226885/16200000 fichiers (0.1% non contigus), 2670709/16367360 blocs
# root@latitude: ~ < 2019_02_13__16_28_05 >
e2fsck -D /dev/mmcblk0p2
e2fsck 1.44.5 (15-Dec-2018)
root : propre, 226885/16200000 fichiers, 2670709/16367360 blocs
/dev/mmcblk0p1 contient un système de fichiers vfat étiqueté « HypriotOS »
# root@latitude: ~ < 2019_02_13__16_28_05 >
fsck /dev/mmcblk0p1
fsck de util-linux 2.33.1
fsck.fat 4.1 (2017-01-24)
/dev/mmcblk0p1: 160 files, 18031/32695 clusters
# root@latitude: ~ < 2019_02_13__16_28_05 >
J'ai retenté un redémarrage, qui a fonctionné, j'ai pu me logger en ssh:
# pierre@latitude: ~ < 2019_02_13__16_56_54 >
ssh pirate@geopoppy.local
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ECDSA host key for geopoppy.local has changed,
and the key for the corresponding IP address 192.168.1.11
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:OsAavrPijDT+sdjeevs2SO1ZA9aujn+5ym+uZ1XBFy0.
Please contact your system administrator.
Add correct host key in /home/pierre/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/pierre/.ssh/known_hosts:32
remove with:
ssh-keygen -f "/home/pierre/.ssh/known_hosts" -R "geopoppy.local"
ECDSA host key for geopoppy.local has changed and you have requested strict checking.
Host key verification failed.
# pierre@latitude: ~ < 2019_02_13__16_56_54 >
ssh-keygen -f "/home/pierre/.ssh/known_hosts" -R "geopoppy.local"
# Host geopoppy.local found: line 32
/home/pierre/.ssh/known_hosts updated.
Original contents retained as /home/pierre/.ssh/known_hosts.old
# pierre@latitude: ~ < 2019_02_13__16_56_54 >
ssh pirate@geopoppy.local
The authenticity of host 'geopoppy.local (192.168.1.11)' can't be established.
ECDSA key fingerprint is SHA256:OsAavrPijDT+sdjeevs2SO1ZA9aujn+5ym+uZ1XBFy0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'geopoppy.local,192.168.1.11' (ECDSA) to the list of known hosts.
pirate@geopoppy.local's password:
Linux geopoppy 4.14.34-hypriotos-v7+ #1 SMP Sun Apr 22 14:57:31 UTC 2018 armv7l
HypriotOS (Debian GNU/Linux 9)
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Feb 13 07:42:28 2019 from 192.168.1.47
pirate@geopoppy:~$ sudo su
root@geopoppy:/home/pirate# journalctl -xe
Des morceaux choisis dans le log:
-- Logs begin at Wed 2019-02-13 14:58:51 UTC, end at Wed 2019-02-13 16:03:59 UTC. --
Feb 13 14:58:51 geopoppy kernel: Loading iSCSI transport class v2.0-870.
Feb 13 14:58:51 geopoppy kernel: libphy: Fixed MDIO Bus: probed
Feb 13 14:58:51 geopoppy kernel: usbcore: registered new interface driver lan78xx
Feb 13 14:58:51 geopoppy kernel: usbcore: registered new interface driver smsc95xx
Feb 13 14:58:51 geopoppy kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
=> vu qu'il est 17h, il doit y avoir un souci de fuseau horaire. Pagrave.
Feb 13 15:00:02 geopoppy avahi-daemon[348]: Successfully dropped remaining capabilities.
Feb 13 15:00:02 geopoppy avahi-daemon[379]: chroot.c: open() failed: No such file or directory
Feb 13 15:00:02 geopoppy avahi-daemon[348]: Failed to open /etc/resolv.conf: Invalid argument
Feb 13 15:00:02 geopoppy systemd[1]: Starting OpenBSD Secure Shell server...
Feb 13 15:00:38 geopoppy systemd[1]: hciuart.service: Control process exited, code=exited status=1
Feb 13 15:00:38 geopoppy systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
-- Subject: Unit hciuart.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit hciuart.service has failed.
--
-- The result is failed.
Feb 13 15:00:38 geopoppy systemd[1]: hciuart.service: Unit entered failed state.
Feb 13 15:00:38 geopoppy systemd[1]: hciuart.service: Failed with result 'exit-code'.
Feb 13 15:00:38 geopoppy ntp[369]: Starting NTP server: ntpd.
Feb 13 15:00:38 geopoppy systemd[1]: Started LSB: Start NTP daemon.
-- Subject: Unit ntp.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit ntp.service has finished starting up.
--
Feb 13 15:00:55 geopoppy ntpd[458]: Listen normally on 6 wlan0 172.24.1.1:123
Feb 13 15:00:55 geopoppy ntpd[458]: bind(26) AF_INET6 fe80::d23:6125:8bc4:c775%3#123 flags 0x11 failed: Cannot assign requested address
Feb 13 15:00:55 geopoppy ntpd[458]: unable to create socket on wlan0 (7) for fe80::d23:6125:8bc4:c775%3#123
-- The start-up result is done.
Feb 13 15:59:57 geopoppy dockerd[370]: time="2019-02-13T15:59:57.743226616Z" level=warning msg="Failed to allocate and map port 9000-9000: Timed out proxy starting the userland proxy"
Feb 13 16:00:06 geopoppy sshd[913]: pam_systemd(sshd:session): Failed to create session: Connection timed out
-- Unit user@1000.service has begun starting up.
Feb 13 15:59:57 geopoppy systemd-logind[346]: New session c1 of user pirate.
-- Subject: A new session c1 has been created for user pirate
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c1 has been created for the user pirate.
--
-- The leading process of the session is 913.
Feb 13 15:59:57 geopoppy systemd[1]: Started Session c1 of user pirate.
-- Subject: Unit session-c1.scope has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit session-c1.scope has finished starting up.
--
-- The start-up result is done.
Feb 13 15:59:57 geopoppy dockerd[370]: time="2019-02-13T15:59:57.743226616Z" level=warning msg="Failed to allocate and map port 9000-9000: Timed out proxy starting the userland proxy"
Feb 13 16:00:06 geopoppy sshd[913]: pam_systemd(sshd:session): Failed to create session: Connection timed out
Feb 13 16:00:30 geopoppy systemd[1432]: pam_unix(systemd-user:session): session opened for user pirate by (uid=0)
Feb 13 16:00:30 geopoppy dockerd[370]: time="2019-02-13T16:00:30Z" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/5b63254f379024b2f2cf21f58a18bdf2be28c085f5d
Feb 13 16:00:30 geopoppy dhcpcd[365]: vethc5352cb: carrier lost
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Interface vethc5352cb.IPv6 no longer relevant for mDNS.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Leaving mDNS multicast group on interface vethc5352cb.IPv6 with address fe80::e96:4095:e2f0:9005.
Feb 13 16:00:30 geopoppy kernel: br-0836112af545: port 1(veth78510cb) entered disabled state
Feb 13 16:00:30 geopoppy kernel: device veth78510cb left promiscuous mode
Feb 13 16:00:30 geopoppy kernel: br-0836112af545: port 1(veth78510cb) entered disabled state
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Interface vethc5352cb.IPv4 no longer relevant for mDNS.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Leaving mDNS multicast group on interface vethc5352cb.IPv4 with address 169.254.53.235.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Withdrawing address record for fe80::e96:4095:e2f0:9005 on vethc5352cb.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Withdrawing address record for 169.254.53.235 on vethc5352cb.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Interface veth78510cb.IPv6 no longer relevant for mDNS.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Leaving mDNS multicast group on interface veth78510cb.IPv6 with address fe80::e819:77ff:fe9e:873c.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Interface veth78510cb.IPv4 no longer relevant for mDNS.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Leaving mDNS multicast group on interface veth78510cb.IPv4 with address 169.254.70.203.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Withdrawing address record for fe80::e819:77ff:fe9e:873c on veth78510cb.
Feb 13 16:00:30 geopoppy avahi-daemon[348]: Withdrawing address record for 169.254.70.203 on veth78510cb.
Feb 13 16:00:30 geopoppy systemd[1432]: Out of memory.
Feb 13 16:00:30 geopoppy systemd[1432]: Out of memory.
Feb 13 16:00:30 geopoppy dhcpcd[365]: vethc5352cb: deleting address fe80::e96:4095:e2f0:9005
Feb 13 16:00:30 geopoppy dhcpcd[365]: vethc5352cb: deleting route to 169.254.0.0/16
Feb 13 16:00:30 geopoppy dhcpcd[365]: veth78510cb: arp if_readrawpacket: Network is down
Feb 13 16:00:30 geopoppy dhcpcd[365]: veth78510cb: dhcp if_readrawpacket: Network is down
Feb 13 16:00:34 geopoppy ntpd[458]: bind(30) AF_INET6 fe80::9244:6183:804:c81f%12#123 flags 0x11 failed: Cannot assign requested address
Feb 13 16:00:34 geopoppy ntpd[458]: unable to create socket on veth8ad24ad (25) for fe80::9244:6183:804:c81f%12#123
Feb 13 16:00:34 geopoppy ntpd[458]: failed to init interface for address fe80::9244:6183:804:c81f%12
Feb 13 16:00:34 geopoppy ntpd[458]: bind(30) AF_INET6 fe80::a4ab:50ff:fe77:1857%13#123 flags 0x11 failed: Cannot assign requested address
Feb 13 16:00:34 geopoppy ntpd[458]: unable to create socket on veth5bfe211 (26) for fe80::a4ab:50ff:fe77:1857%13#123
Feb 13 16:00:34 geopoppy ntpd[458]: failed to init interface for address fe80::a4ab:50ff:fe77:1857%13
Feb 13 16:02:20 geopoppy dhcpcd[365]: send_arp: No such device or address
Feb 13 16:02:20 geopoppy dhcpcd[365]: veth12ff03c: arp if_readrawpacket: Network is down
Feb 13 16:02:20 geopoppy dhcpcd[365]: veth12ff03c: dhcp if_readrawpacket: Network is down
Feb 13 16:03:41 geopoppy ntpd[458]: bind(35) AF_INET6 fe80::22d4:6a72:ac2e:46ab%14#123 flags 0x11 failed: Cannot assign requested address
Feb 13 16:03:41 geopoppy ntpd[458]: unable to create socket on veth1cf5cb2 (34) for fe80::22d4:6a72:ac2e:46ab%14#123
Feb 13 16:03:41 geopoppy ntpd[458]: failed to init interface for address fe80::22d4:6a72:ac2e:46ab%14
Feb 13 16:03:41 geopoppy ntpd[458]: bind(35) AF_INET6 fe80::c8e4:51ff:fe0f:66fd%15#123 flags 0x11 failed: Cannot assign requested address
Feb 13 16:03:41 geopoppy ntpd[458]: unable to create socket on veth5550083 (35) for fe80::c8e4:51ff:fe0f:66fd%15#123
Et pareil que tout à l'heure: le wifi GeoPoppy_Pi3 est visible, mais pas de page de lizmap.
Tout cela est peu convaincant...
Suite de l'aventure: j'ai préféré repartir sur une base saine vide: j'ai donc reflashé la carte SD.
Toujours le message de etcher comme quoi c'est une grosse carte (67.11G).
Avant de démarrer le Pi, j'ai vérifié les partitions, avec notamment le e2fsck -D:
# root@latitude: ~ < 2019_02_13__17_32_36 >
fdisk -l /dev/mmcblk0
Disque /dev/mmcblk0 : 62.5 GiB, 67108864000 octets, 131072000 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x65cdfe05
Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/mmcblk0p1 2048 133119 131072 64M c W95 FAT32 (LBA)
/dev/mmcblk0p2 133120 10239998 10106879 4.8G 83 Linux
# root@latitude: ~ < 2019_02_13__17_32_36 >
fsck /dev/mmcblk0p1
fsck de util-linux 2.33.1
fsck.fat 4.1 (2017-01-24)
/dev/mmcblk0p1: 160 files, 18031/32695 clusters
# root@latitude: ~ < 2019_02_13__17_32_36 >
fsck /dev/mmcblk0p2
fsck de util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
root : propre, 30881/1263600 fichiers, 662258/1263359 blocs
# root@latitude: ~ < 2019_02_13__17_32_36 >
e2fsck -D /dev/mmcblk0p2
e2fsck 1.44.5 (15-Dec-2018)
root : propre, 30881/1263600 fichiers, 662258/1263359 blocs
# root@latitude: ~ < 2019_02_13__17_32_36 >
e2fsck -D -f /dev/mmcblk0p2
e2fsck 1.44.5 (15-Dec-2018)
Passe 1 : vérification des i-noeuds, des blocs et des tailles
Passe 2 : vérification de la structure des répertoires
Passe 3 : vérification de la connectivité des répertoires
Passe 3A : optimisation des répertoires
Passe 4 : vérification des compteurs de référence
Passe 5 : vérification de l'information du sommaire de groupe
root: ***** LE SYSTÈME DE FICHIERS A ÉTÉ MODIFIÉ *****
root : 30881/1263600 fichiers (0.0% non contigus), 662259/1263359 blocs
# root@latitude: ~ < 2019_02_13__17_32_36 >
J'ai démarré le Pi avec cette SD toute fraîche. Il y a eu un bref message comme quoi "resized file system"? (pas eu le temps de bien noter)
Et puis ça a redémarré illico. Ça a mouliné un bon moment, ça disait "docker load --input qgis3server.tar.gz"
J'ai laissé mouliner un moment, puis le Pi était, comme d'habitude, accessible via ssh, avec le réseau wifi fonctionnel, mais toujours pas de lizmap.
En cherchant dans /var/log/messages, j'ai encore trouvé des erreurs, mais bien moins qu'auparavant:
...
root@geopoppy:/var/log# cat messages | grep -B 3 -A 1000 "Feb 13 "
Jan 24 09:43:45 geopoppy kernel: [ 266.410490] Netfilter messages via NETLINK v0.30.
Jan 24 09:43:45 geopoppy kernel: [ 266.415254] ctnetlink v0.93: registering with nfnetlink.
Jan 24 09:43:45 geopoppy kernel: [ 266.503327] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Feb 13 16:51:35 geopoppy kernel: [ 929.610479] EXT4-fs warning (device mmcblk0p2): ext4_dirent_csum_verify:353: inode #525277: comm systemd-tmpfile: No space for directory leaf checksum. Please run e2fsck -D.
Feb 13 16:51:35 geopoppy kernel: [ 929.623111] EXT4-fs warning (device mmcblk0p2): ext4_dirent_csum_verify:353: inode #525278: comm systemd-tmpfile: No space for directory leaf checksum. Please run e2fsck -D.
Feb 13 17:52:23 geopoppy kernel: [ 4578.245194] IPv6: ADDRCONF(NETDEV_UP): br-7b7f57422f5c: link is not ready
Feb 13 18:11:48 geopoppy kernel: [ 5743.265296] br-7b7f57422f5c: port 1(veth3724a1e) entered blocking state
Feb 13 18:11:48 geopoppy kernel: [ 5743.265313] br-7b7f57422f5c: port 1(veth3724a1e) entered disabled state
Feb 13 18:11:48 geopoppy kernel: [ 5743.266065] device veth3724a1e entered promiscuous mode
Feb 13 18:11:48 geopoppy kernel: [ 5743.267074] IPv6: ADDRCONF(NETDEV_UP): veth3724a1e: link is not ready
Feb 13 18:11:51 geopoppy kernel: [ 5746.259579] IPv6: ADDRCONF(NETDEV_UP): veth9294947: link is not ready
Feb 13 18:11:51 geopoppy kernel: [ 5746.259652] IPv6: ADDRCONF(NETDEV_CHANGE): veth9294947: link becomes ready
Feb 13 18:11:51 geopoppy kernel: [ 5746.259885] IPv6: ADDRCONF(NETDEV_CHANGE): veth3724a1e: link becomes ready
Feb 13 18:11:51 geopoppy kernel: [ 5746.260028] br-7b7f57422f5c: port 1(veth3724a1e) entered blocking state
Feb 13 18:11:51 geopoppy kernel: [ 5746.260037] br-7b7f57422f5c: port 1(veth3724a1e) entered forwarding state
Feb 13 18:11:51 geopoppy kernel: [ 5746.260283] IPv6: ADDRCONF(NETDEV_CHANGE): br-7b7f57422f5c: link becomes ready
Feb 13 18:12:01 geopoppy kernel: [ 5755.478868] br-7b7f57422f5c: port 1(veth3724a1e) entered disabled state
Feb 13 18:12:01 geopoppy kernel: [ 5755.482121] eth0: renamed from veth9294947
Feb 13 18:12:01 geopoppy kernel: [ 5755.528468] br-7b7f57422f5c: port 1(veth3724a1e) entered blocking state
Feb 13 18:12:01 geopoppy kernel: [ 5755.528482] br-7b7f57422f5c: port 1(veth3724a1e) entered forwarding state
Feb 13 18:12:01 geopoppy ec2:
Feb 13 18:12:01 geopoppy ec2: #############################################################
Feb 13 18:12:01 geopoppy ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Feb 13 18:12:01 geopoppy ec2: 1024 SHA256:zkJ7tTq2vofdhOomWNlum+v6NaRWIj3pc1GM3m0LCQk root@geopoppy (DSA)
Feb 13 18:12:01 geopoppy ec2: 256 SHA256:RaF5rStLk5PDABD0iFnMJ7G8LVhSENX5h7t/UkeEuBQ root@geopoppy (ECDSA)
Feb 13 18:12:02 geopoppy ec2: 256 SHA256:eWZ7K+F4aoT4DTDhJm0VH6uT4jKGYnCE7LsGufKSUg4 root@geopoppy (ED25519)
Feb 13 18:12:02 geopoppy ec2: 2048 SHA256:wSchWFzbyVPeoU1O/jrqrTqN4G0qhasxOsBE+zOLh1A root@geopoppy (RSA)
Feb 13 18:12:02 geopoppy ec2: -----END SSH HOST KEY FINGERPRINTS-----
Feb 13 18:12:02 geopoppy ec2: #############################################################
Feb 13 18:12:02 geopoppy kernel: [ 5756.643846] EXT4-fs warning (device mmcblk0p2): ext4_dirent_csum_verify:353: inode #525287: comm cloud-init: No space for directory leaf checksum. Please run e2fsck -D.
Feb 13 19:54:25 geopoppy kernel: [11899.967588] EXT4-fs warning (device mmcblk0p2): ext4_dirent_csum_verify:353: inode #525287: comm bash: No space for directory leaf checksum. Please run e2fsck -D.
root@geopoppy:/var/log#
Ah, j'ai trouvé un log qui pourrait être intéressant:
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log#
root@geopoppy:/var/log# cat cloud-init-output.log
Cloud-init v. 0.7.9 running 'init-local' at Thu, 24 Jan 2019 09:39:31 +0000. Up 12.44 seconds.
Cloud-init v. 0.7.9 running 'init' at Thu, 24 Jan 2019 09:39:45 +0000. Up 26.69 seconds.
ci-info: ++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++
ci-info: +--------+-------+------------+---------------+-------+-------------------+
ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
ci-info: +--------+-------+------------+---------------+-------+-------------------+
ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | . |
ci-info: | lo: | True | . | . | d | . |
ci-info: | wlan0: | True | 172.24.1.1 | 255.255.255.0 | . | b8:27:eb:d7:45:ef |
ci-info: | eth0: | False | . | . | . | b8:27:eb:82:10:ba |
ci-info: +--------+-------+------------+---------------+-------+-------------------+
ci-info: +++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++
ci-info: +-------+-------------+---------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+---------+---------------+-----------+-------+
ci-info: | 0 | 172.24.1.0 | 0.0.0.0 | 255.255.255.0 | wlan0 | U |
ci-info: +-------+-------------+---------+---------------+-----------+-------+
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:wSchWFzbyVPeoU1O/jrqrTqN4G0qhasxOsBE+zOLh1A root@geopoppy
The key's randomart image is:
+---[RSA 2048]----+
| +o.o . + |
| . . .o = + O . |
|. . = * o = |
| oE + . . |
|o.. .S .|
|o. + . o . |
|..o * + o o o |
| o.+ oo . = .o . |
| o... ..o.++.. |
+----[SHA256]-----+
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
SHA256:zkJ7tTq2vofdhOomWNlum+v6NaRWIj3pc1GM3m0LCQk root@geopoppy
The key's randomart image is:
+---[DSA 1024]----+
| E |
| . + |
| + o |
| . o + o |
| ooS *.+ o |
| .o*.B.o.o . |
| oo.O+=o . |
| . .+O*o.. |
| .@%B |
+----[SHA256]-----+
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
SHA256:RaF5rStLk5PDABD0iFnMJ7G8LVhSENX5h7t/UkeEuBQ root@geopoppy
The key's randomart image is:
+---[ECDSA 256]---+
|oBO+ . Eooo |
| *+=+ o+... |
|+ =oo. oo.o.. |
| + o .o oo .. |
|. o . .oS .. |
| . .o o... |
| .X... |
| ...*. |
| .oo |
+----[SHA256]-----+
Generating public/private ed25519 key pair.
Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
The key fingerprint is:
SHA256:eWZ7K+F4aoT4DTDhJm0VH6uT4jKGYnCE7LsGufKSUg4 root@geopoppy
The key's randomart image is:
+--[ED25519 256]--+
| ... |
|.. . .. o |
|...o o o |
|... B o . |
|.o.+.++.S + |
|Eoo...o..+.. |
|+O+ .. + o... |
|Oooo . + +. . |
|++. ..o .. |
+----[SHA256]-----+
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
Cloud-init v. 0.7.9 running 'modules:config' at Thu, 24 Jan 2019 09:43:22 +0000. Up 242.92 seconds.
Regenerating machine id
cd /src
+ cd /src
docker load --input portainer.tar.gz
+ docker load --input portainer.tar.gz
Loaded image: portainer/portainer:linux-arm
docker load --input postgres10-2.4-arm32_1.tar.gz
+ docker load --input postgres10-2.4-arm32_1.tar.gz
Loaded image: jancelin/geopoppy:postgres10-2.4-arm32_1
docker load --input qgis3server.tar.gz
+ docker load --input qgis3server.tar.gz
Loaded image: jancelin/geopoppy:qgis3server
docker load --input lizmap_rpi3_3.2rc6.tar.gz
+ docker load --input lizmap_rpi3_3.2rc6.tar.gz
Loaded image: jancelin/geopoppy:lizmap_rpi3_3.2rc6
docker load --input rpi-cloudcmd.tar.gz
+ docker load --input rpi-cloudcmd.tar.gz
invalid diffID for layer 10: expected "sha256:847356773aacd89603f9e8c7dfa06d7c228bf39deaddda6e4aeaf52c9b6070ab", got "sha256:0637aaae8a2c4076409bda423e7bca8d7535c2f0f397f8c9de93e5aaddefdaf5"
docker load --input redis4.tar.gz
+ docker load --input redis4.tar.gz
Loaded image: redis:4
docker load --input tracking_1_0.tar.gz
+ docker load --input tracking_1_0.tar.gz
Loaded image: jancelin/geopoppy:tracking_1_0
cd /home/pirate
+ cd /home/pirate
docker-compose up -d &&
#change docker-compose file
rm /home/pirate/docker-compose.yml
+ docker-compose up -d
Creating network "pirate_default" with the default driver
Pulling cloud (valentinalexeev/rpi-cloudcmd:)...
latest: Pulling from valentinalexeev/rpi-cloudcmd
Digest: sha256:b550f684458812bc7f306f571f11ff4c686d305be173ab32ad3126dce709b9f7
Status: Downloaded newer image for valentinalexeev/rpi-cloudcmd:latest
Creating pirate_redis_1 ...
Creating pirate_postgis_1 ...
Creating pirate_lizmap_1 ...
Creating pirate_tracking_1 ...
Creating pirate_map_1 ...
Creating pirate_cloud_1 ...
Creating pirate_portainer_1 ...
ERROR: for pirate_postgis_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for pirate_cloud_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Creating pirate_redis_1 ... done
ERROR: for pirate_portainer_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for pirate_tracking_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for pirate_map_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for map UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for tracking UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for postgis UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for portainer UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for lizmap UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for cloud UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
mv /home/pirate/docker-compose-arm32.yml /home/pirate/docker-compose.yml &&
# change owner root > pirate
chown pirate:pirate -R /home/pirate/geopoppy/qgis &&
chown pirate:pirate /home/pirate/docker-compose.yml &&
# systemctl checkdocker.sh
chmod +x /home/pirate/check_docker.sh &&
systemctl enable Cdocker.service &&
systemctl start Cdocker.service
+ mv /home/pirate/docker-compose-arm32.yml /home/pirate/docker-compose.yml
+ chown pirate:pirate -R /home/pirate/geopoppy/qgis
chown: cannot access '/home/pirate/geopoppy/qgis': No such file or directory
echo "Installation END"
+ echo 'Installation END'
Installation END
Cloud-init v. 0.7.9 running 'modules:final' at Thu, 24 Jan 2019 09:43:53 +0000. Up 274.55 seconds.
ci-info: no authorized ssh keys fingerprints found for user pirate.
Cloud-init v. 0.7.9 finished at Wed, 13 Feb 2019 18:12:02 +0000. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 5756.61 seconds
2019-02-13 18:12:02,169 - util.py[WARNING]: Failed to write boot finished file /var/lib/cloud/instance/boot-finished
root@geopoppy:/var/log#
Il y a quelques caractères imb!tables au milieu, qui ne fleurent pas très bon.
Et surtout il y a quelques ERRORs avec des timeout en allant chercher sur localhost sans port (?).
Il est question d'ajuster un COMPOSE_HTTP_TIMEOUT : certes, mais où donc?
Docteur? Est-ce grave?
Bonjour,
Quelle est l'image d'installation téléchargé ? La 0.2.3 ?
Quel Raspberry, quelle alimentation ?
Le Raspberry peut tourner pendant une trentaine de minutes avant de finaliser l'installation. Le signal wifi arrive vite, mais le reste met plus de temps, il faut le laisser tourner avec une alimentation adéquate.
Pour avoir lancé l'installation à plusieurs reprise sur un Raspberry Pi 3 B+ avec une carte de 16 Go et l'alimentation officielle, je n'ai pas rencontré de problème.
Est-il possible d'essayer de flasher une carte plus petite ? Cela me parait étrange que la carte 64Go ne passe pas, mais peu être que le flash ne ce passe pas comme il devrait du fait d'un trop grand espace libre..
Bonjour,
L'image d'installation téléchargée: GeoPoppy-0_2_3.img.zip
Raspberry Pi3 B, alimenté par un pijuice.
J'ai laissé tourner une nuit complète: que dalle.
Effectivement, vous avez eu le nez creux avec la carte plus petite: je viens de tout refaire, ce matin, avec une carte de 16Go, et ça vient de passer nickel, je vois le LizMap!
Joie.
Ce serait donc lié à la taille de la carte SD?
Je croyais que ce n'était pas la taille qui comptait (oh, pardon)...
Hmm, je ne comprend pas vraiment pourquoi Etcher aurait autant de mal à flasher la carte SD de 64.. Je ne saurais aider sur ce point.
Pas de problème avec des 32go... &Jamais testé avec des 64.
Je cherche.
Il est possible de brancher un écran sur le pi pour voir la progression de l'installation.
Je suis dans des conditions un peu moins spartiates que mes premiers essais pour faire un GeoPoppy: j'ai donc le luxe d'avoir un écran branché, un réseau câblé, une alimentation digne de ce nom, un clavier, et même une souris. Le Luxe.
Au moment où ça redémarrait sans fin, avec la carte SD 64 bites, j'avais filmé l'écran branché au Pi au ralenti; mais ça n'est guère lisible.