Mensaje de error "Failed start raise network interfaces" en DEBIAN 9.1 STRETCH

11 envíos / 0 nuevos
Último envío
#1 Mar, 12/09/2017 - 14:04
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

Mensaje de error "Failed start raise network interfaces" en DEBIAN 9.1 STRETCH

Estado: 
[SOLUCIONADO]

A petición de la administración y de un usuario que muy gentilmente me han contestado, abro un hilo específico en el que cuento que he tenido algunas dificultades después de instalar Debian 9.0 Stretch en mi laptop Toshiba L870 - 18E y que he relatado aquÍ https://exdebian.org/foro/problemas-de-instalaci%C3%B3n-de-debian-90-stretch-en-laptop-toshiba-l870-18e-activo

 

En el PROMPT de inicio de Debian aparece  el siguiente mensaje de error: Failed start raise network interfaces

He encontrado un hilo en exdebian.org que aborda este mensaje de error. La diferencia es el usuario que tenía un problema, lo tenía con un Anonym8 con una máquina virtual y yo tengo instalado DEBIAN 9.0 en una partición del disco duro con WINDOWS 8. https://exdebian.org/foro/failed-start-raise-netword-interfaces-activo

 

Mar, 12/09/2017 - 14:29
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

Entro en modo administrador y pongo el comando ifconfig -a

 

ifconfig -a
enp9s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.39  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::920e:6f8a:738f:bc46  prefixlen 64  scopeid 0x20<link>
        ether 70:54:d2:ad:a8:10  txqueuelen 1000  (Ethernet)
        RX packets 25267  bytes 12146625 (11.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24390  bytes 10012562 (9.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 214  bytes 15906 (15.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 214  bytes 15906 (15.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp8s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::2216:d8ff:fe8a:4af7  prefixlen 64  scopeid 0x20<link>
        ether 20:16:d8:8a:4a:f7  txqueuelen 1000  (Ethernet)
        RX packets 1252  bytes 102145 (99.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 252  bytes 41096 (40.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

En  /etc/network/interfaces hay varias carpetas con nombres como if-down.d, if-post-down.d, if pre-up.d, if-up.d e interfaces.d y un archivo llamado "interfaces".

El contenido original de : /etc/network/interfaces.d/setup  


auto lo
iface lo inet loopback

 

Mar, 12/09/2017 - 14:37
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

He probado diferentes soluciones que busqué en Google pero las he probado y nada, no me aclaro: https://www.google.es/search?q=%22Failed+start+raise+network+interfaces&oq=%22Failed+start+raise+network+interfaces&aqs=chrome..69i57j0l2j69i60j0.465j0j7&sourceid=chrome&ie=UTF-8

 

 A lo mejor, esto puede ser una pista, lo he encontrado en este foro:

 

https://exdebian.org/foro/informacion-de-enp1s0-por-que-sustituye-eth0-solucionado

Mar, 12/09/2017 - 14:44
caliban
Imagen de caliban
Conectado
moderador
se unió: 14/01/16

Bien   /etc/network/ interfaces ,, es un ar chivo de texto ,con un contenido ,   es ese el que tenes que ver 

cat  /etc/network/interfaces 

ahora sabes el nombre de tu interfaz de red enp9s0: ; el punto es este , algo parece que interfiere con el normal 

funcionamiento de la interfaz , un conflicto , puede ser que networkmanager, ( si es el que comanda el asunto ) entra en conflicto con alguna configuracion en   , /etc/network/interfaces  por ejemplo.

De otro modo tambien podes intentar,, deshabilitar  networkmanager ( o el que sea ) y configurar en tu archivo de interfaces   la enp9s0:   y reiniciar el servicio de red a ver que ocurre 

systemctl restart  network.service

Edito a ver si este enlace te sirve 

NO hace falta cambiar el  nombre de la interfaz a eth0,, eso es solo por comodidad o si tenes configuraciones previas que utilicen la designación eth0 

Mar, 12/09/2017 - 14:45
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

He probado diferentes soluciones que busqué en Google pero las he probado y nada, no me aclaro: https://www.google.es/search?q=%22Failed+start+raise+network+interfaces&oq=%22Failed+start+raise+network+interfaces&aqs=chrome..69i57j0l2j69i60j0.465j0j7&sourceid=chrome&ie=UTF-8

 

 A lo mejor, esto puede ser una pista, lo he encontrado en este foro:

https://exdebian.org/foro/informacion-de-enp1s0-por-que-sustituye-eth0-solucionado

Si, uso NetWorkManager,el archivo de configuración  /etc/NetworkManager/NetworkManager.conf muestra lo siguiente:

 

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

 

Mar, 12/09/2017 - 15:31 (Responder a #5)
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

He seguido los pasos de este link que me pasaste y me ha funcionado: http://www.lapipaplena.org/failed-to-start-raise-network-interfaces/

Gracias y doy por solucionado el tema.

caliban wrote:

Bien   /etc/network/ interfaces ,, es un ar chivo de texto ,con un contenido ,   es ese el que tenes que ver 

cat  /etc/network/interfaces 

ahora sabes el nombre de tu interfaz de red enp9s0: ; el punto es este , algo parece que interfiere con el normal 

funcionamiento de la interfaz , un conflicto , puede ser que networkmanager, ( si es el que comanda el asunto ) entra en conflicto con alguna configuracion en   , /etc/network/interfaces  por ejemplo.

De otro modo tambien podes intentar,, deshabilitar  networkmanager ( o el que sea ) y configurar en tu archivo de interfaces   la enp9s0:   y reiniciar el servicio de red a ver que ocurre 

systemctl restart  network.service

Edito a ver si este enlace te sirve 

NO hace falta cambiar el  nombre de la interfaz a eth0,, eso es solo por comodidad o si tenes configuraciones previas que utilicen la designación eth0 

Mar, 12/09/2017 - 17:05
rockyiii
Imagen de rockyiii
Conectado
administrator
se unió: 11/01/16

Por lo que veo tenes conexión a internet desde la wifi wlp8s0 y desde la Lan enp9s0 ya que a ambas se le asigna dirección ip
¿si inicias el sistema sin la Lan conectada te tira el error?
 

en  /etc/NetworkManager/NetworkManager.conf podrias poner managed=false

 

¿que te ponen los siguientes comandos?

 

su
systemctl status networking NetworkManager
journalctl -b -p err
journalctl  -u networking.service -u NetworkManager.service

 

Mié, 13/09/2017 - 08:16 (Responder a #7)
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

 

#systemctl status networking NetworkManager


● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese
   Active: active (exited) since Tue 2017-09-12 20:17:07 CEST; 16h ago
     Docs: man:interfaces(5)
  Process: 389 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0
  Process: 385 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ 
 Main PID: 389 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/networking.service

sep 12 20:16:33 debian systemd[1]: Starting Raise network interfaces...
sep 12 20:17:06 debian ifup[389]: grep: /etc/resolv.conf: No such file or direct
sep 12 20:17:07 debian systemd[1]: Started Raise network interfaces.

● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor p
   Active: active (running) since Tue 2017-09-12 20:17:10 CEST; 16h ago
     Docs: man:NetworkManager(8)
 Main PID: 440 (NetworkManager)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           ├─440 /usr/sbin/NetworkManager --no-daemon
           └─699 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper
lines 1-23...skipping...
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2017-09-12 20:17:07 CEST; 16h ago
     Docs: man:interfaces(5)
  Process: 389 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
  Process: 385 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=
 Main PID: 389 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/networking.service

sep 12 20:16:33 debian systemd[1]: Starting Raise network interfaces...
sep 12 20:17:06 debian ifup[389]: grep: /etc/resolv.conf: No such file or directory
sep 12 20:17:07 debian systemd[1]: Started Raise network interfaces.

● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2017-09-12 20:17:10 CEST; 16h ago
     Docs: man:NetworkManager(8)
 Main PID: 440 (NetworkManager)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           ├─440 /usr/sbin/NetworkManager --no-daemon
           └─699 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlp8s0.pid -lf /var/lib/NetworkManager/dhclient-a4dd5229-7390-4c39-9988-2

sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   plen 24 (255.255.255.0)
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   gateway 192.168.1.1
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   server identifier 192.168.1.1
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   lease time 43200
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   hostname 'debian'
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   nameserver '80.58.61.250'
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   nameserver '80.58.61.254'
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0849] dhcp4 (wlp8s0):   domain name 'homestation'
sep 13 12:27:32 debian NetworkManager[440]: <info>  [1505298452.0850] dhcp4 (wlp8s0): state changed bound -> bound
sep 13 12:27:32 debian dhclient[699]: bound to 192.168.1.33 -- renewal in 17930 seconds.
~

root@debian:/home/user# journalctl -b -p err


-- Logs begin at Tue 2017-09-12 20:16:24 CEST, end at Wed 2017-09-13 12:46:05 CEST. --
sep 12 20:17:06 debian avahi-daemon[433]: chroot.c: open() failed: No such file or directory
sep 12 20:17:08 debian bluetoothd[436]: Failed to obtain handles for "Service Changed" characteristic
sep 12 20:17:08 debian bluetoothd[436]: Sap driver initialization failed.
sep 12 20:17:08 debian bluetoothd[436]: sap-server: Operation not permitted (1)
sep 12 20:17:10 debian kernel: Bluetooth: hci0 command 0x1004 tx timeout
sep 12 20:17:10 debian bluetoothd[436]: Loading LTKs timed out for hci0
sep 12 20:17:18 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 20:18:07 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 20:18:10 debian bluetoothd[436]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
sep 12 20:18:38 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 21:06:45 debian kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
sep 12 22:39:27 debian kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 20)
sep 12 22:39:27 debian kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 20)
sep 12 22:39:27 debian kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 20)
sep 12 22:39:27 debian kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 20)
sep 12 22:39:27 debian kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 20)
sep 12 22:39:27 debian kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 20)
sep 12 22:47:31 debian kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 25)
sep 12 22:47:31 debian kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 25)
sep 12 22:47:31 debian kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 25)
sep 12 22:47:31 debian kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 25)
sep 12 22:47:31 debian kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 25)
sep 12 22:47:31 debian kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 25)
sep 12 22:52:33 debian kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 69)
sep 12 22:52:33 debian kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 69)
sep 12 22:52:33 debian kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 69)
sep 12 22:52:33 debian kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 69)
sep 12 22:52:33 debian kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 69)
sep 12 22:52:33 debian kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 69)
sep 13 07:26:59 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 13 07:27:12 debian bluetoothd[436]: Failed to set mode: Failed (0x03)

root@debian:/home/user# journalctl  -u networking.service -u NetworkManager.service


root@debian:/home/user# journalctl  -u networking.service -u NetworkManager.service
-- Logs begin at Tue 2017-09-12 20:16:24 CEST, end at Wed 2017-09-13 12:46:05 CEST. --
sep 12 20:16:33 debian systemd[1]: Starting Raise network interfaces...
sep 12 20:17:06 debian systemd[1]: Starting Network Manager...
sep 12 20:17:06 debian ifup[389]: grep: /etc/resolv.conf: No such file or directory
sep 12 20:17:07 debian systemd[1]: Started Raise network interfaces.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.0233] NetworkManager (version 1.6.2) is starting...
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.0502] Read config: /etc/NetworkManager/NetworkManager.conf
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.0921] manager[0x5575bef87040]: monitoring kernel firmware directory '/lib/firmware'.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.0922] monitoring ifupdown state file '/run/network/ifstate'.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.0987] dns-mgr[0x5575bef6e180]: init: dns=default, rc-manager=resolvconf
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.1171] rfkill2: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:08:00.0/ieee80211/phy0/
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.1173] manager[0x5575bef87040]: WiFi hardware radio set enabled
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.1174] manager[0x5575bef87040]: WWAN hardware radio set enabled
sep 12 20:17:10 debian systemd[1]: Started Network Manager.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8361] init!
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8364]       interface-parser: parsing file /etc/network/interfaces
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8365]       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8367]       interface-parser: parsing file /etc/network/interfaces.d/setup
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8368]       interface-parser: finished parsing file /etc/network/interfaces.d/setup
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8368]       interface-parser: finished parsing file /etc/network/interfaces
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8373] guessed connection type (enp9s0) = 802-3-ethernet
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8373] update_connection_setting_from_if_block: name:enp9s0, type:802-3-ethernet, id:Ifupdown (enp9s0), uuid: 44b
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8376] addresses count: 1
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8376] No dns-nameserver configured in /etc/network/interfaces
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8377] adding enp9s0 to connections
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8377] adding iface enp9s0 to eni_ifaces
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8377] autoconnect
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8378] management mode: managed
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8384] devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:08:00.0/net/wlp8s0, iface: wlp8s0)
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8384] device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:08:00.0/net/wlp8s0, iface: wlp8s0): no ifupd
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8385] devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/enp9s0, iface: enp9s0)
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8385] locking wired connection setting
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8386] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8386] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8387] end _init.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8387] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager ma
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8388] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs please use the NetworkManag
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8388] (-1090865984) ... get_connections.
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.8388] (-1090865984) connections count: 1
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.9367] keyfile: new connection /etc/NetworkManager/system-connections/^CondoR^ (a4dd5229-7390-4c39-9988-2daefa7cd
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.9397] settings: hostname: using hostnamed
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.9397] settings: hostname changed from (none) to "debian"
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.9460] dhcp-init: Using DHCP client 'dhclient'
sep 12 20:17:10 debian NetworkManager[440]: <info>  [1505240230.9461] manager: WiFi enabled by radio killswitch; enabled by state file

