Problema sincronización hora

[sunbloquer]

Hola a todos, a ver si alguien me puede iluminar sobre el problema que tengo.

De toda la vida siempre que instalo rasbian (jessy, buster,xxxx) con una Rpi conectada a internet me coge la hora, ya despues entramos en raspi-config y cambiamos locale y utc a nuestro caso para que corrija el desfase horario, bien. Desde que me han puesto fibra en casa no sincroniza la hora en el arranque, si bien ya se que puedo setear la hora correcta, instalar ntp, etc..,etc…

Mi router es este:

Operador OXON3 (Yoigo)
Modelo: SERCOMMFG824CD
No estoy metido en CG-NAT
DNS: 212.230.135.1 - 212.230.135.2

Ya estuvo un informático del operador viendo la configuración del router y todo está correcto, de hecho a entrado por ssh y en remoto en mi pc para ver que lo que digo es cierto. El me dice que SI o SI debes instalar y configurar NTP para que sincronice la hora correctamente y yo le digo que no, nunca ha sido así, si hay internet en la Rpi, hay sincronización de hora.

En el caso de por ejemplo instalar Home Assistant el problema se agrava, ya que no coge la hora, no acepta certificados SSL por el problema de fecha y la instalación no finaliza.

He probado en 3 casas mas con 3 routers y con 3 operadoras:

Operador: JAZZTEL
Router: ARCADYAN
DNS: 87.216.1.65 - 87.216.1.66

Rasbian sincroniza la hora en el primer arranque y Home Assitant finaliza la instalación

Operador: TELEFONICA
Router: ASKEY HGU RTF3505VW
DNS: 80.58.61.250 - 80.58.61.254

Rasbian sincroniza la hora en el primer arranque y Home Assitant finaliza la instalación

Operador: MASMOVIL
Router: SERCOMMFG824CD
DNS: 212.230.135.1 - 212.230.135.2
En CG-NAT

FAIL- Ni sincroniza, ni acaba la instalación, como en mi operador.

Yo le digo que me estan bloqueando el puerto NTP de alguna forma o existe algún problema con los DNS que impide el correcto funcionamiento del sistema y el me dice que el problema es en mi casa.

Todas las conexiones son directas, Rpi directa al router sin ningún tipo de conexión LAN en el router, unicamente la Rpi.

No está instalado NTP

FreshInstall



pi@raspberrypi:~ $ timedatectl
Local time: Thu 2021-11-11 18:21:33 GMT
Universal time: Thu 2021-11-11 18:21:33 UTC
RTC time: n/a
Time zone: Europe/London (GMT, +0000)
System clock synchronized: no
NTP service: active
RTC in local TZ: no

Configuramos

pi@raspberrypi:~ $ sudo raspi-config
Generating locales (this might take a while)...
en_GB.UTF-8... done
es_ES.UTF-8... done
Generation complete.

Current default time zone: 'Europe/Madrid'
Local time is now: Thu Nov 11 19:24:05 CET 2021.
Universal Time is now: Thu Nov 11 18:24:05 UTC 2021.

Si por ejemplo quiero hacerle update al configurador:

pi@raspberrypi:~ $ sudo raspi-config
Get:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Get:2 http://archive.raspberrypi.org/debian bullseye InRelease [23.5 kB]
Reading package lists... Done
E: Release file for http://raspbian.raspberrypi.org/raspbia ... /InRelease is not valid yet (invalid for another 11h 17min 23s). Updates for this repository will not be applied.
E: Release file for http://archive.raspberrypi.org/debian/d ... /InRelease is not valid yet (invalid for another 15h 44min 31s). Updates for this repository will not be applied.

Esta es la máquina:

Código: Seleccionar todo

pi@raspberrypi:~ $ cat /proc/cpuinfo
processor       : 0
model name      : ARMv7 Processor rev 3 (v7l)
BogoMIPS        : 126.00
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

processor       : 1
model name      : ARMv7 Processor rev 3 (v7l)
BogoMIPS        : 126.00
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

processor       : 2
model name      : ARMv7 Processor rev 3 (v7l)
BogoMIPS        : 126.00
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

processor       : 3
model name      : ARMv7 Processor rev 3 (v7l)
BogoMIPS        : 126.00
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

