Et c’est toujours mieux de ne pas être tout seul dans la galère…
Est-ce que tu peux regarder tes fichiers log dans /var/log pour voir si le Pi a redémarré de lui-même avant que Jeedom ne se mette en rade si tu vois des lignes comme ceci ?
Nov 17 19:34:48 RPi4b-Jeedom kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
Ça c’est sûr 
De mon côté, rien d’anormal dans les logs (pas de redémarrage auto)
J’ai lu avec intérêt ton topic (très technique) qui expose ton problème, vraisemblablement lié à un soucis d’horloge.
Tu as pu avancer un peu ou c’est toujours pareil ?
Bonne nouvelle pour toi.
Oui et non. En remettant tout sur la carte SD à la place du SSD, je croyais être sorti d’affaire puisque le système a tenu 2 mois. Mais là, j’ai eu 3 plantages complets en quelques jours : il n’y a plus rien qui marche.
Je pense plus à un problème hardware, il faudrait que je teste une autre alim, un autre Pi et un autre hub USB. Je n’ai pas très envie de racheter encore du matériel inutilement.
Je suis en train d’essayer les idées de @naboleo. Je croise encore les doigts…
Une piste a ne pas négliger, l’alimentation du rpi qui est peut etre limite et, en fonction du nombre de periph USB , peut disjoncter !!! Prevoir une 3A .
Vous avez fait ça ?
Bon alors, j’ai une nouvelle piste qui semble matcher avec le soucis de @Domatizer !
En effet, j’ai retrouvé et analysé le syslog du jour/heure ou mon jeedom a planté et vous savez-quoi? c’est également à 6:17:05
La 17ème minute reviens donc pour moi aussi!
J’ai toute une série de « NUL » suivis de la ligne suivante:
jeedom fake-hwclock[116]: lundi 23 novembre 2020, 05:17:01 (UTC+0000)
J’essaye de copier le code en entier sur ce timing précis mais je ne suis pas sûr qu’il le prenne car c’est chelou:
Nov 23 06:24:01 jeedom CRON[29915]: (www-data) CMD (/usr/bin/php /var/www/html/core/php/jeeCron.php >> /dev/null)
Nov 23 06:17:05 jeedom fake-hwclock[116]: lundi 23 novembre 2020, 05:17:01 (UTC+0000)
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Linux version 5.4.51-v8+ (dom@buildbot) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Nov 23 06:17:05 jeedom systemd-fsck[130]: e2fsck 1.44.5 (15-Dec-2018)
Nov 23 06:17:05 jeedom kernel: [ 0.000000] efi: Getting EFI parameters from FDT:
Nov 23 06:17:05 jeedom kernel: [ 0.000000] efi: UEFI not found.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Reserved memory: created CMA memory pool at 0x000000001ec00000, size 256 MiB
Nov 23 06:17:05 jeedom kernel: [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Nov 23 06:17:05 jeedom kernel: [ 0.000000] On node 0 totalpages: 242688
Nov 23 06:17:05 jeedom kernel: [ 0.000000] DMA zone: 3792 pages used for memmap
Nov 23 06:17:05 jeedom systemd-fsck[130]: rootfs: clean, 91524/936448 files, 1225426/3843094 blocks
Nov 23 06:17:05 jeedom kernel: [ 0.000000] DMA zone: 0 pages reserved
Nov 23 06:17:05 jeedom kernel: [ 0.000000] DMA zone: 242688 pages, LIFO batch:63
Nov 23 06:17:05 jeedom kernel: [ 0.000000] percpu: Embedded 31 pages/cpu s89240 r8192 d29544 u126976
Nov 23 06:17:05 jeedom kernel: [ 0.000000] pcpu-alloc: s89240 r8192 d29544 u126976 alloc=31*4096
Nov 23 06:17:05 jeedom kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Nov 23 06:17:05 jeedom systemd[1]: Started File System Check on Root Device.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Detected VIPT I-cache on CPU0
Nov 23 06:17:05 jeedom kernel: [ 0.000000] CPU features: detected: ARM erratum 845719
Nov 23 06:17:05 jeedom kernel: [ 0.000000] CPU features: detected: ARM erratum 843419
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 238896
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=Composite-1:720x480@60,margin_left=32,margin_right=32,margin_top=32,margin_bottom=32 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=fafcf77d-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Nov 23 06:17:05 jeedom systemd[1]: Starting Remount Root and Kernel File Systems...
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Memory: 671772K/970752K available (9532K kernel code, 1104K rwdata, 3352K rodata, 1088K init, 1201K bss, 36836K reserved, 262144K cma-reserved)
Nov 23 06:17:05 jeedom kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Nov 23 06:17:05 jeedom kernel: [ 0.000000] ftrace: allocating 31763 entries in 125 pages
Nov 23 06:17:05 jeedom systemd[1]: Started Set the console keyboard layout.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] rcu: Preemptible hierarchical RCU implementation.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] Tasks RCU enabled.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Nov 23 06:17:05 jeedom systemd[1]: Started udev Coldplug all Devices.
Nov 23 06:17:05 jeedom kernel: [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Nov 23 06:17:05 jeedom kernel: [ 0.000000] random: get_random_bytes called from start_kernel+0x32c/0x4c4 with crng_init=0
Nov 23 06:17:05 jeedom kernel: [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Nov 23 06:17:05 jeedom kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Nov 23 06:17:05 jeedom systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Nov 23 06:17:05 jeedom kernel: [ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Nov 23 06:17:05 jeedom kernel: [ 0.000274] Console: colour dummy device 80x25
Nov 23 06:17:05 jeedom kernel: [ 0.001036] printk: console [tty1] enabled
Nov 23 06:17:05 jeedom kernel: [ 0.001108] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
Nov 23 06:17:05 jeedom kernel: [ 0.001164] pid_max: default: 32768 minimum: 301
Nov 23 06:17:05 jeedom kernel: [ 0.001619] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 0.001682] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Nov 23 06:17:05 jeedom systemd[1]: Started Helper to synchronize boot up for ifupdown.
Nov 23 06:17:05 jeedom kernel: [ 0.003127] Disabling memory control group subsystem
Nov 23 06:17:05 jeedom kernel: [ 0.028116] ASID allocator initialised with 32768 entries
Nov 23 06:17:05 jeedom kernel: [ 0.036104] rcu: Hierarchical SRCU implementation.
Nov 23 06:17:05 jeedom kernel: [ 0.044527] EFI services will not be available.
Nov 23 06:17:05 jeedom kernel: [ 0.052182] smp: Bringing up secondary CPUs ...
Nov 23 06:17:05 jeedom systemd[1]: Started Remount Root and Kernel File Systems.
Nov 23 06:17:05 jeedom kernel: [ 0.084457] Detected VIPT I-cache on CPU1
Nov 23 06:17:05 jeedom kernel: [ 0.084527] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Nov 23 06:17:05 jeedom kernel: [ 0.116565] Detected VIPT I-cache on CPU2
Nov 23 06:17:05 jeedom kernel: [ 0.116614] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Nov 23 06:17:05 jeedom kernel: [ 0.148744] Detected VIPT I-cache on CPU3
Nov 23 06:17:05 jeedom systemd[1]: Starting Load/Save Random Seed...
Nov 23 06:17:05 jeedom kernel: [ 0.148789] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Nov 23 06:17:05 jeedom systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Nov 23 06:17:05 jeedom kernel: [ 0.148992] smp: Brought up 1 node, 4 CPUs
Nov 23 06:17:05 jeedom kernel: [ 0.149146] SMP: Total of 4 processors activated.
Nov 23 06:17:05 jeedom kernel: [ 0.149181] CPU features: detected: 32-bit EL0 Support
Nov 23 06:17:05 jeedom kernel: [ 0.149216] CPU features: detected: CRC32 instructions
Nov 23 06:17:05 jeedom kernel: [ 0.175862] CPU: All CPU(s) started at EL2
Nov 23 06:17:05 jeedom systemd[1]: Starting Create System Users...
Nov 23 06:17:05 jeedom kernel: [ 0.175967] alternatives: patching kernel code
Nov 23 06:17:05 jeedom kernel: [ 0.177956] devtmpfs: initialized
Nov 23 06:17:05 jeedom kernel: [ 0.195795] Enabled cp15_barrier support
Nov 23 06:17:05 jeedom kernel: [ 0.195863] Enabled setend support
Nov 23 06:17:05 jeedom kernel: [ 0.196458] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Nov 23 06:17:05 jeedom systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 23 06:17:05 jeedom kernel: [ 0.196525] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 0.209766] pinctrl core: initialized pinctrl subsystem
Nov 23 06:17:05 jeedom kernel: [ 0.210854] DMI not present or invalid.
Nov 23 06:17:05 jeedom kernel: [ 0.211355] NET: Registered protocol family 16
Nov 23 06:17:05 jeedom kernel: [ 0.228171] DMA: preallocated 1024 KiB pool for atomic allocations
Nov 23 06:17:05 jeedom kernel: [ 0.229176] cpuidle: using governor menu
Nov 23 06:17:05 jeedom systemd[1]: Started Load/Save Random Seed.
Nov 23 06:17:05 jeedom kernel: [ 0.229819] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Nov 23 06:17:05 jeedom kernel: [ 0.230199] Serial: AMBA PL011 UART driver
Nov 23 06:17:05 jeedom kernel: [ 0.234035] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Nov 23 06:17:05 jeedom kernel: [ 0.253048] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-08-19 17:40, variant start
Nov 23 06:17:05 jeedom kernel: [ 0.257061] raspberrypi-firmware soc:firmware: Firmware hash is e90cba19a98a0d1f2ef086b9cafcbca00778f094
Nov 23 06:17:05 jeedom systemd[1]: Started Create System Users.
Nov 23 06:17:05 jeedom kernel: [ 0.305158] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Nov 23 06:17:05 jeedom kernel: [ 0.309243] vgaarb: loaded
Nov 23 06:17:05 jeedom kernel: [ 0.309911] SCSI subsystem initialized
Nov 23 06:17:05 jeedom kernel: [ 0.310233] usbcore: registered new interface driver usbfs
Nov 23 06:17:05 jeedom kernel: [ 0.310341] usbcore: registered new interface driver hub
Nov 23 06:17:05 jeedom systemd[1]: Starting Create Static Device Nodes in /dev...
Nov 23 06:17:05 jeedom kernel: [ 0.310518] usbcore: registered new device driver usb
Nov 23 06:17:05 jeedom kernel: [ 0.312543] clocksource: Switched to clocksource arch_sys_counter
Nov 23 06:17:05 jeedom kernel: [ 1.369160] VFS: Disk quotas dquot_6.6.0
Nov 23 06:17:05 jeedom kernel: [ 1.369310] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 23 06:17:05 jeedom systemd[1]: Started Flush Journal to Persistent Storage.
Nov 23 06:17:05 jeedom kernel: [ 1.369557] FS-Cache: Loaded
Nov 23 06:17:05 jeedom kernel: [ 1.369841] CacheFiles: Loaded
Nov 23 06:17:05 jeedom kernel: [ 1.370961] simple-framebuffer 3eaf0000.framebuffer: framebuffer at 0x3eaf0000, 0x10a800 bytes, mapped to 0x(____ptrval____)
Nov 23 06:17:05 jeedom kernel: [ 1.371019] simple-framebuffer 3eaf0000.framebuffer: format=a8r8g8b8, mode=656x416x32, linelength=2624
Nov 23 06:17:05 jeedom systemd-tmpfiles[146]: [/usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf:1] Line references path below legacy directory /var/run/, updating /var/run/fail2ban → /run/fail2ban; please update the tmpfiles.d/ drop-in file accordingly.
Nov 23 06:17:05 jeedom kernel: [ 1.376210] Console: switching to colour frame buffer device 82x26
Nov 23 06:17:05 jeedom kernel: [ 1.380662] simple-framebuffer 3eaf0000.framebuffer: fb0: simplefb registered!
Nov 23 06:17:05 jeedom kernel: [ 1.395214] thermal_sys: Registered thermal governor 'step_wise'
Nov 23 06:17:05 jeedom kernel: [ 1.395676] NET: Registered protocol family 2
Nov 23 06:17:05 jeedom kernel: [ 1.402159] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
Nov 23 06:17:05 jeedom systemd[1]: Started Create Static Device Nodes in /dev.
Nov 23 06:17:05 jeedom kernel: [ 1.407499] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 1.413074] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 1.416156] TCP: Hash tables configured (established 8192 bind 8192)
Nov 23 06:17:05 jeedom kernel: [ 1.419448] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 1.422614] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Nov 23 06:17:05 jeedom kernel: [ 1.426105] NET: Registered protocol family 1
Nov 23 06:17:05 jeedom systemd[1]: Reached target Local File Systems (Pre).
Nov 23 06:17:05 jeedom kernel: [ 1.430288] RPC: Registered named UNIX socket transport module.
Nov 23 06:17:05 jeedom kernel: [ 1.433422] RPC: Registered udp transport module.
Nov 23 06:17:05 jeedom kernel: [ 1.436415] RPC: Registered tcp transport module.
Nov 23 06:17:05 jeedom kernel: [ 1.439407] RPC: Registered tcp NFSv4.1 backchannel transport module.
Nov 23 06:17:05 jeedom systemd[1]: tmp-jeedom.mount: Directory /tmp/jeedom to mount over is not empty, mounting anyway.
Nov 23 06:17:05 jeedom kernel: [ 1.442395] PCI: CLS 0 bytes, default 64
Nov 23 06:17:05 jeedom kernel: [ 1.447460] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
Nov 23 06:17:05 jeedom kernel: [ 1.453399] kvm [1]: IPA Size Limit: 40bits
Nov 23 06:17:05 jeedom kernel: [ 1.457279] kvm [1]: Hyp mode initialized successfully
Nov 23 06:17:05 jeedom kernel: [ 1.464819] Initialise system trusted keyrings
Nov 23 06:17:05 jeedom systemd[1]: Mounting /tmp/jeedom...
Nov 23 06:17:05 jeedom kernel: [ 1.467898] workingset: timestamp_bits=46 max_order=18 bucket_order=0
Nov 23 06:17:05 jeedom kernel: [ 1.485142] FS-Cache: Netfs 'nfs' registered for caching
Nov 23 06:17:05 jeedom kernel: [ 1.488936] NFS: Registering the id_resolver key type
Nov 23 06:17:05 jeedom kernel: [ 1.491594] Key type id_resolver registered
Nov 23 06:17:05 jeedom kernel: [ 1.494152] Key type id_legacy registered
Nov 23 06:17:05 jeedom systemd[1]: Starting udev Kernel Device Manager...
Nov 23 06:17:05 jeedom systemd[1]: Mounted /tmp/jeedom.
Nov 23 06:17:05 jeedom systemd[1]: Started udev Kernel Device Manager.
Nov 23 06:17:05 jeedom systemd[1]: Found device /dev/serial1.
Nov 23 06:17:05 jeedom mtp-probe: checking bus 1, device 6: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Nov 23 06:17:05 jeedom mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Nov 23 06:17:05 jeedom mtp-probe: bus: 1, device: 6 was not an MTP device
Nov 23 06:17:05 jeedom mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3"
Nov 23 06:17:05 jeedom mtp-probe: bus: 1, device: 4 was not an MTP device
Nov 23 06:17:05 jeedom mtp-probe: bus: 1, device: 5 was not an MTP device
Nov 23 06:17:05 jeedom systemd-udevd[158]: Using default interface naming scheme 'v240'.
Nov 23 06:17:05 jeedom systemd[1]: Found device TS16GMSA370 boot.
Nov 23 06:17:05 jeedom systemd-udevd[155]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
Nov 23 06:17:05 jeedom systemd-udevd[154]: Using default interface naming scheme 'v240'.
Nov 23 06:17:05 jeedom systemd-udevd[156]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
Nov 23 06:17:05 jeedom kernel: [ 1.496604] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Nov 23 06:17:05 jeedom kernel: [ 1.500821] Key type asymmetric registered
Nov 23 06:17:05 jeedom systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Nov 23 06:17:05 jeedom kernel: [ 1.503204] Asymmetric key parser 'x509' registered
Nov 23 06:17:05 jeedom kernel: [ 1.505652] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
Nov 23 06:17:05 jeedom kernel: [ 1.510864] io scheduler mq-deadline registered
Nov 23 06:17:05 jeedom kernel: [ 1.513280] io scheduler kyber registered
Nov 23 06:17:05 jeedom kernel: [ 1.526933] bcm2835-rng 3f104000.rng: hwrng registered
Nov 23 06:17:05 jeedom kernel: [ 1.530315] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Nov 23 06:17:05 jeedom systemd[1]: Condition check resulted in Huge Pages File System being skipped.
Nov 23 06:17:05 jeedom kernel: [ 1.536426] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Nov 23 06:17:05 jeedom kernel: [ 1.541977] cacheinfo: Unable to detect cache hierarchy for CPU 0
Nov 23 06:17:05 jeedom kernel: [ 1.560304] brd: module loaded
Nov 23 06:17:05 jeedom kernel: [ 1.580477] loop: module loaded
Nov 23 06:17:05 jeedom systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Nov 23 06:17:05 jeedom kernel: [ 1.584899] Loading iSCSI transport class v2.0-870.
Nov 23 06:17:05 jeedom kernel: [ 1.590289] libphy: Fixed MDIO Bus: probed
Nov 23 06:17:05 jeedom kernel: [ 1.593366] usbcore: registered new interface driver r8152
Nov 23 06:17:05 jeedom kernel: [ 1.596019] usbcore: registered new interface driver lan78xx
Nov 23 06:17:05 jeedom systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Nov 23 06:17:05 jeedom kernel: [ 1.598602] usbcore: registered new interface driver smsc95xx
Nov 23 06:17:05 jeedom kernel: [ 1.601679] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Nov 23 06:17:05 jeedom kernel: [ 2.344826] Core Release: 2.80a
Nov 23 06:17:05 jeedom kernel: [ 2.347197] Setting default values for core params
Nov 23 06:17:05 jeedom kernel: [ 2.349655] Finished setting default values for core params
Nov 23 06:17:05 jeedom systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Nov 23 06:17:05 jeedom kernel: [ 2.565542] Using Buffer DMA mode
Nov 23 06:17:05 jeedom kernel: [ 2.567823] Periodic Transfer Interrupt Enhancement - disabled
Nov 23 06:17:05 jeedom kernel: [ 2.570210] Multiprocessor Interrupt Enhancement - disabled
Nov 23 06:17:05 jeedom kernel: [ 2.572651] OTG VER PARAM: 0, OTG VER FLAG: 0
Nov 23 06:17:05 jeedom kernel: [ 2.575042] Dedicated Tx FIFOs mode
Nov 23 06:17:05 jeedom kernel: [ 2.578907] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = ffffffc011074000 dma = 0x00000000ded00000 len=9024
Nov 23 06:17:05 jeedom kernel: [ 2.583582] FIQ FSM acceleration enabled for :
Nov 23 06:17:05 jeedom systemd[1]: Starting File System Check on /dev/disk/by-partuuid/fafcf77d-01...
Nov 23 06:17:05 jeedom kernel: [ 2.583582] Non-periodic Split Transactions
Nov 23 06:17:05 jeedom kernel: [ 2.583582] Periodic Split Transactions
Nov 23 06:17:05 jeedom kernel: [ 2.583582] High-Speed Isochronous Endpoints
Nov 23 06:17:05 jeedom kernel: [ 2.583582] Interrupt/Control Split Transaction hack enabled
Nov 23 06:17:05 jeedom kernel: [ 2.594325] dwc_otg: Microframe scheduler enabled
Nov 23 06:17:05 jeedom systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 23 06:17:05 jeedom kernel: [ 2.594371] WARN::hcd_init_fiq:497: MPHI regs_base at ffffffc010055000
Nov 23 06:17:05 jeedom kernel: [ 2.596707] dwc_otg 3f980000.usb: DWC OTG Controller
Nov 23 06:17:05 jeedom kernel: [ 2.598962] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Nov 23 06:17:05 jeedom kernel: [ 2.601392] dwc_otg 3f980000.usb: irq 9, io mem 0x00000000
Nov 23 06:17:05 jeedom kernel: [ 2.603818] Init: Port Power? op_state=1
Nov 23 06:17:05 jeedom systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 23 06:17:05 jeedom systemd-fsck[286]: fsck.fat 4.1 (2017-01-24)
Nov 23 06:17:05 jeedom kernel: [ 2.606184] Init: Power Port (0)
Nov 23 06:17:05 jeedom kernel: [ 2.608913] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
Nov 23 06:17:05 jeedom kernel: [ 2.613659] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 23 06:17:05 jeedom kernel: [ 2.616197] usb usb1: Product: DWC OTG Controller
Nov 23 06:17:05 jeedom kernel: [ 2.618706] usb usb1: Manufacturer: Linux 5.4.51-v8+ dwc_otg_hcd
Nov 23 06:17:05 jeedom kernel: [ 2.621241] usb usb1: SerialNumber: 3f980000.usb
Nov 23 06:17:05 jeedom kernel: [ 2.624564] hub 1-0:1.0: USB hub found
Nov 23 06:17:05 jeedom systemd-fsck[286]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Nov 23 06:17:05 jeedom kernel: [ 2.627064] hub 1-0:1.0: 1 port detected
Nov 23 06:17:05 jeedom kernel: [ 2.630379] dwc_otg: FIQ enabled
Nov 23 06:17:05 jeedom kernel: [ 2.630392] dwc_otg: NAK holdoff enabled
Nov 23 06:17:05 jeedom kernel: [ 2.630404] dwc_otg: FIQ split-transaction FSM enabled
Nov 23 06:17:05 jeedom kernel: [ 2.630422] Module dwc_common_port init
Nov 23 06:17:05 jeedom kernel: [ 2.631134] usbcore: registered new interface driver uas
Nov 23 06:17:05 jeedom systemd-fsck[286]: Automatically removing dirty bit.
Nov 23 06:17:05 jeedom kernel: [ 2.633593] usbcore: registered new interface driver usb-storage
Nov 23 06:17:05 jeedom kernel: [ 2.636117] mousedev: PS/2 mouse device common for all mice
Nov 23 06:17:05 jeedom kernel: [ 2.640800] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Nov 23 06:17:05 jeedom kernel: [ 2.645440] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 600000 KHz
Nov 23 06:17:05 jeedom kernel: [ 2.649838] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 700000 KHz
Nov 23 06:17:05 jeedom systemd-fsck[286]: Performing changes.
Nov 23 06:17:05 jeedom kernel: [ 2.654870] sdhci: Secure Digital Host Controller Interface driver
Nov 23 06:17:05 jeedom kernel: [ 2.657024] sdhci: Copyright(c) Pierre Ossman
Nov 23 06:17:05 jeedom kernel: [ 2.659751] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Nov 23 06:17:05 jeedom kernel: [ 2.662616] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Nov 23 06:17:05 jeedom kernel: [ 2.665114] sdhci-pltfm: SDHCI platform and OF driver helper
Nov 23 06:17:05 jeedom systemd-fsck[286]: /dev/sda1: 246 files, 109211/516190 clusters
Nov 23 06:17:05 jeedom kernel: [ 2.670273] ledtrig-cpu: registered to indicate activity on CPUs
Nov 23 06:17:05 jeedom kernel: [ 2.672933] hidraw: raw HID events driver (C) Jiri Kosina
Nov 23 06:17:05 jeedom kernel: [ 2.675274] usbcore: registered new interface driver usbhid
Nov 23 06:17:05 jeedom kernel: [ 2.677415] usbhid: USB HID core driver
Nov 23 06:17:05 jeedom kernel: [ 2.680693] vchiq: vchiq_init_state: slot_zero = (____ptrval____)
Nov 23 06:17:05 jeedom kernel: [ 2.687134] Initializing XFRM netlink socket
Nov 23 06:17:05 jeedom kernel: [ 2.689348] NET: Registered protocol family 17
Nov 23 06:17:05 jeedom systemd[1]: Started File System Check on /dev/disk/by-partuuid/fafcf77d-01.
Nov 23 06:17:05 jeedom kernel: [ 2.691621] Key type dns_resolver registered
Nov 23 06:17:05 jeedom kernel: [ 2.694558] registered taskstats version 1
Nov 23 06:17:05 jeedom kernel: [ 2.696722] Loading compiled-in X.509 certificates
Nov 23 06:17:05 jeedom kernel: [ 2.699258] Key type ._fscrypt registered
Nov 23 06:17:05 jeedom kernel: [ 2.701432] Key type .fscrypt registered
Nov 23 06:17:05 jeedom kernel: [ 2.717721] uart-pl011 3f201000.serial: cts_event_workaround enabled
Nov 23 06:17:05 jeedom kernel: [ 2.719980] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 66, base_baud = 0) is a PL011 rev2
Nov 23 06:17:05 jeedom kernel: [ 2.726455] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Nov 23 06:17:05 jeedom kernel: [ 2.730435] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Nov 23 06:17:05 jeedom kernel: [ 2.732697] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Nov 23 06:17:05 jeedom kernel: [ 2.761121] sdhost: log_buf @ (____ptrval____) (f926e000)
Nov 23 06:17:05 jeedom systemd[1]: Mounting /boot...
Nov 23 06:17:05 jeedom kernel: [ 2.782957] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Nov 23 06:17:05 jeedom kernel: [ 2.786716] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Nov 23 06:17:05 jeedom kernel: [ 2.790422] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Nov 23 06:17:05 jeedom kernel: [ 2.795328] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Nov 23 06:17:05 jeedom kernel: [ 2.816590] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Nov 23 06:17:05 jeedom systemd[1]: Mounted /boot.
Nov 23 06:17:05 jeedom kernel: [ 2.822083] of_cfs_init
Nov 23 06:17:05 jeedom kernel: [ 2.824036] of_cfs_init: OK
Nov 23 06:17:05 jeedom kernel: [ 2.840262] Indeed it is in host mode hprt0 = 00021501
Nov 23 06:17:05 jeedom kernel: [ 2.840641] Waiting for root device PARTUUID=fafcf77d-02...
Nov 23 06:17:05 jeedom kernel: [ 2.877613] random: fast init done
Nov 23 06:17:05 jeedom kernel: [ 2.916755] mmc1: new high speed SDIO card at address 0001
Nov 23 06:17:05 jeedom kernel: [ 3.085736] usb 1-1: new high-speed USB device number 2 using dwc_otg
Nov 23 06:17:05 jeedom systemd[1]: Reached target Local File Systems.
Nov 23 06:17:05 jeedom kernel: [ 3.087802] Indeed it is in host mode hprt0 = 00001101
Nov 23 06:17:05 jeedom kernel: [ 3.317003] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Nov 23 06:17:05 jeedom kernel: [ 3.320842] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 23 06:17:05 jeedom kernel: [ 3.323628] hub 1-1:1.0: USB hub found
Nov 23 06:17:05 jeedom kernel: [ 3.325693] hub 1-1:1.0: 4 ports detected
Nov 23 06:17:05 jeedom systemd[1]: Starting Create Volatile Files and Directories...
Nov 23 06:17:05 jeedom kernel: [ 3.616617] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Nov 23 06:17:05 jeedom systemd[1]: Starting Set console font and keymap...
Nov 23 06:17:05 jeedom kernel: [ 3.716984] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Nov 23 06:17:05 jeedom kernel: [ 3.720738] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 23 06:17:05 jeedom kernel: [ 3.723468] hub 1-1.1:1.0: USB hub found
Nov 23 06:17:05 jeedom kernel: [ 3.725760] hub 1-1.1:1.0: 3 ports detected
Nov 23 06:17:05 jeedom kernel: [ 4.016579] usb 1-1.1.3: new full-speed USB device number 4 using dwc_otg
Nov 23 06:17:05 jeedom systemd[1]: Starting Raise network interfaces...
Nov 23 06:17:05 jeedom kernel: [ 4.140250] usb 1-1.1.3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Nov 23 06:17:05 jeedom kernel: [ 4.144750] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 23 06:17:05 jeedom kernel: [ 4.149500] usb 1-1.1.3: Product: RFXtrx433
Nov 23 06:17:05 jeedom kernel: [ 4.151898] usb 1-1.1.3: Manufacturer: RFXCOM
Nov 23 06:17:05 jeedom systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Et voici la copie de la partie des NUL…on voit bien que l’heure n’est pas cohérente dans le log.
Pour ma part, la recherche avec « error » me donne ceci:
Nov 23 06:17:11 jeedom ntpd[604]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Nov 23 06:17:11 jeedom ntpd[604]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Nov 23 06:17:06 jeedom raspi-config[351]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
Nov 23 06:17:05 jeedom kernel: [ 9.959045] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
Nov 23 08:53:41 jeedom systemd[1509]: gpgconf: fatal error (exit status 1)
La recherche avec « critical » ne donne rien
La recherche avec « fatal » donne:
Nov 23 08:53:41 jeedom systemd[1509]: gpgconf: fatal error (exit status 1)
Et la recherche avec « Undervoltage » ne donne rien
Ah bah génial ! Tu as tous les symptômes que j’avais décrit dans mes différent posts Plantage total RPi4b - Serveur de temps NTP
fake-hwclock (que j’ai viré)/00/ lors du copier/coller)Cela prouve qu’il y a un réel problème.
Si si, ton Pi avait bien redémarré à 06:17:05
Bonjour @lone
J’ai fais
pi@jeedom:~ $ egrep -i "error|critical|fatal|undervoltage" /var/log/syslog
Nov 25 02:17:06 jeedom kernel: [ 9.634765] brcmfmac mmc1:0001:1: Direct firmw are load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
Nov 25 02:17:07 jeedom raspi-config[307]: Checking if shift key is held down:Err or opening '/dev/input/event*': No such file or directory
Nov 25 02:17:07 jeedom lightdm[456]: Error getting user list from org.freedeskto p.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org. freedesktop.Accounts was not provided by any .service files
Nov 25 02:17:07 jeedom ntpd[487]: kernel reports TIME_ERROR: 0x41: Clock Unsynch ronized
Nov 25 02:17:07 jeedom ntpd[487]: kernel reports TIME_ERROR: 0x41: Clock Unsynch ronized
Nov 25 02:17:08 jeedom ntpd[487]: error resolving pool 0.debian.pool.ntp.org: Te mporary failure in name resolution (-3)
Nov 25 02:17:12 jeedom lightdm[649]: Error getting user list from org.freedeskto p.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org. freedesktop.Accounts was not provided by any .service files
Nov 25 02:17:13 jeedom /etc/mysql/debian-start[768]: Version check failed. Got t he following error when calling the 'mysql' command line client
Nov 25 02:17:13 jeedom /etc/mysql/debian-start[768]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Nov 25 02:17:13 jeedom /etc/mysql/debian-start[768]: FATAL ERROR: Upgrade failed
Nov 25 02:17:14 jeedom debian-start[755]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Binary file /var/log/syslog matches
pi@jeedom:~ $
Toujours les 17 ème minutes !
Ah bah voilà, toi aussi, finalement c’est à la minute 17 ! On est 3 !!! Cela devient intéressant. 
Maintenant, j’aurais bien envie de faire des stats avec tous ceux qui ont eu un plantage sans explication en leurs demandant d’aller vérifier l’heure du plantage.
On observe bien une mauvaise synchronisation de l’heure.
J’avais aussi viré le service ntpd (donc je n’ai plus ces lignes d’erreurs spécifiquement) et utilisé systemd-timesyncd à la place, ben ça plante quand même !
Ma compréhension du problème
Toutes les heures, à la minute 17, le cron exécute le fake-hwclock. Il y a un souci avec l’horloge qui se désynchronise pour je ne sais quelle raison. Au bout d’un moment, le fake-hwclock doit vérifier l’heure et dire STOP lorsque l’heure a trop dérivée. Et là redémarrage forcé, ça se passe mal et Jeedom n’arrive pas à se relancer correctement.
Si on débranche et rebranche l’alim, tout rentre dans l’ordre jusqu’à la prochaine fois. Depuis que j’ai supprimé le fake-hwclock, ça ne plante plus à la minute 17 définie dans le cron mais plutôt à n’importe quelle heure. De plus, sur tous mes autres Pi qui ne font pas tourner Jeedom, il y a bien le fake-hwclock qui se lance toutes les heures et je n’ai jamais eu souci de ce genre. Donc, le fake-hwclock ne soit pas être le problème. Il doit y avoir quelque chose derrière. Mais quoi ?
Bonjour @Domatizer,
J’ai également lu ton topic (très technique) qui expose ton problème, vraisemblablement lié à un soucis d’horloge.
Toi tu as un RPI 4B @Xboss06 et moi avons un RPI 3B+ mais le mème Pb !
Il faudrait savoir ce qu’en pense les spéciales de notre problème.
Pour compléter, j’ai 2 autres RPi3b et 1 autre Rpi zero W tous sans Jeedom, ils tournent 24/24h et je n’ai jamais eu ce genre de souci.
Oui absolument mais ce n’était pas le même jour.
Ma phrase concernait les 24 et 25 et mon plantage a eu lieu le 23.
Maintenant je balise d’autant que Jeedom gère notamment tous les réveils de la famille 
Apparemment vous avez bien un souci avec le service ntp (synchro de l’heure avec le web).
C’est hors de mes capacités, sorry.
Vu les remontées de Domotizer on dirait bien que c’est directement en rapport avec jeedom mais là il vous faut un spécialiste 
Perso je n’exclurait pas que ce soit du à un problème de connexion internet au moment de la synchro ntp, vous êtes en wifi ?
Non, Ethernet pour ma part…sur livebox 5 fibrée.
Il y a peu de chances que ce soit ça alors.
Vous avez essayé de repartir sur un raspbian neuf ?
Non connexion ethernet pour le PI et connexion fibre pour la box.
La connexion internet est monitorée. Je reçois un SMS lorsqu’il y a une coupure.
Le seul souci, c’est le redémarrage du Pi sans connexion internet.
Là, on a un truc qui force le redémarrage.
Trop de truc qui tourne dessus, on n’arrête pas la prod !
Une machine tout en un, c’est bien, c’est pratique. Mais quand, il faut réparer des trucs, c’est compliqué de ne pas arrêter ce qui marche.
https://blog.vincentdeniau.fr/articles/synchroniser-heure-raspberrypi-fiable
Ca vaut peut être le coup d’essayer…
Re-essayez de faire ça aussi , en parcourant le net j’ai vu que certains avaient eu ce problème, rapsi-config avait « oublié » la timezone
sudo raspi-configInternationalisation Options
I2 Change Timezone
Finish
Yes to reboot now