Hey,
danke für die Info. Ich schaue mir das gleich an und fixe das
Am 13. Juni 2016 09:14:29 MESZ, schrieb Jan-Tarek Butt via Admin admin@lists.ffnw.de:
On 06/13/16 09:10, Jan-Tarek Butt via Admin wrote:
Hi,
Auf srv03 werden die fastd instanzen nicht gestartet.
Ich hab diese jetzt manuell gestartet.
root@srv03 ~ # cat /var/log/syslog | grep fastd@root -A01 Jun 13 06:51:15 srv03 systemd[1]: fastd@root.service: main process exited, code=exited, status=1/FAILURE Jun 13 06:51:15 srv03 systemd[1]: Failed to start Fast and Secure Tunnelling Daemon (connection root). Jun 13 06:51:15 srv03 systemd[1]: Unit fastd@root.service entered failed state. Jun 13 06:51:15 srv03 acpid: starting up with netlink and the input layer -- Jun 13 08:46:39 srv03 systemd[1]: fastd@root.service: main process exited, code=exited, status=1/FAILURE Jun 13 08:46:39 srv03 kernel: [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000007f79ffff] -- Jun 13 08:46:39 srv03 systemd[1]: Unit fastd@root.service entered failed state. Jun 13 08:46:39 srv03 kernel: [ 0.000000] Early memory node ranges -- Jun 13 08:53:14 srv03 systemd[1]: fastd@root.service: main process exited, code=exited, status=1/FAILURE Jun 13 08:53:14 srv03 systemd[1]: Failed to start Fast and Secure Tunnelling Daemon (connection root). Jun 13 08:53:14 srv03 systemd[1]: Unit fastd@root.service entered failed state. Jun 13 08:53:15 srv03 bird: BGP: Unexpected connect from unknown address 10.18.1.5 (port 41781)
Es wird die ganze zeit verstucht fastd@root auszuführen, dafür besteht allerdings keine config.
Stattdessen müssten es fastd@lkibb1 und fastd@lkibb0 sein.
vg Tarek
Admin mailing list Admin@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/admin