Hardware        : BCM2711
Revision        : b03114
Serial          : 10000000e1448294
Model           : Raspberry Pi 4 Model B Rev 1.4

Si yo instalo NTP

Código: Seleccionar todo

pi@raspberrypi:~ $ service ntp status
● ntp.service - Network Time Service
     Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: e>
     Active: active (running) since Thu 2021-11-11 19:27:20 CET; 17h ago
       Docs: man:ntpd(8)
    Process: 2581 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, stat>
   Main PID: 2587 (ntpd)
      Tasks: 2 (limit: 3720)
        CPU: 86ms
     CGroup: /system.slice/ntp.service
             └─2587 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 109:114

Nov 11 19:27:27 raspberrypi ntpd[2587]: Soliciting pool server 2001:720:1014:a2>
Nov 11 19:27:27 raspberrypi ntpd[2587]: Soliciting pool server 144.76.43.40
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>
Nov 12 13:09:35 raspberrypi ntpd[2587]: receive: Unexpected origin timestamp 0x>

y si quiero ver el estado de sincronización de la hora



en raspi-config, establezco la opción

S6 Network at Boot Select wait for network connection on boot

Desinstalo NTP, sigo diciendo que no es necesario instalar este servicio para que coja la hora, de hecho en el video se muestra como con un ISP rechaza la conexión 123 y el otro Operador (telefónica) la acepta sin este servicio instalado.

Desenchufo la Rpi de corriente y vuelvo a iniciar

Código: Seleccionar todo

