hello So to get it working, I had httpd running in the management Rdomain
rcctl set httpd rtable 240 i put the slowcgi running in the main rdomain (default rdomain 0) rcctl set slowcgi rtable 0 followed the man page man bgplg (upped the ram from 1GB to 4GB as I was loading 2 BGP full feeds) and it worked Thanks for your help Claudio ... I think i had a typo in my restricted socket path Tom Smyth On Mon, 19 Nov 2018 at 08:58, Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > > On Sun, Nov 18, 2018 at 10:57:01PM +0000, Tom Smyth wrote: > > Hello, > > > > I have a Looking glass that I want to run on a management interface > > that is in a separate rdomain to the BGP router ... > > > > is there away we can have the the bgprocess in one RDomain (main Rdomain) > > and the the bgp looking glass in another rdomain... > > > > so currently i have httpd in Rdomain 240 > > slowcgi is running in rdomain 0 > > > > ping works but not the bgp commands... > > > > > > I tried setting slowcgi flags but they just didn't take > > > > > > do I need to run slowcgi with route -T240 exec slowcgi ? > > (which would put the entire bgplg and the bgp collector on the same > > Rdomain.. > > any suggestions are welcome ...thanks > > > > I would check that the restricted socket is in /var/www/run and is called > bgpd.rsock. After that I do not really see why bgpctl should not work. > > If there are no errors logged in the httpd error log then you could try to > ktrace -di the slowcgi process and see why bgplg and bgpctl fails. > > -- > :wq Claudio