rockyiii wrote:

¿que te ponen los siguientes comandos?

 

su
systemctl status networking NetworkManager
journalctl -b -p err
journalctl  -u networking.service -u NetworkManager.service

 

Mié, 13/09/2017 - 08:26 (Responder a #8)
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

Tengo 2 conexiones, una LAN y una WIFI

Inicie con LAN sin LAN, puedo conectarme sin problemas a Internet.

rockyiii wrote:

Por lo que veo tenes conexión a internet desde la wifi wlp8s0 y desde la Lan enp9s0 ya que a ambas se le asigna dirección ip
¿si inicias el sistema sin la Lan conectada te tira el error?
 

en  /etc/NetworkManager/NetworkManager.conf podrias poner managed=false

 

¿que te ponen los siguientes comandos?

 

su
systemctl status networking NetworkManager
journalctl -b -p err
journalctl  -u networking.service -u NetworkManager.service

 

Mié, 13/09/2017 - 13:08
rockyiii
Imagen de rockyiii
Conectado
administrator
se unió: 11/01/16

Por lo que veo tenes un problema con bluetooth

sep 12 20:17:08 debian bluetoothd[436]: Failed to obtain handles for "Service Changed" characteristic
sep 12 20:17:08 debian bluetoothd[436]: Sap driver initialization failed.
sep 12 20:17:08 debian bluetoothd[436]: sap-server: Operation not permitted (1)
sep 12 20:17:10 debian kernel: Bluetooth: hci0 command 0x1004 tx timeout
sep 12 20:17:10 debian bluetoothd[436]: Loading LTKs timed out for hci0
sep 12 20:17:18 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 20:18:07 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 20:18:10 debian bluetoothd[436]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
sep 12 20:18:38 debian bluetoothd[436]: Failed to set mode: Failed (0x03)

y con la temperatura del cpu

sep 12 21:06:45 debian kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
........

podrias poner el resultado de

su
systemctl status bluetooth.service
journalctl -b -u bluetooth.service

 

Sobre el tema de la temperatura podes instalar y configurar lm-sensors cpufreqd hddtemp y también no estaría de más laptop-mode-tools

 

¿Marcaste el tema como solucionado? ¿por? De ser asi podrias comentar la solución

Mié, 13/09/2017 - 17:42 (Responder a #10)
viriato
Imagen de viriato
Desconectado/a
se unió: 29/08/17

-- Logs begin at Wed 2017-09-13 15:05:32 CEST, end at Wed 2017-09-13 22:33:31 CE
sep 13 15:05:41 debian systemd[1]: Starting Bluetooth service...
sep 13 15:05:42 debian bluetoothd[422]: Bluetooth daemon 5.43
sep 13 15:05:43 debian systemd[1]: Started Bluetooth service.
sep 13 15:05:44 debian bluetoothd[422]: Starting SDP server
sep 13 15:05:44 debian bluetoothd[422]: Bluetooth management interface 1.14 init
sep 13 15:05:44 debian bluetoothd[422]: Failed to obtain handles for "Service Ch
sep 13 15:05:44 debian bluetoothd[422]: Sap driver initialization failed.
sep 13 15:05:44 debian bluetoothd[422]: sap-server: Operation not permitted (1)
sep 13 15:06:00 debian bluetoothd[422]: Endpoint registered: sender=:1.52 path=/
sep 13 15:06:00 debian bluetoothd[422]: Endpoint registered: sender=:1.52 path=/
sep 13 15:19:46 debian bluetoothd[422]: Endpoint registered: sender=:1.71 path=/
sep 13 15:19:46 debian bluetoothd[422]: Endpoint registered: sender=:1.71 path=/
sep 13 15:19:46 debian bluetoothd[422]: RFCOMM server failed for Headset Voice g
lines 1-14/14 (END)

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: active (running) since Wed 2017-09-13 15:05:43 CEST; 7h ago
     Docs: man:bluetoothd(8)
 Main PID: 422 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─422 /usr/lib/bluetooth/bluetoothd

sep 13 15:05:44 debian bluetoothd[422]: Starting SDP server
sep 13 15:05:44 debian bluetoothd[422]: Bluetooth management interface 1.14 init
sep 13 15:05:44 debian bluetoothd[422]: Failed to obtain handles for "Service Ch
sep 13 15:05:44 debian bluetoothd[422]: Sap driver initialization failed.
sep 13 15:05:44 debian bluetoothd[422]: sap-server: Operation not permitted (1)
sep 13 15:06:00 debian bluetoothd[422]: Endpoint registered: sender=:1.52 path=/
sep 13 15:06:00 debian bluetoothd[422]: Endpoint registered: sender=:1.52 path=/
sep 13 15:19:46 debian bluetoothd[422]: Endpoint registered: sender=:1.71 path=/
sep 13 15:19:46 debian bluetoothd[422]: Endpoint registered: sender=:1.71 path=/
sep 13 15:19:46 debian bluetoothd[422]: RFCOMM server failed for Headset Voice g
lines 1-20/20 (END)

Esto es lo que sale cuando pongo los 2 comandos.

 

Muchísimas gracias por la información que me has traido. Si, tengo problemas  con Bluetooth :(

La solución al problema del hilo está en este link: http://www.lapipaplena.org/failed-to-start-raise-network-interfaces/

rockyiii wrote:

Por lo que veo tenes un problema con bluetooth

sep 12 20:17:08 debian bluetoothd[436]: Failed to obtain handles for "Service Changed" characteristic
sep 12 20:17:08 debian bluetoothd[436]: Sap driver initialization failed.
sep 12 20:17:08 debian bluetoothd[436]: sap-server: Operation not permitted (1)
sep 12 20:17:10 debian kernel: Bluetooth: hci0 command 0x1004 tx timeout
sep 12 20:17:10 debian bluetoothd[436]: Loading LTKs timed out for hci0
sep 12 20:17:18 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 20:18:07 debian bluetoothd[436]: Failed to set mode: Failed (0x03)
sep 12 20:18:10 debian bluetoothd[436]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
sep 12 20:18:38 debian bluetoothd[436]: Failed to set mode: Failed (0x03)

y con la temperatura del cpu

sep 12 21:06:45 debian kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
sep 12 21:06:45 debian kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
........

podrias poner el resultado de

su
systemctl status bluetooth.service
journalctl -b -u bluetooth.service

 

Sobre el tema de la temperatura podes instalar y configurar lm-sensors cpufreqd hddtemp y también no estaría de más laptop-mode-tools

 

¿Marcaste el tema como solucionado? ¿por? De ser asi podrias comentar la solución