Nov 12 13:25:55 raspberrypi bthelper[652]: Changing power off succeeded
Nov 12 13:25:55 raspberrypi bthelper[652]: [#001#033[0;93m#002CHG#001#033[0m#002] Controller DC:A6:32:F5:F8:D3 Powered: no
Nov 12 13:25:55 raspberrypi bthelper[652]: [#001#033[0;93m#002CHG#001#033[0m#002] Controller DC:A6:32:F5:F8:D3 Discovering: no
Nov 12 13:25:55 raspberrypi bthelper[546]: Changing power on succeeded
Nov 12 13:26:00 raspberrypi dhcpcd[650]: eth0: no IPv6 Routers available
Nov 12 13:26:03 raspberrypi systemd-timesyncd[637]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Nov 12 13:26:12 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
Nov 12 13:26:20 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
Nov 12 13:26:45 raspberrypi systemd-timesyncd[637]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).

y ya no sincroniza la hora.

En el caso de Home Assistant sobre Rpi la ultima imágen disponible haos_rpi4-6.6.img.xz

Código: Seleccionar todo

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing...
[14:44:41] INFO: Using udev information from host
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:44:41] INFO: Starting local supervisor watchdog...
21-08-06 14:44:45 INFO (MainThread) [__main__] Initializing Supervisor setup
21-08-06 14:44:45 INFO (MainThread) [supervisor.docker.network] Can't find Supervisor network, creating a new network
21-08-06 14:44:47 INFO (MainThread) [supervisor.bootstrap] Initializing Supervisor Sentry
21-08-06 14:44:47 INFO (MainThread) [supervisor.bootstrap] Seting up coresys for machine: raspberrypi4
21-08-06 14:44:47 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attaching to Supervisor homeassistant/armv7-hassio-supervisor with version 2021.10.6
21-08-06 14:44:47 INFO (SyncWorker_0) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network
21-08-06 14:44:48 WARNING (SyncWorker_0) [supervisor.docker.interface] Can't find homeassistant/armv7-hassio-supervisor for cleanup
21-08-06 14:44:48 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.INITIALIZE
21-08-06 14:44:48 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-08-06 14:44:48 INFO (MainThread) [__main__] Setting up Supervisor
21-08-06 14:44:48 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
21-08-06 14:44:48 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
21-08-06 14:44:48 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface io.hass.os
21-08-06 14:44:48 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.systemd1
21-08-06 14:44:48 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.login1
21-08-06 14:44:48 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.hostname1
21-08-06 14:44:48 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.timedate1
21-08-06 14:44:49 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.NetworkManager
21-08-06 14:44:49 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface de.pengutronix.rauc
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.info] Updating local host information
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.services] Updating service information
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.network] Updating local network information
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.manager] Host information reload completed
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
21-08-06 14:44:49 INFO (MainThread) [supervisor.host.services] Reloading local service hassos-apparmor.service
21-08-06 16:44:49 INFO (SyncWorker_0) [supervisor.docker.interface] Found ghcr.io/home-assistant/armv7-hassio-cli versions: [<AwesomeVersion CalVer '2021.09.0'>]
21-08-06 16:44:49 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/armv7-hassio-cli with version 2021.09.0
21-08-06 16:44:49 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
21-08-06 16:44:52 INFO (SyncWorker_0) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/armv7-hassio-cli with version 2021.09.0 - 172.30.32.5
21-08-06 16:44:52 INFO (SyncWorker_0) [supervisor.docker.interface] Found ghcr.io/home-assistant/armv7-hassio-dns versions: [<AwesomeVersion CalVer '2021.06.0'>]
21-08-06 16:44:52 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/armv7-hassio-dns with version 2021.06.0
21-08-06 16:44:52 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
21-08-06 16:44:54 INFO (SyncWorker_0) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/armv7-hassio-dns with version 2021.06.0 - 172.30.32.3
21-08-06 16:44:54 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
21-08-06 16:44:54 INFO (SyncWorker_0) [supervisor.docker.interface] Found ghcr.io/home-assistant/armv7-hassio-audio versions: [<AwesomeVersion CalVer '2021.07.0'>]
21-08-06 16:44:54 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/armv7-hassio-audio with version 2021.07.0
21-08-06 16:44:54 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
21-08-06 16:44:56 INFO (SyncWorker_0) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/armv7-hassio-audio with version 2021.07.0 - 172.30.32.4
21-08-06 16:44:56 INFO (SyncWorker_0) [supervisor.docker.interface] Found ghcr.io/home-assistant/armv7-hassio-observer versions: [<AwesomeVersion CalVer '2021.10.0'>]
21-08-06 16:44:56 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/armv7-hassio-observer with version 2021.10.0
21-08-06 16:44:57 INFO (MainThread) [supervisor.plugins.observer] Starting observer plugin
21-08-06 16:44:59 INFO (SyncWorker_0) [supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/armv7-hassio-observer with version 2021.10.0 - 172.30.32.6
21-08-06 16:44:59 INFO (SyncWorker_1) [supervisor.docker.interface] Found ghcr.io/home-assistant/armv7-hassio-multicast versions: [<AwesomeVersion CalVer '2021.04.0'>]
21-08-06 16:44:59 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/armv7-hassio-multicast with version 2021.04.0
21-08-06 16:44:59 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
21-08-06 16:45:01 INFO (SyncWorker_0) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/armv7-hassio-multicast with version 2021.04.0 - Host
21-08-06 16:45:01 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-08-06 16:45:01 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 0 Home Assistant secrets
21-08-06 16:45:01 INFO (SyncWorker_1) [supervisor.docker.interface] No version found for ghcr.io/home-assistant/raspberrypi4-homeassistant
21-08-06 16:45:01 INFO (MainThread) [supervisor.homeassistant.core] No Home Assistant Docker image ghcr.io/home-assistant/raspberrypi4-homeassistant found.
21-08-06 16:45:01 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/raspberrypi4-homeassistant with version landingpage
21-08-06 16:45:01 INFO (MainThread) [supervisor.homeassistant.core] Using preinstalled landingpage
21-08-06 16:45:01 INFO (MainThread) [supervisor.homeassistant.core] Starting HomeAssistant landingpage
21-08-06 16:45:01 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
21-08-06 16:45:02 INFO (SyncWorker_0) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/raspberrypi4-homeassistant with version landingpage
21-08-06 16:45:02 INFO (MainThread) [supervisor.os.manager] Detect Home Assistant Operating System 6.6 / BootSlot A
21-08-06 16:45:02 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/hassio-addons/repository repository
21-08-06 16:45:02 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/home-assistant/addons repository
21-08-06 16:45:06 INFO (MainThread) [supervisor.store] Loading add-ons from store: 62 all - 62 new - 0 remove
21-08-06 16:45:06 INFO (MainThread) [supervisor.addons] Found 0 installed add-ons
21-08-06 16:45:06 INFO (MainThread) [supervisor.backups.manager] Found 0 backup files
21-08-06 16:45:06 INFO (MainThread) [supervisor.discovery] Loaded 0 messages
21-08-06 16:45:06 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-08-06 16:45:06 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-08-06 16:45:06 INFO (MainThread) [__main__] Running Supervisor
21-08-06 16:45:06 INFO (MainThread) [supervisor.os.manager] Rauc: A - marked slot kernel.0 as good
21-08-06 16:45:06 INFO (MainThread) [supervisor.supervisor] Fetching AppArmor profile https://version.home-assistant.io/apparmor.txt
21-08-06 16:45:06 INFO (MainThread) [supervisor.host.apparmor] Adding/updating AppArmor profile: hassio-supervisor
21-08-06 16:45:06 INFO (MainThread) [supervisor.host.services] Reloading local service hassos-apparmor.service
21-08-06 16:45:06 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 2021.10.8
21-08-06 16:45:06 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/armv7-hassio-supervisor with tag 2021.10.8.
21-08-06 16:45:06 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/armv7-hassio-supervisor:2021.10.8: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2021.10.8&fromImage=ghcr.io%2Fhome-assistant%2Farmv7-hassio-supervisor: Internal Server Error ("Get "https://ghcr.io/v2/": x509: certificate has expired or is not yet valid: current time 2021-08-06T14:45:06Z is before 2021-08-24T00:00:00Z")
21-08-06 16:45:06 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.UPDATE_FAILED - ContextType.SUPERVISOR / None
21-08-06 16:45:06 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor failed: Can't install ghcr.io/home-assistant/armv7-hassio-supervisor:2021.10.8: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2021.10.8&fromImage=ghcr.io%2Fhome-assistant%2Farmv7-hassio-supervisor: Internal Server Error ("Get "https://ghcr.io/v2/": x509: certificate has expired or is not yet valid: current time 2021-08-06T14:45:06Z is before 2021-08-24T00:00:00Z")
21-08-06 16:45:06 CRITICAL (MainThread) [supervisor.core] Can't update Supervisor! This will break some Add-ons or affect future versions of Home Assistant!
21-08-06 16:45:06 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
21-08-06 16:45:06 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 0 add-ons
21-08-06 16:45:06 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 0 add-ons
21-08-06 16:45:06 INFO (MainThread) [supervisor.core] Skiping start of Home Assistant
21-08-06 16:45:06 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 0 add-ons
21-08-06 16:45:07 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
21-08-06 16:45:07 INFO (MainThread) [supervisor.core] Supervisor is up and running
21-08-06 16:45:07 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant setup
21-08-06 16:45:07 INFO (MainThread) [supervisor.host.info] Updating local host information
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-08-06 16:45:07 INFO (SyncWorker_1) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-homeassistant:landingpage to ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-08-06 16:45:07 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-homeassistant with tag 2021.11.3.
21-08-06 16:45:07 INFO (MainThread) [supervisor.host.services] Updating service information
21-08-06 16:45:07 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2021.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi4-homeassistant: Internal Server Error ("Get "https://ghcr.io/v2/": x509: certificate has expired or is not yet valid: current time 2021-08-06T14:45:07Z is before 2021-08-24T00:00:00Z")
21-08-06 16:45:07 INFO (MainThread) [supervisor.host.network] Updating local network information
21-08-06 16:45:07 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.CREATE_FULL_BACKUP - ContextType.SYSTEM / None
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-08-06 16:45:07 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-08-06 16:45:07 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not healthy
21-08-06 16:45:07 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-08-06 16:45:07 INFO (MainThread) [supervisor.host.manager] Host information reload completed
21-08-06 16:45:37 INFO (SyncWorker_1) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-homeassistant:landingpage to ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3
21-08-06 16:45:37 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-homeassistant with tag 2021.11.3.
21-08-06 16:45:37 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2021.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi4-homeassistant: Internal Server Error ("Get "https://ghcr.io/v2/": x509: certificate has expired or is not yet valid: current time 2021-08-06T14:45:37Z is before 2021-08-24T00:00:00Z")
21-08-06 16:45:37 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
21-08-06 16:46:07 INFO (SyncWorker_3) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-homeassistant:landingpage to ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3
21-08-06 16:46:07 INFO (SyncWorker_3) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-homeassistant with tag 2021.11.3.
21-08-06 16:46:07 ERROR (SyncWorker_3) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2021.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi4-homeassistant: Internal Server Error ("Get "https://ghcr.io/v2/": x509: certificate has expired or is not yet valid: current time 2021-08-06T14:46:07Z is before 2021-08-24T00:00:00Z")
21-08-06 16:46:07 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
21-08-06 16:46:37 INFO (SyncWorker_1) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-homeassistant:landingpage to ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3
21-08-06 16:46:37 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-homeassistant with tag 2021.11.3.
21-08-06 16:46:37 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-homeassistant:2021.11.3: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2021.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi4-homeassistant: Internal Server Error ("Get "https://ghcr.io/v2/": x509: certificate has expired or is not yet valid: current time 2021-08-06T14:46:37Z is before 2021-08-24T00:00:00Z")
21-08-06 16:46:37 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec

Y así hasta 2000 años despues…

(menciono tambien que la Rpi está bien alimentada y la microsd esta en buen estado)

Alguna pista sobre que puedo hacer? Alguien tiene MasMovil, Yoigo….y tiene el mismo problema? Porque seguro que en una instalación limpia y conectado a internet os coge la hora a la primera, verdad?

Como datos, tanto mi IP publica como DNS están localizados en España, podria haber un desfase de hora, no de meses……...

Un saludo y gracias

[sunbloquer]

Si por ejemplo yo hago

Código: Seleccionar todo

pi@raspberrypi:~ $ nmap -p 10-65535 192.168.1.1
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-30 12:32 BST
Nmap scan report for 192.168.1.1
Host is up (0.00078s latency).
Not shown: 65521 closed ports
PORT      STATE    SERVICE
22/tcp    filtered ssh
53/tcp    open     domain
80/tcp    open     http
443/tcp   open     https
49152/tcp open     unknown

ignoro si el 123 usado para sincronizar la hora debiera estar abierto o no.

Si escaneo mi IP PUBLICA

Código: Seleccionar todo

pi@raspberrypi:~ $ nmap -vv xxx.xx.xx.xxx
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-30 12:39 BST
Initiating Ping Scan at 12:39
Scanning xxx.xx.xx.xxx [2 ports]
Completed Ping Scan at 12:39, 3.00s elapsed (1 total hosts)
Nmap scan report for xxx.xx.xx.xxx [host down, received no-response]
Read data files from: /usr/bin/../share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.15 seconds

Y si le hago caso

Código: Seleccionar todo

pi@raspberrypi:~ $ nmap -Pn xxx.xx.xx.xxx
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-30 12:41 BST
Nmap scan report for xxx.xx.xx.xxx
Host is up.
All 1000 scanned ports on xxx.xx.xx.xxx are filtered

Nmap done: 1 IP address (1 host up) scanned in 201.72 seconds

Esto es dar palos de ciego, yo sigo pensando que tengo el 123 inaccesible

Código: Seleccionar todo

pi@raspberrypi:~ $ nmap -p 123 185.207.104.70
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-30 12:54 BST
Nmap scan report for epsilon.h6g-server.net (185.207.104.70)
Host is up (0.041s latency).

PORT    STATE  SERVICE
123/tcp closed ntp

Nmap done: 1 IP address (1 host up) scanned in 0.37 seconds

[sunbloquer]

Una de las preguntas que me hago es que como es posible que con otro ISP me sincronice la hora en el primer arranque y en mi casa no? por que todo lo que leo es que es imprescindible instalar NTP, por lo tanto de que archivo de configuración toma la hora con una instalación limpia?

[egrueda]

Tiene que simplificar (y mucho) tu incidencia. Añadir más ingredientes a la receta sólo distrae y dificulta el rastreo.

una Rpi conectada a internet me coge la hora

si hay internet en la Rpi, hay sincronización de hora.

¿Te has preguntado cómo es eso posible?
¿Cómo hace la raspberry exactamente para actualizar la hora sin que tú le digas nada?

[sunbloquer]

Pues la verdad, por lo que digo. Si esta conectada a internet coge la hora........de un servidor (sin instalar previamente el paquete NTP).

El caso es que en mi casa (YOIGO) y otra casa (MASMOVIL) si yo no le digo que actualice la hora no lo hace.

No la coge del router porque como se ve en el video se conecta a un servidor x al puerto 123 y coge solo la hora.

Sigo sin entenderlo. Y el informático de mi ISP tampoco. Es mas, dice que sin instalarle yo previamente el NTP es IMPOSIBLE que me sincronice la hora en el primer arranque.

Ha estado con el router (con privilegios Superadministrador) me ha dicho y deshabilitado todo lo posible, cambiado DNS y fail. No coge la hora.

[egrueda]

Si no entiendes cómo funciona la sincronización, vas a dar palos de ciego buscando donde no debes.
Antes de arreglar algo, debes saber qué tienes que arreglar.
No tiene sentido que te líes con los dns, el router, los puertos y demás si no sabes cuál es el origen del fallo.
Empieza desde el principio y ve deduciendo desde ahí.

Venga, empecemos por entender qué es y cómo funciona systemd-timesyncd
https://wiki.archlinux.org/title/System ... a%C3%B1ol)

[sunbloquer]

Bien, entiendo que ese servicio-demonio que viene por defecto en todas las distros es el causante que se sincronice la hora en cada arranque.

La configuración que me muestra y que muestra a todo el mundo que instale mi misma distro es

Código: Seleccionar todo

pi@raspberrypi:~ $ timedatectl show-timesync --all
LinkNTPServers=
SystemNTPServers=147.156.7.18
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=147.156.7.18
ServerAddress=147.156.7.18
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=34min 8s
Frequency=0

Pero aún asi, no sincroniza, ya que me faltaria

Código: Seleccionar todo

NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=2, Precision=-21, RootDelay=177.398ms, RootDispersion=142.196ms, Reference=C342F10A, OriginateTimestamp=Mon 2018-07-16 13:53:43 +08, ReceiveTimestamp=Mon 2018-07-16 13:53:43 +08, TransmitTimestamp=Mon 2018-07-16 13:53:43 +08, DestinationTimestamp=Mon 2018-07-16 13:53:43 +08, Ignored=no PacketCount=1, Jitter=0 }
Frequency=22520548

Lo que indica se sincroniza, se comunica para sincronizar la hora.

No es necesario que lo ejecute timedatectl set-ntp true ya que debiera hacerlo el solito.

El servicio está activo pero no sincroniza

Código: Seleccionar todo

pi@raspberrypi:~ $ timedatectl status
               Local time: Sat 2021-10-30 14:42:43 BST
           Universal time: Sat 2021-10-30 13:42:43 UTC
                 RTC time: n/a
                Time zone: Europe/London (BST, +0100)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

Código: Seleccionar todo

pi@raspberrypi:~ $ timedatectl timesync-status
       Server: 147.156.7.18 (147.156.7.18)
Poll interval: 34min 8s (min: 32s; max 34min 8s)
 Packet count: 0

Vamos, que sabe a donde realizar la petición de la hora pero no obtiene respuesta.

El Firewall del router lo bloquea?. Estoy en un bucle del que no salgo

[egrueda]

Siguiente paso, antes de pensar en el router, ¿cuál es el estado del servicio? ¿y su log?

systemctl status systemd-timesyncd

[sunbloquer]

Lo que veo es que esta activo desde hace 2h 19min ago y la hora sin sincronizar.

Pero sigo con mi bucle......si esta raspbian ahora mismo la desenchufo y la llevo a casa de mi vecino (30 metros) con IPS de Telefónica, funciona.

Código: Seleccionar todo

pi@raspberrypi:~ $ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; ve>
     Active: active (running) since Sat 2021-10-30 12:30:05 BST; 2h 19min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 683 (systemd-timesyn)
     Status: "Idle."
      Tasks: 2 (limit: 3720)
        CPU: 177ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─683 /lib/systemd/systemd-timesyncd

Oct 30 12:30:15 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 12:30:57 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 12:32:12 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 12:34:30 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 12:38:57 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 12:47:39 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 13:04:54 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 13:39:12 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 14:13:31 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
Oct 30 14:47:49 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply>
lines 1-21/21 (END)...skipping...
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2021-10-30 12:30:05 BST; 2h 19min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 683 (systemd-timesyn)
     Status: "Idle."
      Tasks: 2 (limit: 3720)
        CPU: 177ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─683 /lib/systemd/systemd-timesyncd

Oct 30 12:30:15 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 12:30:57 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 12:32:12 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 12:34:30 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 12:38:57 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 12:47:39 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 13:04:54 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 13:39:12 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 14:13:31 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Oct 30 14:47:49 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).

[egrueda]

Bien, vemos que el servicio está arrancado correctamente.
Y vemos un timeout intentando conectar con 147.156.7.18, que pertenece al pool de 0.es.pool.ntp.org

¿Qué ocurre si tú manualmente haces una consulta a esa IP?
sudo ntpdate -v 147.156.7.18

[sunbloquer]

Pues como no tengo instalado ntpdate, me muestra:

pi@raspberrypi:~ $ sudo ntpdate -v 147.156.7.18
sudo: ntpdate: command not found

instalo ntpdate y el resultado de la consulta

pi@raspberrypi:~ $ sudo ntpdate -v 147.156.7.18
30 Oct 15:08:30 ntpdate[1544]: ntpdate 4.2.8p15@1.3728-o Wed Sep 23 11:46:38 UTC 2020 (1)
12 Nov 18:07:54 ntpdate[1544]: step time server 147.156.7.18 offset +1137557.788511 sec

Lo último de syslog

Código: Seleccionar todo

Oct 30 14:29:44 raspberrypi rngd[496]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Oct 30 14:35:11 raspberrypi dbus-daemon[350]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.18' (uid=1000 pid=1386 comm="timedatectl status ")
Oct 30 14:35:11 raspberrypi systemd[1]: Starting Time & Date Service...
Oct 30 14:35:11 raspberrypi dbus-daemon[350]: [system] Successfully activated service 'org.freedesktop.timedate1'
Oct 30 14:35:11 raspberrypi systemd[1]: Started Time & Date Service.
Oct 30 14:35:41 raspberrypi systemd[1]: systemd-timedated.service: Succeeded.
Oct 30 14:42:43 raspberrypi dbus-daemon[350]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.21' (uid=1000 pid=1406 comm="timedatectl status ")
Oct 30 14:42:43 raspberrypi systemd[1]: Starting Time & Date Service...
Oct 30 14:42:43 raspberrypi dbus-daemon[350]: [system] Successfully activated service 'org.freedesktop.timedate1'
Oct 30 14:42:43 raspberrypi systemd[1]: Started Time & Date Service.
Oct 30 14:43:13 raspberrypi systemd[1]: systemd-timedated.service: Succeeded.
Oct 30 14:47:49 raspberrypi systemd-timesyncd[683]: Timed out waiting for reply from 147.156.7.18:123 (147.156.7.18).
Nov 12 18:07:54 raspberrypi systemd[1]: Starting Daily apt download activities...
Nov 12 18:07:54 raspberrypi systemd[1]: Starting Online ext4 Metadata Check for All Filesystems...
Nov 12 18:07:54 raspberrypi systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Nov 12 18:07:54 raspberrypi systemd[1]: Starting Rotate log files...
Nov 12 18:07:54 raspberrypi systemd[1]: Starting Daily man-db regeneration...
Nov 12 18:07:54 raspberrypi systemd[1]: e2scrub_all.service: Succeeded.
Nov 12 18:07:54 raspberrypi systemd[1]: Finished Online ext4 Metadata Check for All Filesystems.
Nov 12 18:07:54 raspberrypi systemd[1]: logrotate.service: Succeeded.
Nov 12 18:07:54 raspberrypi systemd[1]: Finished Rotate log files.
Nov 12 18:07:55 raspberrypi fstrim[1547]: /: 12.6 GiB (13492436992 bytes) trimmed on /dev/mmcblk0p2
Nov 12 18:07:55 raspberrypi fstrim[1547]: /boot: 204 MiB (213863936 bytes) trimmed on /dev/mmcblk0p1
Nov 12 18:07:55 raspberrypi systemd[1]: fstrim.service: Succeeded.
Nov 12 18:07:55 raspberrypi systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.
Nov 12 18:07:55 raspberrypi systemd[1]: man-db.service: Succeeded.
Nov 12 18:07:55 raspberrypi systemd[1]: Finished Daily man-db regeneration.
Nov 12 18:07:55 raspberrypi systemd[1]: apt-daily.service: Succeeded.
Nov 12 18:07:55 raspberrypi systemd[1]: Finished Daily apt download activities.
Nov 12 18:07:55 raspberrypi systemd[1]: apt-daily.service: Consumed 1.017s CPU time.
Nov 12 18:07:55 raspberrypi systemd[1]: Starting Daily apt upgrade and clean activities...
Nov 12 18:07:56 raspberrypi systemd[1]: apt-daily-upgrade.service: Succeeded.
Nov 12 18:07:56 raspberrypi systemd[1]: Finished Daily apt upgrade and clean activities.

[egrueda]

Bien, eso indica que la conexión con el servidor NTP externo es correcta.
Es decir, no está filtrado, ni bloqueado, de lo contrario esa prueba te habría fallado.
¿Hasta ahí estamos de acuerdo?

El siguiente paso es averiguar por qué funciona *después* del arranque pero no *durante* el arranque.
¿Se conecta por cable o por wifi?

[sunbloquer]

Conexión directa por cable al router tanto en mi casa como en el resto. Por que el problema es ese. No funciona durante el arranque en los ISP que mencioné.

[egrueda]

Una prueba buena sería ver si el DHCP devuelve un servidor NTP o no.
Digo que sería una buena prueba porque podríamos comprarar la información del router cuando no te sincroniza y del otro router cuando sí te sincroniza.
Hay varias formas de preguntar al servidor DHCP del router, yo suelo usar:
sudo nmap --script broadcast-dhcp-discover

[sunbloquer]

Mi router me dice:

Código: Seleccionar todo

pi@raspberrypi:~ $ sudo nmap --script broadcast-dhcp-discover
Starting Nmap 7.80 ( https://nmap.org ) at 2021-11-12 18:22 GMT
Pre-scan script results:
| broadcast-dhcp-discover:
|   Response 1 of 1:
|     IP Offered: 192.168.1.21
|     DHCP Message Type: DHCPOFFER
|     Server Identifier: 192.168.1.1
|     IP Address Lease Time: 1d00h00m00s
|     Subnet Mask: 255.255.255.0
|     Router: 192.168.1.1
|     Domain Name Server: 212.230.135.1, 212.230.135.2
|     NTP Servers: 147.156.7.18
|     Renewal Time Value: 12h00m00s
|_    Rebinding Time Value: 21h00m00s
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 1.89 seconds

Ahora a ver si el otro está en casa, ya le dije que me iba a acabar empadronando allí

[egrueda]

Anda, mira, no esperaba que tu router te estuviese devolviendo un servidor NTP:

NTP Servers: 147.156.7.18

Ya sabemos de dónde sale el servidor NTP que da el fallo de conexión

[sunbloquer]

Mi router esta seteado asi, no se si por defecto o el informático hizo algo

[sunbloquer]

Estoy a la espera del otro resultado, no vivo en ciudad y mi vecino a 30 minutos.....a ver si me da el resultado suyo.

Creo que lo siguiente seria poner en off el servidor NTP del router a ver que pasa y realizar los pasos de antes, o a lo mejor sincroniza solo.

No tiene ninguna maquina con Linux, lo tendré que hacer yo otro dia.

[sunbloquer]

Nueva instalación, el servidor NTP del router OFF y reiniciado.

Código: Seleccionar todo

pi@raspberrypi:~ $ sudo nmap --script broadcast-dhcp-discover
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-30 12:31 BST
Pre-scan script results:
| broadcast-dhcp-discover:
|   Response 1 of 1:
|     IP Offered: 192.168.1.18
|     DHCP Message Type: DHCPOFFER
|     Server Identifier: 192.168.1.1
|     IP Address Lease Time: 1d00h00m00s
|     Subnet Mask: 255.255.255.0
|     Router: 192.168.1.1
|     Domain Name Server: 212.230.135.1, 212.230.135.2
|     NTP Servers: 147.156.7.18
|     Renewal Time Value: 12h00m00s
|_    Rebinding Time Value: 21h00m00s
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 1.95 seconds

Me sigue cogiendo esa IP

[egrueda]

Quizá porque estás dentro de las 12 horas de validez del DHCP