There is a PR for the JSD/gRPC issue - https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1398398
You can disable those services in the config for an immediate fix - and later upgrade. Kevin On Tue, May 28, 2019 at 6:31 AM Franz Georg Köhler <li...@openunix.de> wrote: > On Sun, May 26, 2019 at 03:15:48PM +0200, Thomas Bellman < > bell...@nsc.liu.se> wrote: > > > > So far, the only problem I have seen is that the Jet Service Daemon > > (jsd) and the na-grpc-daemon starts eating 100% CPU after a few weeks > > on 18.3, but not the other versions. Restarting them helps; for a > > few weeks, then they suddenly eat CPU again. It should also be possible > > to disable them if you don't use them (I haven't gotten around to do > > that myself, though). > > We see the same behaviour with 18.3R1 and regularily need to kill jsd > and na-grpc-daemon. > > We run 18.2 to 19.1 and see those processes eating up CPU only on > 18.3R1. > > We see some IPV6 problems in a VC environment, i.E. PR1413543 and > PR1370329 (RA not working) > > We also see problems in IPV6 forwarding, when connected hosts would not > be able to reach the outside until they either ping the IRB gateway or > traffic comes in from the outside. > > > > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp