error al iniciar debian buster systemd-timesyncd loaded failed

17 envíos / 0 nuevos
Último envío
#1 Dom, 21/01/2018 - 23:37
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

error al iniciar debian buster systemd-timesyncd loaded failed

Estado: 
[SOLUCIONADO]

Hola, como están ?

Les cuento que he bajado e instalado buster, (instalación limpia), y puesto mis cosas en sus sitios.smiley

Pero al iniciar noto algunas lineas con FAILS en rojo, bien al inicio de la inicialización.

No recuerdo de ver estas lineas en la iniciación de stretch 9.3... entonces enpeze a investigar, y encuentro esto:surprise

erro

entonces veo que...

el servicio

y

 

alguien sabe por que se ha provocado este error y que puedo hacer para intentar corregir esto ?crying

muchas grácias por qualquier información...

Estuve en tantos lugares que no se donde fue alguien decia tener un problema identico pero que al reiniciar el servicio funcionaba luego de reiniciarlo, lo que no pasa en mi caso.

Luego explicaba de porque esto sucedia al ser iniciado este y tal servicio antes, bla bla bla...

Pense que pudiera estar relacionado con la sicronisación del reloj, pero busque por ahí y no he llegado a ninguna conclución tampoco.

La verdad es que ya ni se por donde van los tiros... blush Esoy mas perdido que un "Stretch en un garage" ...

Saludos

lalo

Lun, 22/01/2018 - 12:52
caliban
Imagen de caliban
Desconectado/a
moderador
se unió: 14/01/16

Intenta iniciarlo (systemctl  start blablabla) ,a ver que ocurre o que error te escupe.

Por defecto en mi sistema ( debian sid) no inicia en el booteo,pero he podido iniciarlo manualmente sin problemas, por lo que pude investigar ,el error puede deberse a una descoordinacion en la configuración 

de algunos servicios de systemd anterior y actual de tu sistema,, también si existiera en tu sistema por defecto 

un sincronizador de tiempo real  ntpd , por ejemplo , lo que haría innecesario habilitar el service-timesyncd.

 

Lun, 22/01/2018 - 16:03
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

Gracias caliban por tu amable respuesta.

entonces...

sudo systemctl start systemd-timesyncd.service

responde

Job for systemd-timesyncd.service failed because the control process exited with error code.
See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for details.

De systemd anterior no porque es una instalación limpia...

sudo journalctl -xe

