Upgrading the code and restarting the program should not be the same thing. Also, it's not hard to have vtysh complain about a version mismatch with the daemons. If you insist on making update and restart the same thing anyway, there should be a big warning about this, and a way to abort the upgrade. -Chris On 4/5/19 4:58 PM, Donald Sharp wrote:
Except of course you just screwed yourself in vtysh since it now has a different set of cli. Which can be quite different between releases. If you are going to upgrade you should find a maintenance window.
donald
On Fri, Apr 5, 2019 at 10:09 AM Christian Franke <chris@opensourcerouting.org> wrote:
Updating the installed code and restarting the routing daemons should be decoupled.
-Chris
On Fri, Apr 5, 2019, 14:13 Sim <simvirus@gmail.com> wrote:
A solution can be update "/usr/lib/frr/watchfrr" to check strange system behavior like this and reboot (always better to stay isolated)
Regards Sim
Il giorno ven 5 apr 2019 alle ore 13:10 Christian Franke <chris@opensourcerouting.org> ha scritto:
I think older packages used to ask the user whether routing daemons should be restarted during upgrade and refrained from restarts by default.
Not sure if we changed this behavior, I think it was a good thing to allow the users to pick a time when a restart of the routing daemons doesn't affect them and to have that disjunct from the actual upgrade.
All Best, Chris
On Fri, Apr 5, 2019, 09:33 Sim <simvirus@gmail.com> wrote:
The issue is also present with the new 7.0 version.
Regards
Sim
Il giorno ven 5 apr 2019 alle ore 09:20 Sim <simvirus@gmail.com> ha scritto:
Hello, today again a big disservice after auto-update with this packages.
Start-Date: 2019-04-05 09:01:25 Commandline: apt-get -y -qq upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.15, 237-3ubuntu10.17), grub-common:amd64 (2.02-2ubuntu8.12, 2.02-2ubuntu8.13), grub2-common:amd64 (2.02-2ubuntu8.12, 2.02-2ubuntu8.13), udev:amd64 (237-3ubuntu10.15, 237-3ubuntu10.17), grub-pc:am d64 (2.02-2ubuntu8.12, 2.02-2ubuntu8.13), libudev1:amd64 (237-3ubuntu10.15, 237-3ubuntu10.17), grub-pc-bin:amd64 (2.02-2ubuntu8.12, 2.02-2ubuntu8.13), systemd-sysv:amd64 (237-3ubuntu10.15, 237-3ubuntu10.17), libpam-systemd:amd64 (237-3ub untu10.15, 237-3ubuntu10.17), systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.17), libnss-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.17), libunistring2:amd64 (0.9.9-0ubuntu1, 0.9.9-0ubuntu2) End-Date: 2019-04-05 09:01:57
The issue is caused from systemd update and this is the result:
# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface x.x.32.0 0.0.0.0 255.255.255.240 U 0 0 0 ens192 x.x.32.16 0.0.0.0 255.255.255.240 U 0 0 0 ens160
I think that FRR is not a valid product compared to others used in the past.
This is a serious problem!!!
Regards
Il giorno mer 20 feb 2019 alle ore 12:44 Sim <simvirus@gmail.com> ha scritto: > > After apt-get upgrade / upgrade FRR lost all routes. > Reboot or restart the server is the solution to resolve the issue. > I'm new with FRR, but this is not happened with Quagga in the last 10/15 years. > > Is it a "FRR issue" or about Ubuntu 18.04 LTS version? > > # apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be upgraded: > libnss-systemd libpam-systemd libpci3 libsystemd0 libudev1 pciutils > systemd systemd-sysv udev > 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 4,765 kB of archives. > After this operation, 56.3 kB of additional disk space will be used. > Do you want to continue? [Y/n] > Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > libnss-systemd amd64 237-3ubuntu10.13 [105 kB] > Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > libsystemd0 amd64 237-3ubuntu10.13 [205 kB] > Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > libpam-systemd amd64 237-3ubuntu10.13 [108 kB] > Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > systemd amd64 237-3ubuntu10.13 [2,899 kB] > Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev > amd64 237-3ubuntu10.13 [1,101 kB] > Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > libudev1 amd64 237-3ubuntu10.13 [54.1 kB] > Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > systemd-sysv amd64 237-3ubuntu10.13 [12.0 kB] > Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > pciutils amd64 1:3.5.2-1ubuntu1.1 [257 kB] > Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 > libpci3 amd64 1:3.5.2-1ubuntu1.1 [24.1 kB] > Fetched 4,765 kB in 8s (575 kB/s) > (Reading database ... 67479 files and directories currently installed.) > Preparing to unpack .../libnss-systemd_237-3ubuntu10.13_amd64.deb ... > Unpacking libnss-systemd:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Preparing to unpack .../libsystemd0_237-3ubuntu10.13_amd64.deb ... > Unpacking libsystemd0:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Setting up libsystemd0:amd64 (237-3ubuntu10.13) ... > (Reading database ... 67479 files and directories currently installed.) > Preparing to unpack .../libpam-systemd_237-3ubuntu10.13_amd64.deb ... > Unpacking libpam-systemd:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Preparing to unpack .../systemd_237-3ubuntu10.13_amd64.deb ... > Unpacking systemd (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Preparing to unpack .../udev_237-3ubuntu10.13_amd64.deb ... > Unpacking udev (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Preparing to unpack .../libudev1_237-3ubuntu10.13_amd64.deb ... > Unpacking libudev1:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Setting up libudev1:amd64 (237-3ubuntu10.13) ... > Setting up systemd (237-3ubuntu10.13) ... > (Reading database ... 67479 files and directories currently installed.) > Preparing to unpack .../systemd-sysv_237-3ubuntu10.13_amd64.deb ... > Unpacking systemd-sysv (237-3ubuntu10.13) over (237-3ubuntu10.12) ... > Preparing to unpack .../pciutils_1%3a3.5.2-1ubuntu1.1_amd64.deb ... > Unpacking pciutils (1:3.5.2-1ubuntu1.1) over (1:3.5.2-1ubuntu1) ... > Preparing to unpack .../libpci3_1%3a3.5.2-1ubuntu1.1_amd64.deb ... > Unpacking libpci3:amd64 (1:3.5.2-1ubuntu1.1) over (1:3.5.2-1ubuntu1) ... > Setting up libnss-systemd:amd64 (237-3ubuntu10.13) ... > Processing triggers for ureadahead (0.100.0-20) ... > Setting up systemd-sysv (237-3ubuntu10.13) ... > Processing triggers for libc-bin (2.27-3ubuntu1) ... > Setting up udev (237-3ubuntu10.13) ... > update-initramfs: deferring update (trigger activated) > Processing triggers for man-db (2.8.3-2ubuntu0.1) ... > Processing triggers for dbus (1.12.2-1ubuntu1) ... > Setting up libpci3:amd64 (1:3.5.2-1ubuntu1.1) ... > Setting up libpam-systemd:amd64 (237-3ubuntu10.13) ... > Setting up pciutils (1:3.5.2-1ubuntu1.1) ... > Processing triggers for initramfs-tools (0.130ubuntu3.6) ... > update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic > Processing triggers for libc-bin (2.27-3ubuntu1) ... > > > > # apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > > > # ps fax > PID TTY STAT TIME COMMAND > > 955 ? S<s 0:45 /usr/lib/frr/watchfrr -d -r > /usr/lib/frr/watchfrr.sh restart %s -s /usr/lib/frr/watchfrr.sh start > %s -k /usr/lib/frr/watchfrr.sh stop %s zebra bgpd staticd > 1006 ? S<sl 3:59 /usr/lib/frr/zebra -d -A 127.0.0.1 -s 90000000 > 1009 ? S<sl 7:22 /usr/lib/frr/bgpd -d -A 127.0.0.1 > 1016 ? S<s 0:05 /usr/lib/frr/staticd -d -A 127.0.0.1 > > > > # vtysh > > Hello, this is FRRouting (version 6.0.2). > Copyright 1996-2005 Kunihiro Ishiguro, et al. > > xxx# sh ip bgp summary > > IPv4 Unicast Summary: > BGP router identifier x.x.32.34, local AS number xxxxxx vrf-id 0 > BGP table version 6693928 > RIB entries 6, using 960 bytes of memory > Peers 2, using 41 KiB of memory > > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ > Up/Down State/PfxRcd > x.x.118.244 4 xxxx 915579 27779 0 0 0 00:03:45 > Active > x.x.32.33 4 xxxxxx 843680 352816 0 0 0 00:05:16 > Active > > > > # ip add > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet x.x.32.34/32 scope global lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state > UP group default qlen 1000 > link/ether 00:50:56:ba:53:46 brd ff:ff:ff:ff:ff:ff > inet x.x.32.29/28 brd x.x.32.31 scope global ens160 > valid_lft forever preferred_lft forever > inet6 fe80::250:56ff:feba:5346/64 scope link > valid_lft forever preferred_lft forever > 3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state > UP group default qlen 1000 > link/ether 00:50:56:ba:af:9d brd ff:ff:ff:ff:ff:ff > inet x.x.32.3/28 brd x.x.32.15 scope global ens192 > valid_lft forever preferred_lft forever > inet6 fe80::250:56ff:feba:af9d/64 scope link > valid_lft forever preferred_lft forever > > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > x.x.32.0 0.0.0.0 255.255.255.240 U 0 0 0 ens192 > x.x.32.16 0.0.0.0 255.255.255.240 U 0 0 0 ens160 > > > Regards > Sim
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog