netinfod macht komische Sachen beim Systemstart

[nilsbyte]

Hallo liebe macuser,

beim Systemstart hängt mein MacBook einige Sekunden und macht scheinbar garnichts. Jetzt hab ich mal in die Konsole ins Log geguckt und da steht folgendes:

Jan  6 13:19:31 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:31 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:31 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:32 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:32 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:32 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:32 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:33 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:33 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:33 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:33 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:35 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:36 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:36 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:36 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:36 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:37 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:37 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:37 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:37 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:39 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:40 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:40 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:40 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:40 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:41 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:41 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:41 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:41 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:43 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:44 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:44 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:44 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:44 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host
Jan  6 13:19:45 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:45 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.2: No route to host
Jan  6 13:19:45 localhost netinfod local[34]: Cannot send multicall packet to 127.13.0.3: No route to host

Also irgend ein Problem mit netinfod.

Kann mir jemand sagen wo netinfod seine Informationen herbezieht und wie ich diese nervige Angelegenheit abstelle?

 

[bernie313]

Da wird wohl ein Netzwerk gesucht und nicht gefunden.
Etwas derartiges eingestellt?
Netzwerkvolumen(k.A. ob es daran liegt)
oder ein Airport, der ausgeschaltet ist?

 

[nilsbyte]

keine ahnung was da passiert ist, mit airport und netzwerkvolumes hat das aber nix zu tun.

kann mir jemand sagen wo ich die Einstellungen finde, die netinfod verwendet? dann kann man die übers Terminal evtl. bearbeiten/löschen?

 

[maceis]

Die Netinfo Datenbank ("wo netinfod seine Informationen herbezieht") findest Du unter "/var/db/local.nidb".

Ob Du die von Hand bearbeiten solltest, wenn Du nicht genau weisst, was Du da tust, wage ich allerdings zu bezweifeln.

 

[nilsbyte]

Die Netinfo Datenbank ("wo netinfod seine Informationen herbezieht") findest Du unter "/var/db/local.nidb".

Ob Du die von Hand bearbeiten solltest, wenn Du nicht genau weisst, was Du da tust, wage ich allerdings zu bezweifeln.

ich hab als single user mal in diesem pfad geguckt, aber ich weiss nicht genau was ich da machen muss. ich hab keine Lust wegen sowas mein System neu aufzusetzen. Irgendjemand wird mir doch helfen können? *verzweifeltguck*

 

[bernie313]

127.13.0.3 das ist eine merkwürdige Adresse.
Schon versucht mittels verbose Modus zu starten, da wird dir vielleicht ein dazugehöriges Teil gezeigt, was aufgestartet wird.Apfel+V beim Starten gedrückt halten, ansonst hab ich k.A. was das sein könnte außer, das irgendein Dienst eingeschaltet werden soll, aber nicht gefunden wird, aber das weisßt du ja bereits nur was k.A.