jan 22 16:52:56 linux NetworkManager[669]: <info>  [1516647176.6350] device (wlp4s0): supplicant interface state: disabled -> inactive
jan 22 16:52:56 linux wpa_supplicant[683]: wlp4s0: Reject scan trigger since one is already pending
jan 22 16:57:16 linux sudo[3456]:       my : TTY=pts/1 ; PWD=/home/my ; USER=root ; COMMAND=/bin/journalctl -xe
jan 22 16:57:16 linux sudo[3456]: pam_unix(sudo:session): session opened for user root by (uid=0)
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:19 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:20 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:20 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:20 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:21 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:57:33 linux sudo[3456]: pam_unix(sudo:session): session closed for user root
jan 22 16:58:00 linux sudo[3462]:       my : TTY=pts/1 ; PWD=/home/my ; USER=root ; COMMAND=/bin/journalctl -xe
jan 22 16:58:00 linux sudo[3462]: pam_unix(sudo:session): session opened for user root by (uid=0)
jan 22 16:58:04 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba04e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:58:06 linux sudo[3462]: pam_unix(sudo:session): session closed for user root
jan 22 16:58:10 linux sudo[3465]:       my : TTY=pts/1 ; PWD=/home/my ; USER=root ; COMMAND=/bin/journalctl -xe
jan 22 16:58:10 linux sudo[3465]: pam_unix(sudo:session): session opened for user root by (uid=0)
jan 22 16:58:12 linux NetworkManager[669]: <info>  [1516647492.1050] device (wlp4s0): set-hw-addr: set MAC address to 4A:38:A5:94:30:B7 (scanning
jan 22 16:58:12 linux NetworkManager[669]: <info>  [1516647492.5399] device (wlp4s0): supplicant interface state: inactive -> disabled
jan 22 16:58:12 linux kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
jan 22 16:58:12 linux NetworkManager[669]: <info>  [1516647492.5951] device (wlp4s0): supplicant interface state: disabled -> inactive
jan 22 16:58:12 linux wpa_supplicant[683]: wlp4s0: Reject scan trigger since one is already pending
jan 22 16:58:30 linux sudo[3465]: pam_unix(sudo:session): session closed for user root
jan 22 16:59:00 linux gnome-terminal-[1334]: Allocating size to GtkScrollbar 0x5596d6ba06e0 without calling gtk_widget_get_preferred_width/height
jan 22 16:59:10 linux sudo[3487]:       my : TTY=pts/1 ; PWD=/home/my ; USER=root ; COMMAND=/bin/journalctl -xe
jan 22 16:59:10 linux sudo[3487]: pam_unix(sudo:session): session opened for user root by (uid=0)

systemctl status systemd-timesyncd.service ya consta en el post anterior...

Saludos

lalo

Lun, 22/01/2018 - 17:17
rockyiii
Imagen de rockyiii
Desconectado/a
administrator
se unió: 11/01/16

 podrias poner el contenido de:

su
journalctl -u systemd-timesyncd.service
journalctl -b -p err

AGREGO:----

y de:

timedatectl status

 

Lun, 22/01/2018 - 17:24
caliban
Imagen de caliban
Desconectado/a
moderador
se unió: 14/01/16
/lib/systemd/system/systemd-timesyncd.service

##modificar el tiempo de espera entre repeticiones 
[Service]
Type=notify
Restart=always
---------------------
RestartSec=0    → modificar este tiempo 
----------------------

ExecStart=!!/lib/systemd/systemd-timesyncd

Lo que puse arriba es  el .service que podrías intentar modificar (editas como root )para ver si el error persiste  (la ruta del service la indique en la cabecera)

fijate aca como guía 

Lun, 22/01/2018 - 21:06 (Responder a #5)
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

Claro que si rockyiii

gracias por responderme...

sudo journalctl -u systemd-timesyncd.service
 
-- Logs begin at Mon 2018-01-22 13:21:24 -02, end at Mon 2018-01-22 21:56:33 -02
jan 22 13:21:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:35 linux systemd-timesyncd[607]: Cannot resolve user name systemd-t
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Main process exited
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Failed with result 
jan 22 13:21:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Service has no hold
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Scheduled restart j
jan 22 13:21:35 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:36 linux systemd-timesyncd[617]: Cannot resolve user name systemd-t
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Main process exited
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart j
jan 22 13:21:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:36 linux systemd-timesyncd[638]: Cannot resolve user name systemd-t
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Main process exited
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold
lines 1-23...skipping...
-- Logs begin at Mon 2018-01-22 13:21:24 -02, end at Mon 2018-01-22 21:56:33 -02. --
jan 22 13:21:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:35 linux systemd-timesyncd[607]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 13:21:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 13:21:35 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.
jan 22 13:21:35 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:36 linux systemd-timesyncd[617]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 2.
jan 22 13:21:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:36 linux systemd-timesyncd[638]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 3.
jan 22 13:21:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:36 linux systemd-timesyncd[643]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 4.
jan 22 13:21:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: Starting Network Time Synchronization...
jan 22 13:21:36 linux systemd-timesyncd[652]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
jan 22 13:21:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
jan 22 13:21:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 16:51:35 linux systemd-timesyncd[3430]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 16:51:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.
jan 22 16:51:35 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 16:51:35 linux systemd-timesyncd[3433]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 16:51:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 2.
jan 22 16:51:35 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 16:51:35 linux systemd-timesyncd[3436]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 16:51:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 16:51:35 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 3.
jan 22 16:51:35 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 16:51:35 linux systemd[1]: Starting Network Time Synchronization...
jan 22 16:51:36 linux systemd-timesyncd[3439]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 16:51:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 4.
jan 22 16:51:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 16:51:36 linux systemd[1]: Starting Network Time Synchronization...
jan 22 16:51:36 linux systemd-timesyncd[3442]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 16:51:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
jan 22 16:51:36 linux systemd[1]: Stopped Network Time Synchronization.
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
jan 22 16:51:36 linux systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
jan 22 16:51:36 linux systemd[1]: Failed to start Network Time Synchronization.
sudo journalctl -b -p err
-- Logs begin at Mon 2018-01-22 13:21:24 -02, end at Mon 2018-01-22 22:02:24 -02. --
jan 22 13:21:35 linux systemd-timesyncd[607]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd-timesyncd[617]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd-timesyncd[638]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd-timesyncd[643]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd-timesyncd[652]: Cannot resolve user name systemd-timesync: No such process
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 13:21:36 linux kernel: CPU7: Core temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:36 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1)
jan 22 13:21:43 linux bluetoothd[675]: Sap driver initialization failed.
jan 22 13:21:43 linux bluetoothd[675]: sap-server: Operation not permitted (1)
jan 22 14:09:10 linux kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 14)
jan 22 14:09:10 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU7: Core temperature above threshold, cpu clock throttled (total events = 14)
jan 22 14:09:10 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:09:10 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 15)
jan 22 14:31:21 linux kernel: CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)
jan 22 14:31:21 linux kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
jan 22 14:31:21 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:31:21 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 47)
jan 22 14:36:26 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 14:36:26 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1348)
jan 22 16:14:37 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 2077)
jan 22 16:14:37 linux kernel: CPU7: Core temperature above threshold, cpu clock throttled (total events = 2077)
jan 22 16:14:37 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:14:37 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3084)
jan 22 16:51:35 linux systemd-timesyncd[3430]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:35 linux systemd-timesyncd[3433]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:35 linux systemd-timesyncd[3436]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:35 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:36 linux systemd-timesyncd[3439]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:36 linux systemd-timesyncd[3442]: Cannot resolve user name systemd-timesync: No such process
jan 22 16:51:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 16:51:36 linux systemd[1]: Failed to start Network Time Synchronization.
jan 22 17:47:30 linux kernel: CPU6: Core temperature above threshold, cpu clock throttled (total events = 1292)
jan 22 17:47:30 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1292)
jan 22 17:47:30 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:47:30 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3087)
jan 22 17:53:39 linux kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 2091)
jan 22 17:53:39 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU7: Core temperature above threshold, cpu clock throttled (total events = 2091)
jan 22 17:53:39 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 17:53:39 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3104)
jan 22 18:03:49 linux kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 2242)
jan 22 18:03:49 linux kernel: CPU7: Core temperature above threshold, cpu clock throttled (total events = 2242)
jan 22 18:03:49 linux kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:03:49 linux kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3307)
jan 22 18:50:44 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 20:42:38 linux systemd-rfkill[4823]: Failed to open device rfkill1: No such device
jan 22 20:42:39 linux bluetoothd[675]: Sap driver initialization failed.
jan 22 20:42:39 linux bluetoothd[675]: sap-server: Operation not permitted (1)
jan 22 20:42:43 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 20:56:02 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:04:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:09:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:14:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:21:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:26:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:31:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:36:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:41:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:46:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 21:55:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
jan 22 22:00:47 linux wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
sudo timedatectl status
                      Local time: seg 2018-01-22 22:04:14 -02
                  Universal time: ter 2018-01-23 00:04:14 UTC
                        RTC time: ter 2018-01-23 00:04:15
                       Time zone: America/Sao_Paulo (-02, -0200)
       System clock synchronized: yes
systemd-timesyncd.service active: no
                 RTC in local TZ: no

 

Lun, 22/01/2018 - 22:09 (Responder a #6)
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

Hola caliban,

y gracias por responder.

He modificado la linea RestartSec=0 para: RestartSec=50

los resultados son los siguientes

el resultado de sudo journalctl -xe ahora es:

Saludos

lalo

Lun, 22/01/2018 - 22:45
rockyiii
Imagen de rockyiii
Desconectado/a
administrator
se unió: 11/01/16

fijate si con:

su
timedatectl set-ntp true 

al volver a ejecutar

timedatectl status

te sale NTP synchronized: yes

* puede que tengas que reiniciar el pc o ejecutar un

su
systemctl stop systemd-timesyncd
systemctl start systemd-timesyncd

la otra es que pruebes en:

su
nano /etc/systemd/timesyncd.conf 

dejarlo asi:

[Time]
#NTP=
#FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
[Time]
NTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
FallbackNTP=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org

fuente: https://wiki.archlinux.org/index.php/systemd-timesyncd

AGREGO:----

o sino

[Time]
NTP=
FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org

 

Mar, 23/01/2018 - 12:28
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

¿Puedes poner el contenido del archivo /lib/systemd/system/systemd-timesyncd.service?

Veo que hay un bug reportado en su github al respecto, y por el error que muestra, es posible que estés afectado por el mismo (parece ser que ocurre con la versión 236, no se cual es la que tiene Buster, aunque imagino que será esa ya que es la que anda en Sid y no he tenido ese problema).

El asunto parece venir con el usuario con el cual se ejecuta el servicio. Bajo ciertas circunstancias el servicio necesita unas dependencias de otros servicios que no se cumplen con tu configuración por defecto, y de ahi puede venir el problema. Con el contenido del archivo que te he pedido puedo comparar con el mio a ver que cambia y, si es lo que me imagino, se puede solucionar cambiando un parámetro o creando el user y grupo que "busca" el servicio para poder ejecutarse correctamente.

  No hay bar que por bien no venga....
Mar, 23/01/2018 - 13:55 (Responder a #9)
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

Claro Panko

y gracias por responder, aqui va...

#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Network Time Synchronization
Documentation=man:systemd-timesyncd.service(8)
ConditionCapability=CAP_SYS_TIME
ConditionVirtualization=!container
DefaultDependencies=no
After=systemd-remount-fs.service systemd-sysusers.service
Before=time-sync.target sysinit.target shutdown.target
Conflicts=shutdown.target
Wants=time-sync.target

[Service]
Type=notify
Restart=always
RestartSec=50
ExecStart=!!/lib/systemd/systemd-timesyncd
WatchdogSec=3min
User=systemd-timesync
DynamicUser=yes
CapabilityBoundingSet=CAP_SYS_TIME
AmbientCapabilities=CAP_SYS_TIME
PrivateDevices=yes
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelTunables=yes
ProtectKernelModules=yes
MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictNamespaces=yes
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6
SystemCallFilter=~@cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap
SystemCallArchitectures=native
LockPersonality=yes
StateDirectory=systemd/timesync

[Install]
WantedBy=sysinit.target

Saludos

lalo

Mar, 23/01/2018 - 14:09 (Responder a #10)
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

Hola rockyiii 

gracias por responder.

la primera parte:

sudo timedatectl set-ntp true

sudo timedatectl status

                      Local time: ter 2018-01-23 14:55:36 -02
                  Universal time: ter 2018-01-23 16:55:36 UTC
                        RTC time: ter 2018-01-23 16:55:36
                       Time zone: America/Sao_Paulo (-02, -0200)
       System clock synchronized: yes
systemd-timesyncd.service active: no
                 RTC in local TZ: no

el otro comando

sudo systemctl stop systemd-timesyncd

Failed to stop systemd-timesyncd.service: Access denied
See system logs and 'systemctl status systemd-timesyncd.service' for details.

el comando que sugiere la falla...

sudo systemctl status systemd-timesyncd.service

● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2018-01-23 14:56:38 -02; 24s ago
     Docs: man:systemd-timesyncd.service(8)
  Process: 6383 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
 Main PID: 6383 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

el otro comando

sudo systemctl start systemd-timesyncd

Job for systemd-timesyncd.service failed because the control process exited with error code.
See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for details.

ahora no puedo probar LA OTRA...

asi que pueda te lo respondo

Gracias

Saludos

lalo

Mar, 23/01/2018 - 15:40 (Responder a #11)
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

rockyiii wrote:

la otra es que pruebes en:

su
nano /etc/systemd/timesyncd.conf 

dejarlo asi:

[Time]
#NTP=
#FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
[Time]
NTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
FallbackNTP=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org

fuente: https://wiki.archlinux.org/index.php/systemd-timesyncd

reinicie antes de dar estos comandos...

Pude probar ahora,

sudo systemctl start systemd-timesyncd

Job for systemd-timesyncd.service failed because the control process exited with error code.
See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for details.

y

sudo systemctl status systemd-timesyncd.service

● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2018-01-23 16:29:24 -02; 22s ago
     Docs: man:systemd-timesyncd.service(8)
  Process: 1481 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
 Main PID: 1481 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

voy a probar la ultima de tu post a seguir...

ya les envio respuesta. cool

Mar, 23/01/2018 - 17:13
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

Pues lo tienes igual que el mío, excepto el cambio que hiciste del tiempo (de 0 a 50). Prueba a crear un usuario y un grupo, llamados ambos systemd-timesync (si te preguntara por el shell del usuario, ponle /bin/false) y reinicia el sistema a ver si el problema persiste.

El servicio debería haberlos creado (parámetro DinamicUser=yes), pero parece ser que no ha sido así. Este servicio se ejecuta como usuario systemd-timesync, el cual no existirá en tu sistema y por eso da error.

  No hay bar que por bien no venga....
Mar, 23/01/2018 - 17:34
caliban
Imagen de caliban
Desconectado/a
moderador
se unió: 14/01/16

Siguiendo la idea de @panko  he leído otro bug respecto a usuario/grupo  respecto a este service, así como en algunos foros que indicaban la necesidad de crear  usuario y grupo ( cierto es que en versiones mas antiguas de systemd) 

En mi caso ,debian sid , tengo :

cat /etc/passwd |grep systemd
systemd-timesync:x:116:125:systemd Time Synchronization,,,:/run/systemd:/bin/false
...................................................................................
........................................................................
-------------------------------------------------------------------------
cat /etc/group |grep systemd
.....................
systemd-timesync:x:125:
................................

Como se ve ,,  existe un usuario   systemd-timesync    y  un grupo   

Mar, 23/01/2018 - 19:04
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

Pues si, así es como me aparece a mi también. Se me había olvidado el detalle del "home" de dicho usuario, que sería /run/systemd, con lo que la línea de /etc/passwd al comprobarlo quedaría como la tuya:

:~$ grep systemd /etc/passwd
systemd-timesync:x:128:143:systemd Time Synchronization:/run/systemd:/bin/false
.....

y el error en cuestión, que es el que me ha llevado al reporte, es

jan 22 13:21:36 linux systemd-timesyncd[617]: Cannot resolve user name systemd-timesync: No such process

que indica precisamente eso, que va a buscar un proceso ejecutado por ese user que no encuentra.

  No hay bar que por bien no venga....
Mar, 23/01/2018 - 19:18
lalo
Imagen de lalo
Desconectado/a
colaborador
se unió: 22/02/16

Muy bien!

 

Panko le has dado en el clavo... laughsmileylaugh

un

sudo adduser systemd-timesync

ha resuelto el caso.

¡¡¡Muchisimas gracias a todos los que respondieron y se interesaron!!! yeslaugh

 

Saludos

lalo

Mar, 30/01/2018 - 09:00
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

A pesar de ser un  problema solucionado, añado un poco más de info, que siempre puede valer para algo.

El problema en cuestión, bug que ya dije estaba reportado al upstream de systemd, consiste en la gestión dinámica de usuarios. Algunos servicios, en determinadas situaciones (sistemas con systemd, pero que no usan el mismo para el arranque, como podrían ser aquellos que usan sysv-init junto con systemd-shim, p.e.), necesitan usuario para poder ejecutarse y así no hacerlo como root. Al activar el parámetro DynamicUser=yes, parece ser que no se incluyó como dependencia el paquete libnss-systemd, que es precisamente el que se encarga de la gestión de dichos usuarios y crearlos en el momento del inicio cuando sea necesario.

Dicho esto, aunque haya funcionado la creación manual del usuario, también habría servido instalar dicho paquete y reiniciar el sistema. En el segundo caso, además, solucionaría los posibles errores con otros servicios que precisen de un usuario en concreto para su correcto funcionamiento.

 

Edit.....

El paquete libnss-systemd aparece como recomendado y no como dependencia.

Acabo de hacer la prueba de instalar dicho paquete, eliminar el usuario y grupo systemd-timesync, y reiniciar el sistema. Todo funciona correctamente, así que ya sabéis, si tenéis un problema similar, ambas acciones solucionan el problema, siendo la instalación de libnss-systemd la recomendada, ya que más de un servicio hará uso de usuarios propios y podría ocasionar un error similar al expuesto en este hilo.

 

  No hay bar que por bien no venga....